𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕

»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.

📱 https://www.heise.de/news/Android-Google-erschwert-die-Entwicklung-von-Custom-ROMs-10444392.html

#android #grapheneos #google #mobile #handy #customrom

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. 

heise online
Jun 14 at 6:10amWeb
Show threadStullekovskiJun 14
@kubikpixel @GrapheneOS mW wurde der Entwickler von außen mit Dreck beworfen
Show threadSebastianJun 14

@kubikpixel @GrapheneOS Der Artikel beschreibt doch, warum es für CustomROMs schwerer ist:
- gerätespezifische Binärdaten (Treiber) für Pixel-Geräte werden nicht mehr veröffentlicht
- vorgenommene Kernel-Patches werden spät, gesammelt und nur rudimentär dokumentiert veröffentlicht

Ersteres trifft ein CustomROM ausschließlich für Pixel-Geräte natürlich hart, letzteres erschwert auch anderen ROMs das Leben.
Da braucht es kein Glauben an die eine oder andere Seite.

Show threadfloJun 14
@sebastian
@kubikpixel
Bin gespannt, was das kurz- und mittelfristig für mich als Benutzer eines Pixel-Smartphones mit
@GrapheneOS bedeutet.

Hab auch noch ein /e/OS, das dürfte wohl auch betroffen sein ...
Show threadGrapheneOSJun 14
@fasnix @kubikpixel @sebastian Our port to Android 16 will take longer than expected to ship. It already would have been available. It will also take significantly longer for us to support future Pixels instead of being able to do it in a day. As an end user, that's the impact on you. We're backporting the Android 16 Pixel driver/firmware patches to Android 15 QPR2 so our users can still get those patches in a similar timeline as if these AOSP changes hadn't happened and we shipped A16 already.
Show threadfloJun 14
@GrapheneOS
Thanks for all the work you do, very much appreciated!

@kubikpixel @sebastian
Show threadGrapheneOSJun 14
@fasnix @kubikpixel @sebastian Worth noting that /e/OS is not a safe OS to use. It has atrocious privacy and security, being far behind on shipping basic privacy/security patches and OS releases with the full set of privacy/security patches. They mislead users about what is provided and cover up the lack of patches. You would be better off using LineageOS than /e/OS even though it shares those issues because it's not nearly as bad. DivestOS is unfortunately dead partly due to attacks by Murena.
Show threadfloJun 14
@GrapheneOS
Thanks for that.
Have you also detailed information about e.g CashyOS, which also seems to be available for smartphone usage?

@kubikpixel @sebastian
Show threadGrapheneOSJun 14

@fasnix @kubikpixel @sebastian https://eylenburg.github.io/android_comparison.htm is a third party comparison of AOSP-based operating systems. The site also has a bunch of other software comparisons. That's a good starting point.

Also see https://privsec.dev/posts/android/choosing-your-android-based-operating-system/.

Comparison of Android-based Operating Systems

Comparison of Android-based Operating Systems

Show threadGrapheneOSJun 14
@sebastian @kubikpixel We didn't use their binary firmware/driver releases and kernel changes are not being released late. It would be best if people got information about GrapheneOS from us. We have several threads about our port to Android 16 covering the regressions in AOSP and how we're working around it. Our initial baseline port to Android 16 is done and we're working on completing device support.
Show threadSebastianJun 14
@GrapheneOS @kubikpixel Thanks for clarifying. Unfortunately it is not always easy for users to follow all the details, so articles of IT journals seem to be a good entry point for getting a brief summary. But it's obviously more and more neccessary to study primary sources by yourself.
Show threadKevin Karhan Jun 14
@kubikpixel soweit ich beurteilen kann hat @GrapheneOS aber recht was den Zugang zu #Android-#Sourcecode angeht: #Google bietet diesen nicht mehr öffentlich an!
Show threadGrapheneOSJun 14

@kubikpixel Our team being targeted with fabricated stories, spin and harassment speaks to the people doing it and supporting it than us.

We have completed our initial port to Android 16 and are putting device support back together. You should get information about GrapheneOS from us rather than people we have not talked to about it.