Related
Hi,
I checked the web on this issue and have found it being reported on other sites but I can't seem to find the resolution, if there is one....
I received my Nexus 4 last Friday. Been digging it ever since. I came from the SG2 Skyrocket on att. I realized how much I miss the pure Android experience on a phone without the carrier's bloatware and manufacturer software.
however during the Super Bowl, my buddies and I discovered a weird bug on the phone. Upon waking up from a "long" hibernation, my time/clock is off by 20-30 minutes. Once I reboot the phone, the time is corrected. However, it's kinda weird waking up in the morning, my bedside clocks displays the correct time but when i wake up my phone, the time/clock is incorrect.
Has anyone experienced this? Does anyone know the resolution??
Much thanks..........
It happened to me once or twice before on my N4 stock/rooted. What is your setup under Settings>Date and Time ? Sometimes when you have Automatic date & time and Automatic time zone enabled and you are out of mobile network service, the time doesn't get updated until your phone mobile connection is restored. In my opinion, this behavior smells like a bug. Post a screen shot of that settings page if you could....
Hash_Map said:
It happened to me once or twice before on my N4 stock/rooted. What is your setup under Settings>Date and Time ? Sometimes when you have Automatic date & time and Automatic time zone enabled and you are out of mobile network service, the time doesn't get updated until your phone mobile connection is restored. In my opinion, this behavior smells like a bug. Post a screen shot of that settings page if you could....
Click to expand...
Click to collapse
Hi Hash,
Thanks for the feedback. I went into the settings, as you directed, and see that both Automatic date & time (use network provided time) and Automatic time zone (use network provided time zone ) are both checked.
I will try and take a picture tomorrow morning for, again, it was weird looking at my cell phone which says 5:35am when my bedside clock showed 6:00am.
Schwacker
My Issue with Pictures
All,
To document what is happening to my phone, I am attaching pictures to this post. The early morning picture post, I had my Wifi turned on. After the pictures were taken, I turned off WiFi an let it go int hibernation until I woke up at 6am. As you'll see in the second picture, my time/clock was way off.
I am using Beautiful Widgets for the clock but can't see that causing my issues.
Any thoughts? Hate to return the phone for I'm really loving it but don't want the phone if I can't depend on the time!
Thanks!
Schwacker said:
All,
To document what is happening to my phone, I am attaching pictures to this post. The early morning picture post, I had my Wifi turned on. After the pictures were taken, I turned off WiFi an let it go int hibernation until I woke up at 6am. As you'll see in the second picture, my time/clock was way off.
I am using Beautiful Widgets for the clock but can't see that causing my issues.
Any thoughts? Hate to return the phone for I'm really loving it but don't want the phone if I can't depend on the time!
Thanks!
Click to expand...
Click to collapse
Have you tried the stock clock to see if Beautiful widgets is the issue. Try that first. Next thing I would try is to leave WiFi on during sleep and see if the issue is fixed. I would expect to have some lag after a wakeup for the clock to update but no more than 15 seconds. Good luck.
grubbster said:
Have you tried the stock clock to see if Beautiful widgets is the issue. Try that first. Next thing I would try is to leave WiFi on during sleep and see if the issue is fixed. I would expect to have some lag after a wakeup for the clock to update but no more than 15 seconds. Good luck.
Click to expand...
Click to collapse
Thanks Grubbster -- I have to admit and I'm somewhat embarrassed in doing so, I couldn't figure out how to use the stock clock on my home screen and when I couldn't figure it, I thought "hey, I purchased Beautiful Widgets...I'll just add that clock to my screen....".
FYI -- I have always left my wifi on during the night and into hibernation. Last night I had the brain child thinking maybe it's the Wifi that is causing my delays for when I first noticed the time issue on Sunday, it was while I had my Wifi on....so I thought I'd turn it off to see if the time would be correct......freaking weird....
Schwacker said:
Thanks Grubbster -- I have to admit and I'm somewhat embarrassed in doing so, I couldn't figure out how to use the stock clock on my home screen and when I couldn't figure it, I thought "hey, I purchased Beautiful Widgets...I'll just add that clock to my screen....".
FYI -- I have always left my wifi on during the night and into hibernation. Last night I had the brain child thinking maybe it's the Wifi that is causing my delays for when I first noticed the time issue on Sunday, it was while I had my Wifi on....so I thought I'd turn it off to see if the time would be correct......freaking weird....
Click to expand...
Click to collapse
The stock clock is a widget. Just go into your widgets, long press the clock, and drag it to your home screen. Also, does the clock in the status bar show the correct time when waking up?
Check your beautiful widget app settings to see if there is anything related to updating system settings. Maybe a frequency (10 min, 15 min, etc.) that needs to be changed.
grubbster said:
The stock clock is a widget. Just go into your widgets, long press the clock, and drag it to your home screen. Also, does the clock in the status bar show the correct time when waking up?
Check your beautiful widget app settings to see if there is anything related to updating system settings. Maybe a frequency (10 min, 15 min, etc.) that needs to be changed.
Click to expand...
Click to collapse
Ok. Thanks -- duh -- there it is. I'll try this for a day to see if this will resolve the issue.
This has happened to me once, on Faux's kernel. It was my first time ever undervolting my device, and I undervolted by -100 mV (fast binned chip). It did it twice, and both during deep sleep. But the time corrected itself once I go into Settings > Date & Time and unchecking-and-rechecking the Auto Time setting.
Do you use a task killer?
Michealtbh said:
Do you use a task killer?
Click to expand...
Click to collapse
No. No task killer....though I have to admit....I was discussing my issue with a fellow phone geek. He believes my 2 options are: if it's an internal hardware issue, I'll need to get a new phone if it loses connection to the antenna which connects to my att network for the time/clock. Or if it's a software issue, then maybe a flash can resolve it.
I'm also going to contact Google later today and see what my return options are if, by tomorrow, I'm still experiencing this..
Thanks...
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.
So am I the only one who has this lock screen clock "stuck" at a time time problem?
I am literally disgusted by this issue! It happened on the S4 I had, and I thought Samsung definitely has solved the problem but nah they didn't.
The problem is, the lock screen clock gets stuck at a time, and doesn't update with system time. No, it doesn't happen always, but it could happen at a time which could be really important, just like it happened today. I went to bed at 1 a.m, checked the phone when I temporarily woke up, the lock screen clock showed 3:44 a.m. I went back to sleep, suddenly I felt that there's a glimpse of sunlight on my windows, and checked the phone again, and it was actually 6:44 a.m.
Seriously speaking, I am fukcing tired of this problem. No I don't depend on the phone's lock screen clock, but the only time I check it is when I am in bed, sleeping, and that's when the problem has happened today.
Is there really no solution of this? Using a third party lock screen app or what?
Damn I am annoyed!
Maybe get a note 4?
pierrekid said:
Maybe get a note 4?
Click to expand...
Click to collapse
I am considering the Note 7 actually
:good:
I am using stock ROM and I never had this kind of problem.
devilsdouble said:
I am literally disgusted by this issue! It happened on the S4 I had, and I thought Samsung definitely has solved the problem but nah they didn't.
The problem is, the lock screen clock gets stuck at a time, and doesn't update with system time. No, it doesn't happen always, but it could happen at a time which could be really important, just like it happened today. I went to bed at 1 a.m, checked the phone when I temporarily woke up, the lock screen clock showed 3:44 a.m. I went back to sleep, suddenly I felt that there's a glimpse of sunlight on my windows, and checked the phone again, and it was actually 6:44 a.m.
Seriously speaking, I am fukcing tired of this problem. No I don't depend on the phone's lock screen clock, but the only time I check it is when I am in bed, sleeping, and that's when the problem has happened today.
Is there really no solution of this? Using a third party lock screen app or what?
Damn I am annoyed!
Click to expand...
Click to collapse
Most likely you have Greenify-ed something that you should have not.
This happens sometimes, yes. Annoyed me to no end on my S3.
Personally I use Zooper Widget as a lockscreen. (if you set multiple widgets and create a second widget page, you can delete the default lockscreen page by longpressing and dragging it to the bin at the top..) I've not seen Zooper have this bug
Sent from my SM-N9005 using Tapatalk 2
Check any battery save application that you might use. I had the same problem and it was due to an application that was saving battery. Sometimes this happens when i had the power saving mode too.
ShadowLea said:
This happens sometimes, yes. Annoyed me to no end on my S3.
Personally I use Zooper Widget as a lockscreen. (if you set multiple widgets and create a second widget page, you can delete the default lockscreen page by longpressing and dragging it to the bin at the top..) I've not seen Zooper have this bug
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
All right. Does this Zooper Widget support SMS pop up and missed call notifications like stock Samsung lock screen?
I have no idea how to use a widget as a lock screen anyway
tasked28m said:
Check any battery save application that you might use. I had the same problem and it was due to an application that was saving battery. Sometimes this happens when i had the power saving mode too.
Click to expand...
Click to collapse
I do NOT have any battery saving applications installed. If there's one thing I don't care about in mobile phones, that's battery life. So Greenify, and all those apps are not in my phone obviously.
Just updating the topic with a screenshot of the problem which I was talking about. Was lucky to snap the screenshot yesterday before going to bed, cause usually as soon as I press the home button to take the screenshot the time use to update.
From the box, the always on display (AOD) shifted around every minute or so to prevent burn in.
Two days ago I installed the T-Mobile update for my s7 edge. Last night, I was trying out my new wireless charger when I noticed the AOD no longer moves around. I tried charging directly, rebooting, powering off, changing themes/styles to see if it would start shifting around.
Did the update cause this change? Is anybody experiencing the same thing? Is this a bug or intentional (didn't see anything in patch notes). Thank for any input.
I love the AOD but now super paranoid about burn in.
Have you tried turning AOD off, waiting a bit, and turning it back on? Maybe reboot while it's off, then turn it back on.
Yeah, reports circulating that the T-Mobile update is causing the AOD to remain stationary. If you're on T-Mobile, definitely turn off AOD until they release a fix.
Yea I've tried disabling AOD and rebooting but it's still stationary. I went ahead and disabled it entirely and hoping a fix will be released soon. Thanks all.
Damn, disabled mine until it's fixed. Didn't even notice, thanks.
Sent Via My Samsung S7 Edge
Is it dimmed more like the night clock mode? I was thinking maybe they did that and figured it's not a problem any more, but just guessing. I have Verizon version and I jist use the night clock mode all time as the regular clock seems too bright.
hp79 said:
Is it dimmed more like the night clock mode? I was thinking maybe they did that and figured it's not a problem any more, but just guessing. I have Verizon version and I jist use the night clock mode all time as the regular clock seems too bright.
Click to expand...
Click to collapse
The brightness of the AOD is still determined by ambient lighting. The only time the AOD moves to a different position now is when I power up the screen then lock it. If I don't power up the screen, it will stay in that same position with auto brightness in effect.
DNx714 said:
The brightness of the AOD is still determined by ambient lighting. The only time the AOD moves to a different position now is when I power up the screen then lock it. If I don't power up the screen, it will stay in that same position with auto brightness in effect.
Click to expand...
Click to collapse
Yeah, definitely must be a bug then.
I'm annoyed of the Night Clock where it shows the time of an alarm that's set out few days out. I now disabled all alarms so I don't see that. lol.
Also, the stupid + sign on the icon groups in TouchWiz is really awkward and wastes so much space. They didn't have this in Galaxy S6.
Had this issue on a Fresh install (Not present on the Same Version previously (I rolled back after a upgrade)
My default was stuck in the middle and did not move, I went in and change the clock style to the round clock and hands, and mine is moving around the screen as normal