Since there is not much hope Linux phones gets so much better until 2027, when Google will (possibly) roll-out mandatory developer verification (signing with Google-issued keys) for all apps regardless of installation method, time to plan what to do in case worst scenario unfolds and :android: is no longer open for sideloading :blobcatthink:

@GrapheneOS may be an option now, but it runs exclusively on <img class=" title=":google:"/> Pixel devices, ironically - they may become more locked further as Android itself will be - because Google is evil :blobcateyes:

Could a new vendor emerge? Or, less likely, new operating system to conquer it all?

I'd say we need a :nokia: moment in the industry now :blobcatdonutnom:

#android #google #pixel

in reply to Gytis Repečka

Android distributions are Linux distributions. Linux means the Linux kernel. It doesn't mean systemd, glibc, GCC, binutils, GNOME, etc.

Google's planned restriction on which apps can be installed only apply to an OS licensing Google Mobile Services and integrating with privileged access. It's a year away and not clear it will be allowed by the EU, etc.

GrapheneOS runs exclusively on secure devices with proper support for another OS, which are currently only Pixels, nothing else.

in reply to GrapheneOS

We're actively working with a major Android OEM on a subset of their devices meeting our security, update and other requirements so we can have official GrapheneOS support for them. Their current devices don't meet our requirements. GrapheneOS is not in any way inherently exclusive to Pixels. It's security combined with alternate OS support which is exclusive to Pixels. If we didn't care about making sure to provide good security, then we could already support many other devices.