Android: Difference between revisions
the backup situation is crazy (and unfair) |
ADB: "limitations" -> "restrictions", because it's intentional |
||
| Line 56: | Line 56: | ||
In North America, many Android devices like phones or tablets will not allow consumers to unlock and do what they want to modify the software. Therefore, it has been incredibly difficult and nearly impossible to root and install custom ROMs on the device unless an exploit has been found. Some OEMs like [[Samsung]] are now completely blocking [[bootloader unlocking]] on their phones regardless of region. | In North America, many Android devices like phones or tablets will not allow consumers to unlock and do what they want to modify the software. Therefore, it has been incredibly difficult and nearly impossible to root and install custom ROMs on the device unless an exploit has been found. Some OEMs like [[Samsung]] are now completely blocking [[bootloader unlocking]] on their phones regardless of region. | ||
===ADB | ===ADB restrictions=== | ||
Google has been adding more restrictions to what <code>[[wikipedia:Android_Debug_Bridge|adb]]</code> can access.{{Citation needed|reason=since when?|date=2026-05-18}} For instance, if an app is not [https://developer.android.com/privacy-and-security/risks/android-debuggable debuggable], the user [[Data lock-in|cannot read any files in the app's data folder]]. Aside from transparency concerns, this makes full backups impossible, unless the app provides a way to export data. Google and many OEMs provide their own (proprietary) full-backup mechanisms, but those typically [[Forced account|require accounts]] and [[Forced cloud|cloud connections]]. Even if the app has <code>[https://developer.android.com/guide/topics/manifest/application-element#allowbackup allowBackup]</code> enabled, Android 12 forbids backup-restore via ADB unless it's a device-to-device transfer.<ref>https://developer.android.com/about/versions/12/behavior-changes-12#backup-restore</ref> | Google has been adding more restrictions to what <code>[[wikipedia:Android_Debug_Bridge|adb]]</code> can access.{{Citation needed|reason=since when?|date=2026-05-18}} For instance, if an app is not [https://developer.android.com/privacy-and-security/risks/android-debuggable debuggable], the user [[Data lock-in|cannot read any files in the app's data folder]]. Aside from transparency concerns, this makes full backups impossible, unless the app provides a way to export data. Google and many OEMs provide their own (proprietary) full-backup mechanisms, but those typically [[Forced account|require accounts]] and [[Forced cloud|cloud connections]]. Even if the app has <code>[https://developer.android.com/guide/topics/manifest/application-element#allowbackup allowBackup]</code> enabled, Android 12 forbids backup-restore via ADB unless it's a device-to-device transfer.<ref>https://developer.android.com/about/versions/12/behavior-changes-12#backup-restore</ref> | ||