Probably. Hopefully the opposition points out the countless hours people like and others need to do to even partially de-google devices.
Back in the G1 days it was easy. Back then Google paid people full time to make sure AOSP was solid and easy to build/use.
Conversation
That's not an accurate or fair assessment of our work. It is not what we do and what the project provides. GrapheneOS builds privacy and security technologies. AOSP is a solid base for us and we've never had problems building it. You continue to misrepresent the actual issues.
2
1
I was not referring to end products like GrapheneOS (which is why I didn't name it) but was specifically referring to all the work you and others do to get each AOSP to work reliably without Google bits so additive work like GrapheneOS is even possible.
2
AOSP already works reliably without Play services. We currently don't bother bundling assorted apps rather than letting users choose apps of their choice from F-Droid, Aurora Store (Play Store) and elsewhere. We intend to fill in functionality provided by Play services but we
2
1
AOSP works reliably without Play services only after you provide and continually fix lots of tooling to even get it to build and even then one has to extract factory image bits.
That, by itself, is a non trivial amount of work to maintain as I know all to well now.
2
It's not a compliment, it's an attempt to use my name to peddle misinformation which we see as quite harmful towards GrapheneOS and getting the issues we have with hardware addressed. Inventing problems we don't have and distracting from those we do doesn't help us. It hurts us.
1
I was just giving you credit for all the hard work you did on android-prepare-vendor and lots of research and time to work out secure boot and all the other things Google failed to provide in their tools and docs to get AOSP actually working for each hw/release combo.
2
You're talking about support for Pixels, not issues with AOSP. If we didn't support Pixels, none of that would be relevant, and we don't intend to support Pixels in the long-term. We're using them until we have better options available, and ideally we'd have input into making it.
2
is it fair to say that it's more difficult than it need be to get GrapheneOS to run on Google's Pixel product line? Or that there have been vendor-specific barriers that favor Google's own builds of Android? These are the questions from an anti-competitive practices standpoint.
1
The anti-competitive practices are around requiring that Google services need to be built into the OS with privileges unavailable to third party apps. They encourage apps to depend on APIs provided by Play services. The problem is it's not just a set of libraries for apps to use.
That is a major issue. Also, forcing vendors to agree to CTS / CDD compliance for Android-based operating systems without Play services is anti-competitive and a major issue. GrapheneOS deliberately deviates from the Android CTS / CDD when it doesn't make sense for us.
1
Vendors licensing Play services are not allowed to release a device based on AOSP that does not have CTS / CDD compliance. It's one thing to require it to ship their apps / services and use their branding, but what they do is way beyond that and is definitely anti-competitive.
1
Show replies
right, that I'm aware of and hence why I called it the "smoking gun" somewhere in this thread. The ease and practicality of developing and installing an alternative OS for Google's product line is another issue, possibly considered anti-competitive if specific barriers exist. 1/
1
My opinion on that is well-known, but I'm wondering what you think about it and whether you would characterize these challenges as monopolistic and/or a hindrance to developers and users. 2/2
1
Show replies