Related
OK - since the recent ota upgrade to ICS we've been having a few problems with the table touchscreen freezing - unfortunately now it seems to have got stuck almost all the time. Just at the moment, it is not responding at all to touch - just displays the lock screen when powered on, and then times out a little while later to black. I have to push power to get it back on - but the touch screen simply won't respond to unlock it. So far I have tried:
Holding down power until restarts - no effect - reboots still locked.
Using Vol-Down power on and doing factory reset - no effect - reboots into android setup screen touchscreen not working.
Draining power until it won't turn on. Then recharged. This worked! However...
After going through the setup process, resintalling apps etc., I hit the power button to go into standby. I then thought I'd go straight back in, but as soon as I hit the power button again, it wouldn't respond! Left it charging for a couple of hours, and turned on, this time got in - but same again - hitting the power button and coming straight back in, it's not responding again.
So I'm now back with a fully charged tablet that won't respond to touch at all. - perhaps if I leave it a few hours it might respond again - until it goes into standby!? The device is fully stock with WW_epad-9.2.1.11-20120221 (according to the screen at boot up when you hold down vol-d).
Is this likely to be software or hardware related? Do I need to send it for repair/replacement, or is there something else I can try first? Any help much appreciated. (Oh - I don't have external keyboard btw - so without screen it's pretty limited what i can do!)
Cheers,
Colin.
I have already encountered the same problem but with a cutom rom. to find my touch, I had to do a full wipe and new intallation.
I did full wipe using the Power/Vol-D but the touch screen didn't start working again until I let the battery completely drain.
Then I reinstalled everything (screen was working to begin with), however after I'd set everything up and reinstalled all my apps it stopped again.
Yesterday I managed to get an ota update to 9.2.1.17 (it started working for a short time). But then aftger rebooting again, it stopped again.
This morning it is working again, and I have uninstalled all my apps - just the core stuff on there now. For the moment it appears to be working (which is the longest for a while!) - going to see if it stops again while there aren't any extra apps installed...
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.
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!
An hour or so ago everything worked fine, and then I updated my playstores pending apps (only Fleksy was pending) and the "force touch" feature of the phones seems to have completely stopped working, no matter what setting I turned on or off it didn't work...
Anyone has a clue as to what can cause this?
General notes:
1. Using stock Exynos unlocked variant
2. I am using package disabler (which btw didn't improve much my battery life, but that might be just me using the phone too much ) so maybe one of the packages decided that it depends on a disabled one?
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
RazoE said:
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
Click to expand...
Click to collapse
Mine also stop working after I restart my S8 Plus, it will again work if I wait around 20 minutes. Is this software or hardware problem? Any solutions?
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Ady1976 said:
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Click to expand...
Click to collapse
How does it act up on your part? Mine would just stop working if I restart the phone & I should wait sometimes hours before it would work again.
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Ady1976 said:
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Click to expand...
Click to collapse
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
bladefrost said:
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
Click to expand...
Click to collapse
Unless your phone is unlocked no pins etc the phone will just go to the lockscreen, it's a useless feature, most people have the phones locked and thus it's a complete waste of time, it sounds to me the capacitive home button part of the screen was an afterthought because they couldn't install the fingerprint reader under the screen, just had a software update yesterday and still can't turn it off, basic stuff Samsung should enable an ON/OFF toggle switch for this.
Had the same problem with my S8 Plus India Variant(SM-G955 FD), I got my screen replaced from service center, Device was not rooted back then, so was under warranty.
But it is an hardware issue, as since then it has never gone off.
I mean when I press the home button hard it doesn't wake the phone up & no vibration. It happens when I restart the device then it would stop working for few minutes to a few hours sometimes, then it would start working again normally until I restart the phone again. I think this is just a software issue.
My z-flip3 5g has a strange problem. If i close it (by folding the screen closed), then after opening (unfolding) the screen and touching the right side button/fingerprint reader to unlock it, i hear the quiet "click" noise that indicates the phone is unlocked, but the screen stays black. i then have to repeatedly push the lock button on the right to lock the phone again and unlock it again. after several attempts the screen finally turns on. sometimes it will go black a few seconds later and the same issue continues. but other times the screen will stay on and work fine.
i have noticed that if i do not close the phone (folding the screen together) then i do NOT encounter this issue. the phone screen turns on when pushing the right side button (or touching the fingerprint sensor) and everything works fine.
this issue started yesterday, a system update installed yesterday as well, could it be related?
i already restarted many times, booted into recovery mode and wiped the cache. nothing has helped. the only way to avoid the problem is by not closing (folding the screen shut) the phone.
One UI v 5.1
Android 13
Security patch level Feb 1, 2023
fully stock/not rooted
I have same behavior. Did you solve this problem?
Unfortunately no. Did a factory reset, hoping that would help, but the issue persists
Mine has recently started doing the same. Last update was right before this started several weeks ago. I don't have mine set to require fingerprint, it should just turn on after opening. If I open it partway, it will turn on, then turn back off when fully opened.
hi,
i have same problem, it's software problem?
Not completely sure about that. They update this thing so often, it could be coincedence that it started shortly after an update. I want to try blowing out the hinges as I've got some dust under there that I hear when opening the phone. Definitely not a phone to put in your pocket after working in the wood shop!
Digital Dragon said:
Not completely sure about that. They update this thing so often, it could be coincedence that it started shortly after an update. I want to try blowing out the hinges as I've got some dust under there that I hear when opening the phone. Definitely not a phone to put in your pocket after working in the wood shop!
Click to expand...
Click to collapse
and don´t take it to the beach either!
What is also strange is that when I close the phone and open it a few seconds later, there is no issues whatsoever. However, if I leave it closed a few minutes, then when opening it, the problems with the screen staying off happen.
Yes, definitely don't take it to the beach!
@netridah , mine is doing exactly that. Which makes me wonder is it a wake issue, or a mechanical/sensor issue with the hinge.
one more to the bill
I checked the flexes and I warmed up the logic nothing works
I have the same issue: Flip 3 - 5G with OneUI 5.1 - 1 April Patch level
When I open the phone I eventually see for less than one second the lock screen, the goes black and unresponsive.
Then I have to press the button to turn the screen off (even if it is already) and then re-press the button or use the fingerprint to turn it on and it will work (eventually, sometime I have to do it a couple of times).
I already googled it on many forums but no solutions, I've tried to:
Disable the always-on display - no result, at first looked like it did the trick but the day after was having the same issue.
Check all the updates of the system components like always on-on display (settings --> lock screen --> always on display --> info), no help everything is up to date.
Hi,
I have the exact same problem, only difference is that I'm on the z flip 4.
I get the black screen and sometimes when opening or closing the phone the screen can flash in a bright yellow or green color.
I got a motherboard but the problem continued
Next step changing screen is very expensive at the moment
This is driving me crazy - also started the day I updated to OneUI 5.1.
Hoping for a solution soon!
I am also encountering this problem, I went to samsung repair shop 1 month out of warranty, sales person said it is a screen issue and needs to be replaced for 430$. Mine was before the update, i took mine near the pool, got wet maybe, as the alarm for usb charging mentioned unplug it immediately, day after it began randomly dark when phone is openned fully. Zflip 3
Oh just an update, i did some tinkering today, Good lock all updated, disabled clockface, sprayed some contact cleaner on power button, and hinges, fold close and open for a minute or two, fell asleep for 1 hour, and when I woke up, my screen works back to normal, it wakes up when unfolded, no more waiting or hitting the power button several times. hope this stays like this.
piper_indebt said:
Oh just an update, i did some tinkering today, Good lock all updated, disabled clockface, sprayed some contact cleaner on power button, and hinges, fold close and open for a minute or two, fell asleep for 1 hour, and when I woke up, my screen works back to normal, it wakes up when unfolded, no more waiting or hitting the power button several times. hope this stays like this.
Click to expand...
Click to collapse
How to disable the clockface? what would that contact cleaner be?
thanks
firstchris said:
How to disable the clockface? what would that contact cleaner be?
thanks
Click to expand...
Click to collapse
Hi, few days now, I still have occasional blacking out, I've tried putting my phone on safe mode, and this seems to solve the problem. I suspect it may not be hardware fault, but 3rd party software, "good lock" or something else that conflicts wit one ui, that makes the flipping open lag waking up. Contact cleaner used for electrical stuff
Didnt use my z3 for about a week let the battery drain.. then charged it too 100% without turning on the phone.. my phone back to normal now.. hope it works for you guys
Hello,
I am using Z Flip 4 and last night I started having this problem as well. I can confirm 100% that my phone has no hardware nor a history of impact of any sort that's why it's really frustrating having this kind of problem.
Has anyone already found a resolution for this problem?
Z flip 4 here also. Had the same problem with the screen. Took the phone to Samsung and they changed the screen, frame and back panel's for free under warranty.
They said it's a hardware issue.
So better to take the phone to Samsung.