Créer un compteSe connecter

Recherches récentes

Aucune recherche récente

Options de recherche

Disponible uniquement lorsque vous êtes connecté.
mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

649
comptes actifs

mastouille.fr: À proposAnnuaire des profilsPolitique de confidentialité

Mastodon: À proposTélécharger l’applicationRaccourcis clavierVoir le code sourcev4.3.4

#grapheneos

18 messages18 participants3 messages aujourd’hui
Public *
𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕

»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-ROMsPar Andreas Floemer
#android#grapheneos#google
Public
scotty86 🇺🇦🕊️

#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.
Public
Karl Voit :emacs: :orgmode:

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

YouTubeInstalling GrapheneOS the Easy WayPar Mental Outlaw
#Android#security#privacy
Public
Tommaso Gagliardoni

Embrace, Extend, Extinguish:

androidauthority.com/google-no

This was totally expected, and IMHO just a matter of time before things get worse and Google pulls the plug.

Honestly, I can't wait for the whole Android model to die a well-deserved death. Hopefully something better will be born from the ashes.

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.
#android#aosp#google
Public
Final
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.
ExplorerFlux en direct
À propos