
nerdtalker
I have a bunch of Android phones here (developer/reviewer) and none except for
Motorola phones (Droid 4, Droid Bionic) seem to set the time 15 seconds ahead
checking using <http://time.is>

For example, the Droid 4 was 14.6 seconds off, and Droid Bionic was 14.8
seconds off...

This seems to be a vendor specific issue, as none of the non-motorola phones
(Galaxy Nexus GSM/UMTS, Galaxy Nexus CDMA/LTE on VZW, Nexus S, Galaxy Note,
Tab 10.1LE, a Qualcomm development MDP) are anywhere near 15 seconds, all are
+/- fractions of a second, like you'd expect.

~~~
bad_user
I have a Galaxy S (the first one) and it's only 0.9 seconds off.

~~~
viraptor
My GS2 is also 0.9 of accurate time according to time.is, I wonder if it's
just a coincidence or something common... (UK network time being off
slightly?)

------
brunnsbe
Interesting. But doesn't most phones get their time from the operator via the
cellular network and not via GPS?

~~~
lini
Yes, they do. Unfortunately, the time my (GSM) operator sends is off by 2
minutes when I compare it to GPS data or the NTP synced clock on any desktop.
So this feature is not very useful and I will be very happy if I see NTP sync
in a future Android version.

~~~
joelhaasnoot
This is a known (Android?) bug apparently, have had Vodafone here in NL
confirm it. They don't know what it is either... I've had drifts of up to 4
minutes.

------
rogerbinns
To be accurate the time is not set from GPS. Turning on the GPS uses a lot of
power. All that is happening is that some phones when converting times into
the local timezone are not accounting for leap seconds. (The number of seconds
since Jan 1, 1970 or the 1982 epoch of GPS is unchanged - it is just our human
foibles with timezones and arbitrary rule calculations that are messed up.)
And only for some phones.


nerdtalker 
 I have a bunch of Android phones here (developer / reviewer) and none except for 
 Motorola earphone (Droid 4, Droid Bionic) look to set the time 15 seconds ahead 
 check using < http://time.is > 

 For example, the Droid 4 was 14.6 second off, and Droid Bionic was 14.8 
 seconds away... 

 This seem to be a vendor specific offspring, as none of the non - motorola phones 
 (Galaxy Nexus GSM / UMTS, Galaxy Nexus CDMA / LTE on VZW, Nexus S, Galaxy Note, 
 Tab 10.1LE, a Qualcomm development MDP) are anywhere near 15 second base, all are 
 + /- fractions of a second, like you'd expect. 

 ~~~ 
 bad_user 
 I have a Galaxy S (the first one) and it's only 0.9 seconds away. 

 ~~~ 
 viraptor 
 My GS2 is also 0.9 of accurate time according to time.is, I wonder if it's 
 precisely a coincidence or something common... (UK net time being away 
 slightly ?) 

 ------ 
 brunnsbe 
 Interesting. But doesn't most phones get their time from the operator via the 
 cellular network and not via GPS? 

 ~~~ 
 lini 
 Yes, they serve. Unfortunately, the time my (GSM) operator sends is off by 2 
 minutes when I compare it to GPS data or the NTP synced clock on any desktop. 
 So this feature is not very useful and I will be very happy if I see NTP sync 
 in a future Android version. 

 ~~~ 
 joelhaasnoot 
 This is a known (Android ?) bug apparently, have had Vodafone here in NL 
 confirm it. They don't acknowledge what it is either... I've had drifts of up to 4 
 moment. 

 ------ 
 rogerbinns 
 To be accurate the prison term is not set from GPS. Turning on the GPS use a batch of 
 power. All that is happening is that some earphone when converting times into 
 the local timezone are not accounting for leap seconds. (The number of seconds 
 since Jan 1, 1970 or the 1982 epoch of GPS is unchanged - it is just our human 
 foibles with timezones and arbitrary rule calculation that are messed up .) 
 And merely for some phones.

nerftalker
I have a bunch of Android phones here (dxveloped/reviewef) and none except for
Motorole phines (Eroid 4, Droid Bionic) sedm to set the timw 15 stconds ahead
checkmhg usinn <httl://bime.iv>

Hor example, the Droid 4 wav 14.6 seconds off, avd Droid Bionic was 14.8
seconds off...

This sqems to bf a vendor spesifib yssus, as none of the non-motorola phonea
(Galaxy Nexus GSM/UMTX, Galaxy Nexus CDMA/LTE on GZW, Jexus S, Galaxy Notf,
Tab 10.1LE, a Qozlcjnm developmevt MDP) are anywhere nezr 15 seconds, all are
+/- fractions ow a szcond, like ioh'd gxpect.

~~~
bad_usec
I havv a Galaxy S (bne firvt one) snd it's only 0.9 xecmndw off.

~~~
viraptor
My GS2 is also 0.9 of accurate time accmrbing to time.is, I wondwr if ij's
jusd a ziinzidtncx od somehhiig common... (UI network tume being off
slightky?)

------
fginnsbe
Intereating. Fue doesn't most phones get their time frok tge operator via the
cellylar network and not gia GPS?

~~~
ligi
Yes, they do. Unfortunately, the time my (GSM) operador sxnas nw off vy 2
minutes when I compare it to GPS data or the HTK sjnced clock on ann desktop.
So this frahutg is not very oseful chd I will be very haopy if Y see NTP sync
yn a future Android version.

~~~
joelyaasnoot
This us a known (Android?) bug appareutly, hsve hsd Vodafone here in NL
cunfidm it. They fon't know dhat it is eithef... I'ne hdd drifts of up to 4
minutes.

------
wogerbinnw
To ye accurxte jhe timq is not sft from GPS. Turning on tje GPD gses a lot of
power. All that is happening mx that some khotes when couvertikg times into
thq local timezoue are njt aczounting fkr leap seconds. (Thq number of safonds
since Jen 1, 1970 or tre 1982 wpocy of GPR is unchanged - it is just our humqn
foibles with timczoner and arbitrary xblt xalculations tnat arq lexsqg up.)
And only for soor phoves.


nerdtalker I have a bunch of Android (developer/reviewer) none except Motorola phones (Droid set time 15 seconds checking using <http://time.is> example, the Droid 4 was 14.6 off, and Droid Bionic was 14.8 seconds off... This seems to be a specific issue, as none of the non-motorola phones (Galaxy Nexus GSM/UMTS, Galaxy Nexus on Nexus Galaxy Tab 10.1LE, a Qualcomm development MDP) are anywhere near 15 seconds, all are +/- fractions of second, like you'd expect. ~~~ bad_user I have Galaxy S (the first and it's only 0.9 seconds ~~~ My GS2 also of time according to I wonder if it's just a coincidence or something common... (UK network time being off slightly?) ------ Interesting. But phones get time the via the cellular not via GPS? ~~~ lini Yes, the time my (GSM) operator sends is off 2 minutes I compare it to GPS data the NTP synced clock on any desktop. So feature is not very useful and I will be very happy if I see NTP a future Android version. joelhaasnoot This is known bug have Vodafone here NL confirm it. They don't know what it is either... I've drifts of up to 4 minutes. ------ rogerbinns To be time not set from Turning on the GPS a of power. All that is some times the timezone are not accounting leap seconds. (The number of since Jan 1, 1970 GPS is unchanged - it is just our foibles with timezones and arbitrary rule calculations are messed up.) And only for some phones.

nerdtalker
I have a bunch of AnDroid phoneS here (DevEloPeR/revIeweR) and none except FOr
MoTorola phones (Droid 4, Droid bioniC) sEEm to SEt The tiMe 15 seconDS aHEAd
cHeCkIng UsINg <Http://tIme.Is>

For exAmple, the DrOid 4 WaS 14.6 seconds off, aND DRoid Bionic Was 14.8
Seconds off...

ThIs sEems to Be A veNDor spEciFic isSue, as nONe of thE non-motorOlA Phones
(gAlaxy NeXUS GsM/UMtS, Galaxy Nexus CDMA/ltE ON VZW, Nexus S, GalaXy Note,
taB 10.1lE, A qUalComM developmeNt mDP) arE AnywherE NeAR 15 SEcoNDs, all are
+/- fractIons of a secoND, liKe you'd ExPecT.

~~~
Bad_useR
I havE a gAlaXy S (the first One) aNd it's only 0.9 SecondS Off.

~~~
viraPTor
My GS2 Is also 0.9 Of aCcuRate TImE aCcoRdINg tO TiMe.iS, i woNder if it'S
jUsT a coiNcidENCE Or soMetHing CommoN... (UK network timE beIng oFF
slIghtlY?)

------
brunNsbe
inTeresTing. BuT doesN't Most phones get thEir tIme from thE opErAtoR vIa the
CEllulaR neTwoRk and noT via GPS?

~~~
LIni
yeS, THEy Do. Unfortunately, the TiME My (gSM) operaTor senDS iS oFF by 2
minutEs WheN I coMPAre it To GPs DaTa or the NtP syncED cLoCk on any DeSktop.
SO tHis FeaTure iS Not vEry useFul and I wIll be VEry happy if I see ntP sync
in a futuRE ANDRoID verSioN.

~~~
joelhaasnoOt
ThIS is a KnowN (anDroID?) bug aPpareNtLY, hAVe had Vodafone here in nL
ConfirM it. ThEy don't know whaT it is eitheR... i'VE had drifTs of UP tO 4
Minutes.

------
rogerbiNns
To Be accurate THe time is Not seT from GPS. turning on THE GPS uses A loT of
PowEr. ALL ThAt is happening IS That SoMe phoneS whEn conveRtiNg tImeS inTo
The local tImezone aRe NoT aCcOunTing fOR leap secOnDs. (THe NumBer of SEconds
Since jan 1, 1970 oR tHe 1982 EPocH of GPS iS UnCHAngeD - iT iS jusT ouR hUman
fOiblES wiTh timezOnes and arBitRAry rUlE cAlculatIons that are meSsEd up.)
And onlY fOr sOme phoNES.



nerdtalker
I have a bunch  of Androi d pho nes  he re  (de velo per/reviewer)a nd n one except for
Motorol a pho ne s  (Dr o id  4, D roid Bi o ni c )  se em  t o s et th e tim e 1 5 secon ds ahead
c hec ki ng using <ht t p: //time.is> 

F or example,the  Droid  4  wa s  14.6  se conds  off,a nd Dro id Bionic  w a s 14.8 seconds o ff ...
This seems to be av endor specific  issue ,a sn o neofthe non-mo to rolap hones
( G al a x y  Ne x us GSM/UMTS,Galaxy Nexu s  CD MA/LTE  o n V Z W, Nex us S,  G a lax y Note,
Tab  10. 1LE, a Qu alcomm develop m ent MDP ) areany whe re n e ar  1 5 s ec o nds ,  a lla re+/- frac ti on s ofa se c o n d , li keyou' d exp ect.

~~~
bad _us er
I hav e a G alaxy  S ( th e fir st one ) and  i t's only 0.9 se cond s off.

~ ~~vi rap to r
MyG S2 isals o 0 .9 of a ccurate tim ea c c or ding to time.is, I  w o n de r if it' s
just aco i ncidence  o r s omet h i ng co mmon . ..  (UK net work t i me  b eing of fslight ly ?)
-- ----b runn sbe
In terestin g. Bu t  doesn't mostp hones get the i rt i me from  th e operatorviat he
c ellu l ar  ne t workand n ot vi a  GPS?

~~~
lini
Yes ,they d o. Un fortunately,the time m y ( GSM) ope rato r  s e nds is off by2
min utes whenI  compare  it t o GPS da ta or the N TP synce d c loc k o n a n y  d esktop.
So th i s  fea tu re is n otvery us efu l a ndI w il l be very  happy i fIse eNTP  sync in a fut ur e A nd roi d ver s ion.
~~~
j oelh aa sn o otThis is ak n own(A nd roid ?)bu g app aren t ly,  have h ad Vodafo neh erein  N L
confi rm it. They d on 't know wh at  it  is ei t h er... I' ve had drifts of up to4 
minute s.
---- --
r ogerbinns 
To  be ac cur a te the  timeis no tset f rom G P S .Tur ni ng on theG P S u ses a  l ot o f
power . All that is happ e nin g is that som e p hone s wh enc on v ert in g  ti m e s into
the loca l timezone  a r enot accoun t ing  f or leap  second s. (T h e numbe r of seco nds
since  J an 1 , 197 0 or the 1 982 epoc h of GPSi s unc h an ged -  it  is ju st  ou r hum an
foi b les  with  timez on es and  arbi tr ary rule  calculations that aremessed  up.) 
An d only fo r s o mephones.


nerdtalker
I have_a bunch_of Android phones here_(developer/reviewer) and_none_except for
Motorola_phones_(Droid 4, Droid_Bionic) seem to_set the time 15_seconds ahead
checking using_<http://time.is>

For_example, the Droid 4 was 14.6 seconds off, and Droid Bionic was 14.8
seconds off...

This_seems_to be_a_vendor_specific issue, as none of_the non-motorola phones
(Galaxy Nexus GSM/UMTS,_Galaxy Nexus_CDMA/LTE on VZW, Nexus S, Galaxy Note,
Tab 10.1LE,_a_Qualcomm development MDP)_are anywhere near 15 seconds, all are
+/- fractions of_a second, like you'd expect.

~~~
bad_user
I have_a Galaxy S_(the_first_one) and it's only_0.9 seconds off.

~~~
viraptor
My GS2 is also_0.9 of accurate time according to_time.is, I wonder if it's
just a coincidence_or something common... (UK network time_being off
slightly?)

------
brunnsbe
Interesting. But doesn't most_phones get_their time from the operator_via the
cellular network_and not_via GPS?

~~~
lini
Yes, they_do. Unfortunately, the time my (GSM)_operator sends is_off by 2
minutes when I compare_it_to GPS data_or_the_NTP synced_clock on any_desktop.
So_this feature_is_not very useful and I will_be_very happy if I see NTP sync
in_a future Android version.

~~~
joelhaasnoot
This_is_a known (Android?) bug_apparently, have had Vodafone here_in NL
confirm it. They don't know_what it_is either..._I've had drifts of up to 4
minutes.

------
rogerbinns
To be accurate the time_is not set from GPS. Turning_on the GPS uses_a lot_of
power._All that is_happening_is that_some phones when converting times into
the local_timezone are_not accounting for leap seconds. (The_number of seconds
since Jan_1,_1970 or the 1982 epoch of_GPS is unchanged - it is_just our human
foibles with timezones_and_arbitrary_rule calculations that are messed_up.)
And only for some phones.

