Elektrine lite

← Feed

@CallMeButtLove@lemmy.world

2026-05-02 16:42 UTC

Serious question: what's to stop Google from just axing AOSP, and what would that mean for GraphenOS? As a company they seem to have become vindictive and I just feel like as soon as it becomes a big enough thorn in their side they will retaliate.

Replies (2)

  • @deltapi@lemmy.world 2026-05-03 04:08

    Amazon's Fire OS is android but they've announced a new webOS ripoff, VegaOS, Linux running HTML5/react apps. Normally I'd think this kind of diversity is a good thing, but apparently it's locked down even tighter and side loading into Vega OS just isn't a thing at all. Edit: the point I was trying to make is that some vendors are working to get away from Google's Android foundations completely. I would think that graphene could go that route if the rug was pulled. But good luck with device support when the device specific source isn't released.

    Open ##1905490

  • @dogs0n@sh.itjust.works 2026-05-02 17:15

    They are basically heading down that path; I believe they started developing in private then they dump all their code twice a year for the public, which has made developing GrapheneOS (etc) way harder to manage. I can only imagine they want to limit projects like Graphene, but they still want to release source because what made Android big was/is all of the "3rd party" phones like Samsung, etc... but now Google has their own hardware who knows what could happen. It definitely feels like the end times where we are clinging onto our last freedoms (thanks to privacy friendly roms) before we privacy-seeking folk jump to linux phones (when they become useable/stable).

    Open ##1905491