Maven (famous)@lemmy.zip to Comic Strips@lemmy.world · 2 years agoBig Surpriselemmy.zipimagemessage-square61linkfedilinkarrow-up11.63Karrow-down132cross-posted to: nonpolitical_comics@piefed.social
arrow-up11.6Karrow-down1imageBig Surpriselemmy.zipMaven (famous)@lemmy.zip to Comic Strips@lemmy.world · 2 years agomessage-square61linkfedilinkcross-posted to: nonpolitical_comics@piefed.social
minus-squareDaPorkchop_ [they/she/it]@lemmy.mllinkfedilinkarrow-up1·2 years agoYeah, but even without network time updates your device’s internal clock is probably accurate enough to be able to tell if 2 years have passed or not. If it has an error of ≥2 years per 2 years, you need a new clock.
minus-squarefallingcats@discuss.tchncs.delinkfedilinkarrow-up1·2 years agoThe premise was that the spouse set the phone clock into the future. That has nothing to do with how accurate the RTC is (usually <10s/day)
Yeah, but even without network time updates your device’s internal clock is probably accurate enough to be able to tell if 2 years have passed or not. If it has an error of ≥2 years per 2 years, you need a new clock.
The premise was that the spouse set the phone clock into the future. That has nothing to do with how accurate the RTC is (usually <10s/day)