Yeah we’re boned, Everything we have Android like is AOSP based and as the changes happen, keeping them at bay will become unsustainable. Lineage, Graphine and Calyx are all AOSP based.
For now, it will likely be pretty easy for any of the forks to circumvent this particular change. I’m more worried about the future, it wouldn’t be hard for them to start pushing store APK’s to require proprietary hooks, there’s a good chance that eventually people won’t want to keep around Google and non Google versions of apps.
So you have Halium+VM for ~ ubuntu touch (still android drivers, but private)
Or postmarket derivatives, which is real linux, but is barely functional and has miserable battery life.
We’re playing catch up for linux and we can get there, but available phones are super limited and none of the contenders are solid daily drivers yet.
Biggest problem I have is there’s no good way to run Signal. If you do it in Halium under waydroid it eats power and getting it to run/keeping it updated under arm/linux is a part time job.
Luckily this shit (Google Play Protect) is in Google Play Services not AOSP.
The actual big change coming to AOSP is that development is going to start happening behind closed doors. You get the updated code when the new version is released, instead of seeing commits as they appear on the master branch. This might make it harder for the custom ROMs to keep up at all.
I’m more worried about the future, it wouldn’t be hard for them to start pushing store APK’s to require proprietary hooks, there’s a good chance that eventually people won’t want to keep around Google and non Google versions of apps.
If this results in a noticeable decrease in apps available on 3rd party stores, this might be cause for some nice EU action, like they did with Apple. But I’m not too hopeful.
Yeah we’re boned, Everything we have Android like is AOSP based and as the changes happen, keeping them at bay will become unsustainable. Lineage, Graphine and Calyx are all AOSP based.
For now, it will likely be pretty easy for any of the forks to circumvent this particular change. I’m more worried about the future, it wouldn’t be hard for them to start pushing store APK’s to require proprietary hooks, there’s a good chance that eventually people won’t want to keep around Google and non Google versions of apps.
So you have Halium+VM for ~ ubuntu touch (still android drivers, but private)
Or postmarket derivatives, which is real linux, but is barely functional and has miserable battery life.
We’re playing catch up for linux and we can get there, but available phones are super limited and none of the contenders are solid daily drivers yet.
Biggest problem I have is there’s no good way to run Signal. If you do it in Halium under waydroid it eats power and getting it to run/keeping it updated under arm/linux is a part time job.
Luckily this shit (Google Play Protect) is in Google Play Services not AOSP.
The actual big change coming to AOSP is that development is going to start happening behind closed doors. You get the updated code when the new version is released, instead of seeing commits as they appear on the master branch. This might make it harder for the custom ROMs to keep up at all.
If this results in a noticeable decrease in apps available on 3rd party stores, this might be cause for some nice EU action, like they did with Apple. But I’m not too hopeful.