I'm joining the chorus of complains about my Samsung Tab S2 9.7" SM-T810 purchased April 2016. I used it a lot and it still works well, except for a weird problem, which could be due to a recent software update.
Assume the screen turns off, without turning off the device. For example, I just leave the tablet unattended for 2 minutes, which is the timeout period. When I return to the tablet and try to turn the screen on (by pressing Home briefly) the screen won't turn on. In this zombie state, the device is still functional. Pressing Home+Power simultaneously makes the sound expected for a Screendump. Later on, I can recover the image file which shows how the screen should have looked if it was on. A long-press on Home brings up the Google Assistant and I can hear it talking to me.
But I can't turn the screen on for a while, no matter what. As if there was an internal timeout of 1-3 minutes which prevents the screen from turning on. The device probably believes the screen is on, and perhaps does not bother changing its status.
After a minute or two, the tablet eventually responds to the Home button and turns on. Then it works perfectly for hours - unless I allow it to turn off again.
Now I just ordered a new tablet (the P-205) so the old SM-810 will soon go into retirement. Would it make sense to try going back to a prior version of Android ? I have no experience with root on Android, although I "used to be" computer literate in the previous four decades.
Related
Hello all,
I got this phone about a month and a half ago, and since I got it I've noticed a lot of freezing and crashing (more so after the 5.1 update).
Some examples:
-I try unlocking the phone from active display and the screen goes black. The only way to get out of it is to hold the power button to restart.
-Sometimes the phone freezes on the lock screen randomly, and when I pick up the phone to look at it, the time is wrong and I can't physically unlock the phone, only turn the screen on and off, leading to me having to hold the power button down to shut off and restart.
-When on some apps, like twitter for example, the phone freezes, and I cannot do anything except turn off the screen by pressing the power button. When I try waking the phone, it stays black or sometimes theres a flash of the screen I was on before, and then it goes black again. Only thing I can do here is hold the power button down until "Power Off" shows up on the screen, and I press that to shut the phone off.
Today I cleared the cache, and since then the phone has froze once, causing me to do a hard reset. What should I try next? Any idea what the problem could be?
Thank you for the help.
I have pretty much the exact same thing going on. It started last night... I first noticed I had some charging issues where the phone wasn't charging very quickly after the battery died (after a day of heavy use). I let it sit for awhile, then it booted up, and it showed the motorola splash screen. It gets all the way to the lock screen, although I'm unable to unlock the phone. The screen goes dark. It appears to still be getting texts and the like- although this screen blackness issue makes it so I can't unlock the phone. The one thing I can do is hold down the power button and turn it off. I've tried loading fastboot and doing a factory reset, although nothing appears to happen and it boots the same way. The other thing about it is that it appears to be running hot- way hot. Any ideas? I'm running stock rom, Verizon network, just updated to 5.1 when it came out last week.
Hi guys,
This morning when I woke up I jumped update android wear and I've given update (fully charged battery), it has been updated me and after the previous update all applications has shut down and no longer responds.
Neither wrist gestures or touch on the screen, or pressing the button several seconds ...
Not that the screen is left in black, but this off, because I either mobile is connected.
Any remedy?
Regards.
I have the exact same problem. No solution found as of yet.
LeMagDJ said:
Hi guys,
This morning when I woke up I jumped update android wear and I've given update (fully charged battery), it has been updated me and after the previous update all applications has shut down and no longer responds.
Neither wrist gestures or touch on the screen, or pressing the button several seconds ...
Not that the screen is left in black, but this off, because I either mobile is connected.
Any remedy?
Regards.
Click to expand...
Click to collapse
ihave the same problem
I'm just waiting for me to answer the Amazon seller who I bought it. I have sent a request for reimbursement or replacement.
Have you tried to hold down the button for a good while? The watch should produce a long vibrate (keep the button pressed) and then after that should power off.
dunjamon said:
Have you tried to hold down the button for a good while? The watch should produce a long vibrate (keep the button pressed) and then after that should power off.
Click to expand...
Click to collapse
Yes, I have held down more than 30 seconds and does nothing...
Same here. After fiddling with things for a bit, I was able to discover that my watch was actually on, and connected to my phone, and I could see the watch's storage and battery, and even grab a screenshot from the wear app, but the display itself is completely dead after the OTA. Working brilliantly one moment (never any problems with this watch), OTA installs, and BAM, display dead. Digitizer even works, I can press and hold on the display and you feel the vibration that you normally would when selecting a new face.
I should point out that I was completely stock. No root, no third party recovery. The only thing that had been done was developer options had been enabled.
I ended up opening a case with LG and sent it off today for service. But clearly something was broken with this OTA to have this happen to multiple people.
I just spoke with LG SAT and tomorrow will come for him.
He also told me that as I have only one month and seems to be a failure of the clock, they will be responsible for repair or will send me a new one.
Anyway, it seems to me a big failure. I had the watch factory complements and after updating, it was fried.
Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?
Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..
Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.
Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?
Buy a new one. Send yours in as defect. Done.
erase111
I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!
Sorry if this is the wrong place for this. Feel free to point me in the right direction if it needs moved.
Fifth gen Kindle Fire, running Fire OS 5.3.3.0. All current updates, OEM otherwise.
It very often goes into a state where the System & Notification sound bar keeps beeping, like it's constantly trying to turn the volume the entire way up, but the button is not being pressed. The button does not appear to be stuck. When I press the volume down, it'll go down but then go back up on it's own when I let it go.
I've tried a factory reset. If I put it in Do Not Disturb mode, the System & Notifications drop down box still appears at the top of the screen, but it's grayed out.
At the same time, the power button stops functioning properly. It does not lock the screen, but if I hold the button it eventually it will hard shut down the device, and then start in Safe Mode when I power it back up.
Something to note is that it behaves this way often, but not constantly. There are brief periods where it is 100% functional. Just today I turned it on, ran some updates, and all was normal for an hour or so. After that it started with the volume nonsense.
It has barely any use since I purchased it forever ago and was always taken care of, so I don't suspect hardware unless something is defective from the factory. It has done this for as long as I can remember, but it literally saw almost no use for the first year and by the time I noticed it, the warranty was expired.
Any thoughts or suggestions?
SlightlyOpaque said:
Sorry if this is the wrong place for this. Feel free to point me in the right direction if it needs moved.
Fifth gen Kindle Fire, running Fire OS 5.3.3.0. All current updates, OEM otherwise.
It very often goes into a state where the System & Notification sound bar keeps beeping, like it's constantly trying to turn the volume the entire way up, but the button is not being pressed. The button does not appear to be stuck. When I press the volume down, it'll go down but then go back up on it's own when I let it go.
I've tried a factory reset. If I put it in Do Not Disturb mode, the System & Notifications drop down box still appears at the top of the screen, but it's grayed out.
At the same time, the power button stops functioning properly. It does not lock the screen, but if I hold the button it eventually it will hard shut down the device, and then start in Safe Mode when I power it back up.
Something to note is that it behaves this way often, but not constantly. There are brief periods where it is 100% functional. Just today I turned it on, ran some updates, and all was normal for an hour or so. After that it started with the volume nonsense.
It has barely any use since I purchased it forever ago and was always taken care of, so I don't suspect hardware unless something is defective from the factory. It has done this for as long as I can remember, but it literally saw almost no use for the first year and by the time I noticed it, the warranty was expired.
Any thoughts or suggestions?
Click to expand...
Click to collapse
You can try to reload (sideload) FireOS via the stock recovery menu to rule out a software glitch. However, based on symptoms I suspect the board holding the buttons and/or associate ribbon cable is the culprit. Not much you can do about either unless willing to crack open the case.
I wouldn't mind opening it up to replace some things, but I was hoping that based on it working fine for 20 minutes, and then out of nowhere showing problems, that it was software related. I've had it turned off since I posted, fired it back up now, and it's working as it should. I suspect within the hour it'll be back to broken, though.
Edit: Also, as mentioned, the power button stops behaving normally when this happens as well. I haven't looked into the layout of the buttons internally, but I would think that the volume and power buttons would be on separate ribbons leading to separate places?
SlightlyOpaque said:
I wouldn't mind opening it up to replace some things, but I was hoping that based on it working fine for 20 minutes, and then out of nowhere showing problems, that it was software related. I've had it turned off since I posted, fired it back up now, and it's working as it should. I suspect within the hour it'll be back to broken, though.
Edit: Also, as mentioned, the power button stops behaving normally when this happens as well. I haven't looked into the layout of the buttons internally, but I would think that the volume and power buttons would be on separate ribbons leading to separate places?
Click to expand...
Click to collapse
You can view the internals on a self-repair site such as iFixIT or by searching YouTube. The delay prior to acting up suggest heat may play a role. Not necessarily overheating, just the normal warming that electronics emit with use. Good luck.
S21 Ultra, US Factory Unlocked model straight from Samsung. I've had it for a month.
I was in the middle of using it and the screen suddenly went black. It didn’t do any screen off animation or power off animation, it just suddenly turned black.
I know the phone still works because if I hold pwr+vol down I can feel the vibrations as it reboots. I can also use *./adb devices* and it lists the device as connected. It also automatically opens android file transfer when I plug it into my macbook. All these things suggest that the underlying phone works fine.
It’s just that the screen won’t turn on.
What can I do, short of sending it to samsung for a warranty claim?
So I switched to my backup phone, left to take care of some business, and now the s21u is working.............
I'm not sure I can trust it any more. But also, WTF happened?
That's very peculiar... Especially given that you force restarted it with PWB+VOL-UP. I would have expected it to turn the screen on upon restarting.
Maybe back up all your stuff, wipe it and take it to Samsung and see what they would say? Maybe they would find some issue and replace it..
This has happened to me twice since having it since 1/28. Both times I was listening to music. Music stops. Screen goes black....eventually comes back after pressing power button and rebooting. It's almost like Blue Screen of Death behavior
whitehawk66 said:
This has happened to me twice since having it since 1/28. Both times I was listening to music. Music stops. Screen goes black....eventually comes back after pressing power button and rebooting. It's almost like Blue Screen of Death behavior
Click to expand...
Click to collapse
Is your device also a US model? I mean SD888?
This happened to my S10 plus U1 befoce, suddenly blackout (everything still work except screen display) although i used hard restart. Some hours later it become normally. I'm still using it beside S21U U1.
enigmaamit said:
Is your device also a US model? I mean SD888?
Click to expand...
Click to collapse
Model SM-G998U Verizon
i had this issue too in the past with other galaxies - i believe is then it was due to the audio jack - but now it doesnt have one so IDK
finshan said:
S21 Ultra, US Factory Unlocked model straight from Samsung. I've had it for a month.
I was in the middle of using it and the screen suddenly went black. It didn’t do any screen off animation or power off animation, it just suddenly turned black.
I know the phone still works because if I hold pwr+vol down I can feel the vibrations as it reboots. I can also use *./adb devices* and it lists the device as connected. It also automatically opens android file transfer when I plug it into my macbook. All these things suggest that the underlying phone works fine.
It’s just that the screen won’t turn on.
What can I do, short of sending it to samsung for a warranty claim?
Click to expand...
Click to collapse
what's your software version? have you submitted an error report via samsung members app?
I had this same issue on my old S5 where my screen would sometimes go black and still work. As a workaround, I used 'scrcpy' an open-source tool available on Github. I could mirror my phone screen on a PC and control it.