Hi all,
I have a really strange problem with my Note 8T.
No matter what sleep timer I set it at, it stays awake and I have to manually turn it off.
When I press power, double-tap to wake and it goes to the lock screen it turns the screen off as per usual (few seconds).
But if I leave it on the launcher or the settings page for the lock screen etc, it doesn't turn off.
I have never had this problem before with phones or tablets (some of them really cheap ones).
I can set it to 15 secs, 1 minute, etc, but no, it still stays on.
I've gone into Developer settings and made sure the keep screen on while charging (though this isn't the problem) was off!
I've factory reset 3 times (and I've only had it a week).
I contacted the seller (through Amazon UK) and am really considering returning it (which I don't really want to do)!
I'm assuming it's a problem with the screen, but I wanted to see if anyone else has had this problem and if there was a solution!
I really like this phone, it can be sluggish sometimes but I can live with that.
The screen not going off though, not only is that a screen and battery problem, but a security issue too.
Any help or advice would be greatly appreciated.
All the best in these trying times!
I suppose you could try reinstalling your ROM first and/or try to check if autolock works without installing any additional applications. If reinstalling helped, then it was a potential ROM bug. If autolock works without any additional apps installed, then some application might be working permanently in the background and disallowing autolock. If all that didn't help, you might want to get a replacement then I suppose..?
Sent from my Redmi Note 8T using XDA Labs
Related
Hi everyone,
I have been having a very annoying problem with my Galaxy Nexus during the past few days. When it enters to sleep mode (after 15 seconds without activity or when I push the power button) it wakes up itself again after 2 to 10 seconds and does not stay into sleep mode: the lock screen is displayed during 15 seconds before a new sleep mode/'wake up state' loop starts again.
It doesn't happen all the time but it does often enough to waste around 8% of battery every hour without me touching my phone.
I searched the forum for solutions and found in other threads that an application could be the source of the problem. I uninstalled every apps but the problem remained. I did a factory reset without installing any app or update after but the problem also remained. I also tried using only Wi-Fi or only 3G for data or switching to flight mode, but it didn't change anything.
Other solutions suggested on other threads, to disable GPS. It did it too, without more success.
I noticed that the problem only occurs when the phone is unplugged. It never happens during loading.
Have you any ideas that could help me to solve the problem?
Thanks a lot in advance,
Julien
Don't know if it helps but I made some screenshoot of BetterBattery Stats results.
Galaxy Nexus - The 'Waking Up' Problem
I love my Galaxy Nexus (I would like to thank Google for giving them away during the I/O 2012). Jelly Bean (the last version of Android) is simply a blast: it is smoother, snappier, sexier, you name it.
As much as I love JB, I still need to play with my devices, and what a better way to play with an Android phone than to root it. After testing a few ROMs, I ended up using Codename Android in combination with Lean Kernel. I advise you guys to have a look at it, it packages an insane number of customization and parameters that will make your phone even better!
The drawback when you hack around with your phone, is that your start feeling guilty when it starts doing random stuff, such as waking up randomly : I would put it in sleep mode (using the power button), and a few seconds (minutes if I happened to be lucky), the phone would wake up on its own, sometimes indicating it was charging when obviously no cable was plugged…
From there started the usual bug chase that many of us know: backup, factory reset, and a complete reinstallation. Unfortunately, in that particular case it would not change a thing and the problem was occuring even more often. It was becoming obvious that my problem came from the hardware…
The usb connector at the bottom of the Galaxy Nexus has a bad habit of bending downward after some time (it varies, depending of your usage). The solution is thus to take a small knife and pushing it upward so it does not touch the bottom metallic plate. Et voila! Your phone will stop waking up by itself, and your frustration will go away with it.
I guess if a lesson can be learned from that experience, it is that the obvious answer is not often the right one; you should also keep a small knife not too far from your Galaxy Nexus.
It´s work fine to me...
Hi guys
looking for some advice here please as this is slowly driving me crazy.
Bought a tab s 8.4 about a week ago, along with the folio cover.
When I either close the cover or press the power button to put into sleep mode, it'll wake up providing I either open the cover or press power button within about 8 seconds. Anything longer than this and it requires a soft reset to get it to turn back on. From reading this sounds like the sleep of death. I've looked around for solutions to this, installed an app to stop it entering deep sleep but this didn't work, granted I may have the settings wrong on the app but I had it waking up the device every 9 seconds which is the lowest setting, and this still didn't prevent it having to be reset.
Thought it may have been due to apps I'm installing but now done 2 hard resets back to factory conditions, then not connected to the WiFi so it doesn't download my associated apps, and it's still getting the Sleep of death.
As I see it at the moment it's going into the sleep of death straight from factory settings. FYI is does the same with out the case on also.
Any advice, comments or potential apps that's may help would be appreciated as at the moment it's pretty much unusable and will soon to be flying out of the window.
Thanks guys
Kieran
I would suggest going for a ROM update. Either from another country. Or some custom one.
I would update/reinstall the firmware or try a different kernel. This sort of problem usually points to the kernel synaptics touch driver. Maybe you have a kernel problem.
Thanks guys I'll give that a go
Dear Friends,
After updating my htc one m8 to Android 5.0.2 and resetting the phone as needed, i am facing the problem of switching off the screen randomly while i am using it. can anyone help me.
appreciate the support.
thnx
hogrsq said:
Dear Friends,
After updating my htc one m8 to Android 5.0.2 and resetting the phone as needed, i am facing the problem of switching off the screen randomly while i am using it. can anyone help me.
appreciate the support.
thnx
Click to expand...
Click to collapse
Have you checked the screen timeout settings in settings/display & gestures? That's the most likely possibility.
It's not a timeout problem for me.
My timeout settings are at one minute or more and the screen will blank on me in the middle of active use. If I tap the power button repeatedly (the number of times required varies, but it takes fewer if the taps are spaced by a second or so), the screen will come back on, but more often than not, the screen will black again immediately (i.e. in the middle of the unlock process). The screen blacks, but remains responsive to touch. If I tap where a button was before pressing the power button, when I can see again, the app (or launcher screen) has changed accordingly. The problem has gotten more frequent, to the point that my phone is almost unusable as of yesterday afternoon.
I have tried a factory reset as of this morning, which didn't remove the problem. My battery seems to be OK. I'm still getting roughly the same battery life I've always had. I'm stuck, and I'm not finding abundant references to it anywhere, so any help would be appreciated.
A brief history of my interaction with this problem: I bought the phone used about 3 months ago. about 3 weeks in, the blanking problem started to appear, but only in landscape mode apps (games). This was not frequent until about a month ago, when it started becoming more frequent and affecting everyday activity, not just games. About 3 weeks ago, I started having problems with image persistence (which may not be relevant, but I'm not sure either way). Yesterday afternoon it started blanking repeatedly. Restarting the phone had helped in the past, but not this time. Leaving the phone shut down for 2-3 hours also failed.
I am getting very frustrated, and I really like this phone.
Please help, if anyone can.
Thanks very much.
Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc
I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).
Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.
still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.
Joined beta N program, hopefully this issue is resolved on the Pixel C.
New RN8T eea stable locked bootloader. One day it worked cool and then it began. First problem screen never goes off, it works all the time and doesn't want to lock, despite the fact that in the settings sleep is activated after 15 or 30 seconds, no matter what. Strangely enough, the problem disappears in airplane mode, unfortunately it returns after turning it off. The second problem concerns the youtube application, the control panel like pause or time shift does not disappear automatically, it also turns on by itself at random moments. Again, the problem disappears in airplane mode, but returns after turning it off. Factory reset has already been done twice. I encountered a similar problem with youtube earlier on the Internet and apparently it helped disable or kill accessibility, unfortunately it did not help, even removal by adb did nothing. Alternatives like Vanced or OGYoutube work even worse because the control panel never disappears. I thought that both problems may be related to ghost touch, but after a short test nothing like this occurs. I was thinking about unlocking the bootloader and throwing a custom to check if these problems are also there, but once it's a friend's smartphone, two before I get permission to unlock it, it will be a week. In the end it will probably be done, but by then maybe someone will find some magic solution?