My S3 is running stock 4.4.2 and isn't rooted (though it has been in the past). At times my phone will not wake up after the screen turns off.
I have to pull the battery to get it to work again. This doesn't happen all the time, but it can happen 5 or 6 times a day. This has been
happening for about 4 months. I did a factory reset and the same thing happens. There is no rhyme or reason to when this happens.
I have read a bunch of posts about this, but there seems to be no definitive answer. Some say do a factory reset, which I did. Some say
it is the version of Android they have, but this goes back a couple of years and everyone is on different versions of Android.
As a habit, I always press the power button to turn off the screen so I do not make any pocket calls. To use the phone, I press the power
button again, or the home button to wake it up.
The phone is 2 1/2 years old and except for this glitch, it has worked flawlessly.
Any ideas?
Thanks,
Ian
Just a guess, but probably a faulty power switch. It happens fairly often, but usually displays different symptoms than yours. It would be the first thing I'd focus on though since it's very unlikely it's software/firmware related.
Sent from my SGH-T999 using Tapatalk
My thoughts too are that it is an hardware issue rather than firmware. Had a similar problem once and it turned out to be the power button. However, with a device of this vintage, you can never be too sure.
Good luck!
Related
I have had my Htc Evo rooted for a long time now. This problem recently just started and I'm not sure if it's because my phone is rooted or maybe it's just an electrical or hardware problem. The top right button to lock the phone or to wake it up from sleep doesn't register all the time. I sometimes have to push it several times for it to work. Do you think I should restore my phone? Maybe it's because it's rooted? Something got corrupted? I'm leaning more towards hardware problems..
Any ideas?
Thanks!
steveojp said:
I have had my Htc Evo rooted for a long time now. This problem recently just started and I'm not sure if it's because my phone is rooted or maybe it's just an electrical or hardware problem. The top right button to lock the phone or to wake it up from sleep doesn't register all the time. I sometimes have to push it several times for it to work. Do you think I should restore my phone? Maybe it's because it's rooted? Something got corrupted? I'm leaning more towards hardware problems..
Any ideas?
Thanks!
Click to expand...
Click to collapse
Are you just having trouble waking the phone up with the power button, or is it all functions of the power button are acting weird? Does it put the phone to sleep fine? I've had it happen a few times, where the phone wouldn't wake up by pushing that button. That was attributed to the ROM i was using at the time, and also having the min clock setting at 128.
If your case is different, and the button isn't working properly for all of it's functiopns, and not just waking up the phone, it could be a hardware issue, or the button mechanism could be hanging up or something.
k2buckley said:
Are you just having trouble waking the phone up with the power button, or is it all functions of the power button are acting weird? Does it put the phone to sleep fine? I've had it happen a few times, where the phone wouldn't wake up by pushing that button. That was attributed to the ROM i was using at the time, and also having the min clock setting at 128.
If your case is different, and the button isn't working properly for all of it's functiopns, and not just waking up the phone, it could be a hardware issue, or the button mechanism could be hanging up or something.
Click to expand...
Click to collapse
All the functions of the power button is acting weird..sometimes I have to push the button like 10 times for it to wake up so I can unlock my phone. Sometimes I have to push it 5 times or more to turn it off. It's weird though how this randomly started doing this. I was hoping it was the Rom. I'm running Fresh I've never had any problems with it. That's why I leaned more towards the hardware. Is there any way to go around pushing the power button to wake up the phone? Do you think I should restore my phone to see if it maybe fixes the problem?
Thanks!
steveojp said:
All the functions of the power button is acting weird..sometimes I have to push the button like 10 times for it to wake up so I can unlock my phone. Sometimes I have to push it 5 times or more to turn it off. It's weird though how this randomly started doing this. I was hoping it was the Rom. I'm running Fresh I've never had any problems with it. That's why I leaned more towards the hardware. Is there any way to go around pushing the power button to wake up the phone? Do you think I should restore my phone to see if it maybe fixes the problem?
Thanks!
Click to expand...
Click to collapse
If it was me, I would make a nand backup of your current setup, and then try flashing a different rom, and seeing if the problem persists. If it continues, I'd then unroot and return to stock setup. If it happens on stock setup, I'd then take it to Sprint to have it looked at.
Sent from my PC36100 using XDA App
k2buckley said:
If it was me, I would make a nand backup of your current setup, and then try flashing a different rom, and seeing if the problem persists. If it continues, I'd then unroot and return to stock setup. If it happens on stock setup, I'd then take it to Sprint to have it looked at.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Alright, I'll do that. Thanks
bump for update from OP
Power BUtton Problems with Waking etc.
Not sure if you ever resolved your issue, but I have the EVO 3D, NOT rooted but with the latest updates, and ever since the last OTA update that moved me to software level 2.08.651.2, I have had issues with the phone not waking on an inbound call until I hit the power button and then wait about 8 seconds for the screen to come on. I have Factory Restored it 3 times, which seems to fix the problem temporarily, but it always comes back.
I just did a warranty replacement claim to see if that will finally resolve the issue. I even found a post where someone said the stock batteries are somewhat loose, so I took a business card and taped it to the bottom of the battery, opposite of the charging posts so that the fit would be better, still no luck.
steveojp said:
Alright, I'll do that. Thanks
Click to expand...
Click to collapse
Issue: Power button won't turn screen off. Either it doesn't respond to the button push at all or it treats it as a long press and will pop up the phone options menu. Power button wakes phone just fine. Also, if I boot into recovery while experiencing this, not all power button pushes register within recovery (ouch).
It's weird because I experienced this for the first time like 2 months ago a few hours after flashing a Tiamat kernel (actual kernel may have had nothing to do with it), but after fiddling around with my phone it started working again.
Well, it started happening again on Saturday using CM 7.0.3.1 w/ GoDm0dE v5. I got it to work again by doing a factory reset, then restoring a backup. Well, it came back last night and persisted after another factory reset. It was very consistent today -- for hours it would either do nothing after pressing power or it would pop up phone options. Finally, a did a factory reset within CM7 and also within Amon-RA 2.3 and then restored a backup from yesterday and the power button functioned properly for about 1.5 hours.
Has anyone experienced anything similar?
ROM: CM 7.0.3.1
Kernel: Stock
Recovery: Amon_Ra 2.3
HW: 003
Never had that experience. Could be a number of things. It might be the Kernel/ROM mix, the Kernel itself, the ROM itself...But I would think that if it was any of these things, I would have heard about it by now from other users.
It could be something as simple as a short in your power button or the connections underneath it. Might just short out at the right times to make you think it is something you are flashing. Try shooting some compressed air in there (might help).
drgonzo712 said:
Never had that experience. Could be a number of things. It might be the Kernel/ROM mix, the Kernel itself, the ROM itself...But I would think that if it was any of these things, I would have heard about it by now from other users.
It could be something as simple as a short in your power button or the connections underneath it. Might just short out at the right times to make you think it is something you are flashing. Try shooting some compressed air in there (might help).
Click to expand...
Click to collapse
Thanks -- I actually tried the compressed air. I'm thinking it's hardware. It seems to have gotten worse in the past hour.
im having the same issue. i googled it earlier and it seems like theres alot of people have that same problem. its looking like a hardware issue. I can tell you one thing tho its pissing me off.
shdwboy said:
im having the same issue. i googled it earlier and it seems like theres alot of people have that same problem. its looking like a hardware issue. I can tell you one thing tho its pissing me off.
Click to expand...
Click to collapse
I unrooted and it actually started to do the same, but when waking the device. Brought it into Sprint and getting a replacement on Wednesday.
Had this exact same issue up until a few days ago. I took a needle and went around the power button front and back, something unjammed I guess and now it works like a charm. I've also had this with a software problem. My power button wouldn't work, even in recovery. I restored a nandroid and this fixed it. Hope this helps! Best of luck.
I had the same issue. Sprint said it wasn't the button but the board not responding to the button. Got a new phone.
Sent from my PC36100 using XDA App
About three weeks ago my launch Epic 4G Touch got its power button stuck on. In the weeks prior I had had occasional glitches where pressing the power button would turn on the flashlight (an AOKP feature where if you hold the power button from off, it turns on the light), or when pressing it to put it in sleep I'd get the power-off menu. And occasionally it would get worse, where pressing the power button would lead to the entire phone shutting off and restarting after a few seconds, as though I had held the power button down the whole time. Anyway, as I said, it finally reached the point where the button was apparently stuck sending the On signal the entire time. And it was clearly hardware-level, as if I'd pull the battery and put it back in it would INSTANTLY power itself back on.
I took it to the Sprint store, they reviewed it, couldn't fix it, and ordered me a replacement which arrived a few days later. I've had that replacement for about two weeks now without any hardware problems. I did switch to AOKP again, but I've had no issues whatsoever.
Until today, when it progressed through all the above-mentioned symptoms and all the way to stuck ON permanently, in the span of a few hours.
Has anyone else experienced this? Is there any logical reason to suspect this could be a fault of the sofware I've installed? I've never heard this symptom before, which makes me think it's extremely unlikely or others would have caused it, plus the power-on from battery implies to me this can't possibly be a software issue. But I want to be sure before I get it replaced yet AGAIN and cause it again, or have the store try to blame my custom ROM (they never said a word last time).
Help?
EDIT: Pretty confident I just confirmed it's a hardware problem. I booted into CWM to try to make a backup so I could flash to stock and confirm it wasn't software. The power button of course didn't work in CWM either. What I hadn't thought of is that I couldn't get back OUT of CWM without the power button. Even a battery pull would put me right back into it. I finally get desperate and yanked the battery and banged the phone on the desk against its power button a few times, then put the battery back in and the phone didn't power itself back on. I then hit the power button, booted to CWM, and managed to use the power button to reboot to system. So that confirms it's hardware to me. So I guess the question shifts to: two phones in a row with this problem, and I've never seen it mentioned before. Am I just incredibly unlucky, or have others experienced this? Second: anyone successfully manage to use a scenario like this to talk them into a different phone? I'm not loving this chain of events, and I'm not loving to hack my phone to get a good stock experience. I'd really love to switch to a Galaxy Nexus. Any tips?
I have the same problem just got it today....Really need to fix this
Sent from my SPH-D710 using xda app-developers app
Seen a couple different threads about power button. Someone took it in to be repaired/replaced only to have it go bad again later. I guess I have gotten lucky, there was a good while that my power button liked to stick and not function properly. It went away one time after I accidentally left my phone in a hot car. I suppose my issue could have been from something sticky being spilled on the phone though.
Sent from my SPH-D710 using XDA
Hi there,
I have this really annoying behavior of my nexus that sometimes the screen just doesnt want to turn on which means I have to do a hard reset and the worse is that its happens more and more.
Some days ago I read in this forum something about the light sensor but I couldnt find the thread again
Any idea what I can do?
Cheers
Stephan
Are you undervolting on a custom kernel? That can definitely cause your SOD issue.
prshosting.org
no, its the standard google android rom and it happens with 4.3 as well as with 4.4
The only thing is that the device is rooted but that shouldnt cause a problem
I have this same issue, brand new Nexus 7, it hasn't happened yet today but for the first several days (on both stock and then OTA 4.4) I simply COULD NOT make the thing turn on with the power button. I was cringing hard because my Note 2 had that problem out of the box and I had to ship it back for warranty (for six @%$&'ing weeks), but in that case the button felt obviously sloppy. On my Nexus the button has a very crisp feel to it, I was wondering what I could be doing wrong but it seems to have 'broken in' or something because it hasn't happened the last 50 times I poked at it. Honestly, it felt like a software bug rather than a hardware problem.
I also was running stock and had the SOD. I was lucky because I just had to hold the power button for 15 seconds.
diesteldorf said:
I also was running stock and had the SOD. I was lucky because I just had to hold the power button for 15 seconds.
Click to expand...
Click to collapse
yeah, but when u press the power button u do a reset and I guess thats not the idea of standby . Actually I have to do a reset almost every second day, also when the notification led is blinking
Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz
I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.
I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.
Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.