Like many of you I've been flashing roms on my 8.9 like hell. And just like any other n00b, we encounter issues most people in the community already solved and some still a mystery.
One particular issue is my clock not syncing whenever I turn on my device. It is like its going into deep sleep and when I turn it on, it gets delayed for about as long i turned it on. To make matters worse, even when the device is fully on, the clock pauses. It's a headache.
I cannot guarantee that this is the definite solution, but it may help someone here someday. First, let's make sure we have the same symptoms:
1) Clock is not sync or gets delayed as you leave it on.
2) You leave the tablet in sleep and turn in on and notice the clock is no longer sync.
3) If you reboot your device, it gets the clock correct without any adjustment needed.
4) Your timezone settings is correct, I live in the Philippines and we don't have daylight savings here so maybe you did something wrong. Double check your settings first.
If all of these 4 symptoms matches the issue in your device, then my solution may help. If not, then it might be hardware.
Moving on...
Just a brief background, I have already encountered this problem TWICE. Both instances involving me flashing a different kernel. I also have a habit of flashing roms and kernels with battery below 50%, which is definitely inadvisable. My first instance of the issue was when I flashed early builds of CyanogenMod 10, the bug was never resolved until I flashed a leaked version of the official Samsung ICS rom was available when I realized that the problem was fixed. The second instance was with my CyanogenMod 10.1 when after I was configuring my Xbox360 controller to my tablet. I was trying out kernels and reflashing my CM10.1 to revert the settings. Then I discovered that the clock was not in sync again.
My temporary solution was installing ClockSync app and Timezone fixer app which are both created by the same developer. I had to do the following settings:
Date & Time settings:
Automatic date & time: unchecked
Automatic time zone: unchecked
Set date: (specify the date)
Set time: (specify the time)
Select time zone: (specify time zone)
(the rest, just leave it as is).
Clock sync app:
Enable Automatic Synchronization: checked
Interval: 30 seconds (debug mode)
Override system setting: checked
UTC offset: (specify offset)
Time zone fixer:
Update your files, it will require a boot.
These settings are the same settings I had in both occasions. Clock sync became a battery hog, so this definitely wasn't the proper fix. However, the time zone fixer may have helped in a way. So I gave up and un-checked the Clock sync automatic synchronization. My clock was still not sync but I really didn't want to waste battery.
After a few days, just yesterday in fact, I encountered a battery calibration bug. I had to do the whole calibration steps. Somehow, draining the battery helped solve the issue. When I say drain, I mean completely drain from CWM until the tablet won't open.
The second instance assured me that the problem is definitely NOT hardware. Whatever it is, my symptoms can be fixed.
Just to be clear, I do not claim that draining your tablet's battery will solve this issue. But if you do have my symptoms, following my steps may help you just like it did with mine. Somewhere along the line, I may have did something right to fix it. My theory is with the Timezone fixer and battery drain.
Related
Shortly after DST went off, I realized that I had a problem, because all recurring and all-day appts were one hour off (making the all-day appts span 2 days), during March-October 2008, when DST will go back into effect.
After finding no answers anywhere, I discovered that UNCHECKING the TIMEZONE setting ("automatic change time zone and clock") under PHONE options, fixed the problem.
However, I LIKE the idea that my clock will adjust automatically based on the time zone I am in. When I was with Verizon, I hated that the phone wouldn't change automatically.
I can't be the ONLY one with this issue, can I?
Please suggest how to have my cake and eat it, too!
Is EVERYONE keeping the TIME ZONE option unchecked? Or does no one have any recurring/all day appts already set for April of '08? Would really appreciate some help with this.
P.S. Even though we have wm6 on the phone, I did the DST fix from Microsoft, as well as the "extra steps" (which involves going to the clock setting, change the time zone, exit out, go back in and change to correct time zone and exit out), which does take care of the issue...for a little while. I can have the TIME ZONE option checked and it works fine...but only for a little while. Always after a soft re-set, it loses the time zone reading and sometimes it just loses it after the phone sits idle for a while.
I was under the impression that we weren't supposed to apply the DST fix at all on WM6 for the Tilt/Kaiser. I applied it way back and had all sorts of issues.
I removed it and it's been fine ever since the DST switch.
After applying the "fix" and it not changing anything, I did a hard reset and left it alone.
Do you have the Time Zone option checked in Phone settings to automatically set the time zone and clock?
If you have the Time Zone option checked, would you do an experiment?
Make a weekly recurring timed event that starts BEFORE March 1 and ends AFTER November 15, 2008. Then, do a soft reset. Then, go to your calendar and see if the events after the 2nd Sunday in March and before the 1st Sunday in November are an hour off? That's what's happening with my calendar.
And post your results here? Thanks.
I found that the auto time zone setting in Phone settings causes more problems, Activesync auto launches constantly with this setting enabled as well as occasional time jumps (eg. from PST to Mountain Time for no reason).
With the time zone setting un-checked everything is very stable BUT my stock Kaiser did not change DST correctly. I have since applied the DST patch and will wait for the next time change to see what happens.
The issue im speaking of is the actual home screen clock. Every morning I have to re set it because it ends up becoming off by a few hours. I searched this forum and couldnt find anything. I had also posted the question in the Energy rom thread, but it kept getting swamped out by random question. Im running a tilt 2 FYI.
Any help appreciated, thanx
uncleswoop said:
The issue im speaking of is the actual home screen clock. Every morning I have to re set it because it ends up becoming off by a few hours. I searched this forum and couldnt find anything. I had also posted the question in the Energy rom thread, but it kept getting swamped out by random question. Im running a tilt 2 FYI.
Any help appreciated, thanx
Click to expand...
Click to collapse
Did you set your time zone? Did you turn on or off internet time sync? Did you uncheck get time from network under phone settings? Any of these could be the cause of your problems...
Im feeling really dumb this morning...My alarm didnt go off this morning because of this same problem. And I cant for the life of me figure out hwo to make sure the clock is auto updating to the network.
Im running Energy Cookie Reference. I have seen the settings before...but cant locate them today.
Time synchronization?
Hi.
Do you have the automatic time synchronization on? Try to disable it.
Settings -> Personal -> Phone ->
or
Sense settings tab -> data services -> internet time sync ->
Hey thanks for the response...my settings are different though. I found the setting in BSB Tweaks and turned it off...only time will tell if it helps though...we will see if my phone fails to wake me up again tomorrow...
Left Energy yet again because of this issue...I dont know a whole lot about the technicalities but it seemed to me that the phone is 'going to sleep' and actually losing track of the time thus keeping my alarm from sounding in the mornings.
When I hit the power button to wake the screen up in the mornings it would be displaying a time that was hours behind and seemingly random (what lead me to believe the phone was in a deeper sleep than normal). Possibly a really stupid theory...but like I said I dont know a whole lot. I just know it was way unacceptable in my case.
I will still monitor his threads like always and try the latest and greatest ROMS.
Clock Issue with Energy romArrow
I think the problem you are having is the windows alarm bug. I used to get this all the time until i started using g-alarm. it fixes the issue when you first install it. (note that its a paid app.) but here is the description and the registry edit that you need to change to fix the problem.
can't post the link soo you will need to copy and paste the url below if you want to view the webpage.
ageye.de/index.php?s=galarm/support/manual/limitations
Windows alarm bug
Windows Mobile has on some devices a strange behaviour: Although an alarm is successfully added to the WM notification queue (it's like a scheduler) it doesn't go off.
Searching the web gave me following information:
At midnight WM rebuilds the notification queue, therefore it wakes up for about 15 seconds. If the notification queue is too big or the device too slow WM goes to sleep again before it could finish building the queue for the next day.
If you force WM too stay awake for a longer time, it should successfully build the queue on at least more devices.
If you start G-Alarm and it complains about the Windows alarm bug, you've got the default WM settings (15 seconds WakeUpTime). If you press "Yes" G-Alarm changes it to 120 seconds which should be enough.
Here are the registry values G-Alarm changes:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts\ACResumingSuspendTimeout
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts\BattResumingSuspendTimeout
Click to expand...
Click to collapse
My clock has been keeping quite accurate time on Android 2.2.1 and 2.2.2 (not sure about 2.1, since it's only recently that I am saddled with a network provider that does not do NITZ). Since Gingerbread OTA, though, it seems that it's losing about 30 seconds or so per day.
Has anyone else seen this? There are previous reports of this issue for Galaxy S and MDA but not for Nexus One, and all the other threads predate Gingerbread.
Thanks!
yes, I can confirm this. The clock lags 30 seconds or more per day. I put it in the dock when I go to sleep to charge overnight.
I also confirm this.
I can also confirm this is happening on my nexus one running stock 2.3.3
My clock has been almost useless since Gingerbread and the switch to daylight savings. Before daylight savings, it worked perfectly when set to get the time from the network. Last summer on daylight savings it also worked fine, and Froyo handled the switch to standard time with no problem.
Now, if I leave it set to get the time from the network, it will eventually go way off. The time zone changes at some point to Western Argentina Time, when it should be Atlantic Daylight Time. The time will go behind by an hour, and then drift away more and more. The lock screen and clock app will show one time while the status bar shows another, and one or the other of these will not update as the minutes go by. These issues make alarms unreliable and worthless.
Rebooting the phone puts it all back the way it should be. Time zone goes back to Atlantic Daylight Time and the clock is set correctly. Then at some point later in the day, it'll go stupid again. If I turn off setting the time from the network, these problems don't happen, but then the clock will drift and be behind by 10+ minutes after a couple weeks.
So far, my solution has been to leave network time off, and occasionally turn it on just long enough for the clock to sync, then shut it off again. This is extremely frustrating.
Yeah, I have this on the latest stock N1. But, mine is slightly different. The time set from the network is 2mins behind GPS time. If I set the time manually, then hit the network time button it will drop 2 mins back. Doesn't do this on a Blackberry I have on the same network.
I thought I'd come back to this thread to report that my clock issues so far appear to be resolved after updating to 2.3.4 (manually via amon_ra + su zip to keep root).
I changed it back to set the time from the network yesterday, and have yet to experience any of the weird behaviour or lagging I mentioned in my previous post. Normally I would've seen something by now. I didn't see this mentioned in any of the bug fixes for 2.3.4, but so far so good...
I hope the update helps you guys out too.
Been pretty stumped by this and am wondering if anyone has ran into the same issue. The time in the top-right corner will sort of freeze. My lock-screen will always report the right time but the status-bar clock will be as far as an hour behind if I let the phone sit for a while. I found that rebooting, ticking the military time setting on/off, and airplane mode on/off will kind of kick the clock back in and it will update back to the current time but it will quickly lose the time shortly after. I have also tried disabling the network time sync but that has not worked as well. Finally, I have also noticed that this issue causes Alarms and Timers not to go off or go off at a later time which is a pretty big annoyance. I've read that this may be a bug with Android 6.0 but wanted to see if anyone here has ran into this same issue?
FYI, I am on the non-rooted 6.6 update.
Thanks guys!
EvansEssence said:
Been pretty stumped by this and am wondering if anyone has ran into the same issue. The time in the top-right corner will sort of freeze. My lock-screen will always report the right time but the status-bar clock will be as far as an hour behind if I let the phone sit for a while. I found that rebooting, ticking the military time setting on/off, and airplane mode on/off will kind of kick the clock back in and it will update back to the current time but it will quickly lose the time shortly after. I have also tried disabling the network time sync but that has not worked as well. Finally, I have also noticed that this issue causes Alarms and Timers not to go off or go off at a later time which is a pretty big annoyance. I've read that this may be a bug with Android 6.0 but wanted to see if anyone here has ran into this same issue?
FYI, I am on the non-rooted 6.6 update.
Thanks guys!
Click to expand...
Click to collapse
UPDATE: I think I have solved this one. I made sure my APN settings matched the ones ATT lists on their website EXACTLY and I have not seen the issue in 24 hours, will update if issue returns. Hope this info helps someone with the same issue in the future
I have this issue too... did APN settings make the difference?
My APN settings were fine, so the solution make sure your APN settings were correct did not work for me. What did work was I turned off Battery Optimization. Clock has been updating ever since.
Eniac77 said:
My APN settings were fine, so the solution make sure your APN settings were correct did not work for me. What did work was I turned off Battery Optimization. Clock has been updating ever since.
Click to expand...
Click to collapse
What all did you disable? I turned battery optimization off for "Clock", but am still experiencing this issue.
My widgets are very slow to update. It may take him a half hour or longer to update. I have checked battery optimization is not on for those apps, although one of those two apps that I have the problem with background data is grayed out. So I can't turn on allow background data. Not sure why that would be great out.
Any thoughts?
Wunderlist Task List.
DTG/GTD
But, I did some things poking around, don't remember for sure what all, but I had read that changing the Animation Scale etc to .5 would help. I did change that.
Before posting, I had found that Wunderlist was on battery optimization. Changing it didn't appear to help, so I posted. But now, it seems to be working. Maybe it's fixed. I'll post back in a day or two and indicate if it is still working or has stopped again.
Well, no, I'm not saying that. I'm just saying that's the only change I made, and at that point it had started working.
Are you having same problem, albeit different widgets?
FYI... mine is now not working again. I'm not surprised. But am frustrated.
Update...
I am finding that it does eventually update. It feels like the phone has been taken over by something. But, then, other things don't seem slow.
I just installed Gsam battery monitor, and ran the ADB cmds to try to identify apps using battery. Maybe I'll find something using a lot of battery and hence cycles.
My battery does seem to be going down quite a bit faster than it should.
It cleared up for a while after a factory reset,But it's back, and, I find that notifications from Lightflow come in 30 minutes after recieved.
It's like the phone is operating in molasses.
I'm beginning to think this phone is crap. If I switch back to my old Mate 9 it works fine.
jd14771 said:
certain apps aren't syncing well with pie. i had this same issue with Beautiful widgets, could not get the weather or time to update unless i manually updated it.
Under <Problem APP's> App Info > Battery
1.A Make sure the app is allowed background activity
1.B Make sure the app is not set to "optimized"
. (note: by default, the optimized list will only show apps that HAVEN'T been optimized, . you have to select "ALL" at the top to see all apps.)
Under <Problem APP's> App Info > Mobile Data
2.A Make sure "allow background data usage" is enabled.
2.B Make sure "allow app while data saver is on" if you have data saver enabled.
. (enable this if you want to be sure an app will receive background data.)
Click to expand...
Click to collapse
Thanks for the suggestions. I don't seem to be having any luck with that. Had already done those.
But!! ...
I just found a post after doing a global search for another issue I am having that seems to coincide with the widget issues, which is, Play Store freezing during updates. The post was in a Xaiomi forum. He said that he found if he had blue tooth on, his play store would constantly freeze. He turned off BT, and rebooted, and it worked.
I just did the same thing...and it is working...both the play store, and widget updates.
Interesting to have the great feeling of success, along with the frustration of a new (newly realized) issue yet remaining (BT).
Looking for a little further and through the settings on Bluetooth, I turned off Bluetooth scan. Now at first I would still have problems with Bluetooth on even though Bluetooth to scan was off. That of course would be very quickly after turning it on or off at cetera.
so this morning I get up having left Bluetooth on all night, with scan off, and everything's working fine. I did find last night that when I would first turn Bluetooth on even with skin off, the problems would be there. But of course when you first turn Bluetooth on it's going to scan anyway.
so I will update this thread little later after I see a little more about weather. Just having scan off actually cures the problem, in case someone else runs into this and it helps them.