2 ms·

I hate to sound like a jerk, but this comes across like a whining four year old. (The repetitiveness, pleading, shifting appeals, awkward negotiation attempts..

I hate to sound like a jerk, but this comes across like a whining four year old. (The repetitiveness, pleading, shifting appeals, awkward negotiation attempts...) What's stopping the GrapheneOS team from negotiating similar access contracts as OEM's enjoy? I would have hoped they'd have some clout given what they've achieved to date and the quantity and impact of bug fixes they've effected upstream. Are they short on funds? (The posts seem to imply they have some budget available, at least for hiring?) Is there some kind of sorted history between Google and the GrapheneOS team of which I'm unaware? Could they commandeer some about-to-be-abandoned, low-end hardware product, as a means to meeting contrived requirements to become a legit OEM? Or embark on a more organized and deliberate PR campaign (perhaps even legal avenues eg. platform gatekeeper legislation) to pressure Google to maintain Android's open-sourcedness?

izacus 1y ago
They mentioned that Google wants commitments from them that would undermine what GrapheneOS is. That is - they would have to pass GMS test suite which enforces Play Services and other Google app functionality and wouldn't be compatible with their sandboxing of Play Services. They also couldn't ship without Google apps.
kotaKat 1y ago
> What's stopping the GrapheneOS team from negotiating similar access contracts as OEM's enjoy? Google themselves. > Is there some kind of sorted history between Google and the GrapheneOS team of which I'm unaware? https://www.androidauthority.com/google-android-development-aosp-3538503/ https://www.androidauthority.com/google-android-development-... Google is starting to move AOSP private if not in preparation to kill off the "OS" part of it.