sanitation@lemmy.todayBanned from community to Privacy@lemmy.dbzer0.com · 1 month 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-square120linkfedilinkarrow-up1606arrow-down19cross-posted to: onehundredninetysix@lemmy.blahaj.zoneasklemmy@lemmy.worldandroid@lemmy.worldfoss@beehaw.orgopensource@programming.devdegoogle@lemmy.mllinux@programming.devlinux@lemmy.mlandroid@programming.dev
arrow-up1597arrow-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.todayBanned from community to Privacy@lemmy.dbzer0.com · 1 month agomessage-square120linkfedilinkcross-posted to: onehundredninetysix@lemmy.blahaj.zoneasklemmy@lemmy.worldandroid@lemmy.worldfoss@beehaw.orgopensource@programming.devdegoogle@lemmy.mllinux@programming.devlinux@lemmy.mlandroid@programming.dev
minus-squarelucullus@discuss.tchncs.delinkfedilinkarrow-up3·1 month 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-up1arrow-down1·edit-21 day agodeleted by creator
minus-squarelucullus@discuss.tchncs.delinkfedilinkarrow-up2·1 month 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.
deleted by creator
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?