Related
I got my 32GB AT&T Galaxy s4 one week ago today. Had to make an 8 hour road trip to get one but I would say it was very much worth it. I am having this maddening problem where a couple times a day the Display screen timeout keeps re-setting itself to (2 seconds) Unbelievably frustrating considering I can barely get the screen unlocked in 2 seconds and if I blink I have to do it all over again.
But wait, don't walk away just yet, there's more! I have already factory reset 3 stinking times trying to get to the bottom of this and when I woke up this morning it was back to (2 second). Furthermore it shows (2 seconds) in brackets like that so I assumed this was the default value but after checking just now while I was typing this post I noticed after changing it back to my preferred 30 seconds that the 2 second option vanishes. I'll snap a screenshot next time this happens.
Anybody else seen or heard of this problem? I assumed everybodys was doing this until I started searching and found 0 others with the problem. Is my phone The Chosen One?
Yes, i have it also and i found some forums where they discuss same problem, but no solution . Let's think what we have in common..
I have this app called Light Flow, do you?
Also which things you have on?
I have nfc, snart view, smart scroll, air view, air gesture
whatever61 said:
Yes, i have it also and i found some forums where they discuss same problem, but no solution . Let's think what we have in common..
I have this app called Light Flow, do you?
Also which things you have on?
I have nfc, snart view, smart scroll, air view, air gesture
Click to expand...
Click to collapse
Absolutely have Light Flow. I never leave home without it.
NFC. Yes
Smart View. No
Smart Scroll. No
Air View. Yes
Air Gesture. Yes.
I thought for sure it must be Smart Stay malfunctioning but I don't even use that.
maybe it has something to do with Light Flow?? this app caused weird bugs sometimes...
wanna try to turn it off for a while and let me know if it helps?
whatever61 said:
maybe it has something to do with Light Flow?? this app caused weird bugs sometimes...
wanna try to turn it off for a while and let me know if it helps?
Click to expand...
Click to collapse
Worth a shot. I'll play with it and see. Thanks for the idea!
I'm having the same issue and I also use Light Flow - any developments?
Work around
Guys, Did yo get this sorted? I had exactly the same problem which has been driving me mad but managed to sort a workaround which works perfectly. Let me know if this wasn't sorted and I'll post it.
I turned off "Power Saving" mode and it hasn't done it since.
EDIT: Nevermind... just had to give it more time.
Islandguci said:
Guys, Did yo get this sorted? I had exactly the same problem which has been driving me mad but managed to sort a workaround which works perfectly. Let me know if this wasn't sorted and I'll post it.
Click to expand...
Click to collapse
Would you kindly post the workaround? I'm out of ideas at this point.
You all have LightFlow. LightFlow causes other odd issues with Accessibility settings with the S4. Get rid of it and for now use Light Manager. Its much better IMO because it doesn't need to be activated in Accessibility settings, it just works.
Well, I didn't have power saving on and was still getting the problem. I uninstalled light flow and still had the problem. To resolve this for now I use an app called tasker, I had it already because it is a very cool app anyway but once installed if you don't have it just create a rule to deal with the time out issue. My rule for example went like this.
If the time is between 00.01 and 23.59 then set display timeout to 2 minutes. This fixed the problem for me.
In fact you could create other rules to do the same but this does it nicely.
Sent from my GT-I9505 using xda app-developers app
Islandguci said:
Well, I didn't have power saving on and was still getting the problem. I uninstalled light flow and still had the problem. To resolve this for now I use an app called tasker, I had it already because it is a very cool app anyway but once installed if you don't have it just create a rule to deal with the time out issue. My rule for example went like this.
If the time is between 00.01 and 23.59 then set display timeout to 2 minutes. This fixed the problem for me.
In fact you could create other rules to do the same but this does it nicely.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I set my rule to set the display timeout every time the display is turned on. I couldn't make it work the way you did it. I think I need more expertise.
Thanks again.
I haven't seen this issue again since starting this thread. Go figure. I haven't changed anything at all either. Still using lightflow in its entirety just like I was before and never changed anything else that I can recall. Weird.
Ok, I think I have this issue figured out. Here's how I resolved it:
1. Open Light Flow
2. Open Settings
3. Scroll all the way down to the section "Additional LEDs found"
4. Deselect "lcd-backlight control' and exit
I have the same exact problem.. Tried everything but with no luck!! Any one figured it out!??
OutCell said:
I have the same exact problem.. Tried everything but with no luck!! Any one figured it out!??
Click to expand...
Click to collapse
Just to let you guys know, i was able to fix this problem but with a sacrifice.. I reset my phone to factory settings & reinstalled all apps except for Light Flow (The problem did arise after i installed it) and now the screen times out perfectly with the duration i set. :good:
I just hope Light Flow fix this issue soon because i got used to the LED lights indications,, they were very useful.
Solution (I hope)
It's light flow's turn on screen option. They're patching it in the next update, but for now all you have to do is uncheck switch screen on in the notifications.
I tried this tonight. Will post back confirmation from the link
I just registered so I can't post the link to the forum I found it on.
Screen timeout
So I have a Galaxy s4 and started having this same issue with my phone. I would set the timeout for 3 minutes but it would reset back to 0 after so long. I dont have that application you all are talking about. I did root my phone which I do not think matters.
Essentially there are 2 spots to change the screen timeout I found.
My device>Display>Screen timeout
and
My device>Accessibility>Screen timeout (which was set to 0 even though the other was set)
I will let you know if this resolves the screen timeout issue for me.
Thanks
-Jon
goonies83 said:
So I have a Galaxy s4 and started having this same issue with my phone. I would set the timeout for 3 minutes but it would reset back to 0 after so long. I dont have that application you all are talking about. I did root my phone which I do not think matters.
Essentially there are 2 spots to change the screen timeout I found.
My device>Display>Screen timeout
and
My device>Accessibility>Screen timeout (which was set to 0 even though the other was set)
I will let you know if this resolves the screen timeout issue for me.
Thanks
-Jon
Click to expand...
Click to collapse
Disregard....still having the issue.
mharmon said:
I'm having the same issue and I also use Light Flow - any developments?
Click to expand...
Click to collapse
I also was having the same 2 second screen problem and found the unchecking the (turn on screen) to (Switch the screen on for 5 seconds when the notification arrives) in each of the notifications in Light flow has solved my problem. It seems that it was the cause of resetting the screen time out to 2 seconds.
Can someone else try this and confirm that this is the cause???
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Pretty old. Used to happen on my S2 too.
i guess it is an intent that gets activated upon waking of the phone (by turning on the screen)... when you do that, it updates the screen and thats why.
but then again... that is only what i think.. if it should update it while the screen is turned off it would be an active process and use battery
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
malybru said:
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Click to expand...
Click to collapse
Yes it always jump to the correct & exact time....it seems like a battery saving feature...if it is, other people with S4 should also experience it,no?
Tomo1971 said:
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
Click to expand...
Click to collapse
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Xxxdevilxxx said:
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Click to expand...
Click to collapse
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
malybru said:
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
Click to expand...
Click to collapse
oh...will do
New to XDA. Hello all!
I am experiencing this clock lag as well. :/
It doesn't matter if I use a custom lock screen or the Samsung lock screen with "swipe to unlock".
It's easily reproducible, let phone sit for 10-15 min and if you press the unlock button you'll see the wrong time for anywhere from a fraction of a second to a few seconds! and then it will update to correct time. Super annoying if I just want to know the time. Also, I've found that the amount the clock is behind is proportionate to the amount of time the phone as been idle....to a point...
I've seen the clock be over an hour off but it doesn't drift much more than than. Like a few folks mentioned, this should be running in the back ground. What is confusing to me is the clock in the top right is correct, so the phone is monitoring the clock...it's just not updating the lock screen clock.
Hopefully we can find a work around.
Not too keen on a new launcher...at least not until others who have seen that lag switch over and confirm it as a fix...but I don't think it will help, because the lock screen is still a Samsung process not controller by the launcher (i don't think)
Any thoughts?
The clock on the main unlock screen is essentially a widget. As a power saving feature, it only updates as necessary, which would be when you turn your phone on to look at the time. The time at the top of the screen in the notification bar is not a widget, it is a built in process that is always active. That is why it is current and the large clock, "the widget", is off until you turn your phone on to look at it.
My phone does the same thing. As does pretty much everyone's. It is not anything wrong with your phone, it is just the way it is set up. It is usually only delayed by a second or two, at best.
If it is an issue, you can always just remove the widget and use the time at the top of the screen to check. Or try a different app and set the update frequency.
It's not that big of a deal to me, I know it's always off until it refreshes, so I just give it a second to update.
For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
JollyGreen527 said:
For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
Click to expand...
Click to collapse
Dial *#0*# check some test for dimming, sleep etc.
JollyGreen527 said:
For some reason my screen won't shut off when I press the power button or by itself after any amount of time. I made sure all of the settings were set right that might keep it on. I know it's not hardware damage because I've pretty much never dropped it or handled it hard. The power button still works because it will get the turn off, restart, etc screen to go. Any idea how to fix it? I already did a factory reset.
Click to expand...
Click to collapse
Download wakelock detector and see which app is keeping your screen on.
Dialed that number, the dimming worked, but the sleep button didn't do anything. I'll try that app out and see what it says.
In my understanding *#0*# dialing is for hardware check, if sleep is not working from there means it has nothing to do with any app & better to take to service centre.
Sent from my SM-N9005 using XDA Free mobile app
It didn't do it until after I tried to change my boot screen. Know if that would do anything? No boot animations go off besides the galaxy note 3 one (no Tmobile or samsung animation, and no shut off animation). I also rooted it so would they still help me even though the knox counter is 0x1?
Any help? Using the wakelock app it says that system manager application is used a lot more than anything else. Not sure what it does.
JollyGreen527 said:
It didn't do it until after I tried to change my boot screen. Know if that would do anything? No boot animations go off besides the galaxy note 3 one (no Tmobile or samsung animation, and no shut off animation). I also rooted it so would they still help me even though the knox counter is 0x1?
Click to expand...
Click to collapse
Try to flash complete stock ROM & clear Data & Catch before & after flashing from recovery may HELP.
That fixed it. I'm not sure why I didn't already try that since it seems kinda obvious. Don't know what made it do that though. Do you happen to know if modifying the boot animations can mess other things up?
Mine its not rooted still stock and all of the sudden started acting up with the screen ....i did the *# test and when i went to sleep it went straight to the lock screen ...any idea what could cause it
help
JollyGreen527 said:
That fixed it. I'm not sure why I didn't already try that since it seems kinda obvious. Don't know what made it do that though. Do you happen to know if modifying the boot animations can mess other things up?
Click to expand...
Click to collapse
how do you do that cause I'm having same problem s
scooby 777 said:
how do you do that cause I'm having same problem s
Click to expand...
Click to collapse
Mine does this every time I reboot my phone. I have to press and hold the home key, pick the pie chart, pick RAM and pick "Clear Memory". Then it's fine til the next time I reboot.
I had my note 3 with the same problem and solved it recovering the original system/media/bootsamsung*.qmg files.
to solve the problem plug the charger and unplug it immediately and plug it back in again. This is also the reason why the problem is caused. So doing it again will solve the problem.
Well, even when the tap2wake option is turned off sometimes when I unlock the phone I'm all of a sudden in some sub-options menu, or some mini app is running, or the torch is on --> you get the idea.. I mean, has anyone else experienced that?
charliebigpot said:
Well, even when the tap2wake option is turned off sometimes when I unlock the phone I'm all of a sudden in some sub-options menu, or some mini app is running, or the torch is on --> you get the idea.. I mean, has anyone else experienced that?
Click to expand...
Click to collapse
Had that on a previous phone while using a protective foil and/or a case that did not exactly fit the phone. Could that be the problem for you?
sxtester said:
Had that on a previous phone while using a protective foil and/or a case that did not exactly fit the phone. Could that be the problem for you?
Click to expand...
Click to collapse
Thanks for the answer! but I'm not using any foil/case. I'm thinking about using the screen recoding function to see what goes on in my pocket
I have had this a couple of times, only notice when the phone gets hot in my pocket.
I always have tap to wake turned off because it always wakes my phone when it is in my pocket.
I'd love to know if there is a solution to this problem.
Put a lock on the phone, so that way whatever is turning the screen on can't continue and eventually it'll go back to sleep. I had this problem and this is the only solution I've found. Its worth it for the amazing battery life.
Sent from my D5803 using XDA Free mobile app
Anyone else seeing this behavior? On my 995, whenever I restart, or power on my phone.. I have to use the Knock Code to get into my phone, and it says "fingerprints unavailable for use" or something to that effect.
I find this odd behavior.
Its not odd behavior its LG behavior.
Unfortunately there's no way around it.
turn off secure startup in security...
Your fingerprint is encrypted and you phone can't access encrypted data until you unlock it after a reboot. So its kinda a catch 22 where you will always have to unlock with a pin after startup instead of fingerprint. Your fingerprint is biometric data and obviously can't be changed so it needs to more secure on your phone than your pin which you can change. It is this way on most phones with fingerprint readers.
Double0EK said:
Its not odd behavior its LG behavior.
Unfortunately there's no way around it.
Click to expand...
Click to collapse
It's not just LG, my Samsung S7 and Note 7 both required pin code on first log in after a reboot/boot up
It's part of Android now.
nest75068 said:
It's not just LG, my Samsung S7 and Note 7 both required pin code on first log in after a reboot/boot up
It's part of Android now.
Click to expand...
Click to collapse
It's not even Android. My work phone is an iPhone and it has the same behavior. Which drives me nuts because our work phones require us to change pin codes every couple of months and we can't recycle codes.
I turned off secure startup as I don't need kids messing with my phone and I imagine after ten attempts if wipes it?
reaverclan said:
I turned off secure startup as I don't need kids messing with my phone and I imagine after ten attempts if wipes it?
Click to expand...
Click to collapse
30 attempts for secure boot
If I'm right, the op is taking about setting the fingerprint to unlock but it still requires the pattern. You will notice this if you use a third party app or launcher to lock screen. E.g. Nova launcher double tap to lock screen. It will tell you fingerprint is unavailable.
A work around to this is to doubly tap the top part of the screen (the bar where the date and signal strength is).
This will allow you to unlock with fingerprint.
If you use the stock lg launcher then double tapping anywhere on screen shows you to unlock using fingerprint.
koppee1 said:
If I'm right, the op is taking about setting the fingerprint to unlock but it still requires the pattern. You will notice this if you use a third party app or launcher to lock screen. E.g. Nova launcher double tap to lock screen. It will tell you fingerprint is unavailable.
A work around to this is to doubly tap the top part of the screen (the bar where the date and signal strength is).
This will allow you to unlock with fingerprint.
If you use the stock lg launcher then double tapping anywhere on screen shows you to unlock using fingerprint.
Click to expand...
Click to collapse
I'm working with a developer of Screen Lock Pro to try and find a workaround for this. Currently his app will work on Android 5 and 6 by delaying the lock for 5-10 seconds but it's currently not working on Android 7 on LG (it is working on Pixel and Nexus devices).
Hmmm... Not sure I understand this behavior. My fingerprint is much more complex than a 4-digit code that can eventually be brute-forced (phone wipe or not - in theory I mean).. so why wouldn't my fingerprint be the top-most factor in unlocking the phone? I mean.. say I'm one of those guys that uses his last four of an SSN like an idiot, and someone knows that about me.. boom, they're in my phone. Do iPhones do this for real (as stated above)?
CHH2 said:
It's not even Android. My work phone is an iPhone and it has the same behavior. Which drives me nuts because our work phones require us to change pin codes every couple of months and we can't recycle codes.
Click to expand...
Click to collapse
Interesting. I wonder what type of MDM Solution your company is running...
dbornack said:
Hmmm... Not sure I understand this behavior. My fingerprint is much more complex than a 4-digit code that can eventually be brute-forced (phone wipe or not - in theory I mean).. so why wouldn't my fingerprint be the top-most factor in unlocking the phone? I mean.. say I'm one of those guys that uses his last four of an SSN like an idiot, and someone knows that about me.. boom, they're in my phone. Do iPhones do this for real (as stated above)?
Click to expand...
Click to collapse
Yup, every time I restart my iPhone, it asks for my pin number and the finger print reader is inoperable. Even when I don't restart my iPhone for a while, it will occasionally lock out the reader and require a pin to wake.
rudbwoy said:
Interesting. I wonder what type of MDM Solution your company is running...
Click to expand...
Click to collapse
Had to figure out where in the menus to dig through to find out who it is. (I seriously do not like how Apple sets their phones up.) Looks like it is AWMDM.
CHH2 said:
Had to figure out where in the menus to dig through to find out who it is. (I seriously do not like how Apple sets their phones up.) Looks like it is AWMDM.
Click to expand...
Click to collapse
Airwatch, by VMware. MDM....aka you're being watched...
rudbwoy said:
Airwatch, by VMware. MDM....aka you're being watched...
Click to expand...
Click to collapse
I always assume as much. Not really a bother for me. The iPhone is a work phone that I don't like carrying or touching. My personal phone is always my go to for anything unless it is work related.
I have this on my nexus 6p also. When ever i reboot the phone it requires me to use my pattern to unlock. It's a "feature" of sorts. Not going to go into my thoughts as to why but i think i may understand why they did that.
In case anyone is wondering, a few conditions that force you to use backup method are being left alone (with no smart locks enabled or active) for 4 hours, a reboot, and a failed scan 5 times in a row.
The reboot case is due to encrypted data (no matter what you do, your phone is encrypted on boot, unless you fix that, however, you phone will still treat it as such). The only reason I can imagine for the time out is in case a ninja chops off your fingers in your sleep. As for the wrong input, that seems annoying sure, but odds are if you got the fingerprint wrong 5 times in a row, it's not you.
Yeah v10 does this as well on fresh boot ups.
I'm not sure I understand the reason behind it I would think it would be less secure this way.
Sent from my LG-H901 using XDA-Developers mobile app
Vuciz said:
In case anyone is wondering, a few conditions that force you to use backup method are being left alone (with no smart locks enabled or active) for 4 hours, a reboot, and a failed scan 5 times in a row.
The reboot case is due to encrypted data (no matter what you do, your phone is encrypted on boot, unless you fix that, however, you phone will still treat it as such). The only reason I can imagine for the time out is in case a ninja chops off your fingers in your sleep. As for the wrong input, that seems annoying sure, but odds are if you got the fingerprint wrong 5 times in a row, it's not you.
Click to expand...
Click to collapse
I'm not sure I'm following as to why encryption matters. Are you saying my fingerprint data is encrypted? If so, why isn't my PIN also encrypted?
Speaking of fingerprints has anyone run into the issue where the phone "forgets" your print? I have had this happen at random times and while the fingerprint data is still saved the phone fails to recognize my finger so I have to set it up again.
Sent from my LG-H901 using XDA-Developers mobile app