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?
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 have this problem where I will receive an SMS while my phone is asleep and by the time I get to my phone the screen turns off. It is literally on for ~3 seconds. Is there anyways to change extend this time to maybe 10 seconds? I always find myself having to turn the screen on again. I'd rather use a tweak to the system rather than using a new app. Running stock ICS with root by the way.
No.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
SmsPopup is highly recommended; extremely configurable and you'll get a nice popup notification with a quick reply option and reminders if you like.
I would like to ask if it is possible to make app that would run on background and would change time on my device every few seconds. Lets say every 5 seconds change time by 3 hours (forward).
Hey,
Clock Sync is an gold APP but the Lowest sync time is 30 s
You can find it in play store
Hey guys, I need help on how to edit my android call timer seconds to count faster in 4 seconds interval (4,8,12...) instead of the normal 1 seconds interval whenever I pick up a call
I've never heard of such a thing. And it's likely buried deep in the framework to adjust, if it's possible.
Not sure why anyone would, and so I doubt anyone has tried.
:good: