I have looked through this forum, in the QandA and have not seen anyone post this problem. Is anyone experiencing the issue where your screen wont auto turn off? I have changed display timeout to 30 seconds, 1minute, 2 minutes, 5 minutes and so on... display wont turn off on its own. Also, when charging, if a notification comes up, screen awakes, but wont shut off again. Just curious if other users are having a similar issue or if I am the only one. I know this was a problem for S3 owners, but there was no real problem identifying what was causing it. Any help would be appreciated.
Set up as follows:
Stock JB Build
Rooted
Stock Kernel
(Only Titanium app data {not system} restored)
Almost all syncing data set to 1 hour refresh or greater
Smart Stay is turned off
Pattern Lock enabled
I think that covers most bases and options, but if I am missing something, I would love to know.
jdmadonna said:
I have looked through this forum, in the QandA and have not seen anyone post this problem. Is anyone experiencing the issue where your screen wont auto turn off? I have changed display timeout to 30 seconds, 1minute, 2 minutes, 5 minutes and so on... display wont turn off on its own. Also, when charging, if a notification comes up, screen awakes, but wont shut off again. Just curious if other users are having a similar issue or if I am the only one. I know this was a problem for S3 owners, but there was no real problem identifying what was causing it. Any help would be appreciated.
Set up as follows:
Stock JB Build
Rooted
Stock Kernel
(Only Titanium app data {not system} restored)
Almost all syncing data set to 1 hour refresh or greater
Smart Stay is turned off
Pattern Lock enabled
I think that covers most bases and options, but if I am missing something, I would love to know.
Click to expand...
Click to collapse
settings>developer options>Stay awake
Interesting thing though, i turn off stay awake, and it snaps back on at random. don't know why.
crazy talk said:
settings>developer options>Stay awake
Interesting thing though, i turn off stay awake, and it snaps back on at random. don't know why.
Click to expand...
Click to collapse
Thank you for your input. However, I had checked that option, it was not on to begin with, I turned it on, and then off again, it did not reenable itself, but it still is not the culprit. I am baffled right now.
jdmadonna said:
I have looked through this forum, in the QandA and have not seen anyone post this problem. Is anyone experiencing the issue where your screen wont auto turn off? I have changed display timeout to 30 seconds, 1minute, 2 minutes, 5 minutes and so on... display wont turn off on its own. Also, when charging, if a notification comes up, screen awakes, but wont shut off again. Just curious if other users are having a similar issue or if I am the only one. I know this was a problem for S3 owners, but there was no real problem identifying what was causing it. Any help would be appreciated.
Set up as follows:
Stock JB Build
Rooted
Stock Kernel
(Only Titanium app data {not system} restored)
Almost all syncing data set to 1 hour refresh or greater
Smart Stay is turned off
Pattern Lock enabled
I think that covers most bases and options, but if I am missing something, I would love to know.
Click to expand...
Click to collapse
I had this problem too I disabled stay awakenin dev settings, but that didnt fix it. Then I think I found another setting I. Accessories or dock settings and unch3cked something in there....man I just cant remember
Sent from my SGH-T889 using Tapatalk 2
Related
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
nomad4ever said:
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Same thing here, never had an issue with 4.1.2 but now it happens 2-3 times a day
Sent from my Galaxy Nexus using xda premium
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
andQlimax said:
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
Click to expand...
Click to collapse
Let me know how that works... I have been having this problem also. Screen is blank every 2 days it happens once. Ever since 4.2 update. Before that I had no issues like this.
Also un related but I've started to notice faint horizontal lines in my screen. I use auto brightness. Is this normal or return for warranty?
i can confirm this happens to me too.
4.2 stock only rooted with custom recovery.
Same here folks, It may a bug in the 4.2 builds since Sprint did not officially release 4.2 yet.
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
same issue here, I'll try to keep the brightness to manual to see if it works
chanchan305 said:
same issue here, I'll try to keep the brightness to manual to see if it works
Click to expand...
Click to collapse
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
MondoMor said:
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
Click to expand...
Click to collapse
bfprd0 said:
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
Click to expand...
Click to collapse
I experience this issue, but not that frequent. Once every 4 or 5 days, i don't know. I've managed to pull a logcat today as i was near of pc, as posted before, adb/phone is responsive, it even locks the screen normally, there was nothing useful on dmesg. I don't normally use auto-brightness, but enabled it a little while ago, although now i'm not sure if it was enabled the first time it happened. This last time, it wasn't enabled, that I'm sure.
It happened to me both when I was using XDA-app. I have almost 0 user apps installed right now, also uninstalled XDA. Reporting back in a few.
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
ogdobber said:
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
Click to expand...
Click to collapse
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
bk201doesntexist said:
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
Click to expand...
Click to collapse
ok...star this issue https://code.google.com/p/android/issues/detail?id=40019
Is anyone else having a issue where NFC turns off on its own at random times? I'll try to S-beam with my girlfriend's S3 and impress friends only to find out that it previously turned off without me doing it. I use the Power Toggles app (link: https://play.google.com/store/apps/...t=W251bGwsMSwxLDIxMiwiY29tLnBhaW5sZXNzLnBjIl0.) and think that MAYBE this is causing the issue, but I'm not 100% sure
dundada08 said:
Is anyone else having a issue where NFC turns off on its own at random times? I'll try to S-beam with my girlfriend's S3 and impress friends only to find out that it previously turned off without me doing it. I use the Power Toggles app (link: https://play.google.com/store/apps/...t=W251bGwsMSwxLDIxMiwiY29tLnBhaW5sZXNzLnBjIl0.) and think that MAYBE this is causing the issue, but I'm not 100% sure
Click to expand...
Click to collapse
Yes, you're not the only one. I'm on stock and not using that app but I'm still getting nfc off randomly. I don't use s beam often, so I just have a tasker profile that turns nfc on every few minutes, but it would be nice to know what's going on so I wouldn't have to. There's no pattern, it can stay running fine through reboots, and over the course of days, but then will turn off randomly multiple times in an hour.
I have a Galaxy S5, and my NFC also turns off randomly.
I installed mmuzzy 4.2.1 ROM on my phone and have been quite happy with it. The only problem I have is that the screen dims after about 30 seconds and I can't find a brightness setting that will allow me to disable this feature. Does anyone have a way to turn this off?
apastuszak said:
I installed mmuzzy 4.2.1 ROM on my phone and have been quite happy with it. The only problem I have is that the screen dims after about 30 seconds and I can't find a brightness setting that will allow me to disable this feature. Does anyone have a way to turn this off?
Click to expand...
Click to collapse
settings -> display -> sleep (not sure if that is what you want as you've probably seen it). I don't think there is a setting to stop it from dimming before turning off. Increasing the time to off keeps it from dimming as soon.
Sorry, not good enough
mwalt2 said:
settings -> display -> sleep (not sure if that is what you want as you've probably seen it). I don't think there is a setting to stop it from dimming before turning off. Increasing the time to off keeps it from dimming as soon.
Click to expand...
Click to collapse
I want the dimming off completely.
I turned the developer options on and told to leave the screen on when charging. But it still dims. Once it dims, it's impossible to see the screen while in the car. 4.1 never dimmed. I may go back to the 4.1, since this seriously impacts my ability to use the phone in my car.
apastuszak said:
I want the dimming off completely.
I turned the developer options on and told to leave the screen on when charging. But it still dims. Once it dims, it's impossible to see the screen while in the car. 4.1 never dimmed. I may go back to the 4.1, since this seriously impacts my ability to use the phone in my car.
Click to expand...
Click to collapse
You might be able to set up a tasker profile to keep the screen on in the car. I've done that in the past for use in the car. I would guess that this feature is at the kernel level, so you could try a different kernel.
Sent from my Galaxy Nexus using xda premium
mwalt2 said:
You might be able to set up a tasker profile to keep the screen on in the car. I've done that in the past for use in the car. I would guess that this feature is at the kernel level, so you could try a different kernel.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm just rolling back to 4.1. 4.2.1 didn't buy me anything feature-wise.
It seems someone has files a bug for this
http://code.google.com/p/android/is...im&colspec=ID Type Status Owner Summary Stars
If people could please star this issue, I would really appreicate it. I have a Nexus 10 now, and don't have an option to roll back to 4.1 and this is really annoying.
hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?
Install a custom rom like cyanogen or something stock based.
I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.
Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?
Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su
I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.
Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.
No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...
So let me know if you have the same issue... No matter how long I set my screen off time for, it always goes go sleep after 10 seconds!
Don't have that issue here. ATT version
I do not have that issue either (AT&T). Perhaps there is an email account or other "administrator" that requires a short screen timeout? I have seen that before.
seniorstew said:
So let me know if you have the same issue... No matter how long I set my screen off time for, it always goes go sleep after 10 seconds!
Click to expand...
Click to collapse
Are you talking about the main screen or the active display when the actual screen goes off?
seh6183 said:
Are you talking about the main screen or the active display when the actual screen goes off?
Click to expand...
Click to collapse
The main screen. I turned moto display off and it still happens
I ever tried rebooting into safe mode and same problem.. Going to try a factory reset later
My motoz2 is doing this same thing. And it is frustrating. (Verizon). Have you figured out how to fix this?
Do you have adaptive brightness turned on?
Sent from my Moto Z (2) using Tapatalk
So I did a master reset and didn't connect my tumi battery until the play store updated the moto mod app to the newest version.. No more screen issue! I highly recommend anyone who gets this phone, update the app first before you attach any type of mod.