[Certified] Android 14.0.1 for Teracube 2e 2nd Batch (SN: 2021)

Yes, I get those too. :sweat_smile:

Some days I have to do Duolingo 3 times because it fails in those 5 minutes. No other Apps running in the background.
It helps if I push the power button for 1-2 sec after the screen freezes. Then only the current app crashes after 2–3 minutes of frozen screen but it doesn’t reboot.

But yes, I would say reboots 4 Times a day while charging or just lying around. Strangely it crashes mostly if i use apps that don’t take a lot of resources but are open for a long time (Duolingo, Royal road).

Do you have a recommended backup way? I have lots of apps with certificates (MFA, banking, certificates etc.) on it and it would be annoying to all redo them.

Either, honestly. I know I’m asking a lot. If you are willing/able, I think just the reset should be sufficient, but if issues persist, a reflash of the update would be prudent.

@Saijin_Naib any tips on the backup? With root I would try Titanium backup, but I can get that only by resetting, right?
Can I help you in debugging this issue?
Any log I can send or behaviour I should try to narrow it down?

Logs can be sent to support@myteracube.com using adb logcat and referencing this thread.

Hmm… Yeah, those backup solutions require rooting, which can lead to failure to boot and just complicate things further (IMO). I do not break out of trusted boot/locked bootloader. except to flash to /e/OS and then I re-lock everything. Others have success with root and those tools and like it.

With the design of more modern Android, the appdata storage is protected and things like adb desktop backup have been deprecated and do not perform as they were initially intended (full-device/state backup & restore), so you are kind of limited to what Google/Android decide should be accessible without root from MTP, and what the app’s vendor decides should be opted-in to being able to be backed up and restored with Android’s built-in account backup/restore.

/e/OS uses SeeedVault, which sidesteps some of that (it still respects apps that do not allow backups of their content), but it isn’t available on stock Android without rooting and some invasive steps.

Your normal user-dirs (DCIM, Documents, Downloads, Pictures, Videos) should hold most user-generated data that one might care about, but the appdata you want doesn’t have an easy method to backup & restore (by design).

sorry for the delay
factory reset done, problem is still around. regular reboots which also lead to a basically unsuable phone due to lag for some minutes after the reboot.
When i check the ram usage after a reboot it doesnt look like ram is fully used though. Only unusual thing for me are the two android systems being shown

2 Likes

That is super odd…

Are you able to re-flash the image again two more times? That should ensure both A/B partitions are updated and match.

just to make sure we are on the same page:
you want me to factory reset two more times? it can happen right after each other? nothing special to do on top?

Did you follow the recommendation to reflash, rather than just factory reset, especially if there’s still issues? If you did, and the problem is still happening, the followup recommendation from today is to reflash twice in a row, so that both the A and B versions of the system match the clean version, and don’t potentially restore whatever is causing your specific reboot storm.

I only did the factory reset.
it remained Android 14 after the factory reset which i found a bit odd.
Do you want me to install a previous version of Android? or just reinstalling Android 14?

Re-installing the latest official image twice in a row is my current recommendation. I don’t think we need to go back-level at this point, especially since this seems to be an isolated issue on your device. It feels like something didn’t go well in a flash or update on-device.

1 Like

Factory reset is just wiping your data and starting over with the existing version of the OS that’s currently installed. It won’t reset any corrupted parts of the system, just gets you back to where it was before you ran the initial setup on that specific OS version.
If anything was corrupted in the actual flash, then Factory Reset won’t fix it. It needs a new flash, preferably after verifying the hash or doing a new download if you can’t validate the file hash against known good.
Currently going through an issue with supporting MS Windows 11 that’s similar, where you need to actually download the installation files and re-run the setup (basically like an Android reflash) to fix some corrupted files in the system store. Doing a Windows reset just leaves it broken, because its immutable files aren’t as pristine as they should be. Probably an AV caused corruption, but… not really sure, just know the workaround at this point.

1 Like

Downloaded the installation file from this thread and installed it twice in a row.
So far it looks good, no restart that i know of.
It still shows the two different android systems in the ram usage overview but i don’t really care about that.

If you don’t hear anything again from me, consider it solved.

thank you so much

1 Like

well, guess that was too early.

reboots are back, frequency went down to like 2 a day and the impact it has on the usage has improved a lot. Its lagging way less after the reboots.

1 Like

What is your battery’s age, and about what runtime do you get?

Do you notice if the reboots happen when it is hot, or if you’re heavily using the device?

Is this update confirmed to work with AT&T?

I just exchanged my battery a couple of weeks ago so i have no issues with the runtime, especially compared to the previous battery.

I can’t see a link between temperature and usage, it happened on either end of the scale for both

1 Like

Are you using a microSD Card as shared internal storage on this device?

No, i am not using a card

1 Like

At this juncture, I’d suggest reaching out to support@myteracube.com to discuss warranty repair or replacement for your phone.

I repaired my Issues !!! No more reboots or crashing apps. :smiley:
Probably not all steps needed but this worked for me.

  • Backup to Google Backup (system > Backup)
  • I have taken out my sd Card.
  • Backup of /storage/emulated/0 with “DriveSync to GoogleDrive”
  • I followed this reset manuell for Android 13 Link
  • Skipped connection to google account
  • Download upgrade zip and Upgrade to 14
  • Connecting android to GoogleAccount
  • Restore of last Google Backup
  • Restore of /storage/emulated/0 with “DriveSync to GoogleDrive”
  • insert cd card
1 Like