Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Support migation from old phone to a new one #4528

Open
nazar-pc opened this issue Dec 16, 2024 · 1 comment
Open

Feature request: Support migation from old phone to a new one #4528

nazar-pc opened this issue Dec 16, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@nazar-pc
Copy link

I believe it would be nice to have a built-in feature for migration from old phone to a new one.

The ideal workflow I imagine is the following:

  1. Have two phones, both with Graphene OS, let's assume the latest stable version
  2. Connect them to each other with USB-C cable
  3. Select "Migration from an old phone" on the new device during setup process
  4. Confirm on the old device
  5. Both phones go into "Airplane mode" to avoid messing with data consistency and start streaming data to a new phone
  6. After migration is finished successfully, old phone is asking to confirm proceeding with factory reset

I'd expect that in case of matching versions of the OS the only thing I'd have to reconfigure would be biometric and maybe a few other things that are stored in the secure element, everything else including various application credentials would seamlessly move to the new device.

From my understanding the big challenge and the reason most developers do not allow to backup their apps seems to be connected to various possible inconsistencies, but if implemented on OS level it would be possible to prevent most of them.

Seedvault is not a real solution with the number of errors and apps that forbid their backups or do not implement backups properly. I did submit bug reports to all affected apps to their developers, though I don't remember any of them actually fixing things, even those that were Open Source.


Here is an example of status quo: https://discuss.grapheneos.org/d/16182-experience-report-of-grapheneos-migration-from-pixel-6-to-pixel-8-seedvault

@thestinger thestinger added the enhancement New feature or request label Dec 16, 2024
@thestinger
Copy link
Member

The thread you've linked is from before Android 15, where Seedvault now works much better partly due to device-to-device mode being the default. It backs up all apps now. They can still exclude data but can't opt-out of device-to-device backups, only cloud backups, and the regular exclusions have become cloud-only exclusions. They would need to explicit exclude data from device-to-device backups to have it left out of the backups now.

We do plan to implement direct USB backup/restore to avoid needing a storage drive to transfer the files but it will backup/restore exactly what the existing backup system does and there's no viable alternative to that. We can improve how backup/restore works quite a lot since Seedvault isn't very good and can add some extra backup/restore functionality for more system data not covered by it but most is covered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants