I have a Rogers HTC Dream. I've had it for months now. I recently upgraded it to the newest version (1.86).
I was just fiddling with a new app I downloaded - "shake alarm" (where you need to shake it to stop the alarm) from the market. to test it, I set an alarm within a minute. after I closed the phone, I put it on idle. then it started to restart itself and it won't stop!
I've taken the battery out many times to stop it but it still won't load properly!
can someone please help me?
Well, I think the only thing you may be able to do is to do a wipe. Turn on your phone by holding home and power. Release when the recovery screen comes up. Open the keyboard, press Alt + W
When that is done, you can press Home and Back to restart. This resets everything back to factory, you'll have to set everything back up. I think that your downloads will be saved the first time you load up Market, but they'll be gone after that, so try to install them all at one time (that's if they are saved).
hm, I tried but it won't let me past the HTC loading screen.
Urgent!
My HTC dream has the same problem, its keeps on restarting and doesn't let me get to the recovery screen. Can't downgrade using fast boot as well, as it from Singtel. It used to happen before but used to get ok once i'll take out the battery and boot it again but now it just keeps on restarting. Anybody with a solution?
Or can anybody tell me why its happening?
The lock screen on my wife's Captivate has stopped working. It doesn't require you to swipe. If you set an unlock pattern, it doesn't require that either.
If you short press the power button the screen goes off. However, if you press the power button again, the phone returns to where she was without prompting for the unlock. If you let it time out, the screen goes off. However, once again, pressing the power button goes right into the phone.
I have tried requiring a unlock pattern, not requiring one, changing it, changing the screen time out. I have also switched back to TouchWiz from Launcher Pro.
I rebooted the phone and that fixed the problem for a couple of days. Now the problem is back.
This phone is a pure virgin, only 2 weeks old. It's not rooted. It is build 1010. It's running stock JH7.
I also have a Captivate and have never experienced this problem. I'm suspecting perhaps one of the apps that she is using. The irony is that I have often thought this might be a desirable mode.
Any ideas?
Thanks,
Rich
Any apps installed? There us an app in the market called no lock I think that will do that as a feature
Sent from me
After writing that question it got me thinking. I decided to install ATK and kill one app at a time to see if killing any of the apps would fix the problem.
Sure enough, I figured out that it appears to be Tango that is misbehaving. Once I killed Tango, the phone lock worked again. I started Tango back up and the screen lock continued to work. I then made a Tango video call. After ending the video call I tried the lock screen again. Bam! It no longer locks. I kill Tango and the lock is again restored.
For some reason Tango doesn't affect my Captivate (build 1006). I'm not sure why it affects my wife's.
Who says ATK isn't necessary?
-Rich
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
ummm the power button on the nexus one has an incredibly high failure rate, all over the forum here. its a design defect from the factory. that's why it has always been recommended to root the device immediately, and use trackball wake, so you avoid using the power button as much as possible. you have to send the device to HTC for repair, that's your only option...
Thanks for the information. I will have to look into repairs.
You are already running a rooted rom with track all wake. Use it. To reboot the the phone use quickboot. At this stage you really don't need the power button on your phone.
pcflet01 said:
... now that I have installed CM7.
I push the power button and the screen turns on and then back off almost immediate
Click to expand...
Click to collapse
This is a problem with CM7. Most advise turning off the screen off animation if it becomes a big problem for you. Make sure you are using the newest nightly and hope for a fix. I don't know if the RC's have this problem, but I would bet it appears on the 7.0.3 release.
At first glance that seems to have helped. Thanks for the advice!
No problem.
Also you can use widget locker to lock the screen then the trackball to wake, with that and quickboot I don't even touch my power button anymore. Although your problem doesn't sound like a broken power button so in your position I would switch ROMs and see what happens.
pcflet01 said:
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
Click to expand...
Click to collapse
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
As others have mentioned, this does not sound like a powerbutton issue, because the powerbutton still turns on the screen. The problem is that the screen turns off immediately after it turns on.
When you flashed 7.0.3, did you come from a previous CM verison? From stock? My first suggestion would probably be to wipe the /system partition (in CWM, it is under mounts and storage -- with Amon_RA, you need to find a flashable zip to do it) and reinstall CM and gapps. This will not cause any data loss. Sometimes, if you install a new ROM over an old one, the upgrade script in CM can get confused and carry over files that aren't supposed to be carried over. The system wipe fixes that.
I've been using this RC since it came out in late June. Only this week did it start flipping out on me.
Sent from my Nook Color!
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
bassmadrigal said:
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
Click to expand...
Click to collapse
I'm currently using S2E for apps2ext and some data2ext. How would a system wipe and reinstall interact with that? I'm a bit nervous on that front.
A system wipe shouldn't change any of that. It is one benefit of using S2E as it is a standard app that is stored in the /data partition without any changes to the /system partition.
Anyway, to be safe, it is a good idea to do a nandroid backup anytime you are doing something that involves the majority of the features in recovery.
It's a hardware problem for me. Failed completely as of today.
Sent from my Nexus One using Tapatalk
CM7 7.1.0
My power button seems to be in the process of completely failing. The new CM7 update to 7.1.0 has made it possible for me to lock the screen without using the power button using the "Notification power widget" -> "Go to sleep". Now the only times I have to use the power button are to shut the phone down or wake it up, which seems to be easier when the phone is plugged in to a wall charger. Are there any simple apps for shutting the phone down and maybe waking it up at a set time?
The only reliable trick I found to turn it back on was to plug into the wall and take the battery out/in a few times till it vibrated.
I ended up getting a replacement phone and then I sent the Nexus to HTC. They quoted a $55 repair cost off warranty which my credit card insurance would've covered, but when I asked for an invoice they offered to just waive the charges. Finally over a month later it came back fixed.
The app Easy Reboot can shut the phone down.
Sent from my Nook Color!
I also use an app called Lock Screen, which just locks the screen. I have it stored in my dock, because I don't like the space being used in the notification widget.
CM7 has an option for one of the items in the notification tray widget to be a lock screen button.
cmstlist said:
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
Click to expand...
Click to collapse
THANK YOU!!!! This has been driving me crazy. Turning off the screen-off animations did nothing, but turning off the screen-on animation seems to have fixed the issue. My power button is toast (my new power button ribbon cable just arrived... time for surgery), and I've been using the trackball to wake my phone. Before the power button died, it did the same thing. I'm using CM7.2. I installed it after rooting and went straight to cm7.2 from stock, so obviously the cyanogemnod crew haven't fixed the issue since 7.0.3 when this thread started.
My phone was working just fine till today morning my phone hung up. As a general response I pressed the power key to lock it. Nothing happened. Nothing. So I waited it out. Soon the phone was back but the power key became totally dead. It wasn't locking the screen. I used the Screen lock app on emanoN rom v4 to lock the phone and it was working. The screen was getting locked. Figuring this must be some freak bug I tool out the battery and restarted the phone. Same problem except now even simply pressing and not long pressing the lock key would prompt the shut down menu. If ignored the phone just casually restarts. This is annoying because if out of reflex i press the power key , my phone will restart. Now, sometimes the power key does do it's job of simply locking and unlocking the phone. But sometimes it just restarts the phone.
I thought this was a problem with the ROM and so i shifted to godell's MORe ROM. Same problem. Now I've shifted to fresh stock 2.3.6 flashed using Odin and I'm still having the same problem. Pressing power does not lock and instead prompts the shut down/restart menu. and Sometimes the phone just restarts at random . Please help me fix this.
I'm going to go for a full downgrade to 2.3.3 [Since my 2.3.6 upgrade just flashed the MODEM*.md5 and CODE*.md5 files]
But before that.. Why is this happening? Is there any fix?
Thanks!
I have completely reflashed to gingerbread 2.3.3 using odin and problem persists.
I do not think this is a hardware issue,because the button's reactivity is just fine. It's just the action that it does after the keyPress.
Your power key problem might be a hardware issue... :| How old is your phone? You might have used it too much. My friends galaxy mini- the volume up button doesnt work because he used it too much.
It's about an year old.. I'd say 10-11 months or so..
I've got an AT&T HTC One M7. It's non-rooted and has stock firmware. Android updates from AT&T are installed when pushed. It's all pretty routine. As of yesterday evening, this phone started rebooting and won't stop.
If I leave it alone, it vibrates (normal startup notification), goes to the green on white "htc" screen for a few seconds, then goes blank and starts over. I can get to the bootloader screen, and I've gotten it to start in safe mode as well, but it always restarts again within a few seconds.
Things I've done/found:
- Holding down the volume down button while it restarts takes me to the bootloader menu, but the buttons don't seem to work correctly when I get there, and it always restarts again within a few seconds.
- I managed to start it in safe mode a few times--I think by holding volume up and volume down at the same time--but it restarted before I could do anything.
- I removed the SIM card. Same thing.
- I let it reboot until it died. As soon as I plugged it in, it started the same thing again.
I'm starting to think it's hardware failure, like the power button is constantly making contact, even though the button feels fine to the touch. Note that I get to the bootloader just by holding the volume down button. I don't have to touch the power button. I'm not certain whether that's normal. Can anyone give me any ideas or even just verify that it seems like a hardware problem?