Cross posted
So of you followed my latest "journey", I had a perfectly funtiocnal phone, I screwed up the lockscreen font sending me into bootloop, I managed to eventually get an update zip that flashed the correct lockscreen font to the phone, and all is well. Except for one annoying thing
I noticed now when I press the power button to wake the phone, the bottom capacitive buttons will light up first, then the display will light up. There's a noticeable lag where there wasn't one before.
Thinking it might be my system, I took a nandroid backup, then factory reset the phone (Settings -> Privacy -> Factory Reset). When it was done reloading the factory restore, I tried turning the screen off and on, delay was still there. I restored my backup, phone was back to normal, but delay was still there.
Any ideas where this delay came from? I'm going to try flashing a few other backups I have and see of they all do it.
I noticed this too. I think it's Virgin Mobile's way of "fixing" the flickering screen problem... just don't let it power on until it's cooled down. Thus we get a slow-to-turn-on screen.
Related
This just happened like 45min-1hr ago. I was getting everything cleaned up before i got off of work and i was texting someone and my phone froze, so i soft resetted. it turned back on then it froze again so i once again soft resetted then i put it back in my pocket. i heard the sound the phone plays whenever it turns on and was like okay it's back on everything will be fine. i took it out and the screen is black. i thought it was on sleep mode or w/e but it wasnt. i took out my battery and put it back in and turned it on but the screen is once again black. anyone know how to fix it? i think my screen is broken
i have a touch pro also.
Possibly not the answer you want but have you tried hard-resetting the device? OK it wiped everything but at least you might get a working device from it. Had to do it once on my Trinity, it locked up on receiveing an SMS and a soft reset wouldn't complete, hard reset cured it.
just a regular hard reset? vol down center button. my cousin came over and said it mighta been my backlight? just tried turning it on again and it's real dim but i can barely see the screen.
I was thinking a regular hard reset, but as you have some display, albeit very dull have you checked the backlight hasn't got itself turned all the way down?
deedee said:
I was thinking a regular hard reset, but as you have some display, albeit very dull have you checked the backlight hasn't got itself turned all the way down?
Click to expand...
Click to collapse
how would i check if the backlight is all the way down?
Go into the backlight settings and see where the sliders are.
tricky i know when the screen is very dull, but it might be possible.
that's not probable. minimal backlight doesn't mean black screen.. unless it's a device i'm completely unfamiliar with... tho it is still unprobable.
as deedee suggested, i'd hard-reset
I'm having the same problem, did you find a fix?
OK so I downloaded & installed the latest OTA update (RV23RC03; 1.057) with the power mode choices, and it has completely destroyed my touch screen response! I previously had ZERO problem with this- every key press registered on both the original ROM and the 1st update. Since the latest update, everything takes 2 or 3 presses, sometimes VERY firmly, many times still without registering. This totally sux
Is anyone else having this issue? I should note that I do have a matte screen protector on; this previously caused NO problems.
Is there an easy reasonably safe way to revert back to the 1st update (RV07RC06; 1.029)? A link and/or instructions appreciated. Thanks.
Acer, are you out there? This exact issue occurred with my A510 on its 1st update, after which it became nearly unusable for me. Since it was < 30 days I was able to return it. No such luck this time. Why are these updates doing this? It's driving me nuts!
No issues with touch on update. It seems to be running better actually.
Try to completely reset thru recovery with wipe data maybe.
More specific instructions
Itchiee said:
No issues with touch on update. It seems to be running better actually.
Try to completely reset thru recovery with wipe data maybe.
Click to expand...
Click to collapse
That's so amazing. I went from no problem at all, to I can hardly use this any more; only thing that changed was the update.
Can you please be specific about how to reset through recovery. (Step-by-step if possible) and how to wipe data.
Thanks.
You can reset data thru settings/privacy but you will lose everything and start fresh.
I'll check on the other method later on for you.
Also turn up touch sensitivity in settings/display if you haven't...
Edit - it appears that the stock recovery doesnt have those options.
You can still reset by inside ICS like above, or...
Factory Reset:
WARNING: reset will start immediately
Volume button (one dot) and Power button, once buzzes release power button and then toggle the rotation switch on and off a few times
Yes of course, I have set screen sensitivity to high. I think I'd rather go back to 1st update, rather than wipe everything (I do have a backup but it's still a hassle). I can't believe no one else is having this problem.
Any idea how to revert to last update?
Someone in a german android forum mentioned that it help on his device after the update to set the sensitivity to the lowest setting and then back to middle or high.
I tried playing with sensitivity settings, turning on/off,resetting and no luck.
I actually found the ROM from before the update on this website and flashed it as update.zip with vol +power. It worked, I now have 1.029 back and touch screen works perfectly. I'm sorry to lose power management but i think I'll stay where I am . Don't ask me about a Jellybean update; I'll want it but after this I'll be afraid to try it. If anyone has an explanation for this i'd love to hear it.
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
This issue make absolutely no sense to me, and only started yesterday.
First, I am stock, unrooted, no mods, no crazy sideloaded apps, just a good old Nexus 5.
When I go to wake the phone, I have noticed that the lock screen is 100% unresponsive. I cannot enter a pattern lock. I then switched to a PIN lock, thinking maybe there was an issue with the pattern. Again, unresponsive screen. So I took my screen lock off completely, thinking there is maybe an issue with the lock screen in general. Again, even with no lock screen, I cannot swipe screens, open apps, nothing. This also includes the soft keys at the bottom.
I decide to factory reset my phone. I update only my Google apps, and again notice the same issue. The screen is totally unresponsive, but then 2 white lines will flash at the top, and the screen will work.
Once those white lines flash, the screen is completely responsive like normal, there are no other issues until the phone goes to sleep again. Sometimes the little lines flash 2 seconds after waking up, sometimes 30 seconds, sometimes I have to hard reset the phone.
I also am linking to a YouTube video that I recorded of the issue in case I am not making sense.
So can anyone explain this to me? What could cause this issue on a phone that has never been rooted or flashed or anything?
Thanks in advance for the help!
https://www.youtube.com/watch?v=2r3U9MhZuG0&feature=em-upload_owner
Weird. Issue. Maybe you should stick everything from your sd to your pc.
And flash a factory image from fresh install from here - https://developers.google.com/android/nexus/images - if you're lucky the drivers maybe corrupt and not the hardware
Sent from my Android 5.0 Nexus 5
Could also be a loose connection. Maybe the flex cable to from your screen wiggled its way out a bit. I've never seen that before on any phone. I'd back everything up and flash a factory image. If the issue persists, contact Google and see if you can RMA the device.
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!