Over the last couple weeks, I sometimes had the problem, that the S7 would just reboot randomly, sometimes multiple times in a row, after freezing for a few seconds first. It seemed to get better when I switched it off for some time and let it rest before rebooting.
Now yesterday it started crashing and rebooting again. But it would only go up until the lock screen, while being quite laggy. Sometimes I could swipe away notifications before it crashed, sometimes not even that. When I typed in the password, it crashed at the latest. Then, later, it would barely show the lock screen before crashing, only scaling up the brightness in steps, again very laggy.
Today, I can't even get the phone to the lock screen. After the Samsung and Galaxy S7 logos, the screen would go black (also, when the Samsung logo starts appearing for the first time in this drawing motion, it only draws a little party of the first "s" before freezing for some time). If I touch the home button (and sometimes the power button), the soft buttons would light up (but only once, if they go dark and I press again, nothing happens). But no lock/ start screen whatsoever.
What I tried so far: hard reboot, wipe cache partition, factory reset, both combined. Tried flashing TWRP to get some more options, but it doesn't let me due to this fap lock.
Also, I can only get into recovery mode by pressing power + down + home, then in download mode selecting the restart option, and then applying power + up + home.
Had anyone had this problem before, or any tips what else I could try?
Flash stock with ODIN 3.12.3 or newer?
I will try flashing 6.1 or 7.0 and report back whether it worked.
It didn't work. Though now, sometimes, when tapping the screen it seems to recognize button presses. Also, the voice assistant keeps randomly bursting phrases.
IQHU said:
It didn't work. Though now, sometimes, when tapping the screen it seems to recognize button presses. Also, the voice assistant keeps randomly bursting phrases.
Click to expand...
Click to collapse
If flashing a new firmware with ODIN doesn't cure the problem then it's most likely a hardware problem.
Dammit. Since the back has a crack, I doubt they'd repair it... Thanks anyways!
IQHU said:
Dammit. Since the back has a crack, I doubt they'd repair it... Thanks anyways!
Click to expand...
Click to collapse
Yep unfortunately it sounds like a hardware problem, did you use CSC with the other 3 firmware files?
CSC = Factory reset after flashing (Use this one)
HOME_CSC = No reset
You could try checking the "Repartition" box in ODIN options tab to ensure a clean flash
Make sure you use ODIN 3.12.3 or newer too
---------- Post added at 09:37 ---------- Previous post was at 09:34 ----------
IQHU said:
It didn't work. Though now, sometimes, when tapping the screen it seems to recognize button presses. Also, the voice assistant keeps randomly bursting phrases.
Click to expand...
Click to collapse
Voice assistant is not enabled by default, which sounds like something is pressing either the screen or buttons to activate the setting
Which could also be a reason why nothing else responds properly, imaging holding your finger on the screen, then using your other hand to try and use the phone
Possible the digitizer (touch panel) across the screen is damaged, or possible that a button(s) are damaged and permanently pressed in
Related
My TF has done this three times now since yesterday's FOTA. The device hasn't crashed as I can still use ADB and the notification bar relects the true battery status, time etc. I can also turn the screen on and off with the power button but I can't unlock it due to the screen not accepting touch input.
This happens regardless if use a custom rom or not.
Has anyone else had this experience?
Roach2010 said:
My TF has done this three times now since yesterday's FOTA. The device hasn't crashed as I can still use ADB and the notification bar relects the true battery status, time etc. I can also turn the screen on and off with the power button but I can't unlock it due to the screen not accepting touch input.
This happens regardless if use a custom rom or not.
Has anyone else had this experience?
Click to expand...
Click to collapse
My device had this issue, but with the 3/25(?) firmware (it came from overseas -- Taiwan). I basically thought I had a brick, but yesterday I used not-quite-pristine US system.img via a nandroid backup, and it brought it back to life. Still working, 18 hours later (and with the latest OTA update).
If you still have cwm / nandroid access, PM me and I'll post up the system.img that I used to fix my issue, yesterday. It was basically an image I found on Android Central, and I yaff2'd it and added my own md5sum so that nandroid could recognize it. My ongoing concern is that the permissions could be all screwy and softlinks could be broken. But, given the choice of that versus a bricked tablet, I could live with broken softlinks.
mine has done it 3 time while playing fruit ninja but only while playing that and not whit normal use as browsing and all that
Fisken said:
mine has done it 3 time while playing fruit ninja but only while playing that and not whit normal use as browsing and all that
Click to expand...
Click to collapse
Same here. Touchscreen stopped responding while playing that game, but that happened even before the OTA.
How can you get it to start responding again or force a reboot? I just got mine in the mail, pushed the lock button, and now it won't respond to any of my touches. Stuck at the lock screen.
jonnyktyler said:
How can you get it to start responding again or force a reboot? I just got mine in the mail, pushed the lock button, and now it won't respond to any of my touches. Stuck at the lock screen.
Click to expand...
Click to collapse
Hold the power button for 10-12 seconds to force power it off. Release button. Wait a couple seconds. Power on as normal (a 5-6 second hold down of the power button). If still no joy... you're screwed perhaps.
ok thanks a lot holding the power button down for a long time did force it to turn off, now it's working again.
Hello! I have a stock Android Lollipop 5.0.1 Nexus 5 and for the past week or so I have been experiencing a weird issue.
The device randomly crashes. By "crashes" I mean the screen goes black, but the backlight is still on (it's a lighted black). I can push the power button and it will turn completely black (locked) and if I push it once more it turns lighted black again.
To get the device back into usable state I have to keep the power button pressed until the phone resets. Sometimes I keep it pushed for a full minute and nothing happens, sometimes 10 seconds are enough. Sometimes it will go through the "Google" logo and then stay in the lighted black state until I finally manage to reboot it again. Sometimes it crashes again right after it boots up.
It's weird because a lot of the times it's ok throughout the day and then when I go out in the evening, I take it out of the pocket and I see it crashed. Sometimes it crashes while I actually use it.
Last night it started doing something else: instead of lighted black, the screen is filled with static noise. It doesn't move or anything, it's a still image. Today, when a crash like that occurred, the screen glitched first (random lines on the screen, some parts got moved, really weird). I will get some photos if it happens again.
The problem is that I can't identify what's causing it. There is no particular app or action that I do / use that triggers this. It also doesn't seem to be movement-based, as it sometimes happens while it's sitting still on a table.
I updated to 5.0.1 about a day before this started happening, but I'm still not sure if it's software or hardware-based.
I tried a factory reset and booting into safe mode, none of these helped. I will only consider flashing a custom ROM as a final resort, because I'm not sure if it voids the warranty.
PS: the device is still under warranty, but I'm away for the holidays and will be until the beginning of the next year. And I'd like to have a usable device, especially while I'll be on the road.
Smith_S9 said:
Hello! I have a stock Android Lollipop 5.0.1 Nexus 5 and for the past week or so I have been experiencing a weird issue.
The device randomly crashes. By "crashes" I mean the screen goes black, but the backlight is still on (it's a lighted black). I can push the power button and it will turn completely black (locked) and if I push it once more it turns lighted black again.
To get the device back into usable state I have to keep the power button pressed until the phone resets. Sometimes I keep it pushed for a full minute and nothing happens, sometimes 10 seconds are enough. Sometimes it will go through the "Google" logo and then stay in the lighted black state until I finally manage to reboot it again. Sometimes it crashes again right after it boots up.
It's weird because a lot of the times it's ok throughout the day and then when I go out in the evening, I take it out of the pocket and I see it crashed. Sometimes it crashes while I actually use it.
Last night it started doing something else: instead of lighted black, the screen is filled with static noise. It doesn't move or anything, it's a still image. Today, when a crash like that occurred, the screen glitched first (random lines on the screen, some parts got moved, really weird). I will get some photos if it happens again.
The problem is that I can't identify what's causing it. There is no particular app or action that I do / use that triggers this. It also doesn't seem to be movement-based, as it sometimes happens while it's sitting still on a table.
I updated to 5.0.1 about a day before this started happening, but I'm still not sure if it's software or hardware-based.
I tried a factory reset and booting into safe mode, none of these helped. I will only consider flashing a custom ROM as a final resort, because I'm not sure if it voids the warranty.
PS: the device is still under warranty, but I'm away for the holidays and will be until the beginning of the next year. And I'd like to have a usable device, especially while I'll be on the road.
Click to expand...
Click to collapse
I have none of your issues, try booting the device in safe mode and see if the problems still occure. It must be a or multiple downloaded apps that are causing your issues. Or try a data factory reset and restore/download your apps one by one amd try to identify the culpritt.
gee2012 said:
I have none of your issues, try booting the device in safe mode and see if the problems still occure. It must be a or multiple downloaded apps that are causing your issues. Or try a data factory reset and restore/download your apps one by one amd try to identify the culpritt.
Click to expand...
Click to collapse
I said in the post that I tried both of those things. The crash occurred seconds after booting in safe mode and factory reset did not help either.
Smith_S9 said:
I said in the post that I tried both of those things. The crash occurred seconds after booting in safe mode and factory reset did not help either.
Click to expand...
Click to collapse
Flashing the 5.0.1 factory image in fastboot should fix your issues. Or try flashing system.img first, maybe thats enough.
Same issues with my Nexus 5
gee2012 said:
Flashing the 5.0.1 factory image in fastboot should fix your issues. Or try flashing system.img first, maybe thats enough.
Click to expand...
Click to collapse
I am experiencing SAME exactly issues in my N5 with 5.01 and 5.1 . EXACTLY... you are not alone
Seems a software problem (third party app ?) , started in 5.01 and now is in 5.1 , of course system and boot images where flashed with fastboot, so no solution using
Stock, Rooted, using Nova Launcher - Smartwatch 2 - Google Cardboard - Chromecast and many apps.
But started ..if memory helps .. after installing Cardboard 3D apps.
reimer1 said:
I am experiencing SAME exactly issues in my N5 with 5.01 and 5.1 . EXACTLY... you are not alone
Seems a software problem (third party app ?) , started in 5.01 and now is in 5.1 , of course system and boot images where flashed with fastboot, so no solution using
Stock, Rooted, using Nova Launcher - Smartwatch 2 - Google Cardboard - Chromecast and many apps.
But started ..if memory helps .. after installing Cardboard 3D apps.
Click to expand...
Click to collapse
My phone had an issue with the screen. I went to the LG service and they replaced the screen entirely, so that's that.
again and again...
i'm in the same case... I don't have any clues or solutions, i'm just wainting like a dumb... I don't know what to do, i always have to make the thing with the power button and the lower sound button to make it show the boot screen, but it glitch after few seconds... PLS HALP
I factory reset my phone and during the process of signing in, agreeing to T&C's etc, a strange problem started occurring - the touchscreen became super unresponsive (had to press something three of five times for it to respond), however, at the same time, the phone would quickly vibrate on touch multiple times, but again, not actually do anything. Moreover, a weird blue text box started appearing around the options I touched and I can't swipe down to access the normal settings menu.
And to top it all off, if I long hold the power button to force restart/power off, it just won't do it. (tried the old "turn it off and on" trick to see it'll do the trick)
Everything was all normal until this point, had my phone for a couple of months, haven't dropped it or anything. Does anyone know why this is happening, and if so, how to fix this?
Thanks so much in advance!
shnk said:
I factory reset my phone and during the process of signing in, agreeing to T&C's etc, a strange problem started occurring - the touchscreen became super unresponsive (had to press something three of five times for it to respond), however, at the same time, the phone would quickly vibrate on touch multiple times, but again, not actually do anything. Moreover, a weird blue text box started appearing around the options I touched and I can't swipe down to access the normal settings menu.
And to top it all off, if I long hold the power button to force restart/power off, it just won't do it. (tried the old "turn it off and on" trick to see it'll do the trick)
Everything was all normal until this point, had my phone for a couple of months, haven't dropped it or anything. Does anyone know why this is happening, and if so, how to fix this?
Thanks so much in advance!
Click to expand...
Click to collapse
In fact, I can't swipe at all ... in the app drawer if I swipe, it just goes to the next app , instead of the next screen.
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.