Conversation

holy fucking shit, android (aosp) actually has useful working backups that don't require you to upload everything to google servers and which you can manually trigger and have it work they're just incredibly well hidden h/t for giving me the right direction
3
182
note: this is mostly useful as a replacement for `adb backup`/`adb restore` that doesn't require blood sacrifices to restore half of your data instead of none of your data it doesn't work remotely and AFAIU requires a userdebug build
3
40
Replying to
CTS largely operates via adb. There's a whole lot of functionality available in `adb shell` that's largely to support the CTS. So, CTS has access as `adb shell` and as the many apps it installs, including device managers, accessibility services, etc. that it authorizes.
1
2
Replying to and
CTS is kind of unprivileged and does most of the testing via apps, but it also does a whole lot of stuff via `adb shell` that an app could never do, and it uses `adb shell` to install the thousands of different app-based test suites, etc.
1
1
Replying to and
If you look at the CTS modules list, you'll see a lot of modules with the term "Host" in their name, and that means a test suite that operates via `adb shell` and largely does the work on the host running the CTS test harness, not within an app on the device like most tests.
1
1
Replying to and
To fully pass the CTS, you need to have a non-test-key-signed release / user build. Something that amuses me is that the public CTS build published by Google isn't signed with release keys and it gets mad about the apps it sees using the test key that it installed itself.
1
2
Show replies