Conversation

This Tweet was deleted by the Tweet author. Learn more

Replying to

Neither of those things requires / involves root access when done properly. Backup services need to be built into the OS for important security reasons. However, it's entirely possible to have a generic encrypted backup service supporting any sync service via SAF, etc.

This Tweet was deleted by the Tweet author. Learn more

Replying to

GrapheneOS still maintains the OS security model including the application security model. It has nothing to do with what you claim. Don't need to be have it explained why you think things are designed the way they are as someone deeply involved in implementing these things.

Replying to

If you don't want that security model, nothing stops you from turning on debug mode for an app, signing it with your key and installing it. You don't need to do that to backup and restore data unless the app excludes it from backups. A debug build of either OS or app bypasses it.

Replying to

Google Android isn't iOS. It doesn't stop you from easily installing whatever software you want including modified proprietary apps. It's trivial to change the debugging flag and sign the app with your own key. OS doesn't help them obfuscate their code, etc. in any way either.

This Tweet was deleted by the Tweet author. Learn more

Replying to

Google doesn't make the hardware or operating system for any Android devices with a permanently locked bootloader. I never said you had to do what I suggested for every app update and you obviously wouldn't be doing it by hand. It's trivial to change debug flag and sign an app.

Replying to

Non-Pixel phones don't run Google Android. They only use certain components from Google as part of licensing Google's mobile apps/services. It's not their OS. Part of the point of what I was talking about here is how they're gradually expanding that to provide more components.

Replying to

A Samsung phone does not run an OS from Google. It's a misconception. It's an OS from Samsung signed with their keys and updated by them. They include highly privileged components (Play services, Play Store, mainline modules) from Google under a license/partnership with them.

Replying to

If you're talking about Android OEMs locking down their devices, that doesn't involve Google. Not their hardware, not their firmware, not their OS. Their apps and services are bundled, sure. AOSP itself is an open source project and the vendors fork it just like GrapheneOS.

11:00 AM · May 17, 2021Twitter Web App

Replying to

Android is an OS family defined around compatibility rules. AOSP is the open source reference implementation fulfilling the compatibility rules. It's not like ChromeOS. It's inching towards potentially being that way but it's nothing like that today and is far from a specific OS.