It has probably happened again, Google has rolled out an update to users that is actually not intended for the public at all. Among other things, a user in the Google forum reports that he received Android 13 with the code “TP1A”. It is therefore not the current beta, but an early finished firmware.
You could probably live with that if everything worked afterward. But the affected owner of a Google Pixel 4 complains about the lack of SafetyNet approval so that some Google services no longer work. It has now emerged that the codename stands for the first finished release of Android 13.
Google is rolling out firmware that isn’t even available to the public yet
Unsurprisingly, Google is working on the final version of Android 13 to roll it out in late summer. But it is inexplicable how it could happen again that this internal version is played out to real users. That just can’t happen.
Android 13 is actually still in the official beta
We are currently still in the beta testing phase for Android 13. Beta 3.2 is officially out now, which is the first road to overall platform stability. According to Google’s schedule, at least one last beta should follow next July. So this firmware build that has been distributed is far too early and not intended for the public.
Now the user can only hope that Google will notice the error and push another update afterward so that at least the problems with SafetyNet are fixed. Switching back to an older Android version on your own is associated with some handicraft work and that is not for every user.
If you like our news and you want to be the first to get notifications of the latest news, then follow us on Twitter and Facebook page and join our Telegram channel. Also, you can follow us on Google News for regular updates.