I've been having an issue that I thought was due to the ROM I'm running (dastin1015's CM10.1 Wild For The Night - Jun 21) until my dad reported it on his handset (not a smartphone, some Eriksson flip phone thing). The network-based time changes to an hour behind the actual time, with relative frequency.
When I view the clock/alarm settings it shows our timezone (EST) as GMT -4 instead of GMT -5, and also implies the phone thinks I'm not located in this timezone. It will display a "home" time (which is the correct time) as it does if you are traveling outside of your time zone, and display the current network-based time as an hour behind the real time.
Someone on the Sprint community forum mentioned that toggling airplane mode once (on and off again) should temporarily fix the issue. It does, but almost always, the phone will revert to the incorrect time a few minutes later.
Screenshots illustrating the problem:
http://goo.gl/89OJR
http://goo.gl/qSM9r
http://goo.gl/GbvUz
Has anyone else experienced this? If so, were you able to fix it? I use my phone as my alarm clock and I need the time to be accurate.
I have experienced this, but only on the stock unrooted ROM. I have been running Dastin's WFTN for longer than I can remember, and haven't had this problem with it. Sorry, I know that isn't very helpful to finding a solution for you, just thought I would confirm that I have seen the problem before.
Sent from my Evo 3D CDMA using xda premium
electrickoolaid said:
I've been having an issue that I thought was due to the ROM I'm running (dastin1015's CM10.1 Wild For The Night - Jun 21) until my dad reported it on his handset (not a smartphone, some Eriksson flip phone thing). The network-based time changes to an hour behind the actual time, with relative frequency.
When I view the clock/alarm settings it shows our timezone (EST) as GMT -4 instead of GMT -5, and also implies the phone thinks I'm not located in this timezone. It will display a "home" time (which is the correct time) as it does if you are traveling outside of your time zone, and display the current network-based time as an hour behind the real time.
Someone on the Sprint community forum mentioned that toggling airplane mode once (on and off again) should temporarily fix the issue. It does, but almost always, the phone will revert to the incorrect time a few minutes later.
Screenshots illustrating the problem:
http://goo.gl/89OJR
http://goo.gl/qSM9r
http://goo.gl/GbvUz
Has anyone else experienced this? If so, were you able to fix it? I use my phone as my alarm clock and I need the time to be accurate.
Click to expand...
Click to collapse
Go to settings-time and date, and disable nework time. That way you can set any time zone you want
Sent from Mwakious powered EVO 3D
Related
I work and live in different time zones, I noticed the atrix doesnt update the time unless I turn off the wireless and then re-enable it. Is this supposed to be normal?
settings -> Date and time
is automatic checked? how often are you on wifi, and how often on mobile data? I'm not sure it gets a constant check when on wifi.
cegna09 said:
settings -> Date and time
is automatic checked? how often are you on wifi, and how often on mobile data? I'm not sure it gets a constant check when on wifi.
Click to expand...
Click to collapse
The time is technically correct except for it is an hour less than it should be. It is set to automatic, im on wifi 20% of the day the rest mobile data. If I turn on airplane mode then turn it back off the correct time is displayed. I think they may have a bug
I travel for business quite and go between time-zones. I also find same issue happening with my new Atrix phone. If I turn the airplane mode on and off several times, time correct based on time zone I am in. Automatic date and time setting checked on.
Hi Everyone,
Atrix did not adjust automatically the time fthis morning. Is anybody else experiencing this issue?
In date and time the 'automatic' settings is checked.
I had to reboot for the time to be automatically updated.
Thank you.
Alarm went off an hour earlier than all the manually set clocks.
No glitch here. In Indiana on an eastern time zone.
I travel for work and the Atrix has worked fine for me in different time zones. My captivate failed to auto-switch one time though - so i think it has something to do with tower signals more then phone.
I reported this at launch, Im in indiana and live in CST but work in EST. This phone has not correctly changed timezones once, and didnt even update to the correct time for daylight savings time yesterday. The only way i've found to fix is either turn on/ turn off airplane mode or cycle power.
Is anyone else seeing a large amount of clock drift on their thunderbolts? I gain 122 seconds a day and 14 seconds at every boot according to ClockSync. ClockSync has been keeping my system clock corrected to date and I suppose that works but still, 2 min a day and 14 seconds at a reboot? That seems to be an awful lot.
So, is anyone else seeing this?
TB - Rooted, Das BAMF 1.4 but not OC'd.
mezman said:
Is anyone else seeing a large amount of clock drift on their thunderbolts? I gain 122 seconds a day and 14 seconds at every boot according to ClockSync. ClockSync has been keeping my system clock corrected to date and I suppose that works but still, 2 min a day and 14 seconds at a reboot? That seems to be an awful lot.
Click to expand...
Click to collapse
There's the actual time, there's Linux system time, there's the time kept by the RTC hardware, and there's cellular network time. They're all a bit different.
Clocksync is an NTP client, and tries to keep Linux system time in reasonable sync with external NTP servers, which should be in reasonable sync with the actual time (UTC). That's all on the order of milliseconds, if everything is working as it should.
CDMA and LTE network time is required to be in close sync with UTC, too - on the order of microseconds. This is a better source than a remote NTP server. In fact, some Stratum 1 NTP server get _their_ time from a CDMA network.
Most CDMA phones get their time from the network, and I suspect the TB does, too. I don't know if Android uses the kernel time discipline to keep the system time in sync with network time, I suspect it does.
I doubt Clocksync does anything good on a CDMA/LTE phone, the time received from the network is better, and probably being used to begin with. As I recall, GSM/UTMS base stations only need frequency accuracy, so Clocksync is probably useful there.
The difference you're seeing on boot is probably the difference between RTC time and system time, after the latter has been synched with network time. The RTC is only there to keep time when the device is powered off, so not much money is put into keeping it accurate. A CDMA/LTE phone is expected to be getting time from the network while in use.
So you're saying that I shouldn't be using ClockSync then as it's setting my system time different than the CDMA/LTE time my TB should be getting from the network? Or is it just redundant and unnecessary?
Also, I could see the RTC being 14 seconds off network time but once the phone is up and connected to the Verizon network, shouldn't it sync it's time with the CDMA/LTE time? Until I force ClockSync to update the system time, it remains 14 seconds off from NTP time, regardless of time since the phone booted.
It appears that Android may be setting system time to match GPS time. See the issue discussed at code.google.com/p/android/issues/detail?id=5485
Huh, that's a good read. Seems that no only is Android setting the time to GPS time, but doing it incorrectly. I guess though, if I turn on my phone in a building where it can't get a GPS signal, will my phone sync the system time to GPS time next time it can see the sky?
I have a program to sync the internal clock every three days to the atomic clock (I'm not expecting it to be as good as that!) but on average it's out by nearly 30sec every three days, 10sec a day! WOW!
Anyone else noticed this?
I would expect maybe no more than 0.5sec every day for a device like this.
Are you stock? I'd set my network to 2g only, but if I powered off and then back on, it would be reset to both on stock, but when I rooted, the problem went away.
I only bring it up in case the date/time setting is another of those toggles that doesn't save and therefore resetting your date/time with the network.
My amaze keeps asking me for the time zone when it powers up. The only way around it is to disable network time.
I've been using the app BetterBatteryStats as recommended by XDA to determine why my RAZR is awake much of the time, even when the screen is off and data is turned off. It turns out the problem is the internal process IMS_Data_Retry. This process apparently keeps attempting to establish a data connection over cellular data, at least 4G LTE. It aquires a wake lock while doing its work. This one process can keep the phone awake 95% of the time. The only way I have found to semi-stop it is to turn on 4G LTE. Even then, while it stops consuming CPU time (supposedly), the count of retry attempts keeps going up. (Putting the phone in Airplane mode also stops it, but then calls are stopped as well.)
There is a setting in /system/build.prop that I thought controlled this process:
ro.cdma.data_retry_config=default_randomization=2000,max_retries=infinite, 0, 0, 120000, 180000, 540000, 960000
I looked at some code references I found ( http://hi-android.info/src/com/android/internal/telephony/cdma/CdmaDataConnectionTracker.java.html ) and learned that the above values are in milliseconds. It seems that the default_randomization value is added to the other values in the list to create a schedule of retry attempts, but I wasn't able to figure out all the parameters to the method, if I even have the right one. I tried changing "infinite" to a small number under 10, but it had no effect - the process just keeps retrying forever.
Is there a dev out there who knows more about this? I want to limit this process because I seldom use cellular data right now and am usually on WiFi. It hinders any attempt to extend battery life. Is it a bug? Is it fixed in a later release (I'm on .748 stock) ? Do any of the custom ROMs have this problem? Can the build.prop setting I found be given values that limit the amount of time this process holds wake locks?
Thanks.
Did you ever get any resolution on this? For me, I think the problem started with the ICS update this summer. I constantly have gsm_data_tracker, RILJ, and IMS_Data_Retry using up the battery (in that order from highest to lowest). I tried wiping cache which helped the 1st time it cropped up and then it came back. I also tried a tip I saw somewhere for turning on airplane mode, rebooting, and turning off airplane mode (though mine as soon as it reboots, it already turns off airplane mode which it shouldn't). That worked for several weeks, but I had to do it EVERY DAY when I got to work. I think it's something with the 3g repeaters in the building. I did have it so it was wifi only (mobile radio off) on my work profile in profile scheduler, but then I needed cell for some mms stuff, so I ended up enabling it again. Basically when I come in the building and forget about my phone for an hour or 2, I go to get it out of my backpack and it will be hot from processing and 20% or more of the battery gone when I've done nothing in 2 hours of being at work. I saw somewhere that someone though either gsm_data_tracker or RILJ was related to something with the alarm, which I do use my phone as my alarm, but I use a 3rd party app. With the time change, there were a few days I woke up before it ever went off, so I turned it off before it did alarm. There were no differences with the partial wakelocks or battery drain in those cases. Unfortunately, I don't have another alarm readily available to get up for work right now and on the weekends when I don't need an alarm, I can't replicate the cell repeater at work issues, since I wouldn't be around the cell repeaters. As fart as in the building at work, until I reboot with airplane mode and all of that, the cell signal will bounce between like 0 bars/3g and lots of bars (no indication of network) and some bars with 1x network. It's all over the place. The airplane mode/reboot used to stabilize that, but it doesn't seem to be doing the trick anymore the last few days that I've tried that. I have to leave my phone on the charger as much as possible at work so that I don't leave for the day with a dead phone.
I live in Saskatchewan, Canada, which doesn't do daylight savings time and uses the same timezone (CST) all year.
My phone is set to use network-provided time and timezone, and it's an hour off this morning due to using CDT instead of CST. I changed the phone manually to a different timezone and time, then changed it back to "network-provided" time and timezone, and it flipped to the correct time and timezone.
So it seems like something is wrong with the phone, and not with the network.
I talked to the cell provider support, apparently it's affecting a bunch of Android phones.
If you find a solution to this, please let me know.
I live in Iran and this new year, the stupid parliament decided to discard the daylight time saving. But apparently they haven't make the necessary arrangements with the phone companies and Time Authorities. My galaxy phone is using network-provided time, and it's an hour ahead. I tried changing the time manually but Banking apps and VPN won't work with manual adjusting of time.