sanitation@lemmy.today to Privacy@lemmy.dbzer0.com · 2 days agoYour phone is about to stop being yours. — Starting September 2026, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, sign…keepandroidopen.orgexternal-linkmessage-square117fedilinkarrow-up1564arrow-down18cross-posted to: onehundredninetysix@lemmy.blahaj.zoneasklemmy@lemmy.worldandroid@lemmy.worldopensource@programming.devdegoogle@lemmy.mltechnology@lemmy.worldandroid@lemmy.world
arrow-up1556arrow-down1external-linkYour phone is about to stop being yours. — Starting September 2026, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, sign…keepandroidopen.orgsanitation@lemmy.today to Privacy@lemmy.dbzer0.com · 2 days agomessage-square117fedilinkcross-posted to: onehundredninetysix@lemmy.blahaj.zoneasklemmy@lemmy.worldandroid@lemmy.worldopensource@programming.devdegoogle@lemmy.mltechnology@lemmy.worldandroid@lemmy.world
minus-squarelucullus@discuss.tchncs.delinkfedilinkarrow-up2·1 day agoAfaik GrapheneOS won’t be affected, neither will e/OS. The real problem with them still being based as AOSP is, that google might stop the AOSP project. That would mean the forks would need to do that continous based development themselves.
minus-squareInui [comrade/them]@hexbear.netlinkfedilinkEnglisharrow-up1·1 day agoIt affects Graphene because people using it still get their apps from Google Play, Aurora Store (also the Play Store), and F-Droid, etc.
minus-squarelucullus@discuss.tchncs.delinkfedilinkarrow-up1·edit-220 hours agoI searched for statements from GOS and e/OS and what I found tells a different story https://discuss.grapheneos.org/d/26337-android-developer-verification-are-we-screwed-no-doesnt-apply-to-gos/25 https://xcancel.com/GrapheneOS/search?f=tweets&q=certified&since=&until=&near= https://community.e.foundation/t/e-os-statement-about-google-developer-verification/79892 Do you have different information?
Afaik GrapheneOS won’t be affected, neither will e/OS. The real problem with them still being based as AOSP is, that google might stop the AOSP project. That would mean the forks would need to do that continous based development themselves.
It affects Graphene because people using it still get their apps from Google Play, Aurora Store (also the Play Store), and F-Droid, etc.
I searched for statements from GOS and e/OS and what I found tells a different story
https://discuss.grapheneos.org/d/26337-android-developer-verification-are-we-screwed-no-doesnt-apply-to-gos/25 https://xcancel.com/GrapheneOS/search?f=tweets&q=certified&since=&until=&near=
https://community.e.foundation/t/e-os-statement-about-google-developer-verification/79892
Do you have different information?