zlacker

>>kotaKa+(OP)
Meaning to use your device you need to have a contractual relationship with a foreign (unless you are in the US) third party that decides what you can or cannot do with it. Plus using GrapheneOS is less of an option every day, since banks and other "regulated" sectors use Google Play Protect and similar DRMs to prevent you from connecting from whatever device you want. Client-side "trust" means the provider owning the device, not the user.

Android shouldn't be considered Open Source anymore, since source code is published in batches and only part of the system is open, with more and more apps going behind the Google ecosystem itself.

Maybe it's time for a third large phone OS, whether it comes from China getting fed up with the US and Google's shenanigans (Huawei has HarmonyOS but it's not open) or some "GNU/Linux" touch version that has a serious ecosystem. Especially when more and more apps and services are "mobile-first" or "mobile-only" like banking.

>>arielc+542
Less and less of AOSP is being updated also, as Google rolls most of its new features and updates behind the Play Services system. Install Graphene and you will see what I am talking about - the SMS app for example hasn't been updated in probably a decade and looks and functions like it did back in Android 4 (KitKat). Same with the other built-in apps. While I used Graphene myself for a solid 6 months, the features you have to give up on using or find some obtuse workaround for aren't appealing to the "normies" who just want their phone to do what they want, no matter the unseen ethical cost (in this case, sacrificing the ability to freely install 3rd party apps). Someone on another forum said it very well - people like "us" were Google's foot in the door, now along with Apple they have such a stranglehold on the mobile OS space that a 3rd viable and comparable contestant becomes less and less likely by the day. Throw in how Google starting with Android 16 is not releasing updated drivers with AOSP and Graphene probably doesn't have much life left in it, either.

>>archvi+oB2
> While I used Graphene myself for a solid 6 months, the features you have to give up on using or find some obtuse workaround for aren't appealing to the "normies" who just want their phone to do what they want

Did you use GrapheneOS with the Play Services? Sounds like you didn't. Of course if you don't use the Play Services, you lose... the Play Services. But GrapheneOS allows you to run them in the sandbox.

> Throw in how Google starting with Android 16 is not releasing updated drivers with AOSP and Graphene probably doesn't have much life left in it, either.

This sounds incorrect. Google decided to stop sending the device tree of the Pixel devices in AOSP. And GrapheneOS is still fine, though it will take more effort because they won't get the device tree from Google.