Database Users

Bizarre clock issue. Anyone get this, or am i mad

OK, i got a weired bug with mine.
Lets say for example it is 22.15.
I then turn the screen off (hitting the power button)
After exactly 15 minutes i turn it back on.
The clock still displays 22.15 then after about a second it flicks to 22.30.
Is anyone getting that problem, coz, though liveable, its bloody annoying.

yep, that's normal - bit annoying, but hey
Due to other issues, I don't even turn mine off anymore - just switch the screen off; no such issues then

My Vario does that, but it only stays on the previous time for less than half a second and then it updates.
A lot of, although not all, devices, whether they're PDAs, phones or other personal devices that have an LCD screen, don't bother to continue updating the display in memory whilst the display is off. I guess it must save some battery otherwise they woudn't have put this "feature" in

Keitaro said:
My Vario does that, but it only stays on the previous time for less than half a second and then it updates.
A lot of, although not all, devices, whether they're PDAs, phones or other personal devices that have an LCD screen, don't bother to continue updating the display in memory whilst the display is off. I guess it must save some battery otherwise they woudn't have put this "feature" in
Click to expand...
Click to collapse
Ah yeah, good point. I can put up with it, and believeing that it means i get better battery life (though probably minimal) i will cope
Ta

The same thing happened to my MDA. I noticed that if I close all of the programs running, from Settings/Memory, the clock "live updates"

Screen Timeout

here is my issue.
unless i manually change my screen timeout my screen turns of no matter what im doing unless i touch it. watching something on hulu or playing need for speed it doesn't recognize that im doing something and black. is there a fix for this or do i have to change it every time.

dro3432 said:
here is my issue.
unless i manually change my screen timeout my screen turns of no matter what im doing unless i touch it. watching something on hulu or playing need for speed it doesn't recognize that im doing something and black. is there a fix for this or do i have to change it every time.
Click to expand...
Click to collapse
i did notice thie issue with need for speed as well

IN MY CASE, THE SCREEN NEVER TURNS OFF! ONE TIME, I left out alone without my phone and three hours later I come back and the battery is 20 percent and the screen still on.
Sent from my Nexus S using XDA App

For games, the publisher needs to fix it and add permissions to keep the screen on.

nxt said:
For games, the publisher needs to fix it and add permissions to keep the screen on.
Click to expand...
Click to collapse
this.
it may be annoying playing NFS:S but just tap the break when you see the screen dim a bit

sleep of death

I'm now on my third nexus 7 and in general absolutely love the device but I'm getting fed up with the issues.
My first device suffered from sever flickering, the second had the backlight bleed and now the third refuses to wake after the screen is turned off about fifty percent of the time.
This is not the same issue as people are reporting in other posts as the charger is never connected when I have a problem. It doesn't matter if the screen times out or if I press the power button to after I finish using the device.
I'm using the stock ROM (with the 4.1.1 update), no root and have only installed the kindel app so its about as vanilla as can be.
The second nexus I had did this once but I had already organised the return and didn't think much of it.
Anyone else having similar issues or able to recommended a fix as this nexus is perfect in every other way?

Factory reset, leave it that way for a while, does it happen? If no, then you probably have an app doing something wonky.

Turn off automatic backlight, manually set it to around 40% and see if the flicker and the "SOD" goes away.

As the poster above said, turn off automatic brightness and see if that fixes it.

Nospin said:
As the poster above said, turn off automatic brightness and see if that fixes it.
Click to expand...
Click to collapse
Automatic brightness is on my N7 (and other devices) 100% of the time... No SOD problems here.

lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.

THANKS!
Just got my first nexus 7 yesterday and after pretty much falling in love, was dismayed about the unexplained black outs for no apparent reason. Could not wake up the device afterward without holding down the power key for 10 sec then leaving it alone for a while.
After reading your post, I realized that the incidents occurred after switching from manual to automatic brightness in a dimly lit room, followed by mysterious recoveries when moving to brighter room. I will monitor, but hope for the best. (Will probably just use manual settings as I found the automatic mode to be too dim in all settings anyway - old eyes!)
I am already pretty raw on this point as I just spent the last 10 years or so with a laptop that would not wake up from sleep, and just learned to live with it after wasting SO much time trying to get to the bottom of it. If you have saved me from that, or from having to exchange the n7, I owe you big time. Thanks again!
Compusmurf said:
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
Click to expand...
Click to collapse

did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying

seven2099 said:
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
Click to expand...
Click to collapse
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back

seven2099 said:
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
Click to expand...
Click to collapse
i have similar issue with forced sleep, it cannot waken sometimes. TnT
anyone can help?

Further investigation shows this has nothing to do with brightness and that all tablets with this issue should be returned/exchanged immediately.
Quick google search will allow you to find that comes directly from Asus support.
Total fail, asus ftl

new tab rendered more quality issues. opened it at the shop, returned it immediately and went samsung.
Asus will always be asus.. too bad cuz my tf300 was pretty decent in terms of quality, just had wierd screen lift and squeecky issues.
Galaxy Tab 2.0 7inch is a much better choice now.

I have exactly the same problem with my current device. About 30% of the time, the power button would just stop working so I couldn't turn the unit on or off, unless I plugged it in to the charger. It didn't turn on for a full day once so I did a full factory reset which included re-flashing the stock rom and the problem persisted, the button would still not work! So I packaged it up for return and left it sitting for a couple of days. Just before I went to post it, I checked that the issue remained and to my surprise it turned itself back on again! I kept it and since then, it has only happened once.
I do intend to return it though, but only when I hear Asus are shipping units which are built properly. Clearly a hardware issue but pretty weird since it seems random and is not reproducible by any means I know of.

I am experiencing a similar issue. Does setting a manual brightness fix the issue?

It is my 3rd Nexus now with exactly the same problem.
I found out that the Nexus is in APX-mode (NVFlash) when it's in this state (SoD). Windows tries to install a APX driver when it is connected via USB.
The problem occured always with 16GB Nexus. A friends 8GB works fine.
Nexus 7 (C9) - Stock Rom 4.1.2. - locked - not rooted

Turning off the auto-brightness fixed the issue for me. Minor workaround to a major problem.

[Q] Clock Time Jump

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.

Always on display no longer moves around

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