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?
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.
The battery life on my 3D is far worse than my 4G, which had the extended battery (obviously). But until an extended battery is available for the 3D, I will have to deal. In order to make the battery last longer, I'd like to automatically disable background data (or auto sync) when the signal is less than 2 bars for a few minutes. Can any of you help me with this?
I've created a profile that will disable auto sync when signal is "2" or less. But I'd like to enhance it by saying it has to remain less than "2" for 3-5 minutes, so it isn't constantly enabling/disabling auto sync when I go through tunnels, etc.
Thanks in advance!
Dave
Power saver feature that is built in does that.
Oops, reading comp fail. I thought you said battery. Sorry.
-----
3vo. That is all that needs be said.
user7618 said:
Power saver feature that is built in does that.
Oops, reading comp fail. I thought you said battery. Sorry.
-----
3vo. That is all that needs be said.
Click to expand...
Click to collapse
Yeah, it does it when the battery reaches 15%. I want it to do this at any battery level, but only when the signal is weak.
Dave
I've made some progress with this. It's not perfect, but I think it will work.
First, create a task called "weak signal"
Check state, signal level is 0-1
Set variable %WEAKSIGNAL to 1
Wait 3 minutes
If %WEAKSIGNAL = 1
Disable auto sync (I wish this could be background data, but I don't see an option)
Then create a second task called "normal signal"
Check state, signal level is 3-8 (left a gap to prevent flapping)
Set variable %WEAKSIGNAL to 0
wait 15 seconds
If %WEAKSIGNAL = 0
Enable auto sync
I'll test this for a few days and see if it improves things. Coincidentally, I've been in areas with weak signals each day since I got the 3D. As a result, I'm lucky if the battery lasts 8 hours. I know disabling always-on data will fix this, but I don't like that the weather and everything stops syncing. Hopefully this will be a happy medium.
Dave
The tasker script seems to be working perfectly! It has definitely improved my battery life in weak signal areas, and I haven't noticed any ill effects.
Dave
dodgeboy said:
I've made some progress with this. It's not perfect, but I think it will work.
First, create a task called "weak signal"
Check state, signal level is 0-1
Set variable %WEAKSIGNAL to 1
Wait 3 minutes
If %WEAKSIGNAL = 1
Disable auto sync (I wish this could be background data, but I don't see an option)
Then create a second task called "normal signal"
Check state, signal level is 3-8 (left a gap to prevent flapping)
Set variable %WEAKSIGNAL to 0
wait 15 seconds
If %WEAKSIGNAL = 0
Enable auto sync
I'll test this for a few days and see if it improves things. Coincidentally, I've been in areas with weak signals each day since I got the 3D. As a result, I'm lucky if the battery lasts 8 hours. I know disabling always-on data will fix this, but I don't like that the weather and everything stops syncing. Hopefully this will be a happy medium.
Dave
Click to expand...
Click to collapse
Only problme I see with this is that it will kick in if you have a weak signal but still are connected to a wifi hotspot.
Could someone explain how to do this ? how to add this task? So i could save the battery when signal is low . Thanks
I am also having pretty horrific battery life, only 6 hours where my 4G use to last 36... So I thought I'd take this idea and make my own little modifications to it.
First I thought I would explain to those not familiar with Tasker. It is an app that allows you to setup your phone to automatically do "tasks" based on contexts. These contexts can be things like whether your connected to wifi, what time of the day it is, how good your signal strength is, anything your phone can "sense." And tasks are basically anything your phone can do, like turn on and off settings or launch applications.
Market Link: https://market.android.com/details?id=net.dinglisch.android.taskerm
Dev Website: http://tasker.dinglisch.net/
Now for my take on dodgeboy's 'profile'.
Code:
Context 1: Signal Strength, from 0 to 2
Context 2: Wifi Connected, Invert (Not connected to wifi)
Enter Task 1: Wait 1 min
Enter Task 2: Auto-Sync Off
Enter Task 3: Notify,[Title] Low Signal, [Text] Auto Sync Off, Permanent (I wanted a notification that auto sync was off)
Exit Task 1: Wait 15 sec
Exit Task 2: Auto-Sync On
Exit Task 3: Notify Cancel (Clears that Permanent notification)
Here is a link to my exported profile. Just put it on your phone's sd card. Once tasker is open, hit menu, profile data, import one profile.
http://db.tt/gb9w8O4
Let me know what you think. Haven't tested it beyond testing it at my desk by "death gripping" the phone.
ok, so there is some issue with my profile. Occasionally it will not perform the exit tasks, so the notification stays up and the auto-sync remains off. Not sure why it sometimes works and sometimes doesn't..? Maybe I'll try a 2 profile setup like the OP using a variable. Will post back if I get around to making a new profile(s), or if I figure out what is wrong with my current profile.
Thmstec said:
ok, so there is some issue with my profile. Occasionally it will not perform the exit tasks, so the notification stays up and the auto-sync remains off. Not sure why it sometimes works and sometimes doesn't..? Maybe I'll try a 2 profile setup like the OP using a variable. Will post back if I get around to making a new profile(s), or if I figure out what is wrong with my current profile.
Click to expand...
Click to collapse
Are you waiting for it to go through the wait period? The way I wrote it, it needs to stay in one state for a period of time before it changes whether or not the auto sync is enabled. If you want it to happen immediately, just write it without the variable and wait sections.
The reason I want it to wait is because when you enable auto sync, it seems to perform at least a partial sync immediately. I don't want this script to make the battery worse, because it is constantly syncing as it comes in an out of signal range.
Thanks for all the comments, very helpful !!! It is noticeable the battery saving
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.
Hello,
Like some of the other users, I had GPS problems after installing these two ROMs: connecting to the satellites took a very long time, if at all. Below I describe my fix, gathered from searching on the web, including here on XDA, and by using trial-and-error testing. Hope it helps others.
Install GPS Test by Chartcross. This helps monitor the GPS activities. There are other similar apps out there, but I like this one for the purpose of monitoring the GPS.
Install FasterGPS, by Dominik Schürmann. This is to edit the file /system/etc/gps.conf. You could edit it manually, but I like the GUI of this app.
Check if your /system/etc/suplcert/cacert.txt is "MIIDazCC......neEj8Nq/", then under the advanced settings, make sure SUPL_HOST is "supl.sonyericsson.com", SUPL_PORT=7275. Each cacert corresponds to a particular SUPL server. The above cacert is for the Sony server. If the host doesn't correspond to the cert, then you will not benefit from a quick retrieval of GPS info via the internet. Instead your GPS will download the info from the satellites themselves at a very slow rate (50 b/s according to Wikipedia). Your GPS would still work, but it won't acquire a fix quickly. Sorry I don't know what the cert for Google is.
Set NTP server to something close to you. Some people suggest to enter several servers (more can't hurt), some people suggest not to do that (more does hurt, if the previous ones fail.) I imagine that, at the higher level, the ntp pool servers don't usually fail. Thus I choose a single server that is close to me. In addition, I stay at the "country" level instead of going down to the numerical prefix level. (I.e. I don't bother with 0.uk.pool.ntp.org.) I figure going down to the numerical prefix level would more likely expose me to server failures.
Set INTERMEDIATE_POS=1 (enabled), then set ACCURACY_THRES=0 (passing all positions). With this value GPS Test usually reports satellites "in view" very quickly [<= 1 sec]. [Note: "in view" not "fix".] When I set the threshold to something non-zero (even a large value like 5000), it takes several seconds to see them.
Set ENABLE_WIPER=1, which supposedly turns on wifi positioning. Not sure what that does, but sounds like it can help . I assume the GPS system reads info from the wifi to get a rough estimate position. GPS Test probably isn't affected by this, although something like Maps might.
Set REPORT_POSITION_USE_SUPL_...=1. Again this sounds like a useful thing. My trial-and-error testing didn't discover anything conclusive about this. If anyone know more, please let me know.
Set DEFAULT_AGPS_ENABLE=TRUE, DEFAULT_USER_PLANE=TRUE. These are probably already true by default, but I figure it doesn't hurt to be explicit.
Reboot your phone if you had to change the SUPL setting. I had to do this to see the change. Would love to hear your experience on this.
With the above settings, GPS Test usually reports about 10 satellites in view in about 1 sec; satellites signals popping up above 10 db in about 5 sec, and the GPS acquiring a fix with about 4 satellites in less than 30 sec. All this _inside_ my house, which is a timber frame house with tile roof. I get this even with airplane mode on, i.e. no network connection!
If I use GPS Test to download AGPS data first, then the fix could be even faster, at less than 15 sec. And once the GPS has acquired a fix then, within a short time span, it will do so again very quickly (< 5 sec). Thus I have no problem as I switch from app to app and the GPS sensor turns on and off.
If my AGPS data is several days old, I still can get a fix in about 1 min.
Still, sometimes no matter what I do, the GPS would take more than 1 min to acquire a fix. Not sure why this happens, but it usually occurs after I haven't used the GPS in a while. In those cases I might have to wait up to 5 min for a fix.
Notes:
I assume you have root (since you managed to install ROMs )
According to the official ntp pool website,
As pool.ntp.org will assign you timeservers from all over the world, time quality will not be ideal. You get a bit better result if you use the continental zones (For example europe, north-america, oceania or asia.pool.ntp.org), and even better time if you use the country zone (like ch.pool.ntp.org in Switzerland)
Click to expand...
Click to collapse
More about my choice of accuracy threshold: if a threshold is active, it seems like the GPS would wait for the signal of a satellite to be of a certain strength before reporting it as in view. I figure it is better to just grab all the satellites possible, even if there is no signal yet.
The app GPS Status & Toolbox, by MobiWIA - EclipSim is also a very useful monitoring tool. I like the feature that reports how "stale" the AGPS data is. Wish GPS Test had this as well.
Toggling on the GPS from the settings menu simply allows apps to turn on the GPS. This doesn't use any battery. Only when an app starts using the sensor does it take energy. I recommend having this on. Having said that, do make sure you don't have any rogue app keeping your GPS engaged.
Install NTPSync, by Dominik Schürmann again. This helps set your clock. Not sure if this is necessary, but it gives me a good feeling that my clock is accurate
gps
its still not working
zivalarasa said:
its still not working
Click to expand...
Click to collapse
After running GPS Test out in the open for, say, 1 min, does it report any "in view" satellite at all? Any satellite have signal > 10db?
GPS Test
HHest said:
After running GPS Test out in the open for, say, 1 min, does it report any "in view" satellite at all? Any satellite have signal > 10db?
Click to expand...
Click to collapse
GPS test runs and doesnt find any sattellite. It ran for around 10 minz
zivalarasa said:
GPS test runs and doesnt find any sattellite. It ran for around 10 minz
Click to expand...
Click to collapse
I assume you had GPS working at some point prior to installing the ROM? If you've done all the steps (particularly steps 3, 5, and very importantly 9), then I'm afraid I'm out of suggestions.
spelling?
On the off chance... perhaps you have a spelling error?
I find it quite easy to spell "sonyericsson" wrong, especially the ericsson part. Now I have a way to memorize it: "Eric" (that's easy), "Eric's" (as in something belonging to Eric), ericsson = "Eric's son"
Hi Guys,
Ive spent a good amount of time today getting HyperDrive 15 (with safestrap) on my Vzw GS4. Its on and configured the way I like it, except for one thing.
The time is 1 hour ahead of what it should be. I think its not accounting for daylight saving time.
I can manually enter the timezone and it displays the correct time, but as soon as I switch it to get the time from the network, it bumps the time forward an hour.
Ive even tried the "Clock Sync" app and it also shows the time (both atomic and device) as being 1 hour ahead of what it should be.
Ive looked all over and I cant figure out how to get the network time to display the right time.
Any advice?
dead.burdock said:
Hi Guys,
Ive spent a good amount of time today getting HyperDrive 15 (with safestrap) on my Vzw GS4. Its on and configured the way I like it, except for one thing.
The time is 1 hour ahead of what it should be. I think its not accounting for daylight saving time.
I can manually enter the timezone and it displays the correct time, but as soon as I switch it to get the time from the network, it bumps the time forward an hour.
Ive even tried the "Clock Sync" app and it also shows the time (both atomic and device) as being 1 hour ahead of what it should be.
Ive looked all over and I cant figure out how to get the network time to display the right time.
Any advice?
Click to expand...
Click to collapse
What time zone are you in?
You say it's "not accounting for daylight savings time" but if daylight savings time is on, then you would be 1 hour ahead of standard time, which would account for you showing one hour fast if you're in an area that doesn't observe DST.
If the "Automatic time zone" is putting you in the wrong zone, then switch that off, set the proper timezone, and then see how it goes. If that works, try turning "Automatic time zone" back on - if that pushes you an hour ahead, contact your network provider and ask them to fix it.
k1mu said:
What time zone are you in?
You say it's "not accounting for daylight savings time" but if daylight savings time is on, then you would be 1 hour ahead of standard time, which would account for you showing one hour fast if you're in an area that doesn't observe DST.
If the "Automatic time zone" is putting you in the wrong zone, then switch that off, set the proper timezone, and then see how it goes. If that works, try turning "Automatic time zone" back on - if that pushes you an hour ahead, contact your network provider and ask them to fix it.
Click to expand...
Click to collapse
Im on mountain time. When i use network time, it causes the phone to be 1 hour ahead of what it should be. I can uncheck those, set the time, then recheck "use network time" and the time will stay correct, but if I set it to use the network time zone, then it causes the time to move forward an hour again.