this post was submitted on 21 May 2026
26 points (67.6% liked)
DeGoogle Yourself
16970 readers
108 users here now
A community for those that would like to get away from Google.
Here you may post anything related to DeGoogling, why we should do it or good software alternatives!
Rules
-
Be respectful even in disagreement
-
No advertising unless it is very relevent and justified. Do not do this excessively.
-
No low value posts / memes. We or you need to learn, or discuss something.
Related communities
!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think everybody saw that coming. While some people will still try to defended them, saying it's not censorship, or it was a mistake, slowly we'll see small evidences of Graphene being enshittified.
The nature doesn't allow a good thing and a big tech company co-exist.
This is just my guess, but I'm almost sure you'll see some ads or maybe even spywares on Graphene version for Motorola phones.
And yes, maybe they provide two different versions, one fully enshitified and other for the people, but slowly, the good version will get less attention and less updates, and this will make people be forced to choose for the enshittified version of the OS.
Graphene is open source so what's up with your panic?
The base OS of Android is, but the widely dispersed version maintained by Google with the hardware drivers required for it to work with the actual hardware is not.
That's why projects like Graphene can't work on every phone. They have to rely on either reverse engineering hardware drivers or the manufacturers providing the drivers. For many years, Google openly released the drivers for all the hardware in their Pixel line of phones, which allowed Graphene and other customized versions of Android to easily work on Pixel phones.
Manufacturers usually don't release drivers separately and instead they're only available built into the manufacturers customized Android version. Android Open Source Project is the open source base, then Google builds their proprietary stuff on top as "Android", then the various phone manufacturers build their own versions on top of Google's "Android" with: manufacturer specific crud added, phone specific crud added, and often phone carrier specific crud added.
the difference is that Google is actually doing bad things, and you're just sharing conjecture about something you believe MIGHT POSSIBLY happen at some point in the indeterminate future.
this is without even considering that the belief in question is supported by a new account, registered hours ago to post an accusation without any proof to back it up besides a random issue posted to a random Codeberg, that was created very recently by an account with no history, to share rumors about Tracfone.
do you believe every single thing people tell you? because if so, I have some oceanfront property in Wyoming to sell you, and there's a Nigerian prince who wants to finance it it, he just needs you to send me $10,000 so he can unlock his assets and send you $1,000,000.
Maybe we find out the profit from including ads and spyware isn't so much, and it all turns out great? Moto sees the chance to get on the right side of consumers and sells phones as a result.
Is this ...conjecture? I will make two points.
Very tangential, but Android source code is getting a heavily delayed release, and this is harming projects like Graphene