Should Android ROM projects remain private-source?
Android ROMs operate with complete control over a user's device.
The Project Elixir controversy highlighted why transparency and source review matter.
I've published an archive and a statement regarding source transparency:
https://github.com/orgs/ascp-oss/repositories
Interested in hearing opinions from ROM maintainers and Android developers.
BTW, anyone knows how to install additional spell check dictionaries for AOSP keyboard which comes with GrapheneOS.
GrapheneOS notes Android 17 “sort of” support, reflecting early compatibility work rather than a fully stable rollout across devices. 📱
It tracks Android 17 privacy upgrades like stronger permissions and encryption while maintaining its hardened AOSP-based security model. 🔐
#TechNews #GrapheneOS #Android #Privacy #Security #OpenSource #FOSS #Mobile #MobileSecurity #Encryption #AOSP #CyberSecurity #DataProtection #Linux #UserPrivacy
For those who are researching the different AOSP projects out there, you will probably cross paths with this site at some point (and probably should 😂 )
Google klärt auf: Das ist alles neu bei Android 17
https://fed.brid.gy/r/https://www.mobiflip.de/google-klaert-auf-das-ist-alles-neu-bei-android-17/
Android 17 AOSP is here
10th Gen Honda Civic Updates Are Signed with AOSP Test Keys
https://juniperspring.org/posts/honda-evil-valet/
#HackerNews #HondaCivic #10thGen #AOSP #TestKeys #CarUpdates #TechNews #Automotive