DeGoogle Yourself

13906 readers

24 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 5 years ago

MODERATORS

CrypticCoffee@lemm.ee

Byereddithellolemmy@lemmy.world

chevy9294@monero.town

CrypticCoffee@lemmy.ml

342

Google is Killing Open Source Android Apps (Here's Why) (techlore.tv)

submitted 1 week ago by ExtremeDullard@piefed.social to c/degoogle@lemmy.ml

65 comments fedilink hide all child comments

Fuck Google with a stiff wire brush.

you are viewing a single comment's thread
view the rest of the comments

[–] LedgeDrop@lemmy.zip 3 points 6 days ago (1 children)

As far as I understood from Graphene, when Google released the source code for Android 16, they also stripped all the reference code for Pixel devices.

Historically, Google would ship the code for Pixel and a software emulator as "reference designs". Now, it's only shipped with the emulator.

The Graphene Team needed to reconstruct the pixel code from the Android 15 release. Fortunately, the divergence between Android 15 and 16 was minimal, but I'm certain the division will widen as time goes by.

[–] Corridor8031@lemmy.ml 1 points 6 days ago

yeah i think i understood it like that too, but they sounded confident that this was a one time issue and that it wont really be a problem now for future releases

but sry i am not really sure what you mean/ the connection is to the topic/ the os/ driver and firmware blobs?