Android: Difference between revisions
cit-need on G limiting ADB |
the backup situation is crazy (and unfair) |
||
| Line 57: | Line 57: | ||
===ADB limitations=== | ===ADB limitations=== | ||
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}} | 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> | ||
===Android Cast restricted to Google-signed receivers=== | ===Android Cast restricted to Google-signed receivers=== | ||