I'll believe it when I see it. These days, words are basically meaningless from these large tech companies. Actions are what matter.
at the very least, I'm not convinced this internal branch and AOSP will be close to feature parity if they do throw some stuff out.
Kindle Fire is based on AOSP, that was my mistake. I will say Amazon is a rare OEM in this regard; they're tablet-only, and happy with AOSP because they have their own app store that don't need Play Services integration.
Isn't ART Apache 2-licensed? They don't have to provide the source. I don't see why they would completely close it though. It would lead to forks, plus they have a lot of control through Google Play Services etc. already.
And here's where we need to apply antitrust pressure.
For instance some parking meters / train ticketing machines / payment terminals run Android. source: I work for company that makes some of them though we are moving away from Android to more classical embedded Linux.
Google play services doesn't matter in these contexts.
https://cs.android.com/android/platform/superproject/main/+/...
Give you an example: Recently the Open Source Initiative held board elections. Three of the candidates were disqualified. Two were disqualified for refusing to use proprietary software with Stallman-like stubbornness after explicitly being told that use of proprietary software was non-negotiable for board participation. Lunduke tried to weave it into his neo-Nazi narrative of cultural bolsheviks infesting open source, but the reality is the proprietary software in question is DocuSign -- and there is no alternative in the open source world that does what DocuSign does.
So if the steward organization of open source cannot function without proprietary software, what hope do the rest of us have? Especially with online services using remote attestation and refusing to function unless you're using a known, approved stack from boot to UI layer. May as well buy a Mac and an iPhone and be done with it. Save you lots of hassle and you'll look less like a dweeb.
GrapheneOS actually explicitly pushes for services to switch away from Play Integrity API or SafetyNet API towards the Android Attestation API for that reason.
https://grapheneos.org/articles/attestation-compatibility-gu...
And notably, long term if Google becomes an unreliable maintainer for Android, the other major Android providers are likely to coordinate a list of "approved signing keys" so that apps can use those with the standard Android HW Attestation API.
That's what Google has been strongly pushing to developers.