Slow wake up when pressing power button - HTC One X+

Hi, I am running the Revolution HD 8.0 on my phone and have been quite happy with it untill recently. The problem is, that randomly the phone takes up to a minute to wake up when I press the power button. The screen just stays black and no buttons are responding. After about 30 seconds to one minute the lock screen comes on and everything works just as normal. This happens only a few times per day. Many times the phone wakes up instantly.
I have tried a factory reset of the Revolution HD and removed all user data but it still happens.
I contacted the HTC support but all they tried was a hard reset (power + volume up + volumne down). It didnt help and they told me to send the phone in to have it checked out. Since I have opened the phone a few times I do not expect to get any warranty repairs on it.
Do you have any ideas on what could be causing this and what I can try to fix it or find out more about it?
Thanks. Regards,
krautsalat82

You should try EliteKernel, so far is the most advance and battery ~ performance + temperature balanced kernel. From my opinion...
http://forum.xda-developers.com/showthread.php?t=2012320

Thanks for the reply! I have just flashed the kernel and will give it a try. Keeping my fingers crossed it will fix this issue.

I have to say the situation has improved a lot. However it still happened once since I flashed the EliteKernel. I mean if it happens once a day I could actually live with it but the root of the problem seems still to be there. Any other ideas what I can try and what could cause this? Are there any logs I could read out after it happens?

Related

My Galaxy TAB 10.1 wont turn on, I need help!

I tried the different methods or hard reset, Power + Volume buttons, Power + touch screen, still nothing; I let it charge for several hours still nothing, blank screen. The product IS under warranty but I have received it as a gift and don't have the receipt, plus the person who bought it paid by cash and can not obtain the receipt from the store, what can I do , ? Thanks
I have experienced thos with my SGT on several occasions. I just let it charge a while, then press the power button down for a minute plus. It usually starts up. If not, I let it charge a bit longer and try again. Seems to be happening ever since I put pershoot's kernel on my tab. Maybe I need to update it?
Sent from a distant planet with the aid of my towel.
ButtonBoy said:
I have experienced thos with my SGT on several occasions. I just let it charge a while, then press the power button down for a minute plus. It usually starts up. If not, I let it charge a bit longer and try again. Seems to be happening ever since I put pershoot's kernel on my tab. Maybe I need to update it?
Sent from a distant planet with the aid of my towel.
Click to expand...
Click to collapse
The "sleep of death" is an issue in honeycomb itself. Pershoot's kernel should fix this not cause it. You should always use the latest version of his kernel, he works hard to fix these issue for us. Since kernel flashing takes all of two minutes there is not reason not too.
This thread is a double post.
I have experienced it two times with 10.1 Wifi and stock rom. It just would not turn on. Tried all combination. I've then waited five minutes, tried again, and it worked. It booted and the battery was at 98%. This is a really scary bug!
this happened to me before
unplug it from the charger and keep pressing on the power buttons until you see the samsung galaxy tab logo

Strange sleep issue after .13 update

So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
EDIT: Just happened again, although now I can't seem to get the thing back on. The screen is just off and vol. up + power only makes the thing vibrate after a few seconds. I simply left the prime on the lock screen and came back and it was stuck again.
Prime BT tether lockups
XHolyPuffX said:
So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
Click to expand...
Click to collapse
Mine does the exact same thing when I tether it to my Sensation with BT.
I'm still on 2.11.1 though
UPDATE
I just manually updated my pad to .13 this morning. It did NOT alleviate my problem but it didn't make it any worse. Unlike many other user who report the lockups when sleep now, mine still only occurs when I tether BT and it goes to sleep. On the upside, I've tested my wifi and do confirm an improvement ~20% increase in signal strength and quality.
According to dd-wrt on my router signal increased from about ~49% to 63%
and Wifi analyzer signal strength ~77-68dB to ~54-47dB. I have not tested GPS.
Apparently the build variance between pads are reflected by the variance in the effects of the update
nattylite said:
Mine does the exact same thing when I tether it to my Sensation with BT.
I'm still on 2.11.1 though
Click to expand...
Click to collapse
How do you get it back on? I can't seem to power it up now.
EDIT: Nevermind, I just held power and it turned back on after about 5-7 seconds. I think it might be a "Wifi off during sleep" issue..but idk.
XHolyPuffX said:
So all seemed to be fine and dandy after the update, but I went to check something on my tablet and it wouldn't wake up. Pressing the power button, or even holding it didn't do anything; the screen was black. I held volume up and power and it vibrated, then I held it again and it vibrated again. The third time I did this, it finally booted up again.
Dunno what this means.
EDIT: Just happened again, although now I can't seem to get the thing back on. The screen is just off and vol. up + power only makes the thing vibrate after a few seconds. I simply left the prime on the lock screen and came back and it was stuck again.
Click to expand...
Click to collapse
same thing is happening to me after the update. My prime never used to do that but something in the update screwed with it. is there anyway we can revert back?
Doubt this is an update issue as I haven't seen it yet or most others. Or they all would be posting about it. That is strange though. You all didn't root n go messing around with stuff did you? Lol. If anything I'd try a fresh reboot. Maybe even clear out all the caches. Something else is seeming to cause this. By any chance did you install chrome beta? Some users reporting strange things since installing it. I don't think its the app but it is strange though or coincidence.
demandarin said:
Doubt this is an update issue as I haven't seen it yet or most others. Or they all would be posting about it. That is strange though. You all didn't root n go messing around with stuff did you? Lol. If anything I'd try a fresh reboot. Maybe even clear out all the caches. Something else is seeming to cause this. By any chance did you install chrome beta? Some users reporting strange things since installing it. I don't think its the app but it is strange though or coincidence.
Click to expand...
Click to collapse
no I didn't root. I may factory reset if it keeps doing it and see if that works. I got a decent working prime and it would suck if this update is giving me problems. yes I did install chrome beta but this issue happened before I even installed it so that can't be it.
Ok, this has to do something with the update.
My perfectly fine from before prime wouldn't unlock. I couldn't get it to respond. (I thought it was dead..) I tried to unlock and pressed volume, did nothing.
I just read this thread and tried holding the power button and it vibrated and booted after the hold...
Asus needs to stop the patch roll out untill this is fixed...
Same problem for me. And after a short sleep, it wakes up, but there is a delay of about one half second that didn't used to be there.
-gary
After that one sleep, it has not yet repeated since last night for me
not only did mine do the same thing but it also killed my battery life while my Prime was sleeping... epic fail asus its time to return for a refund and never look back.
Maybe try reverting back and see if the problem goes away.
This hard-to-wake-up issue happened to me once after the update, but my Prime did finally wake up. Have not had the issue since. There was a lag in the wake up yesterday also, as others have mentioned, but even that seems to be gone now (or I'm just used to it).
Possible fixes for this situation:
1) Hard reset (stick an open small paper clip into the little hole just below the microSD) -- I'm sure most of you have tried this already...
And, if that doesn't work:
2) Hard reset, then reapply the .13 firmware update manually right after (assuming that is possible)
My tendency is to always do a hard reset just before any firmware updates -- makes me feel a little more confident. I was lazy and did not do that yesterday, but it won't happen again.
enough with this crap
Dude, you really gotta stop trolling, this is the third thread you are spewing this crap in in the last three I read.. You obviously are not returning it, you just like to *****.
PrimeTimeBro said:
not only did mine do the same thing but it also killed my battery life while my Prime was sleeping... epic fail asus its time to return for a refund and never look back.
Click to expand...
Click to collapse
unsure if this is the right thread, but mine's been acting up since the update as well. when i'm actively using it and turn off the screen, it boots up as quick as before to the unlock screen. however, after letting it sit for a few hours, it seems to have shut off where i'll have to hold the power button on for a few seconds (after 2 or 3 tries) to get it to boot up again as if i reset the tab.
Having the same issues with mine as well. I have installed Chrome Beta, but had it running for a few days pre-update without issue.
I almost always keep mine in the dock, but haven't had a chance to determine if it only happens in the dock or not.
i have seen this occur in the past ..before the update.. i thought the battery was dead but plugging in the charger didnt do much.. held the power+vol up 3 times finally woke up .. and said 36% battery left... i m on the verge of returning this after 2 weeks of use.. just cant get over these silly silly issues
Mine just did the same thing. I'm on the newest update. Had to hold power button 10+ seconds for it to come back.
Sent from my Transformer Prime TF201 using Tapatalk
Mine died over night with a charge of 36% in balanced mode. Had to hold the button down for 10 seconds to get it to turn on today after it was plugged in the charger for 20 minutes. Now when i wake it out of sleep there is a .5/1.5 second delay for the screen to come on.
Same issue
Had absolutely no issues with my tablet prior to this update - no random reboots, but now if it's off for a minute or more, I have to hold power in for 7-12 seconds to boot up the system.
Hey, just a thought.
Maybe also include the first few of your tablet's serial number to see if the problem is consistent with some batch(es) and not others? May help others that's going to update...

Broken lock screen

Hey,
I've had my Galaxy S3 for around 2 months or so now and I upgraded to the latest UK firmware the other day (XXBLG8) via flashing in Odin.
Around 3 days ago (Just after I flashed the ROM) I noticed a problem where when I tried to lock the phone, the screen would only dim and from that point the touchscreen would not work whatsoever. The phone would only undim the screen whenever I touched the lock button or home button. The capacitive touch buttons don't respond either. When I press the power button again, it just dims the screen once again. The screen will go off after a little while, but the only way to get my phone back is to hold the power button down firmly for around 10 seconds to kill the phone altogether. I then restart it, the phone works as normal. It doesn't have this problem EVERY single time I lock the screen, only once in a while, but it's happening every day and it's ridiculous.
This is only occurring on the new ROM from what I can tell. Has anyone else had this problem, or do they have a solution to this dumbfounding issue?
Thanks
- Ross
Razyre said:
Hey,
I've had my Galaxy S3 for around 2 months or so now and I upgraded to the latest UK firmware the other day (XXBLG8) via flashing in Odin.
Around 3 days ago (Just after I flashed the ROM) I noticed a problem where when I tried to lock the phone, the screen would only dim and from that point the touchscreen would not work whatsoever. The phone would only undim the screen whenever I touched the lock button or home button. The capacitive touch buttons don't respond either. When I press the power button again, it just dims the screen once again. The screen will go off after a little while, but the only way to get my phone back is to hold the power button down firmly for around 10 seconds to kill the phone altogether. I then restart it, the phone works as normal. It doesn't have this problem EVERY single time I lock the screen, only once in a while, but it's happening every day and it's ridiculous.
This is only occurring on the new ROM from what I can tell. Has anyone else had this problem, or do they have a solution to this dumbfounding issue?
Thanks
- Ross
Click to expand...
Click to collapse
re-flash the rom and if it persists flash again. Sometimes phones like to be fickle buggers hope this solves it :fingers-crossed:
LiquidNarwhal said:
re-flash the rom and if it persists flash again. Sometimes phones like to be fickle buggers hope this solves it :fingers-crossed:
Click to expand...
Click to collapse
Yeah, will probably do that within the next few days if there is no solution. I'll backup using CWM to my SD and then re-flash if the problem persists. I can't be bothered to set up a fresh AGAIN for no reason lol.

Is my Galaxy hardware fried? Question about constant reboots.

So last week my phone started acting a bit strange. The side power button began not functioning properly. Basically - when I press the button to turn the screen off it is unresponsive 90% of the time, or it will load the "Shut-Down Menu" on even the slightest touch. Furthermore, my phone will constantly just shut off. Sometimes this happens when I am using the phone or other times when I'm just trying to turn the screen off the whole phone will just shut down.
There seems to be no constant circumstance that makes the phone shut off, it happens all the time!
I have had it ROMed for the last several months and the ROM I was using at the time it started had absolutely no issues at all. I upgraded to a JB ROM a few days ago and the SAME problem is still there.
Even further, when I am in the CWM Recovery the Power Button (which is used for Enter) is a bit funky (works about half the time) and it will STILL force shut down in CWM.
Also, this happens when phone is plugged in so I don't think it's a battery thing?
Does this seem like a software or hardware problem.... thanks for the thoughts.
dsebbs said:
So last week my phone started acting a bit strange. The side power button began not functioning properly. Basically - when I press the button to turn the screen off it is unresponsive 90% of the time, or it will load the "Shut-Down Menu" on even the slightest touch. Furthermore, my phone will constantly just shut off. Sometimes this happens when I am using the phone or other times when I'm just trying to turn the screen off the whole phone will just shut down.
There seems to be no constant circumstance that makes the phone shut off, it happens all the time!
I have had it ROMed for the last several months and the ROM I was using at the time it started had absolutely no issues at all. I upgraded to a JB ROM a few days ago and the SAME problem is still there.
Even further, when I am in the CWM Recovery the Power Button (which is used for Enter) is a bit funky (works about half the time) and it will STILL force shut down in CWM.
Also, this happens when phone is plugged in so I don't think it's a battery thing?
Does this seem like a software or hardware problem.... thanks for the thoughts.
Click to expand...
Click to collapse
It appears it is a hardware problem with solely the power button. When you press and hold the power button, it will reboot the system without warning, so it could be constantly "depressing" the power button.
Volcomstone000095 said:
It appears it is a hardware problem with solely the power button. When you press and hold the power button, it will reboot the system without warning, so it could be constantly "depressing" the power button.
Click to expand...
Click to collapse
Yeah that would make sense... ughhh...
Well, I guess it's a good excuse to get the S3.
dsebbs said:
Yeah that would make sense... ughhh...
Well, I guess it's a good excuse to get the S3.
Click to expand...
Click to collapse
Haha quite possibly! I'd try calling AT&T and maybe see if you can get a refurb if it's under warranty.
Same thing started happening to mine. The power buttons ****ed. Yesterday, it stopped working almost completely. I'm sending it in for warranty tomorrow. It was a ***** trying to reset the phone in recovery after flashing stock, I had to press the power button repeatedly to get the click the register and it powered down a few times.
If you can't get it fixed under warranty. Do a search for power switch problems on captivate. The switch on that phone has the same problems. I have cleaned my captivate power switch a few times using contact cleaner and it works good. Sorry I'd post a link but I'm using the phone app now.
Sent from my SGH-I777 using xda app-developers app

Question Realme GT 5G just turned off - now in bootloop

Hi,
Just few minutes ago my brand new phone just broke on me. I was holding it in my hand, locked screen, like minute later I tried to unlock it to no avail, screen just stayed black. There was a sound when I touched it by the fingerprint sensor, but no light up from behind the screen. I tried holding down power, then power+volume up, phone only vibrated, no reaction on the screen. I've connected it to the charger, and now it seems to be in bootloop - screen is turned off, and every few seconds phone vibrates. I've managed to somehow turn it back on once, phone booted to system, everytthing worked just fine, then I locked screen and it just stayed black, now I can't reproduce that, can't even turn it off, it's just vibrating every so often. Did it really brick in my hand? Software of Hardware? Everything worked just fine, maybe battery was draining a little bit too much for my taste, (15-20%/hour with screen on+lte/wifi) but 120Hz refresh rate+bright setting and AOD turned on 9am-9pm could do that. Do you guys have any suggestions, or I'm expecting trip to the service?
Sorry, but i cannot guess any reason. I am stumped as this bootlooping shouldn't beb happening... Very strange. May be its better to show it to service center guys.
Btw, i had tried this on my previous android phone to shut it down, like a hard shutdown. I had pressed power + volume down + volume up keys together to shut it down completely. Basically by pressing all the 3 keys. If you want to try, you can try it. I have not tried it on my GT, but had used it on Oneplue 2 and Honor View 10.
Hope your issue gets resolved asap...
Okay, I've contacted support via livechat, they told me it's definetly just software glitch, and to resolve this I have to wipe dialer cache (?) and all system settings - I did it, everything worked just fine, but today, again, same thing happened. First time phone just died in my hand, second time it was while listening to music via Pulsar, today I was just sharing wifi as a hotspot, phone randomly broke connection and would not unlock, but still I could tell it was on, because of vibrations and sounds. Not a software glitch after all? If I manage to unlock it I'll just recover it to factory settings, we'll see if that helps, but I don't like the sound of that.
What apps are -you- installing?
Launchers and power management apps are prime suspects...
Otherwise, mobo failure. It may be firmware but how far do you want to take it?
It should run fine out of the box.
Last time I played with launchers was with good old SGS about 5 years ago, only app out of ordinary was AccuBattery to check that SoT drain, but could it make such a damage without root privilages?
d4m4in said:
Last time I played with launchers was with good old SGS about 5 years ago, only app out of ordinary was AccuBattery to check that SoT drain, but could it make such a damage without root privilages?
Click to expand...
Click to collapse
Accubattery isn't the culprit...

Categories

Resources