If I set my clock 5 minutes slow on my phone, and then set the Date & Time to be automatic, should it correct the time? and if so, how long before it does so?
mcvpjd3 said:
If I set my clock 5 minutes slow on my phone, and then set the Date & Time to be automatic, should it correct the time? and if so, how long before it does so?
Click to expand...
Click to collapse
I believe it depends on whether your carrier provides clock sync or not.
mcvpjd3 said:
If I set my clock 5 minutes slow on my phone, and then set the Date & Time to be automatic, should it correct the time? and if so, how long before it does so?
Click to expand...
Click to collapse
If your network does support auto date and time just reboot the phone and the correct time should be displayed.
Related
Been using the clocksync app from market. Using it to auto correct the time drift issue I keep experiencing.
Every time you hit the windows button and open that menu bar, the clock is fine. As soon as you close it your clock stops 'ticking' until the menu is closed usually causing up to 3 seconds of time drift, over the course of a day my time usually half an hour out at least.
Download the app and try opening and closing the menu and test it for yourself
Why does this happen? I'm happy using this app to resync time every few hours if I have to, just reporting this bug like a good tester xD
Edit: I can confirm that most interaction with the ui pauses the clock. For example, closing a menu or sliding down the notification bar.
ryannathans said:
Been using the clocksync app from market. Using it to auto correct the time drift issue I keep experiencing.
Every time you hit the windows button and open that menu bar, the clock is fine. As soon as you close it your clock stops 'ticking' until the menu is closed usually causing up to 3 seconds of time drift, over the course of a day my time usually half an hour out at least.
Download the app and try opening and closing the menu and test it for yourself
Why does this happen? I'm happy using this app to resync time every few hours if I have to, just reporting this bug like a good tester xD
Click to expand...
Click to collapse
this was already known if you read the frx04 thread then you would know that everyone suggests you use clocksync because the clock is still bugged..
shatred said:
this was already known if you read the frx04 thread then you would know that everyone suggests you use clocksync because the clock is still bugged..
Click to expand...
Click to collapse
Actually, this is the first time I've seen someone suggest that they've found a concrete way of reproducing the problem.
However, this is certainly not the only source of clock drift, since I get clock drift when my phone is just sitting there doing nothing. Nonetheless, the fact that it's reproducible will hopefully be helpful to some dev in running down the problem.
the clock is always off, when its sleeping or idle even when you are using it the clock is ALWAYS off a couple ms and those ms increase every second. so bassicly after 15min in life the clock on your phone thinks it have only been 14 mins.
Use clock sync people! its free downloadable from the market and you can set it to auto set time every 30min, 1 hour, 2 hours etc. i prefer every 1 hour as that is very accurate
i did not read it good sorry*
manekineko said:
Actually, this is the first time I've seen someone suggest that they've found a concrete way of reproducing the problem.
However, this is certainly not the only source of clock drift, since I get clock drift when my phone is just sitting there doing nothing. Nonetheless, the fact that it's reproducible will hopefully be helpful to some dev in running down the problem.
Click to expand...
Click to collapse
I can confirm that menu open/close actions do cause clock drift. Not sure why ryannathan's menu takes so long to close. In my case, my menu closes a lot faster and the system clock loses only a few hundredths of a second each time (not a fixed amount, it is variable).
It's especially obvious when you are within ClockSync as the "offset" number increases in magnitude rapidly when you hit the menu button over and over again to repeatedly open/close it.
Edit: Looks like it doesn't help that we don't seem to have access to an RTC. I was curious to see how well the hardware clock was keeping in sync as compared to our system clock, but hwclock can't find an RTC to access.
Is there currently anyone working on this issue?
ryannathans said:
Is there currently anyone working on this issue?
Click to expand...
Click to collapse
i guess not, as most important things are worked on now like battery life, wake up, sleep and a stable running system.
shatred said:
i guess not, as most important things are worked on now like battery life, wake up, sleep and a stable running system.
Click to expand...
Click to collapse
I think it's unreasonable to expect work to "kick off" in less than a day. It is probably bumped up in priority thanks to a reproducible scenario, however, it's a pretty deep-down bug so the people most likely to have the skills to work it are the ones working on power management right now.
(e.g. I have barely any clue where to even start with something like this, so I'll be sticking with my GPS work for now.)
Updated first post to include information about most interections with ui. Check the edit.
Can someone confirm this?
I would like to extend from 10 minutes, the standard maximum possibility on Ics for lock the screen. Do you know if it is possible?
I was supposing it was some parameter on the system.
Thanks.
Hi,
In order to increase the wakeup time, follow the following steps:
System->Display-> Sleep and from the menu select the time you want...
In my phone, I have 30 minutes as maximum time.
Hope this resolve your problem.
I use a widget called screen toggle timeout to set mine to never
Sent from my M886 using xda premium
jbrt said:
I use a widget called screen toggle timeout to set mine to never
Sent from my M886 using xda premium
Click to expand...
Click to collapse
Thanks for your responses but...
- If you increase the screen time, it will be ever displaying.
- My company forces me for strong password when screen is locked. The solution I need is something can increase the delay time between the screen is off and the screen is locked. I have tested many solutions in the market but it dont work: everytime you getup the device the password screen is the first action, later the application that apparently can extend the delay, I expect you understand my meaning.
I think the delay time of the lock screen after the screen is off (from seconds to 10 mins) is stored in some table in the system, and maybe is not complex to change...
So I have set up Tasker to toggle my data every 5 minutes while the screen is off. Seems to be working great so far - I have it set so that it bleeps every time the task is run (for debugging purposes), and when I sent myself a Google Voice text it came through after the data was toggled back on. So far so good.
The profile I have set up for this just runs a toggle task every 5 minutes on a schedule. What exactly is happening here? I assume it is waking my phone every 5 minutes to do this... I've set this up to hopefully conserve some battery (my ghetto version of Juice Defender), but, since this is running on a schedule, will it end up eating up more battery than it conserves?
kimboinatl said:
So I have set up Tasker to toggle my data every 5 minutes while the screen is off. Seems to be working great so far - I have it set so that it bleeps every time the task is run (for debugging purposes), and when I sent myself a Google Voice text it came through after the data was toggled back on. So far so good.
The profile I have set up for this just runs a toggle task every 5 minutes on a schedule. What exactly is happening here? I assume it is waking my phone every 5 minutes to do this... I've set this up to hopefully conserve some battery (my ghetto version of Juice Defender), but, since this is running on a schedule, will it end up eating up more battery than it conserves?
Click to expand...
Click to collapse
do you still use tasker?
i mean 2012 seems like 100000 years ago
I've searched for this and haven't found an answer one way or the other.
I've got an EVO LTE running ICS, Charmeleon rom.
I want to set a PIN lock on the phone so i can enable encryption. but if i do that, the biggest timeout i can set is 15 minutes. I was hoping there was some setting i could tweak somewhere to really increase the maximum timeout. I'd prefer it to be something more like 2 hours, or even a day.
I did see there's an app called delayed lock that'll do this for me, but I want to use the encryption on ICS and it says it wont work with encryption enabled.
Is there someway to increase the lock timeout?
Just to be clear - i'm not talking about the screen turning off - i'm talking about the phone locking and having to enter a pin. Once i boot up the phone I don't want to have to re-enter that PIN again unless the phone has been idle for at least 2 hours (or longer).
Thanks
Use Widgetsoid to place an "Always On" toggle widget on homescreen.
Tap it to make timeout period Infinite. Tap it again to return to normal few minute timeout period.
SachinShekhar said:
Use Widgetsoid to place an "Always On" toggle widget on homescreen.
Tap it to make timeout period Infinite. Tap it again to return to normal few minute timeout period.
Click to expand...
Click to collapse
There's no way to just change the timeout period within android itself? It seems pretty silly/stupid that we can't just set it to X minutes.
Do you know if this app will work if encryption is enabled?
Thanks
merkk said:
Do you know if this app will work if encryption is enabled?
Click to expand...
Click to collapse
Yes, it'll work even if encryption is enabled.
File system is decrypted at the time of boot. Its not that file system encryption/decryption is performed at every screen lock/unlock. So, firmware (which isn't encrypted at all) can read configuration/activity at anytime.
SachinShekhar said:
Yes, it'll work even if encryption is enabled.
File system is decrypted at the time of boot. Its not that file system encryption/decryption is performed at every screen lock/unlock. So, firmware (which isn't encrypted at all) can read configuration/activity at anytime.
Click to expand...
Click to collapse
The only reason I asked was i saw a similar app on the market which said it didn't work with encryption
https://play.google.com/store/apps/details?id=de.j4velin.delayedlock2
If you scroll down to the 'important' section it mentions it doesn't work with full encryption on ICS.
merkk said:
The only reason I asked was i saw a similar app on the market which said it didn't work with encryption
https://play.google.com/store/apps/details?id=de.j4velin.delayedlock2
If you scroll down to the 'important' section it mentions it doesn't work with full encryption on ICS.
Click to expand...
Click to collapse
This app has problem with that because its hitting lock directly which is attached with encryption system directly. Screen timeout case is different.
Oh - hold on a second. I think we might be talking about two different things.
I'm not talking about the screen timeout. I'm talking about the lock. If i put a PIN lock on my phone, the most i can set it to is 15 minutes before I have to re-enter the PIN to unlock the phone. I'd prefer it if I only had to enter the PIN either when the phone restarts, or every few hours, not every few minutes.
merkk said:
Oh - hold on a second. I think we might be talking about two different things.
I'm not talking about the screen timeout. I'm talking about the lock. If i put a PIN lock on my phone, the most i can set it to is 15 minutes before I have to re-enter the PIN to unlock the phone. I'd prefer it if I only had to enter the PIN either when the phone restarts, or every few hours, not every few minutes.
Click to expand...
Click to collapse
The lock initiates only after screen is timed out (or, you press lock button). So, I was considering normal usage case (when you're using device for several hours with considerable intervals).
Anyway, I'll update if I get a solution. Currently, I don't have any idea regarding this..
yeah - but I dont want to have to keep the screen on for a couple of hours just to avoid the phone locking. I'd like to have some battery left at the end of the day
Thanks for the help.
Hey there.
One thing I remember from Gingerbread is how, when on lockscreen, the screen would turn off after some 7 secs. So say I wanted to check the clock I could just turn on the screen and put the phone away again. On JB it seems like it uses the same timeout setting as the rest of the system, one I keep at 1 min..
Is there a way to make to make it seperate? I want the screen to turn off after 10 secs when Im on the lockscreen, so I dont have to press the, quite, inconviniently placed power button on my phone, each time (seeing as I got tap2wake on my phone)
Kocayine said:
Hey there.
One thing I remember from Gingerbread is how, when on lockscreen, the screen would turn off after some 7 secs. So say I wanted to check the clock I could just turn on the screen and put the phone away again. On JB it seems like it uses the same timeout setting as the rest of the system, one I keep at 1 min..
Is there a way to make to make it seperate? I want the screen to turn off after 10 secs when Im on the lockscreen, so I dont have to press the, quite, inconviniently placed power button on my phone, each time (seeing as I got tap2wake on my phone)
Click to expand...
Click to collapse
You can try my app, KinScreen. It allows setting a different timeout for the lockscreen. However, the lockscreen timeout doesn't seem to have an effect in KitKat (where the default is 10s).
Kocayine said:
Hey there.
One thing I remember from Gingerbread is how, when on lockscreen, the screen would turn off after some 7 secs. So say I wanted to check the clock I could just turn on the screen and put the phone away again. On JB it seems like it uses the same timeout setting as the rest of the system, one I keep at 1 min..
Is there a way to make to make it seperate? I want the screen to turn off after 10 secs when Im on the lockscreen, so I dont have to press the, quite, inconviniently placed power button on my phone, each time (seeing as I got tap2wake on my phone)
Click to expand...
Click to collapse
Have you found a way to do this? My new 4.3 JB smartphone used to have a lockscreen screen timeout of 5 seconds, which I liked, but somehow it is now something like 30 seconds... which is TOO long for my liking... I've tried any combination of settings to revert this but with no luck...
BTW, 30 seconds is not even my screen timeout ... I have it set to 1 minute. So... I have absolutely no clues...
MegaSharkXDA said:
Have you found a way to do this? My new 4.3 JB smartphone used to have a lockscreen screen timeout of 5 seconds, which I liked, but somehow it is now something like 30 seconds... which is TOO long for my liking... I've tried any combination of settings to revert this but with no luck...
BTW, 30 seconds is not even my screen timeout ... I have it set to 1 minute. So... I have absolutely no clues...
Click to expand...
Click to collapse
Only way I could come up with was to use Tasker. Make a profile that does when on lockscreen timeout is 7 secs and when not its 1 minute.
Not very ideal.
Kocayine said:
Only way I could come up with was to use Tasker. Make a profile that does when on lockscreen timeout is 7 secs and when not its 1 minute.
Not very ideal.
Click to expand...
Click to collapse
Can you share how was your Tasker profile created? I remember trying to do a similar profile on my previous smartphone (actually it was running KitKat) and I couldn't figure a way for a profile to detect lockscreen for the timeout to be set differently.
Also you can't set it below 7 seconds....
Interestingly enough, I suspect Tasker was the reason why I lost my "short" lockscreen screen timeout in the first place on my new smartphone
MegaSharkXDA said:
Can you share how was your Tasker profile created? I remember trying to do a similar profile on my previous smartphone (actually it was running KitKat) and I couldn't figure a way for a profile to detect lockscreen for the timeout to be set differently.
Also you can't set it below 7 seconds....
Interestingly enough, I suspect Tasker was the reason why I lost my "short" lockscreen screen timeout in the first place on my new smartphone
Click to expand...
Click to collapse
That was indeed the trick. To detect the lockscreen. I came across this plugin:
https://bitbucket.org/laceous/android-atlockscreen/wiki/Home
AtLockScreenTaskerConditionPlugin.1.0.0.apk
AtLockScreenTaskerSettingPlugin.1.0.1.apk
Those you'll need. It runs a background service, without battery drain ofcourse, that uses something 4 mb ram.
Attached is the entire "project" you can import to get something that works.
Kocayine said:
That was indeed the trick. To detect the lockscreen. I came across this plugin:
https://bitbucket.org/laceous/android-atlockscreen/wiki/Home
AtLockScreenTaskerConditionPlugin.1.0.0.apk
AtLockScreenTaskerSettingPlugin.1.0.1.apk
Those you'll need. It runs a background service, without battery drain ofcourse, that uses something 4 mb ram.
Attached is the entire "project" you can import to get something that works.
Click to expand...
Click to collapse
Thanks! But I managed to do it yesterday all by myself just using Tasker and nothing else wanna know how?
MegaSharkXDA said:
Thanks! But I managed to do it yesterday all by myself just using Tasker and nothing else wanna know how?
Click to expand...
Click to collapse
Yes we want to know how! What Android version? I haven't been able to change the lockscreen timeout on KitKat from the default 10s (higher or lower) on stock Nexus 5 ROM.
Sent from my Nexus 5
Flyview said:
Yes we want to know how! What Android version? I haven't been able to change the lockscreen timeout on KitKat from the default 10s (higher or lower) on stock Nexus 5 ROM.
Sent from my Nexus 5
Click to expand...
Click to collapse
So basically this is set by using two profiles:
. Event Screen on -» Display timeout 7 seconds
. Event Screen unlocked -» Display timeout 60 seconds
The only caveat I can think of is that instantly lock after sleep should be activated to prevent false positives.
Now if only I could set the timeout to a value lower than 7 seconds...
MegaSharkXDA said:
So basically this is set by using two profiles:
. Event Screen on -» Display timeout 7 seconds
. Event Screen unlocked -» Display timeout 60 seconds
The only caveat I can think of is that instantly lock after sleep should be activated to prevent false positives.
Now if only I could set the timeout to a value lower than 7 seconds...
Click to expand...
Click to collapse
Cool.
However, the reason I didn't go with something like this is because there's times where I'll have the lockscreen disabled thru a widget OR if I wake up right after it had turned the screen off (and there's a time of 5-15 secs before actually locking the phone). That would result in having an extremely fast dispaly timeout at times where it's not actually wanted. The way I've gone about it ensures, for the most part, that it only applies when locked.