As of writing, it's November 4th, 2025. I used Android's GPS clock feature, which lets Android get the clock time from GPS satellites. Strangely, my clock was set to March 21, 2006. I tested it again a day later, on November 5th, 2025, and the time was set to March 22, 2006, so both are one day later. I tested once again on November 10th after a reboot to make sure it wasn't just a temporary glitch, and indeed it set my date to March 27th, 2006.
This is Android 7, a version from 2017, which is an offline "workhorse". It seems newer Android versions don't even have the GPS-based clock feature. It is at least not in the date and time settings.
The last GPS rollover was in April 2019, and the next one will be in November 2038 (unrelated to the Year-2038-bug which will be in January), but I remember that the GPS-based clock worked just fine at least until 2023 (not tested since then), so can't be related to that.
Can you test the GPS-based clock setting with your phone to see if the same happens, if you have a phone with this feature? Is this a common issue?
I release this post into the public domain, CC0 1.0.
This is Android 7, a version from 2017, which is an offline "workhorse". It seems newer Android versions don't even have the GPS-based clock feature. It is at least not in the date and time settings.
The last GPS rollover was in April 2019, and the next one will be in November 2038 (unrelated to the Year-2038-bug which will be in January), but I remember that the GPS-based clock worked just fine at least until 2023 (not tested since then), so can't be related to that.
Can you test the GPS-based clock setting with your phone to see if the same happens, if you have a phone with this feature? Is this a common issue?
I release this post into the public domain, CC0 1.0.
