Thank you, did so.
1 Like
The Zirconia update failed for me (13 Beta 1 to 13 Beta 2) three times (rebooted each time). Finally my phone appeared to ālockā so I left it sit for 45 minutes. It got to the āunable to start Androidā screen so I did a factory reset. Everything worked after that, & the update to Beta 2 worked without a hiccup.
This makes me wonder if many of us who had problems just kept updating and never āwipedā the phone for a clean install. I updated to the Android 12 Betas from 11, then 12 to 13. Maybe some āleftoversā were goofing things up?
1 Like
Update:
I did the Return to the Original Android 10 (RttOA10) and install the Beta 2 update. Running the RttOA10 batch file at the Windows command prompt was a little brute force-ish but it worked the first time. After getting my Google account re-established on the phone so I could download the new Beta 2 image, the installation of the image went smoothly. Hopefully the next update will be a little more straight forward.
2 Likes
Can you check if you emailed the logs to devs@myteracube.com? I donāt see them in the inbox.
1 Like
Awesome, thanks so much! That it passes basic integrity means Iām likely to try upgrading again when I have a weekend to burn. If it ends up passing the upgrade and not forcing a factory reset for corrupted data, Iāll post whatās different. If it still requires the wipe, no sense in muddying the waters.
1 Like
Quick question: will there be a way to upgrade on zirconia from Android 12 to 13 the same way we upgraded from 10 ā 11 and from 11 ā 12 beta? I think Iāve read somewhere one needs to upgrade the installer, so is there a way to avoid that?
1 Like
The notes for upgrade to this build are in the opening post:
Things may change with a subsequent release, but anything we know about that will be posted alongside the new release.
Word to the wise - this is definitely still a Beta. I did the upgrade from 12 and after installing the APK to patch the installer, everything went well. After about 1 day of use my phone screen went dark and started boot looping. After removing the battery and putting it back in, I got an error in (what looked like) fastboot saying there was corruption, and the system needed to be recovered.
I lost my data (nothing important) and so far itās been stable since yesterday, but Iām not sure if this was a āone time thingā or a ticking time bomb.
Otherwise the system feels great - snappy, seemingly great on battery, and the camera is SO MUCH faster. Good job team!
4 Likes
Just upgraded to 13.0.1 again and no mandatory wipe this time. I believe the failure point was in trying to avoid the mandatory wipe by disabling my screen lock first, before kicking off the upgrade. It makes sense that the storage is still encrypted and the Android 11 is aware of how to handle it, but Android 13 sees it as a fresh OS and has no idea how to deal with an encrypted system with no hint as to the key.
There does seem to be a live wallpaper bug in 13.0.1, regarding app intents. When I try to apply a live wallpaper, I get the following error:
No activity or application found to handle: android.service.wallpaper.CHANGE_LIVE_WALLPAPER
1 Like
Horrible experience. I updated to Android 13 the day after getting my new TeraCube with seemingly no issues. Now that I have had time to evaluate, Iām getting nothing but problems. SD card randomly wonāt mount after restart. Apps take 15 sec + to load and are glitchy. Screen randomly blanks requiring me to pull the battery to restart. The most annoying is that I canāt receive or make phone calls. Going to reset and try Android 12 to see if it is any more stable.
1 Like
Welcome!
Sorry to hear you are having such issues.
Would you be open to flashing 13 Beta 2 again and using the phone for a bit without the MicroSD card and not restoring your prior Android backup?
It would help to isolate where you might be having problems.
Iāve tried resetting to factory load and am having no luck there either. I followed the directions to the letter and the PC still refuses to recognize my phone via USB. Iāve tried installing the drivers several times just to be certain. Even tried the more āmanualā method of using the SP flash tool directly. No dice.
Any suggestions?
1 Like
I can try this. But I didnāt use a flash method to install 13. How do I go about doing this? Same process as before?
1 Like
Yep! Be aware that with SPFlash your phone must be powered off when connected to be detected.
1 Like
As a note, my sdcard loads on every second reboot. When it boots and says the sdcard canāt be loaded, just tell it to reboot and it will load up the second time. It happen consistently for me, but knowing it will work after the reboot makes it fairly simple.
Android 13 hangs at the unlocked bootloader screen for two minutes before moving on. It seems excessive.
Googleās Webview has some sort of issue, whether itās with our Android 13 or the webview itself. Whichever version is loaded when it boots up wonāt work. Switching to the Beta/Dev/Canary webview will solve the issue, until the next reboot. When it reboots and the alternate build fails to render, just switch back to the default webview. Thereās a chance this is caused by the sdcard loading issue.
That being said, despite those issues, itās been fairly snappy in general, and itās nice to be able to tap to pay without having a fail-tap and re-unlock every time, like Android 11 had been doing since Google hardened their validation several months ago.