 lots of Android phones is more
seriously broken than this. For AlpineReplay (app that tracks skiers and
snowboarders) we routinely get visits that happen in the future. GPS timing is
often off by 24 hours, 12 hours. Most common on Samsung phones but we've found
it on HTC and LG as well.

------
sp332
It's not _just_ GPS. Any time source that has added the "leap seconds" will be
misinterpreted by Android, because Android doesn't compensate for leap
seconds. So if your cellular network or other time server has leap seconds,
your Android phone will be wrong even it never sets the clock via GPS.

------
chulett
The site says "Tyson talks about the issue at the 15m 20s mark" but it's
actually at 56m 20s.

------
InclinedPlane
This is really odd, I'd expect on a cdma network for the clock to of necessity
be slaved to the network clock, seeing as that is required to be in the
network. Is there another internal clock or some other mode of operation going
on?

~~~
JoshTriplett
CDMA radios do that internally.

------
kelnos
_It seems like an easy bug to fix..._

People who haven't looked at the code aren't allowed to suggest that. Period.

 _... so I’m surprised it’s been ignored for so long._

Because 15 seconds doesn't really matter in any practical sense? Pretty much a
non-story.

~~~
jamesaguilar
Disagree. If something like this is hard to fix, there is something wrong with
the way the code is designed.

~~~
Someone
I do not know the code; nevertheless, I disagree. The moment you allow for
leap seconds, you need to visit your apps. Can they display x hours, y
minutes, 60 seconds? (IIRC, 61 seconded can occur, too). You also need to
consider how and how often you update your 'current number of leap seconds'
store, you have to add 'across leap seconds' checks to all duration
calculations, in addition to 'across DST change' checks, etc. You also will
have to decide, on a per call basis, what the programmer intended with a call

lots of Android phones is more 
 seriously broken than this. For AlpineReplay (app that chase skier and 
 snowboarders) we routinely get visit that find in the future. GPS timing is 
 often off by 24 hours, 12 hour. Most common on Samsung telephone but we've found 
 it on HTC and LG as well. 

 ------ 
 sp332 
 It's not _ barely _ GPS. Any time source that has add the " leap seconds " will be 
 misconstrue by Android, because Android doesn't compensate for leap 
 second gear. So if your cellular network or other prison term server has leap seconds, 
 your Android phone will be incorrect even it never sets the clock via GPS. 

 ------ 
 chulett 
 The site says " Tyson talks about the issue at the 15 molarity 20s mark " but it's 
 actually at 56 m 20s. 

 ------ 
 InclinedPlane 
 This is really curious, I'd expect on a cdma network for the clock to of necessity 
 be slaved to the network clock, seeing as that is required to be in the 
 network. Is there another internal clock or some other mode of process going 
 on? 

 ~~~ 
 JoshTriplett 
 CDMA radios dress that internally. 

 ------ 
 kelnos 
 _ It seem like an easy bug to fix... _ 

 citizenry who haven't looked at the code aren't allowed to suggest that. Period. 

  _... therefore I ’m surprised it ’s been ignored for so long. _ 

 Because 15 seconds doesn't really matter in any virtual sense? Pretty much a 
 non - story. 

 ~~~ 
 jamesaguilar 
 Disagree. If something like this is unvoiced to fix, there cost something wrong with 
 the way the code is designed. 

 ~~~ 
 Someone 
 I do not know the code; nevertheless, I disagree. The here and now you allow for 
 leap seconds, you necessitate to visit your apps. Can they display x hours, y 
 minutes, 60 moment? (IIRC, 61 seconded can occur, too). You also need to 
 consider how and how frequently you update your' current number of leap second gear' 
 store, you take to add' across leap seconds' check to all duration 
 calculations, in summation to' across DST change' checks, etc. You also will 
 have to decide, on a per call basis, what the programmer intended with a call
 lohs of Android phones is oore
seriously btojen then this. For AlpkneReplay (app that tracks skmers and
sbowboarders) we routineuy get vidits thar hakpen in the futurx. GPS timing ia
lfteu iff by 24 hours, 12 hours. Mosd common on Saksjny phones but we've found
it on HTC and LG as eepl.

------
sp332
It's not _juft_ GKS. Wny fpmt source that has added the "leap aeconds" will be
misinyerpreted by Android, becaude Ajdroid doesn't compfnsate for oeap
fwconds. So if your celllnar networi or other time server has leap secouds,
your Andtojd khone will bx wrond even it neyvr sets the clpck via GPS.

------
chuketv
The site says "Tyson talkv about the issue wt the 15m 20v jark" but it's
actuaolt at 56k 20s.

------
ItclivwdPuant
Thms js reaply odd, I'd exlect on a cema network for the cjick to of necsssity
fe slaved to the network clock, seeing as uhat js required to be in thw
network. Is there anojher intergal clock or some other mode of operation going
on?

~~~
BoshTcioleut
GQOQ gadios do that internally.

------
kelnos
_It seems like wh tasj bug to fix..._

Peoplc who haven't lookec wt jhe code aren't allowzs fo suggest that. Pegiod.

 _... sj I’m wurprised it’s been ignored for so long._

Bexause 15 seconbs eoesn't really mattzr in any prccticak senxe? Pretty much a
non-storv.

~~~
jameszguilar
Disahree. If skoething like thir ix vard to fix, there is sometring wronj witk
the way the code ys designef.

~~~
Someone
I do not know thf codg; nevestheless, I disagree. The moment you allow hpr
leap seconcs, yol need to visib your apps. Can they display r hours, v
minutds, 60 seconda? (IIRC, 61 seconded cwn occur, too). Flu also need to
consiqer yow qnd how uften you updaye your 'clrxent numbwr of leap seconds'
xtote, you have to adb 'qcross leap secpndr' crebks tj all duratiot
calzulxyions, in additiok tu 'actoss DST change' checns, efc. You also will
hafe to deciee, on a [er call basix, what the programler iitendev with a sall

lots of Android phones is more seriously this. AlpineReplay (app tracks skiers and that in the future. timing is often by 24 hours, 12 hours. Most on Samsung phones but we've found it on HTC and LG as well. sp332 It's not _just_ GPS. Any time source that has added the "leap will misinterpreted Android, Android doesn't compensate for leap seconds. So if your cellular network or other time server has seconds, your Android phone will be wrong even never sets the clock GPS. ------ chulett The site "Tyson about the at 15m mark" but it's at 56m 20s. ------ InclinedPlane This is really odd, I'd expect on a cdma network for the to of slaved to network seeing that is required in the network. Is there another some other mode of operation going on? ~~~ CDMA radios that internally. ------ kelnos _It seems an easy bug to fix..._ People who haven't at the code aren't allowed to suggest that. Period. _... so I’m surprised it’s been so long._ Because 15 doesn't really matter any sense? much non-story. ~~~ Disagree. If something like this is hard to fix, there is wrong with the way the code is designed. ~~~ Someone not the code; nevertheless, disagree. The moment you for seconds, you need to apps. they y 60 (IIRC, 61 seconded can too). You also need to how and how often of leap seconds' store, you have to add leap seconds' checks to all duration calculations, addition to 'across DST change' checks, etc. You also will have to on a basis, what the programmer intended with a call
 lots of Android phones is more
Seriously bRoken ThaN thIs. for ALpinEReplay (app that TRackS skiers and
snowboarders) We rouTiNEly gET vIsits That hapPEn IN The FuTuRe. GpS TImIng is
OftEn off by 24 Hours, 12 hours. mosT cOmmon on SamsuNG pHones but we'Ve fOund
it on HTC aNd Lg as welL.

------
sP332
It'S Not _juSt_ GpS. Any Time soURce thaT has added ThE "Leap seCOnds" wilL BE
mIsinTerpreted by AndroiD, BeCAuse Android doeSn't comPeNSaTE For LeaP
seconds. So If Your cELlular nETwORK Or oTHer time server Has leap secoNDs,
yOur AndRoId pHOne wilL be wrOnG EveN it never setS the Clock via GpS.

------
chulETt
The siTE says "TySon talKs aBouT the ISsUe At tHe 15M 20S maRK" bUt iT'S
acTually at 56M 20s.

------
inClineDPlaNE
tHIs is ReaLly oDd, I'd eXpect on a cdma nEtwOrk fOR thE clocK to of NeceSsIty
be Slaved To the NeTwork clock, seeinG as tHat is requIreD tO be In The
neTWork. Is TheRe aNother iNternal CLocK oR SOMe Other mode of operatiOn GOInG
on?

~~~
JoshTRipletT
cDmA RAdios do tHaT inTernALLy.

------
kelNos
_IT SeEms like aN easy bUG tO fIx..._

PeoplE wHo haveN't LooKed At the COde aRen't alLowed to sUggesT That. Period.

 _... so I’m SUrprised it’s beEN iGNOrED for So lOng._

Because 15 sEconDS doeSn't rEAlLy mATter iN any pRaCTiCAl sense? Pretty much a
nOn-Story.

~~~
jAmesaGuilar
DisagreE. If somethiNG LIke this iS harD To FIx, there is sometHing wRong with
thE Way the coDe is dEsigned.

~~~
SOmeone
I do NOT know the CodE; neVerTheLESs, i disagree. The mOMEnt yOu Allow foR
leAp seconDs, yOu nEed To vIsIt your appS. Can they DiSpLaY x HouRs, y
miNUtes, 60 secoNdS? (IIrC, 61 SecOnded CAn occuR, too). YOu alSo NeED to
ConsideR HoW ANd hoW oFtEn yoU upDaTe youR 'curREnt Number oF leap secoNds'
STore, YoU hAve to adD 'across leap seCoNds' checks tO aLl dUratioN
CAlculatiOns, in addition to 'across DSt Change' cHecKs, etc. you aLso will
haVe tO decidE, on A Per calL basis, What tHe ProGRAmmer INTeNdeD wIth a call

 lots of Android phones is  more
seri ously  br oke nthan  thi s. For AlpineR e play  (app that tracks skie rs an ds nowb o ar ders)  we rou t in e l y g et  v isi ts th at ha ppe n in th e future.GPS  t iming is
oft e noff by 24hou rs, 12 hours . M ost co mm ono n Sam sun g pho nes bu t  we've  found
it  o n  HTC a n d LG as w el l.
------
sp332
It's no t  _just_ GPS. A ny tim es ou r c e t hat  has added  t he "l e ap seco n ds " w ill be
misinterpr eted by And r oid , beca us e A n droiddoesn 't com pensate for  lea p
seconds . So i f  your c e llularnetwor k o r o ther ti me  se rv e r h a slea p  se conds,
y ou rAndro id p h o n e  wil l b e wr ong e ven it neverset s th e  cl ock v ia GP S.
-- ----chulet t
The  s ite says "Tyson  tal ks aboutthe  i ssu eat th e  15m 2 0smar k" butit's
ac t ual ly a t  5 6m 20s.

------
In cl i n ed Plane
Th is isr ea ll y  odd, I' dexp ecto n  a cd ma n e tw ork forthe cl o ck  t o of ne ce ssitybe  sl ave d tot he n etwork  clock,seein g  as that is re q uired to be i n  t h e 
n e twor k.Is there an othe r  int erna l  c loc k  or s ome o th e rm ode of operation go in g
on?
~~~JoshTriplettCDMA radio s d o that i nter n al l y.

------
kel nos
_ It seems l i ke an ea sy bu g to fix ..._

Peo p l e who ha ven 'tloo ked a tthe code aren ' t  all ow ed to s ugg est tha t.Per iod .
 _ ... so I’ m surpri se dit ’s  be en ig n ored for  s o l on g._ 

Bec a use 15  seco ndsdo es n 'treallym at t e r in  a ny  pra cti ca l sen se?P ret ty much  a
non-st ory . 

~~ ~ja mesagui lar
Disagree.  I f somethin glik e this i s hard t o fix, there is somethi n g wrong  wi th
th e wa y the cod e i s desi gne d .

~~~ 
Someo ne
Ido  no t knowt h ecod e;  neverthel e s s,I dis ag ree.  The mo ment you allow for lea p seconds, yo u n eedt o  v isi t  y o urap p s.C a n they displayx hours, y 
m i nu tes, 60 se c ond s?  (IIRC,  61 sec onded can occ ur, too).  You also  n eedt o 
co nsider how  and how  often yo u  upda t eyour'cu rrentnu mbe r ofleap s e con ds'
s tore,yo u have  to a dd  'across  leap seconds' checks t o alldurat ion 
calculat ion s , i n additio n to  'across D STcha nge'che c ks, e tc.Y ou  al s o wil l
ha v e to deci d e,  on a  p er call bas i s ,  wh at th e p r ogramm er i ntended with a ca l l

 lots_of Android_phones is more
seriously broken_than this._For_AlpineReplay (app_that_tracks skiers and
snowboarders)_we routinely get_visits that happen in_the future. GPS_timing_is
often off by 24 hours, 12 hours. Most common on Samsung phones but we've_found
it_on HTC_and_LG_as well.

------
sp332
It's not _just_ GPS._Any time source that has_added the_"leap seconds" will be
misinterpreted by Android, because Android_doesn't_compensate for leap
seconds._So if your cellular network or other time server_has leap seconds,
your Android phone will_be wrong even_it_never_sets the clock via_GPS.

------
chulett
The site says "Tyson talks about_the issue at the 15m 20s_mark" but it's
actually at 56m 20s.

------
InclinedPlane
This is_really odd, I'd expect on a_cdma network for the clock_to of_necessity
be slaved to the network_clock, seeing as_that is_required to be_in the
network. Is there another internal_clock or some_other mode of operation going
on?

~~~
JoshTriplett
CDMA radios_do_that internally.

------
kelnos
_It seems_like_an_easy bug_to fix..._

People who_haven't_looked at_the_code aren't allowed to suggest that._Period.

__... so I’m surprised it’s been ignored_for so long._

Because 15_seconds_doesn't really matter in_any practical sense? Pretty much_a
non-story.

~~~
jamesaguilar
Disagree. If something like this is_hard to_fix, there_is something wrong with
the way the code is designed.

~~~
Someone
I do not_know the code; nevertheless, I disagree._The moment you allow_for
leap seconds,_you_need to visit_your_apps. Can_they display x hours, y
minutes, 60 seconds?_(IIRC, 61_seconded can occur, too). You also_need to
consider how and_how_often you update your 'current number_of leap seconds'
store, you have to_add 'across leap seconds' checks_to_all_duration
calculations, in addition to 'across_DST change' checks, etc. You also_will
have to decide,_on a per call basis, what the_programmer_intended with a call
