yeah, the problem with a pre-installed OS is that you don’t know what’s in it, the carrier could have installed a fork or spyware that defeats the purpose of GrapheneOS.
it’s much more secure to download, verify, and install the OS to your phone yourself.
hopefully people wake up to all the bad-faith surveillance happening and become willing to take that step, which is much easier than it sound
Would a hard fork not splinter the software support, killing the ecosystem? E.g. some devs only support that hard fork, others only the android compatible version.
I would be fine with that split. That would be an almost ideal situation even, and a thin compatibility layer like proton or even just an invisible container system similar to docker or flatpak could handle getting more of android onto the fork when it all stops being completely compatible. More effort but hopefully only needed short term.
Hardware compatibility is the major problem with alternative android. Basically I have to buy a 10 year old used phone as is. Would this only make this worse?
Anyway, maybe AI code generation could actually help with things like hardware compatibility. Things like an AI agent could iterate on reading about a smartphone model and testing various configurations and patch drivers to make it compatible for many more devices. Not sure if AI is suitable for that, but you should be able to define stringent test cases for this.
I’m really hoping we get a hard fork of AOSP that gets really popular.
it’s called GrapheneOS.
it gets popular by you installing it and telling your friends
Im already doing that but we don’t have big players selling it in stores.
yeah, the problem with a pre-installed OS is that you don’t know what’s in it, the carrier could have installed a fork or spyware that defeats the purpose of GrapheneOS.
it’s much more secure to download, verify, and install the OS to your phone yourself.
hopefully people wake up to all the bad-faith surveillance happening and become willing to take that step, which is much easier than it sound
Why graphene? Lineage os much more popular and supports many more devices.
U can’t trust Google hardware
Don’t let the grapheme crowd hear you. Maybe Motorola will work it out.
Would a hard fork not splinter the software support, killing the ecosystem? E.g. some devs only support that hard fork, others only the android compatible version.
I would be fine with that split. That would be an almost ideal situation even, and a thin compatibility layer like proton or even just an invisible container system similar to docker or flatpak could handle getting more of android onto the fork when it all stops being completely compatible. More effort but hopefully only needed short term.
Hardware compatibility is the major problem with alternative android. Basically I have to buy a 10 year old used phone as is. Would this only make this worse?
Anyway, maybe AI code generation could actually help with things like hardware compatibility. Things like an AI agent could iterate on reading about a smartphone model and testing various configurations and patch drivers to make it compatible for many more devices. Not sure if AI is suitable for that, but you should be able to define stringent test cases for this.
AI can’t code around missing security chips and features in hardware.
Well if that’s what is holding up more hardware compatibility for open android.