Android 17 QPR2 Beta 1 is randomly sending Pixels to a date that does not exist

It’s all the time anticipated that an Android beta can have bugs. It’s what they’re for — discover all of the bugs and (hopefully) repair them earlier than the secure replace comes out. Normally, these bugs come all the way down to issues like app crashes, system freezes, or battery drains. However the Android 17 QPR2 Beta 1 has achieved one thing I by no means anticipated on my Pixel 10 Professional: reinvent time as we all know it.

It began one morning when it was virtually 4 AM, and as I pulled down my fast settings panel to show off darkish mode, I noticed the date, which was July twenty eighth on the time, instantly develop into “0 Jan.” I’m undecided if I ought to name that January 0th or Jan 0rd, however both manner, it was an odd factor to witness. A reboot mounted it, however then the following day the identical bug occurred once more, this time setting the date again to Wednesday, January 1st. That made a bit extra sense, given January 1st was certainly a Wednesday, besides, this can be a unusual bug.

I’m not the one one that is having this bizarre little bug. I discussed it on a associated Reddit thread, and a minimum of one different Pixel consumer commented that they, too, have a Pixel that thinks it’s a flux capacitor.

I’m undecided what would trigger a bug like this, however in case you’re within the QPR2 Beta 1 and encounter it, a reboot fixes it. I wouldn’t trouble, although. The time within the standing bar stays right, and the calendar and duties apps are unaffected, so there isn’t a purpose to panic.

I think about this will likely be mounted in one of many beta updates we get earlier than Android 17 QPR2 turns into secure. Have you ever encountered this date-altering bug or the rest bizarre and humorous within the newest beta? I’d love to listen to about it.