Was this a kernel change you made? The previous poster said the cam doesn't work on OMGB, and I was under the impression you're using the same kernel as the OMGB ROM...
Was this a kernel change you made? The previous poster said the cam doesn't work on OMGB, and I was under the impression you're using the same kernel as the OMGB ROM...
I did no kernel change. Only some modifcations in ramdisk (init.rc)
Well I'm kinda confused why cam works for RHOD100 folks on your build, but not on OMGB...
I guess it's not a big deal, unless someone on a RHOD100 feels like helping figuring it out. I alas do not have such a device.
I see that users have posted CDMA SOD's problems and restarts have been given no help or at least one orientation to try to solve the problem ...
It's probably a RIL issue, and unfortunately we don't really have many people who are RIL experts. Heck, the guy who wrote the CDMA stuff from nothing but stubs doesn't even have a CDMA device... what does that tell you.
I see that users have posted CDMA SOD's problems and restarts have been given no help or at least one orientation to try to solve the problem ...
I need some help. I got to the following step
In your CMD window type this command:
Fastboot flash recovery cwm_recovery.img
Reboot: (Or hit the reset button)
In your CMD window type this command:
Fastboot reboot
and now my phone is stuck. It boots and loads minipooploader but says flash_read_image failed and could not do normal boot resorting to fastboot mode. It doesn't seem I can do anything. I try to enter the last two commands before recovery but it says (waiting for device). I can't get it to enter into recovery to flash the next step and apply update from sd card and install cm7.2.
Please someone help me. Hopefully I can fix this as I just got the phone as a replacement for my broken one.
I need some help. I got to the following step
In your CMD window type this command:
Fastboot flash recovery cwm_recovery.img
Reboot: (Or hit the reset button)
In your CMD window type this command:
Fastboot reboot
and now my phone is stuck. It boots and loads minipooploader but says flash_read_image failed and could not do normal boot resorting to fastboot mode. It doesn't seem I can do anything. I try to enter the last two commands before recovery but it says (waiting for device). I can't get it to enter into recovery to flash the next step and apply update from sd card and install cm7.2.
Please someone help me. Hopefully I can fix this as I just got the phone as a replacement for my broken one.
After you type "fastboot reboot", once the phone restarts and the blue screen is shown again, press the power button right away and keep it pressed until you go into recovery mode.
After you type "fastboot reboot", once the phone restarts and the blue screen is shown again, press the power button right away and keep it pressed until you go into recovery mode.
but... the notification light kept on all the time (green when standby, orange when in use). that i think would make the batt drains faster.
I've read through the posts but can't seem to find anyone with the same tiny problem, the the end call key is the power button (as well as the power button itself) is there any way to change that in the KeyChars map file perhaps.
When I type in the line into the command window it just says waiting for device. It says on the blue screen usb is online and this is a cold boot. Forcing fast boot but doesn't do anything. If I hold down the power button it will say so on the phone but volume rocker doesn't do anything. What am I doing wrong or what do I need to be doing? Hopefully there is a way to fix this. Thanks for your help so far.
Happened again, I made a phone call, the screen went of when I raised the phone near my face, called finished and the screen never came on again, the phone was completely unresponsive. Left alone for a while. Nothing. As as I plugged in the USB cable it rebooted.
Thing is, for me this issue is easy to replicate. It happens only on long calls (over 10 minutes give or take). On short calls I never experience this. But during long calls it happens each and every time.
Posting last kmsg.