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:

213
active users

#grapheneos

26 posts25 participants4 posts today

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.

Ihr überlegt ein neues #Smartphone zu kaufen? Ggf. ein #Google #Pixel wegen langer Updates & #GrapheneOS? Überlegt gut, ob Ihr nach Erscheinen das neue 10er kaufen wollt oder lieber eines der 9er Serie? Die 9er Reihe hat Support bis August 2031, das 9a bis April 2032.

Warum nicht (mehr) die 10er Reihe?

"Im April 2025 erhielten wir¹ durchgesickerte Informationen darüber, dass Google Schritte unternimmt, um das Open-Source-Projekt #Android abzubauen. Uns wurde gesagt, dass der erste Schritt die Abschaffung der Geräteunterstützung mit der Einführung von Android 16 sein würde. Wir erhielten keine Details oder eine Bestätigung, sodass wir uns nicht frühzeitig darauf vorbereiten konnten."

Das macht die Unterstützung der 10er Reihe für das #GrapheneOS - Projekt signifikant schwerer. Das Projekt prüft die Unterstützung anderer Geräte anderer Herstellern, der Prozess scheint schwierig - siehe #Fairphone: grapheneos.social/@GrapheneOS/

Quelle: grapheneos.social/@GrapheneOS/

¹ Entwickler von GrapheneOS

@kuketz
@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.

Kolejny krok Google ku zamknięciu Androida.

Google wykorzystując swoją pozycję monopolisty już od jakiegoś czasu poczynia kroki ku ograniczeniu rozwijanego przez siebie Androida. Firma cały czas swoimi kolejnymi kontrowersyjnymi decyzjami związanymi głównie z Play Integrity oraz usługami Google rzuca kłody pod nogi użytkownikom wymagającym transparentności oraz chcącym używać systemu w duchu open source.
Najnowszym i chyba najbardziej niepokojącym krokiem ku ograniczeniu dostępności systemu od Google jest ostatnia decyzja o przeniesieniu całego kodu źródłowego Androida do swoich repozytoriów, do których dostęp mają tylko licencjonowani producenci OEM. Co prawda kod źródłowy będzie dostępny w dalszym ciągu, jednak dopiero gdy system będzie w pełni gotowy do użytku. Wiąże się to z większym opóźnieniem w wydawaniu kolejnych odsłon robocika, co znacząco utrudni pracę niezależnym deweloperom takich systemów jak np. GrapheneOS, LineageOS, CalyxOS itp.
Kroki poczynianie przez Giganta z Mountain View można łączyć z toczącymi się przeciw niemu wieloma postępowaniami antymonopolistycznymi, z których wiele przegrywa w sądach w USA. według nieoficjalnych przecieków Google może w ten sposób szukać oszczędności i zabezpieczać się przed podziałem korporacji na mniejsze kawałki.

Artykuł od AntyWeb przystepnie przybliżający omawiany problem:
antyweb.pl/google-zamyka-andro

AntywebGoogle "zamyka" Androida. Dłużej poczekamy na aktualizacje?Android – system, który napędza większość smartfonów na świecie zawsze był znany ze swojej „otwartości”. Co to znaczy? Mówiąc najprościej, Google, twórca Androida, udostępniał publicznie jego kod źródłowy w ramach projektu AOSP (Android Open Source Project).

»Android – Google erschwert die Entwicklung von Custom-ROMs;
Google erschwert die Entwicklung von Custom-ROMs wie Lineage für Pixel-Smartphones. Besonders die gehärtete Android-Version GrapheneOS trifft es.«

Ich kann dem nicht urteilen, ob nun @GrapheneOS Recht hat oder ein indirektes Marketing für sich betreibt? Deren Hauptentwickler wurde früher kritisch betrachtet aber auch Google sollte man im Auge behalten.

📱 heise.de/news/Android-Google-e

heise online · Android: Google erschwert die Entwicklung von Custom-ROMs
More from Andreas Floemer

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

Etwas beunruhigend, dass das mit den überhitzenden und sich aufblähenden Akkus bei Googles #Pixel-Reihe ein systematisches Problem zu sein scheint. 😕 Es droht ggf. akute Brandgefahr, ein kostenloser Austausch ist möglich.
computerbase.de/news/smartphon androidauthority.com/pixel-6a-

Der #Akku meines #Pixel6a hat sich kürzlich dem Augenschein nach ebenso aufgebläht, während ich passenderweise auf ein neues Gerät migriert bin. Bleibt zu hoffen, dass #Google dieses Problem bei neueren Geräten in den Griff bekommen hat und #GrapheneOS die Maßnahmen und Vorabwarnungen ebenso umsetzt...

ComputerBase · Pixel 6a: Akku-Probleme bei einigen Modellen zwingen Google zum HandelnBy Michael Schäfer

#Google blockiert zunehmend die Möglichkeiten, vollständig freie und sichere Betriebssysteme wie @GrapheneOS auf #Pixel Geräten zu installieren. Eine neue Einschränkung bei der Firmware-Nutzung macht es schwerer, alternative Android-Distributionen ohne proprietäre Google-Komponenten zu betreiben. Das betrifft nicht nur die Freiheit der Softwarewahl, sondern auch Projekte, die den Fokus auf Sicherheit und Datenschutz legen.

#Android #GrapheneOS #FOSS #Security

grapheneos.social/@GrapheneOS/

GrapheneOS MastodonGrapheneOS (@GrapheneOS@grapheneos.social)In May, we began preparing to port to Android 16 despite our most active senior developer responsible for leading OS development being unavailable (https://grapheneos.social/@GrapheneOS/114359660453627718). Android 16 launched today and porting is going to be significantly more difficult than we were expecting.

@GrapheneOS is one of the very few (maybe the only!) platforms that do provide excellent default protection against megacorp #espionage and even state actors like #trojanhorses and border espionage by rogue states like #USA, #China, #Russia, ...

One of the few systems that isn't hackable by #Palantir and other bad actors.

If you do want protection, do yourself a favor and switch to #GrapheneOS using a (cheap/used/older) #Pixel phone. Recommended: Pixel 8 or newer.

Setup (flashing) is basically connecting your phone via a proper USB-C cable to another Android device and pressing a few buttons in the web browser: youtube.com/watch?v=L1KZWjZVnA + grapheneos.org/install/web 👍

Please do setup a monthly bank transfer of just a few bucks if you want to fund their effort: grapheneos.org/donate (they really do have many donating options!)

They're currently porting #Android16 which should be available soon.

Android 16 lanceret blog.google/products/android/a

#GrapheneOS : Desværre har #Android foretaget ændringer, som vil gøre det meget sværere for os

Vi bliver sandsynligvis nødt til at fokusere på at lave GrapheneOS-enheder hurtigere, end vi havde forventet

Vi forstår ikke, hvorfor disse ændringer blev foretaget

🇺🇸 DOJ har anmodet om, at Android og Chrome opdeles i separate virksomheder

De er måske ved at forberede sig på det x.com/GrapheneOS/status/193259 (tråd)

Google · Android 16 is hereBy Seang Chau
In May, we began preparing to port to Android 16 despite our most active senior developer responsible for leading OS development being unavailable. Android 16 launched today and porting is going to be significantly more difficult than we were expecting.

We did far more preparation for Android 16 than we've ever done for any previous yearly release. Since we weren't able to obtain OEM partner access, we did extensive reverse engineering of the upcoming changes. Developers also practiced by redoing previous quarterly/yearly ports.

Unfortunately, Android has made changes which will make it much harder for us to port to Android 16 and future releases. It will also make adding support for new Pixels much more difficult. We're likely going to need to focus on making #GrapheneOS devices sooner than we expected.

We don't understand why these changes were made and it's a major turn in the wrong direction. Google is in the process of losing multiple antitrust cases in the US. Android and Chrome being split into separate companies has been requested by the DOJ. They may be preparing for it.

We're hard at work on getting the port to Android 16 done but there's a large amount of additional work we weren't expecting. It can be expected to take longer than our usual ports due to the conscription issue combined with this. It's not good, but we have to deal with it.

Having our own devices meeting our hardware requirements (https://grapheneos.org/faq#future-devices) would reduce the time pressure to migrate to new releases and could be used to obtain early access ourselves. Based on talks with OEMs, paying for what we need will cost millions of dollars.
GrapheneOS logo
GrapheneOSGrapheneOS Frequently Asked QuestionsAnswers to frequently asked questions about GrapheneOS.