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.
Related
This is kind of a last resort - to see if anyone has any experience with this problem. I have Googled around for similar problems and haven't quite found the same issue anywhere.
OK, so let me emphasise, this is not a bootloop - there is clearly some kind of hardware or firmware problem where the phone is interpreting the power button as being pressed.
I can power on, and the phone will get to various points before then rebooting, as though the power button were being held down:
- often it only gets to the splash screen and then reboots
- sometimes I can get it into recovery, but whatever option I happen to highlight (I have about a second or two to do so) just gets selected as though the power button were pressed
- sometimes the phone will even boot and can be used for a little while (enough even for me to back up the files off it), but sooner or later a message will pop up saying something along the lines of "Continue holding power button to reset", again - OBVIOUSLY the system thinks the power button is pressed down.
The problem happened while the phone was under guarantee, the repair place kept it for weeks, eventually "replaced the motherboard" (so they say) and it seemed to work for a time. Now the problem is back and there is no more warranty. A reputable repair place has had a look and said they can't do anything.
I have tried taking the top cover off and fiddling with the microswitch (only thing I could think of) to see if there is anything obvious going on there, but that doesn't seem to be the cause of the problem.
Any ideas, before we ditch the phone as a $XXX loss?
Just to update - I managed to catch the phone when it wasn't going crazy, go into fastboot and flash CM10.2. Could've restored to stock I suppose, but I am concerned that may somehow have been the cause of the problem in the first place.
As of 12 hours later the phone is behaving itself. Can't be sure a new ROM is what did it, but fingers crossed...
Having been on the same version of CM Marshmallow and making no changes to my phone's software/hardware for a few weeks (except for regularly updating apps), my hardware buttons have all of a sudden stopped working. (I have no way to change volume or turn the screen on/off with the hardware buttons)
They also do not work in TWRP. Having factory reset the phone (using the latest official factory reset .tar.gz) , they don't work on stock android 6.01 and updating to the latest CM with open gapps they are still broken.
They do however ALWAYS work to hold down power and volume down for fastboot (even when not working for volume/screen on) and always work fine whilst in fastboot (for scrolling the menu and selecting options, but do not recovery, eg. TWRP)
Any ideas on what may be causing this much appreciated thanks :good:
TLDR: Hardware buttons only work for turning phone on when powered off, rebooting into fastboot, and for using fastboot (so its unlikely that this is a hardware issue, but not impossible). They don't work with any AOSP/CM/TWRP software, and I don't know why...
EDIT: Although not really a work around, I can at least turn off the screen using Cyanogenmod's double tap status bar, and turn on the screen with this app for the light sensor: https://play.google.com/store/apps/details?id=com.wolandsoft.wtn Still no idea how to control the volume though, except for toggling ''do not disturb``
EDIT 2: No fix booting into safemode. Also, the USB connection for charging/data transfer temporarily broke until I rebooted the phone, and I suspect that this may be related
try cleaning with paper towel you wet with alcohol, fixed my mom's iPhone that way.
spacecaptain said:
try cleaning with paper towel you wet with alcohol, fixed my mom's iPhone that way.
Click to expand...
Click to collapse
Cheers, I have cleaned with an air can and a glasses cleaning cloth on all surfaces accessible for following a replace your battery tutorial and this has so far fixed all issues that I was having.
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.
Hi guys!
My Pixel 2 turned its back on me yesterday. When I woke up and took my phone to check the notifications, the display wouldn't turn on. I knew the device was working, since the fingerprint reader vibrated, but thought that either it's the BSOD I've been reading about on the internet, or the screen went bust totally. It seems neither is the case.
After some tinkering I know for sure that:
1) the device itself is fully working - software works, calls can be made, assistant works, it's fully accessible with adb, it responds to all input, charges normally
2) the touch input works just fine, I can blindly use the phone, but cannot see anything on screen at all
3) the screen does not work anywhere, not only when the system is booted up - forced reboot (power + volume down), reboot to recovery mode with adb, charging with phone powered down - everything works, but display won't ever turn on
4) it's not an issue with proximity sensor - using adb I was able to check that proximity sensor works just fine during calls, and normally returns a non-active state. Also, the screen is theoretically either on or off, depending on device state, but with no visual difference
Everything drives me to think it's a hardware failure (though I've seen failing touch or failing display+touch, haven't seen failing display with working touch yet) and I've already filled na RMA and I'm sending the device back for warranty.
The whole thing was so sudden and not expected though I thought I'd share and ask if anyone had experienced something similar? Is my reasoning that it's a hardware error valid, or maybe I'm missing something and there's something more I can try?
Cheers!
M.