Conversation

twitter.com/DanielMicay/st Due to A/B updates and rollback, this isn't really as bad as it sounds. If you were using the beta channel and installed this problematic release, then after upgrading you're prompted to wipe due to incompatible data. If you don't it'll just fail to boot.

Quote Tweet

twitter.com/DanielMicay/st Unfortunately, some users upgrading from this cancelled beta release may encounter a broken upgrade path to the next beta release where the device forces you to do a factory reset. This is caused by downgrading the kernel, but we're unsure exactly why.

Show this thread

1

After failing to boot a few times, it rolls back the newer beta release and goes back to the problematic one. It'll successfully boot up again and will then try the upgrade process again. Need to back up the data and accept wiping the next time around. Nice having A/B updates.

2

Replying to

so how do you actually back up data without google services (which aren't a thing on grapheneos afaiu)? i've yet to find a way to do it that wouldn't make having a locked bootloader completely pointless, e.g. TWRP

1

Replying to

We include Seedvault which provides support for backing up app data. Some apps go out of the way to blacklist backing up data, which they're supposed to do for caches, hardware-specific data, data that can be easily re-generated, login sessions, etc. but many are very lazy.

1

Replying to

and

So, unfortunately, a lot of apps choose to explicitly disable backups and it won't work for those. Seedvault is comparable to adb backup but without the arcane syntax and poor error reporting. You're prompted to restore in SetupWizard and it can restore when reinstalling an app.

2

Replying to

so... I don't understand how Seedvault can possibly work on Pixel 2, given that it doesn't have an SD card slot

1

Replying to

It can back up to a USB flash drive or a cloud backup service providing a Storage Provider. If you have anything like Termux with a Storage Provider, it's going to show up as one of the possible targets for storing the backup.

2

1

Replying to

ohhhh that's way more useful than I initially thought, thanks

2

Replying to

Definitely does have caveats including how it's unfortunately very common for apps to take the lazy approach of disabling backups instead of keeping things that are not portable separate and including a blacklist of things that shouldn't be backed up.

1

Replying to

tbh even if just the OS settings would be restored it would make the phone a lot more useful for me, since I could actually use it without getting every bit of the build perfect on the first time (rn I'm fighting with the build system over open_gapps and the build system wins)

1

1

Replying to

It restores a decent amount of stuff but not everything. It's going to be getting substantially better in Android 11. The stock OS has slightly better integration of AOSP backup / restore because Play services has some extra bits and pieces to get more into app-based backups.

8:26 AM · Sep 12, 2020Twitter Web App

Replying to

and

They're gradually moving it into AOSP though, which seems to be what's happening in Android 11 to some extent. github.com/stevesoltys/se Every Android distribution does have LocalTransport as a sample / testing backup service implementation but it's just meant for the CTS to use.

Adapt to Android 11 AOSP changes · Issue #94 · seedvault-app/seedvault

There might be changes in Android 11 (to be released in September) that require adaption to Seedvault to run on that new version of AOSP. Candidates are: Package visibility in Android 11 Storage up...

1

1

Replying to

and

So, I don't think there's really anything else that knows how to use LocalTransport and there wouldn't be any guarantees of it not changing in the future. Essentially all these things back up the same data via the same AOSP API. adb backup does NOT use a backup service though.

2

Show replies