eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

228
active users

#aosp

1 post1 participant1 post today

Look, Android/AOSP/Google is showing some worrying signs re direction - Gemini specifically.

Graphene OS seems the premiere option but tbqh I just need to degoogle - my threat model includes folding the second a teenager threatens me with a house brick okay?

...no I don't wanna talk about it.

#CalyxOS has released a blog post with updates on the status of the project with respect to the changes made to #AOSP with #Android 16.

Basically updates may be slightly delayed temporarily while they re-tool their processes to work around the missing device trees for Pixel devices.

Title: Community update - our progress on CalyxOS after the release of Android 16

Link: calyxos.org/news/2025/06/26/co

calyxos.orgCommunity update - our progress on CalyxOS after the release of Android 16Community update - our progress on CalyxOS after the release of Android 16
📱 Smartphonen – det glemte led i digital suverænitet?

Vi taler meget om behovet for europæisk digital uafhængighed. Men alligevel kører næsten alle smartphones på Apple iOS eller Google Android – to amerikansk ejede systemer, som styrer vores adgang til apps, data og tjenester.

Og hvad bruger vi telefonen til?
🪪 MitID
📲 Pas, kørekort og sundhedskort
🏦 Netbank og betaling
🚆 Rejsekort og billetter

Alt det kræver en enhed godkendt af netop Apple eller Google – og i Androids tilfælde, at den består Google Play Integrity Check.

📌 Dermed bliver vi og vores myndigheder afhængige af amerikanske selskaber for adgang til essentielle funktioner.

💡 EU arbejder allerede for alternative app stores – men vi har også brug for en uafhængig europæisk certificering af både apps og telefoner, baseret på åbne platforme som fx AOSP.

👉 Digital suverænitet handler ikke kun om servere. Den handler også om det, vi har i lommen.

📷 Billedtekst:
Nokia N9 var en banebrydende smartphone med styresystemet MeeGo. Den kom lige da Microsoft overtog Nokia – og projektet blev lukket. Men arven lever videre i bl.a. Sailfish OS.

#digitaluafhængighed #europa #mitid #android #aosp #apple #google #foss #cybersikkerhed #digitalsuverænitet #nokia #meego #sailfishos
Continued thread

Digital suverænitet handler ikke kun om hvor serverne står.
Det handler også om, hvem der bestemmer over det, vi bærer i lommen.

📷 Billedtekst:
Nokia N9 var en visionær smartphone med styresystemet MeeGo – lukket ned efter Microsofts opkøb. Men idéen om en europæisk vej lever videre i bl.a. Sailfish OS.

#Digitalsuverænitet #AOSP #FOSS #MitID #cybersikkerhed #EUtech #Apple #Google #decentralisering #digitaluafhængighed
6/6

Continued thread

Sehr gute Analyse, was Google da konkret mit #AOSP vorhaben könnte (ich frag mich aber: Wer will wirklich Googles "Pixel OS", mMn ist dessen aggressives 'Design' so dermaßen an der Praxis und gutem Geschmack vorbei entwickelt, da braucht es erst Samsung und Co., die es alltagstauglich biegen):

Rumour: Google intends to discontinue the Android Open Source Project

osnews.com/story/142553/rumour

via mstdn.social/@osnews/114670436

www.osnews.comRumour: Google intends to discontinue the Android Open Source Project – OSnews

Thinking of buying a new #smartphone? Maybe a #Google #Pixel because of long updates & #GrapheneOS? Think carefully about whether you want to buy the new 10 series after its release or rather one of the 9 series? The 9 series has support until August 2031, the 9a until April 2032.

Why not (more) the 10 series?

"In April 2025, we received leaked information about Google taking steps to strip down the Android Open Source Project. We were told the first step would be removal of device support with the launch of Android 16. We didn't get details or confirmation so we didn't prepare early."

This makes supporting the 10 series significantly harder for the #GrapheneOS project. The project is looking into supporting other devices from other manufacturers, the process seems difficult - see #Fairphone: grapheneos.social/@GrapheneOS/

Source: grapheneos.social/@GrapheneOS/

@GrapheneOS

#aosp #AndroidOpenSourceProject
#googlepixel #grapheneos

GrapheneOS MastodonGrapheneOS (@GrapheneOS@grapheneos.social)@frej@fosstodon.org Fairphone's devices have atrocious security and very poor long term firmware/software support. They lack proper updates from the start and are missing more of our requirements than a typical Snapdragon Android device. They're further from providing what we need than most Android OEMs. We don't think they're capable of building what we need and they haven't shown an interest. They're partnered Murena who are misleading people about privacy and heavily attacking GrapheneOS.

Dang, it sounds like #Google is really trying to kill #FOSS #Android OSes.

https://tilvids.com/videos/watch/848e13c7-1bcf-49d3-ad75-02055c0b9576

What are my #AOSP peeps planning to do?

If OS updates get a lot slower because of this, I might have to go back to iPhone. 😭🤦‍♂️🤦‍♂️🤦‍♂️

#CalyxOS #GrapheneOS #LineageOS #Calyx #GOS #Lineage

UPDATE: This update from the #CalyxOS project helps answer some questions: https://calyxos.org/news/2025/06/11/android-16-plans/

It would seem that all Pixel devices will require a lot more work to port Android 16 to. It's not impossible, by any stretch, but Google has absolutely stopped helping the community in any way.

This is very bad news, all around. Not the worst news, by far, but quite bad.

Google's latest AOSP changes will complicate custom ROM development for Pixel devices. 🔧

With Android 16, the absence of device trees and driver binaries means developers will face significant challenges. 📉

This shift to Cuttlefish as the reference platform could hinder projects like GrapheneOS and LineageOS, making development much more difficult.

androidpolice.com/googles-late

Android Police · Google’s latest AOSP move spells doom for custom ROMs on Pixel phonesGoogle just made Pixel custom ROM development harder

#AOSP isn't dead, but #Google just landed a huge blow to custom #ROM developers
Some people are speculating Google is planning to discontinue AOSP, company says these claims are false.
Google removed device trees and driver binaries for #Pixel #phones from #Android16 #sourcecode, significantly complicating custom ROM development. #Android-maker intentionally omitted these resources as it shifts its AOSP reference target from Pixel to a virtual device called "Cuttlefish."
androidauthority.com/google-no

Android Authority · AOSP isn't dead, but Google just landed a huge blow to custom ROM developersGoogle has confirmed it isn't discontinuing AOSP, but it's making a change that makes it harder for devs to build Android for Pixel phones.

Google released the AOSP code for Android 16 this week, but without the usual device trees & drivers for Pixel devices, instead using the "cuttlefish" virtual device as a reference target. It'll make custom ROM development for Pixels and other devices harder. androidauthority.com/google-no #Android #Google #AOSP #OpenSource #CustomROMs

Android Authority · AOSP isn't dead, but Google just landed a huge blow to custom ROM developersGoogle has confirmed it isn't discontinuing AOSP, but it's making a change that makes it harder for devs to build Android for Pixel phones.

There has been some unsettling change in the recent release of #Android16 to #AOSP.

As custom ROM makers found out by surprise, #Pixel device-specific source code is missing this time. The code was usually released together with AOSP. Without this device-specific code it's not possible to build or run AOSP 16 on any recent Pixel device. Therefor custom ROMs for Pixel devices based on AOSP 16 cannot be built.

calyxos.org/news/2025/06/11/an

#Android #Google

[1/2]

calyxos.orgAndroid 16 and Pixel SupportAndroid 16 and Pixel Support