Database Users

[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.

Help! Several major issues on 4.3 (home button, SIM, lock screen)

My N4 was away to repair a broken screen. Got it back on Wednesday and it immediately updated to 4.3. All was well, except for one weird issue where hitting a notification from the pull down would take me to the app via the pattern lock. I put this down to having played with some lock screen settings in Setting Profiles app (trying to disable it in certain settings), but it might not have been.
I've done the first device restart today, and after rebooting there are a few big issues.
1. I don't appear to have any mobile network, though wifi is connected. I had a good signal before the reboot.
2. I'm not getting a lock pattern or any lock screen at all, and it's not asked for the SIM pin
3. Hitting a notification in the pull-down makes the 'lock' clicking sound as it takes me to the app
4. The home button doesn't work. I see a slight dim of the screen and it makes the lock click sound, but nothing happens. Back and multitask work fine
Help! Any ideas? Are they known issues? Can't seem to find any reference online.
I'm on stock, using Nova Launcher

!!11oneone said:
My N4 was away to repair a broken screen. Got it back on Wednesday and it immediately updated to 4.3. All was well, except for one weird issue where hitting a notification from the pull down would take me to the app via the pattern lock. I put this down to having played with some lock screen settings in Setting Profiles app (trying to disable it in certain settings), but it might not have been.
I've done the first device restart today, and after rebooting there are a few big issues.
1. I don't appear to have any mobile network, though wifi is connected. I had a good signal before the reboot.
2. I'm not getting a lock pattern or any lock screen at all, and it's not asked for the SIM pin
3. Hitting a notification in the pull-down makes the 'lock' clicking sound as it takes me to the app
4. The home button doesn't work. I see a slight dim of the screen and it makes the lock click sound, but nothing happens. Back and multitask work fine
Help! Any ideas? Are they known issues? Can't seem to find any reference online.
I'm on stock, using Nova Launcher
Click to expand...
Click to collapse
Those are not any known issues or anything I have read since Andrid 4.3 came out. Try a factory reset to see if that solves the problem. If not, maybe the screen wasn´t the only thing broken on your device. Ask for warranty.

Thanks, will see how I get on this evening and try a factory reset if it doesn't fix itself.
Seems to be a weird problem related to the lock screen and when it should/shouldn't kick in...

!!11oneone said:
Thanks, will see how I get on this evening and try a factory reset if it doesn't fix itself.
Seems to be a weird problem related to the lock screen and when it should/shouldn't kick in...
Click to expand...
Click to collapse
Glad I could help.

Ok, I've done a factory reset. Not had much chance to play as it took hours to reinstall everything. But I've just had the word issue where selecting something from the notification tray (the setting profiles shortcut) took me to the lock screen to put in my pattern first, then took me to the app.
EDIT no pattern to when it does it, seems random and can be while I'm using the device, so the lock screen shouldn't kick in for any reason
Any ideas? Faulty device?

[Q] Screen shuts off trying to unlock

My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks

prerunnerseth said:
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
Click to expand...
Click to collapse
When I use the power button on the back of the phone instead of the knock-on, I had this same problem. I was rooted but on stock rom. I've read other posts about the same problem. I would try to put in my pattern and midway through the screen turns off. Sometimes it would be two seconds, sometimes like 10. Don't know what the problem was.
My knock-on feature was barely working. Some guy recommended getting this case: http://www.amazon.com/gp/product/B00FEQU1NG/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1
I needed one anyway so I got it. Haven't had an issue with the knock-on feature anymore. No idea why haha but whatever, it works. Kind of a ghetto workaround.

I'm having the exact same issue.
Factory reset several times, installing my usual apps or having just the default apps without updating them didn't make any difference.
After a factory reset I disabled the knock knock feature and still, when I try to bring my screen up and unlock, it immediately shuts off, preventing me from swiping.
Another side effect is, when I make a phone call, the screen immediately goes blank and it will never turn back on unless I restart by holding on to the power button, this is especially inconvenient when I need to dial some options (i.e.) voice mail options, corporate automated options.
All of the above happened while I had my Incipio feather shine case. (incipio.com/cases/smartphone-cases/lg-smartphone-cases/lg-g2-cases/lg-g2-cases-verizon/feather-shine-case-for-lg-g2-verizon.html) I took the case off and did another factory reset last night, and so far the knock-on rate has improved from 0% to at least 60-70%... Strangest thing.... If anyone else can shed some light onto what the hell happened/is happening, I'd really appreciate it! It's been a frustrating ride since this problem surfaced about a couple weeks ago. I had this phone for about 2 months now....

I'm having this problem too. It happens with both knock on and power button wake. I have noticed that the screen is not actually immediately turning off, though. In a completely dark room, I can still see faint outlines of my lock screen. Then, after the brief time out for dimming, the screen will go to its dimmed brightness (which is far brighter than what's concurring after waking the phone). I'm able to unlock, reboot, and usually that will solve the problem for a little while, but this is getting frustrating.
Stock rom, rooted, TWRP, Nova Launcher, and xposed. I'm not sure what's causing this.

I know it's been said many times but if you block the sensors with your fingers after waking the device, your screen will turn back off. Its a security feature/bug and I would assume this is what's happening here.

I ended up getting a certified-like new replacement from verizon... While I had the old one, I did a test with that sensor you're talking about and it didn't really make a difference. I made sure the sensor area was clean without anything covering it and the problems persisted. I really hope LG can find the root cause of this and fix it... Very frustrating.

Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.

yonba said:
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
Click to expand...
Click to collapse
exactly. the sensor in very sensitive to being covered. Because its hypersensitive and having undesireable effects I would consider this a bug since it is buggy.

I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).

Having this issue with my G2, its very annoying. Knock on does not work and screen shuts off after about half a second that I press the power button. Had to reflash to stock the first time this happened and fixed it but after about a month the same problem occured. I could however open by pressing one of the volume button together with the power button.
Hoping to find permanent fix for this problem.

thirtynation said:
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Click to expand...
Click to collapse
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX

bigiuly said:
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
Click to expand...
Click to collapse
Please tell me where to find these settings

taqikazmi said:
Please tell me where to find these settings
Click to expand...
Click to collapse
Settings / Led Control

bigiuly said:
Settings / Led Control
Click to expand...
Click to collapse
There is no option in settings like LED.

taqikazmi said:
There is no option in settings like LED.
Click to expand...
Click to collapse
In settings of Lightflow app

bigiuly said:
In settings of Lightflow app
Click to expand...
Click to collapse
I installed the app and fund the settings but all of them are already unchecked

4.4.2 bug fix??

Bug fix ??
When updated to 4.4 on verizon I noticed that the screen doesnt lock or go back to the slide setting I set it to after a missed call. This is a headache because screen stays on, it makes me accidentally open apps and make calls, and runs battery fast because screen stays on. For those who have updated already does 4.4.2 fix this? Also is the lowest brightness still super high? Or did it get fixed back to how it was on 4.2.2? Thanks in advance.

...

You post your question, and then minutes later post ..... as if we don't care about you. Pipe-down, please.
To answer your question, I haven't had the issue you're saying. The screen locks back automatically on mine, and furthermore, the Active Notifications shows I've missed a call. Check your dialer settings, reboot your phone, and worst case scenario, FR the phone.
flacco40 said:
...
Click to expand...
Click to collapse

[Q] Screen won't turn off

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.