So, say I install a new kernel, or update the rom, or just want a reboot or whatever.
Well my phone will reboot quickly, but then will seem to lag really badly when the phone is turned on.
For quite a long time (maybe 20-60 seconds, i havent counted) my power button doesn't do anything. My phone is responsive to touch, etc, but the power button won't put it to sleep.
Then about 20-60 seconds, again I haven't actually counted but it seems like a while, the phone will randomly load settings I have saved on boot from Trickster MOD and Franco's Display Control app. It is at that point that my power button is functioning again.
I'm not sure if it's these settings causing any problems, but it's weird and annoying cause I can't really do anything until the settings apply. It seems like maybe it's stalling on getting SU permissions, because once that toast message appears everything suddenly works.
Anyone ever have this issue? Running Paranoid latest, and Franco 38.
I'll keep messing with stuff to see if I can solve it myself, but just wondering if anyone else has had this issue.
I'm also experiencing a delayed response from trickstermod and franco's display app after reboot (I got used to it); but my power button is functioning well.
Sent from my Nexus 5 using Tapatalk
I actually have noticed the power button not working sometimes, usually with an xposed module that I reset. I always deleted the module and thought it was a bug. Ended up turning me away from xposed. Maybe I should look back into it again lol.
Sent from my Nexus 5 using Tapatalk
I think this delay is different for every rom/kernel. I noticed a serious delay on AICP (with a custom theme) to load widgets and to have all toast notifications at boot and this delay is significantly on SlimKat (power button is immediately functional after entering my PIN code). I've kept the same Xposed modules.
Related
I've recently picked up my new Infinity and I've noticed that after the screen times out (I've set it to 30 seconds), it won't turn back on after I press the power button. Sometimes I have to press it numerous times before it will show the lock screen; other times, I've had to press the outer button down to reboot it.
Is anyone else having this issue or know what the issue is?
I have "same" problem and is driving me crazy. Did a cold boot, did a factory reset (through cold boot and through OS) - didn't help.
When my pad is in a locked/sleep state for longer time, it doesn't wake up anymore. It is draining battery as a sponge, but doesn't receive e-mails etc...so it could be it freezes or the wifi is off.
This problem is usually reported with a fact that one has enabled to turn off wifi when in sleep state (prime forums)...
My case:
- i had set wifi to never sleep
- i fiddled with build.prop and i think only after that the problem emerged (i mention this because there is a setting about sleep/wifi thing)
- i have restored orginial build.prop
- i have tried to set wifi to turn off in sleep
- i switched back to never sleep
- i coold boot, factory reset
Nothing helps anymore.
It is better with the Power Fx widget i think.
It happens less regulary, but it still does and I also don't know what else to do.
Some are reporting there is a bug in 4.0.3 ICS - but i don't know.
I think this is not a HW issue, and i refuse to do so
Hopefully JB update will solve this, too.
BTW: as i mentioned in my other topic on this matter, i am pretty surprised that factory reset didn't change my bootanimation and some other stuff on the system folder. Because of this fact i think factory reset will not help with this problem as it seems it leaves some things intact, which could also mean that if there is something wrong with SW it just doesn't overwrite/change it and that's why the problem is still here (broken file, changed file, cache...i don't know).
If this problem persist for a week or so and if there is still no JB update i will probably just go and install the latest update manually, which i think should overwrite all files. But, not sure.
Please if anyone has any idea on what is going on....
I have this same issue. It usually occurs after long periods of being idle and I pick it up to use it, hit the power button to wake it up, and it just doesn't wake up.
I have to hold the power button + vol down button to restart it.
Sometimes it'll happen when I just put it to sleep too or after short idle periods.
It's somewhat embarrassing when in public using it and randomly have to reboot; it also did it once when I was in class taking notes, thankfully SuperNote saves as I go.
Any ideas what the cause is? I'm only rooted, no custom recoveries, ROMs, kernels, etc. I'm running the stock ROM .26
Over this past week the back light for my Nexus S 4G appears to randomly shut off. Right now it has happened about 5 times and when I need to use it right then, preventing me from just stopping to investigate what may be causing this. The screen still comes on allowing me to quickly unlock using the pattern and then restart by holding down the power button. The one time I was able to investigate a little I was navigating into the settings menu when the screen just went blank. I pressed the power button a few times and could see the hardware buttons below lighting up as if the screen was on but that was it.
I'm currently running Slim Bean (Android 4.2.1) Beta and will be trying another rom but wanted to see if anyone else may have encountered this issue before I bring it up with that thread.
Yeah experienced this too in most 4.2 ROMs that I've tried. Some people say it's a bug with the auto- brightness settings but I don't buy it since I don't really use auto-brightness but still get the error. I'm back to 4.1.2
Glad to hear. I was becoming worried I had some hardware that was failing.
I will turn auto brightness off and see how it goes.
Thank you
So it has happened quite a bit since my last post. Even with auto-brightness turned off. I'm blaming this bug for my alarm not continuing after I snoozed it a few times. (I know they are unrelated but its just really annoying).
It happened again about ten minutes ago and I managed to output a bug report feature on 4.2.1. Not sure if it is of any use to anyone. Message me if you would like it.
Hi - I have tried multiple Lollipop based ROMs on my OPO. All the Lollipop ROMs have exhibited the same failure on my OPO: When the phone wakes up, I will randomly see a totally black - and basically unusable - desktop, but have a fully working Status Bar and working pull-down Navigation Bar. Holding the power button also brings up the shut-down options. so, I know that my phone isn't dead or frozen, I just can't see anything on my desktop. If I press the power button momentarily to lock the phone, I will see the unlock 3x3 pattern grid when I power on, and I can unlock the phone - but, I see a black desktop.
I recently loaded the official CM12 nightlies, and I am seeing the exact same thing. One thing I have finally determined (which I suspected previously), is that there was some sort of App crash during the phone sleep that had a pop-up message on the screen when the phone woke up. After a lot of random finger mashing and loud screaming at the phone, I saw my desktop again, and saw that "Google App" had crashed. After clearing the error pop-up, my phone has worked fine without rebooting ... for now.
The problem with this is that the black desktops become more frequent as time progressed, eventually reaching the point where I would reboot my OPO and it would power up to a black desktop. In the past, I occasionally saw a flash that looked like a pop-up message before the black desktop, and now I have confirmed that is what is happening.
Does anybody know what is going on?
The problem can be the gapps package you're flashing. Try another one.
MickyMax said:
The problem can be the gapps package you're flashing. Try another one.
Click to expand...
Click to collapse
Thanks! Do you have a suggested gapps I should try? I loaded pa_gapps-modular-mini-5.0.1-BETA7-20150111a-signed with this build.
Hey guys,
strange and frustrating problem. I was using my phone pretty extensively today (although nothing crazy), mostly thanks to Pokemon Go. Tonight after using my phone normally, I went to press the power button to turn the screen off and nothing happened. I was able to reboot (by changing one of the long-press actions to bring up the power menu via GravityBox) and then was unable to power on the phone. It seems like my hardware power button has suddenly become unresponsive. This leaves me unable to power on/off the phone, including booting into the bootloader. Also, I seem to be unable to wake my phone up by double tapping the screen or swiping up.
The phone otherwise functions fine. If I get a notification, the screen wakes up and I can use the phone. Otherwise, the only way I've been able to get into the phone is by connecting it to a computer and issuing ADB commands. The IR blaster functions fine which makes me think it's not the hardware button?
Has this happened to anyone else before? Can the power button just break like that without any water / physical damage? The fact that I also can't wake the screen makes me think it's a software issue. One other thing I suspect is that my phone abruptly died yesterday (battery died despite software thinking it still had juice left). In the past, with the modified kernel / rom, this has resulted in some nasty issues, including 4G not working and the Android system process basically exploding. I thought I lucked out when I powered it on after that, but maybe it just took a day for this issue to manifest itself.
I'm going to make a NANDROID backup and try flashing a few different things to see if I can fix it. I'll post my progress here.
Current build:
- Verizon M8, S-OFF
- TWRP
- Android GPE 6.0 (MRA58K.H13)
Edit: I haven't been able to find a fix. I'm a bit afraid to try a full RUU since I can't use the hardware keys to reboot into the bootloader should something go wrong. It may just be that my PWR hardware button is f'd which really sucks. I'm not sure I'm up to cracking open the phone to fix it. In the meantime I downloaded an app called Gravity Screen On/Off which uses the phone's proximity sensor to wake the screen up and it seems to work ok for now.
Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:
UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??
BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.
So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/
So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?
Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.
I haven't had this happen since upgrading to Oreo a week ago, so far so good!