Hey, I recently had my friend flash the unofficial CyanogenMod10 ROM onto my HTC Desire C (Non-NFC version)
I am encountering an error where about 80% of the time when my phone is asleep, and I press the power button to wake it, it will flash on and then go back to sleep.
If I press the power button as quick as I possibly can it will still happen, however; if I hold it down it will stay on until I let it go, at which point it will definitely go back to sleep; I honestly don't know what's happening.
It sometimes also occurs when I've taken a screenshot; it has a high chance of going to sleep when I take my finger off of the power button, same as when I hold down to view the power menu. (That shows reboot, turn off, airplane mode, etc.) and when let go of the button it usually also shuts off, what's happening, is this a problem with the ROM, or something I may have changed?
Also this issue only started occurring about 2 days after the initial flash, whereas until the point everything was working nice and smoothly.
This issue is really annoying...
P.S: Would I be better off using the newest JellyTime ROM rather than the vanilla CM ROM on my Desire C?
Thanks!
Related
Hi,
I have a sensation running the latest RCmix3d ROM. I know it has some bugs as it's not a stable version yet, but the biggest one is the inability to turn my phone off. Any time I press the power button and power off, the screen goes blank and then does a fastboot back on again. There's no HTC down animation or anything. It's as if I hit the hot reboot button (a full restart and hot restart options do the same thing as power off too).
I can only turn the phone off by removing the battery. I don't like doing this because I'm pretty sure it can't be good for the phone or battery. I have no idea what's causing this and it's very irritating as there are times when I need to turn my phone off.
Was there an issue with the flashing process, or is it a known bug in the ROM? Any help would be appreciated!
My Sensation has the Revolution HD3.6.2 by Mike. I started having issues with my sleep button where it would stop responding occasionally until eventually it would stop responding altogether when the phone was on and I could not put to sleep or wake up at all. Now, if I plug into charger with battery out then install battery it will not boot automatically or with holding power button at all. When removing charger it will boot automatically because the phone thinks the power button is always depressed. I have taken the phone case off and cleaned the area many times and it physically clicks normal with no response. I was going to try an updated ROM to see if this was a programming issue however since the phone thinks the power button is always depressed I can not use ROM manager, right when I click down or up it automatically loads that option. The rest of the phone works perfectly and do not want to replace due to a failed sleep/power button, are there options to working around the power button or anything else I should be doing?
Thanks
So I have a bricked Sensation?
ChillOutWayne said:
So I have a bricked Sensation?
Click to expand...
Click to collapse
ok then
It's not bricked. Don't worry software is fine. Sounds like a hardware fault that the power button contact has worn out.
I find that on my infuse 4G, sometimes after the phone goes to sleep, when I press the power button to turn the phone back on, the display would not wake up. The phone would be on, since if I press the volume rocker, I would hear the volume up and down keys. The capacitive keys would not light up as well tho, or respond.
The only thing I can do is a battery pull. I can still call the phone tho, so I know phone has not crashed.
This happens to my infuse 4G regardless or rom, be it, stock, CM, Aeon, whatever. Prolly happens about once a week.
Another screen related issue is that sometimes, it would take the screen like 5 seconds to wake up. So you press power button, nothing happens, you think you didnt press it, and press it again. Then of course the screen turns off, registers the second press, turns it right off again. Drives me insane lol.
t10 said:
I find that on my infuse 4G, sometimes after the phone goes to sleep, when I press the power button to turn the phone back on, the display would not wake up. The phone would be on, since if I press the volume rocker, I would hear the volume up and down keys. The capacitive keys would not light up as well tho, or respond.
The only thing I can do is a battery pull. I can still call the phone tho, so I know phone has not crashed.
This happens to my infuse 4G regardless or rom, be it, stock, CM, Aeon, whatever. Prolly happens about once a week.
Another screen related issue is that sometimes, it would take the screen like 5 seconds to wake up. So you press power button, nothing happens, you think you didnt press it, and press it again. Then of course the screen turns off, registers the second press, turns it right off again. Drives me insane lol.
Click to expand...
Click to collapse
that is what we call SOD (or sleep of death) it is most common while using the LB3 modem, try flashing KL2 from here (if your not on JellyBean that is) if you on JB then download and flash the one from here. hope this helps
You can also try deleting any script in /system/etc/init.d that runs zipalign. As a first step just rename the init.d folder to something else.
i have a 32gb white nexus 5, fully charged. stock OS, rooted with TWRP recovery. using Faux123 kernel.
what's weird is that i am unable to turn on the device:
- if i power off the phone and attempt to power it on
- reboot the phone (it will shut off like it's rebooting, but won't turn back on)
pressing and releasing the power button, holding the power button for X amount of time and releasing, etc will not turn on the phone.
in order to turn it back on i have to use vol down + power...even then i have to hold it, release, hold, release, etc and by random chance the phone will boot into bootloader.
the power button doesn't seem to be the issue because it works fine turning the display on/off while the phone is on.
i have not figured any pattern or why this is happening.
has anyone else experienced similar issues?
Your best bet is to go back to stock. Stay stock for a bit and have a baseline to know how your phone is. Then after you start customizing it with 3rd party kernels, ect, you'll know if it's the phone or mods you did.
Same probleme here
I have an odd problem and I don't want to re-flash my ROM until I figure out what it is. Whenever I power down the phone, I can't power it back up again unless I remove the battery for a few seconds and put it back in.
When I press the Power button after powering down (and leaving the phone "dead" for a few minutes), it won't turn back on. If I press and hold the Power button, the soft touch buttons at the bottom (home, menu, back, search) will start flashing. If I try to power up from power off state after the phone has been charging overnight, nothing will happen. The battery in/out trick clears it allows it to power up normally. Other than this the phone seems to work fine.
DETAILS:
Phone: Sensation 4G TMO version
ROM: ViperS C2 5.3.0 (De-sensed)
S-OFF (Juponutbear trick)
Latest 4EXT recovery.
Any thoughts what could cause this? I was running CM11 but decided to go back to ViperS because of battery life. This just started happening with my most recent flash effort. (I do a full wipe each time and install the updated WiFi package thing.)
RealSkier said:
I have an odd problem and I don't want to re-flash my ROM until I figure out what it is. Whenever I power down the phone, I can't power it back up again unless I remove the battery for a few seconds and put it back in.
When I press the Power button after powering down (and leaving the phone "dead" for a few minutes), it won't turn back on. If I press and hold the Power button, the soft touch buttons at the bottom (home, menu, back, search) will start flashing. If I try to power up from power off state after the phone has been charging overnight, nothing will happen. The battery in/out trick clears it allows it to power up normally. Other than this the phone seems to work fine.
DETAILS:
Phone: Sensation 4G TMO version
ROM: ViperS C2 5.3.0 (De-sensed)
S-OFF (Juponutbear trick)
Latest 4EXT recovery.
Any thoughts what could cause this? I was running CM11 but decided to go back to ViperS because of battery life. This just started happening with my most recent flash effort. (I do a full wipe each time and install the updated WiFi package thing.)
Click to expand...
Click to collapse
go to settings and untick fastboot
Thanks! That seems to have done it. Fastboot was OK on other ROMs. Wonder why not this one?