home.social

#calyxos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #calyxos, aggregated by home.social.

  1. Google reCAPTCHA Update Sparks Concerns For Privacy-Focused Android Users

    digitalescapetools.com/2026/05

    > New Google verification flows tied to Play Services and hardware attestation are raising concerns across the privacy and de-Googled Android communities.
    #grapheneos #calyxos #degoogle

  2. CalyxOS released Android 16 test builds for Pixels, Fairphone, and Motorola devices, adding updated FOSS apps and expanded deGoogled Chromium changes 📱
    The privacy-focused ROM replaced apps like Orbot and Organic Maps, while limiting telemetry and delaying unfinished security features pending audits 🔒

    🔗 calyxos.org/news/2026/05/04/ca

    #TechNews #Tech #CalyxOS #Google #Android16 #Android #Privacy #OpenSource #FOSS #DeGoogled #Cybersecurity #Linux #Signal #Tor #Fairphone #Pixel #Chromium #Security #ROM

  3. CalyxOS released Android 16 test builds for Pixels, Fairphone, and Motorola devices, adding updated FOSS apps and expanded deGoogled Chromium changes 📱
    The privacy-focused ROM replaced apps like Orbot and Organic Maps, while limiting telemetry and delaying unfinished security features pending audits 🔒

    🔗 calyxos.org/news/2026/05/04/ca

    #TechNews #Tech #CalyxOS #Google #Android16 #Android #Privacy #OpenSource #FOSS #DeGoogled #Cybersecurity #Linux #Signal #Tor #Fairphone #Pixel #Chromium #Security #ROM

  4. #CalyxOS hat sich ohne Probleme auf meinem #Pixel8a installieren lassen.
    Durch das Skript geht es fast automatisch.
  5. #calyxos está volviendo a la vida después de cambio de integrantes. Ayer instalé la nueva versión (en beta) para probar. Mi único gran problema fue con la copia de seguridad de Whatsapp, que aunque aparece en la cuenta de google, Whatsapo me dice que no existe (y cometí el estúpido error se no hacer una copia local, que si hice con Signal)

  6. CalyxOS is almost back on track and has a test build available.

    Title: #CalyxOS progress report - our test build with Android 16 is here

    Source: calyxos.org/news/2026/05/04/ca

    #Android

  7. Just read the latest progress report from CalyxOS and I'm really glad they've finally released the Android 16 test build.

    Very excited to try the new Material You design system once it stabilizes and big kudos to @calyxos for not backing down and continuing to deliver privacy focused android.

    #foss #opensource #android #calyxos #tech #technology #privacy #oss

  8. Since switching from #CalyxOS back to stock #Android a few days ago, my battery life has gone to hell. I could go all day on a charge with my Pixel 6a. Now if I use my phone for any period of time I'm lucky if I make it to lunch.

    Kinda hoping the folks at Calyx are getting close to finalizing all the changes they've been making for future releases.

  9. My next phone will run either #CalyxOS or #GrapheneOS. I was hoping for Calyx, because it runs on a Moto you can get on ebay for about $100. Graphene only runs on recent Pixels, which are $300-600.

    The good folks at Calyx, who Iʼm sure are doing the best they can, have yet to offer a timeline as to when CalyxOS will be available again after a recent operational reboot — though they assure us it will be soon.

    The phone I have is on its last legs so I need to make the call asap. So frustrating.

  10. Forgive my kvetching, but it drives me nuts that #AOSP-based #Android OSes always treat hyphenated words as words.

    For example, if you type in "apple-cart," you get a red squiggly underline and it tries to recommend replacing it with "apricot" or something. The only way around it is to add every. single. hyphenated. word. you. use. into the dictionary. 😮‍💨

    It's been a constant, daily annoyance for the past five and a half years, and the only fix is to install something like GBoard and use its spelling correction engine or whatever you call it, and I'd rather not.

    I've experienced it on #CalyxOS and #IodéOS, but I don't recall if #GrapheneOS has the same issue, because I only tried it briefly.

    #LineageOS #Iodé #Iode #IodeOS #Graphene #GOS

  11. If you're using Google Maps on #CalyxOS and it stopped working recently, that's because latest Google Maps needs a newer #microG version to work. As CalyxOS paused development, the workaround for now is to downgrade Maps to version 1068495399 (March release).

    1. Uninstall Google Maps app
    2. Open Aurora store, find "Google Maps" app
    3. Click "Select version"
    4. Put "1068495399"
    5. Add Google Maps to block list in Aurora to prevent automatic updates

    Source: community.iode.tech/t/google-m

  12. If you're using Google Maps on #CalyxOS and it stopped working recently, that's because latest Google Maps needs a newer #microG version to work. As CalyxOS paused development, the workaround for now is to downgrade Maps to version 1068495399 (March release).

    1. Uninstall Google Maps app
    2. Open Aurora store, find "Google Maps" app
    3. Click "Select version"
    4. Put "1068495399"
    5. Add Google Maps to block list in Aurora to prevent automatic updates

    Source: community.iode.tech/t/google-m

  13. If you're using Google Maps on #CalyxOS and it stopped working recently, that's because latest Google Maps needs a newer #microG version to work. As CalyxOS paused development, the workaround for now is to downgrade Maps to version 1068495399 (March release).

    1. Uninstall Google Maps app
    2. Open Aurora store, find "Google Maps" app
    3. Click "Select version"
    4. Put "1068495399"
    5. Add Google Maps to block list in Aurora to prevent automatic updates

    Source: community.iode.tech/t/google-m

  14. If you're using Google Maps on #CalyxOS and it stopped working recently, that's because latest Google Maps needs a newer #microG version to work. As CalyxOS paused development, the workaround for now is to downgrade Maps to version 1068495399 (March release).

    1. Uninstall Google Maps app
    2. Open Aurora store, find "Google Maps" app
    3. Click "Select version"
    4. Put "1068495399"
    5. Add Google Maps to block list in Aurora to prevent automatic updates

    Source: community.iode.tech/t/google-m

  15. New podcast episode: Put some privacy in your smartphone! 📣 🎧

    How can you use an Android smartphone while protecting your privacy? Who should you turn to for more privacy-friendly Android alternatives?
    Can you install Linux on your phone?

    With @fla from @Framasoft , we answer these questions!

    👉 projets-libres.org/en/podcast/

    #podcast #opensource #privacy #eos #iodeOS #calyxos #postmarketos #fairphone #commown #murena #ubuntutouch #grapheneos

  16. Nouvel épisode du podcast : met de la vie privée dans ton smartphone 📣 🎧

    Comment faire en sorte d'utiliser un smartphone Android tout en garantissant sa vie privée ? A qui s'adresser pour installer alternatives d'Android plus respectueuses ?
    Peut-on installer Linux sur son téléphone ?

    Avec @fla de @Framasoft nous répondons à ces questions !

    👉 projets-libres.org/podcast/s4e

    #podcast #privacy #vieprivee #smartphone #framasoft #calyxos #eos #iodeOS #graphene #postmarketos #ubuntutouch

  17. CW: GrapheneOS
    I've been using @GrapheneOS for several months, now. I couldn't be happier. I had been using @calyxos. But, when I got a new phone I decided to try GOS. What luck! Shortly after I put #GrapheneOS on my Pixel 8 there was a staff melt down at #CalyxOS that disrupted the COS production. So I would have been stuck without upgrades. But, I have to say that I prefer the way GOS does privacy/security, anyway. And GOS support is more helpful. Go Go #GOS!!
  18. "If you care about privacy and security, you should install GrapheneOS on a Google Pixel phone instead."

    This was a reply on Bluesky to my post where I said I was willing to install CalyxOS on my Fairphone. [1]

    Before buying a Fairphone, I considered buying a Google Pixel. However, I didn't like the idea of depending on a cloud system to store my photos and music. Not to mention, it's a Google product. I wanted to be able to use an external storage card.

    I chose the Fairphone because of the company's mission and the ability to install either /e/OS or CalyxOS. I prefer to stay out of OS wars, but if you can make a case for why one alternative Android OS is better than another in terms of privacy, I'd like to hear it.

    #CalyxOS #eOS #GrapheneOS #Fairphone #GooglePixel #Google

  19. @pojntfx At the moment, I cannot fully understand the document you shared, so I used an AI assistant (sorry in advance) to try to understand it.

    I want to install #CalyxOS on my #Fairphone soon:

    "On CalyxOS specifically: CalyxOS uses microG, which implements partial Play Integrity support — but it typically only reaches MEETS_BASIC_INTEGRITY, not MEETS_STRONG_INTEGRITY. The wallet as architected would reject it outright."

    That is really problematic. Where is the #DigitalSovereignty here?

    Cc @sovtechfund

    #EU #Germany

  20. Meine Startbedingungen sind etwas anders: Ich habe das 'ungesicherte' #calyxOS auf dem #Smartphone, bin also schon länger #entgoogelt. Nur es gab immer weniger App-Updates, insbesondere die Banking-App wollte sich jetzt nicht mehr aktualisieren und funktionierte somit nicht mehr.
    Root, Entwickleroptionen, OEM-Entsperrung ist alles kein Problem gewesen. Nur die Installation bleibt hängen. Die Firmware-Updates sind mit calyxOS wohl auch nicht mehr aktualisiert worden.
    Die Firmware ist auf dem Stand Mai 2025 (März 2026 verfügbar), scheinbar noch für Android 14, während calyxOS schon auf Android 15 ist.
    Firmwareupdate habe ich nicht hinbekommen. #e OS kommt bis zu Schritt 9/24 nach https://e.foundation/installer/ danach wird das #Fairphone5 nicht mehr erkannt. Ich muss mal ein paar Foren bemühen... Demnächst mehr!

    Bei der Recherche bin ich über den Punkt 'Mobile Datennutzung immer aktiviert' bei den Entwickleroptionen gestolpert. Damit waren dann reichlich Updates wieder möglich: Aurora hatte mehr als 20 Updates für mich im Angebot - nu geht auch das Banking wieder - Ups!
    Das ist mir bei Verifizierungsaufgaben schon früher aufgefallen: Über WLAN geht's nicht, auf mobile Daten umgestellt und schon ging alles durch. Traurige Erkenntnis.

    Weitere Erkenntnis: Mein Arbeits-WLAN #eduroam geht nicht, wenn die SIM-Karte aus dem #Handy ist! Was werden den da für Daten gebraucht um ins WLAN rein zu kommen? - huiuiui!

  21. Meine Startbedingungen sind etwas anders: Ich habe das 'ungesicherte' #calyxOS auf dem #Smartphone, bin also schon länger #entgoogelt. Nur es gab immer weniger App-Updates, insbesondere die Banking-App wollte sich jetzt nicht mehr aktualisieren und funktionierte somit nicht mehr.
    Root, Entwickleroptionen, OEM-Entsperrung ist alles kein Problem gewesen. Nur die Installation bleibt hängen. Die Firmware-Updates sind mit calyxOS wohl auch nicht mehr aktualisiert worden.
    Die Firmware ist auf dem Stand Mai 2025 (März 2026 verfügbar), scheinbar noch für Android 14, während calyxOS schon auf Android 15 ist.
    Firmwareupdate habe ich nicht hinbekommen. #e OS kommt bis zu Schritt 9/24 nach https://e.foundation/installer/ danach wird das #Fairphone5 nicht mehr erkannt. Ich muss mal ein paar Foren bemühen... Demnächst mehr!

    Bei der Recherche bin ich über den Punkt 'Mobile Datennutzung immer aktiviert' bei den Entwickleroptionen gestolpert. Damit waren dann reichlich Updates wieder möglich: Aurora hatte mehr als 20 Updates für mich im Angebot - nu geht auch das Banking wieder - Ups!
    Das ist mir bei Verifizierungsaufgaben schon früher aufgefallen: Über WLAN geht's nicht, auf mobile Daten umgestellt und schon ging alles durch. Traurige Erkenntnis.

    Weitere Erkenntnis: Mein Arbeits-WLAN #eduroam geht nicht, wenn die SIM-Karte aus dem #Handy ist! Was werden den da für Daten gebraucht um ins WLAN rein zu kommen? - huiuiui!

  22. Meine Startbedingungen sind etwas anders: Ich habe das 'ungesicherte' #calyxOS auf dem #Smartphone, bin also schon länger #entgoogelt. Nur es gab immer weniger App-Updates, insbesondere die Banking-App wollte sich jetzt nicht mehr aktualisieren und funktionierte somit nicht mehr.
    Root, Entwickleroptionen, OEM-Entsperrung ist alles kein Problem gewesen. Nur die Installation bleibt hängen. Die Firmware-Updates sind mit calyxOS wohl auch nicht mehr aktualisiert worden.
    Die Firmware ist auf dem Stand Mai 2025 (März 2026 verfügbar), scheinbar noch für Android 14, während calyxOS schon auf Android 15 ist.
    Firmwareupdate habe ich nicht hinbekommen. #e OS kommt bis zu Schritt 9/24 nach https://e.foundation/installer/ danach wird das #Fairphone5 nicht mehr erkannt. Ich muss mal ein paar Foren bemühen... Demnächst mehr!

    Bei der Recherche bin ich über den Punkt 'Mobile Datennutzung immer aktiviert' bei den Entwickleroptionen gestolpert. Damit waren dann reichlich Updates wieder möglich: Aurora hatte mehr als 20 Updates für mich im Angebot - nu geht auch das Banking wieder - Ups!
    Das ist mir bei Verifizierungsaufgaben schon früher aufgefallen: Über WLAN geht's nicht, auf mobile Daten umgestellt und schon ging alles durch. Traurige Erkenntnis.

    Weitere Erkenntnis: Mein Arbeits-WLAN #eduroam geht nicht, wenn die SIM-Karte aus dem #Handy ist! Was werden den da für Daten gebraucht um ins WLAN rein zu kommen? - huiuiui!

  23. Meine Startbedingungen sind etwas anders: Ich habe das 'ungesicherte' #calyxOS auf dem #Smartphone, bin also schon länger #entgoogelt. Nur es gab immer weniger App-Updates, insbesondere die Banking-App wollte sich jetzt nicht mehr aktualisieren und funktionierte somit nicht mehr.
    Root, Entwickleroptionen, OEM-Entsperrung ist alles kein Problem gewesen. Nur die Installation bleibt hängen. Die Firmware-Updates sind mit calyxOS wohl auch nicht mehr aktualisiert worden.
    Die Firmware ist auf dem Stand Mai 2025 (März 2026 verfügbar), scheinbar noch für Android 14, während calyxOS schon auf Android 15 ist.
    Firmwareupdate habe ich nicht hinbekommen. #e OS kommt bis zu Schritt 9/24 nach https://e.foundation/installer/ danach wird das #Fairphone5 nicht mehr erkannt. Ich muss mal ein paar Foren bemühen... Demnächst mehr!

    Bei der Recherche bin ich über den Punkt 'Mobile Datennutzung immer aktiviert' bei den Entwickleroptionen gestolpert. Damit waren dann reichlich Updates wieder möglich: Aurora hatte mehr als 20 Updates für mich im Angebot - nu geht auch das Banking wieder - Ups!
    Das ist mir bei Verifizierungsaufgaben schon früher aufgefallen: Über WLAN geht's nicht, auf mobile Daten umgestellt und schon ging alles durch. Traurige Erkenntnis.

    Weitere Erkenntnis: Mein Arbeits-WLAN #eduroam geht nicht, wenn die SIM-Karte aus dem #Handy ist! Was werden den da für Daten gebraucht um ins WLAN rein zu kommen? - huiuiui!

  24. Meine Startbedingungen sind etwas anders: Ich habe das 'ungesicherte' #calyxOS auf dem #Smartphone, bin also schon länger #entgoogelt. Nur es gab immer weniger App-Updates, insbesondere die Banking-App wollte sich jetzt nicht mehr aktualisieren und funktionierte somit nicht mehr.
    Root, Entwickleroptionen, OEM-Entsperrung ist alles kein Problem gewesen. Nur die Installation bleibt hängen. Die Firmware-Updates sind mit calyxOS wohl auch nicht mehr aktualisiert worden.
    Die Firmware ist auf dem Stand Mai 2025 (März 2026 verfügbar), scheinbar noch für Android 14, während calyxOS schon auf Android 15 ist.
    Firmwareupdate habe ich nicht hinbekommen. #e OS kommt bis zu Schritt 9/24 nach https://e.foundation/installer/ danach wird das #Fairphone5 nicht mehr erkannt. Ich muss mal ein paar Foren bemühen... Demnächst mehr!

    Bei der Recherche bin ich über den Punkt 'Mobile Datennutzung immer aktiviert' bei den Entwickleroptionen gestolpert. Damit waren dann reichlich Updates wieder möglich: Aurora hatte mehr als 20 Updates für mich im Angebot - nu geht auch das Banking wieder - Ups!
    Das ist mir bei Verifizierungsaufgaben schon früher aufgefallen: Über WLAN geht's nicht, auf mobile Daten umgestellt und schon ging alles durch. Traurige Erkenntnis.

    Weitere Erkenntnis: Mein Arbeits-WLAN #eduroam geht nicht, wenn die SIM-Karte aus dem #Handy ist! Was werden den da für Daten gebraucht um ins WLAN rein zu kommen? - huiuiui!

  25. None of the non-Google-OSes does officially support my Galaxy Tab A9+ 5G 😭

    #lineageOS #CalyxOS #GrapheneOS #e_OS #iodéOS

  26. Hilfe!

    Das Kind hat ein Handy mit CalyxOS ohne Google Play-Dienste.
    Jetzt kommt der soziale Druck. Die anderen™️Kinder haben Spiele-Apps.

    Wie macht Ihr das? In F-Droid habe ich auch nichts gefunden.

    Gesucht wird u.a. Tetris und Escape Puzzle.

    Gibt es evtl. Repositories für F-Droid mit Spielen?

    EDIT: vielen Dank für Eure Tipps. Es sieht so aus, als wenn ich die perfekten Spiele aus f-droid präsentieren, und trotzdem müssten es dieselben Spiele wie bei den anderen sein. Zum Verzweifeln.
    Die Tipps werde ich trotzdem noch weiter verfolgen.

    :BoostOK:

    #CalyxOS #F-Droid #Handy # #FDroid #MobileGaming #GoogleFree

  27. I am so happy to see that CalyxOS is finally getting back on the track. Can't wait for the new releases: calyxos.org/news/2026/02/24/ca

    #calyxos #android

  28. #Frage #Android #Betriebssystem #CalyxOS

    Moin!
    Weiß eigtl jemand, was mit CalyxOS passiert ist? Entwickeln die noch oder ist die angekündigte Pause von letztem Jahr nun zu einem Ende von CalyxOS geworden?
    Wenn das Projekt gestorben ist, fände ich das extrem schade, weil ich das OS auf meinem Phone wirklich sehr mag, gerade was die Oberfläche und die Bedienbarkeit angeht. Dann muss ich mich langsam um ein neues Betriebssystem für mein Phone kümmern, worauf ich gar keine Lust habe. 😕

  29. Waiting for a new version of CalyxOS. Only Linux mobile platform that really worked for me. Tried Ubuntu Touch and others. No joy. CalyxOS worked just great (on a Fairphone 5). Status: calyxos.org/news/2026/02/24/ca

  30. @GrapheneOS @attilax @LearnToLivePrivate @RustRaven @jmoupah @Yrrussaj @sebsauvage @jolla Hey Graphene OS folks.

    First, it's really great that you guys have created a security focused deGoogled Android operating system.

    Given the problems of American big tech, I applaud you for creating an alternative.

    So full credit where credit is due.

    That being said, constantly badmouthing every other non-Apple and non-Google smartphone maker and operating system is not a good look.

    And jumping into any thread on Mastodon where there's a mention of another alternative smartphone maker or OS to badmouth them is not a good look.

    You say Jolla is no good. SailfishOS is no good. Fairphone is no good. Murena is no good. CalyxOS is no good. Dumbphones are no good.

    I'd imagine you'd probably win more people over if you talked more about why people should choose Graphene instead why they shouldn't choose one of the others.

    Because right now, there are tradeoffs with every mobile OS.

    That includes Graphene.

    For example, there are people for whom limiting their exposure to Google and Apple is more important than choosing the most locked down option available.

    For such people, needing to buy a Google Pixel phone to run Graphene is a massive negative.

    That's even if the Google Pixel is the best hardware from a security perspective.

    And in that case, yeah there are other options that may be a better fit for those people.

    There's another issue.

    There seems to be many Reddit threads and YouTube videos and blogs out there from people who were enthusiastic about Graphene, but have soured on it.

    And the funny thing is there's a pattern to it. "Cult-like" and "toxic" seems to be phrases that tend to be used a lot.

    I've also noticed a recurring pattern you put for why the other alternatives are bad is because people connected with those businesses or companies badmouth Graphene.

    It seems to me like Graphene constantly bags those other projects. When anyone connected with those projects responds, that response is presented by you guys as evidence of bullying and harassment, without that context.

    And the recurring line about how people should just stick with iOS or Google Android if they don't choose Graphene? Just shameful. And completely misses the point of why some people are looking for alternative platforms in the first place.

    And the more people who choose an alternative OS, the more normal it becomes to do it, which ultimately leads to more people looking at alternatives like Graphene.

    #Android #Jolla #SailfishOS #AOSP #Graphene #GrapheneOS #Murena #Calyx #CalyxOS #Linux #infosec #opensource

  31. It's interesting how alternatives to the classic corporate #Android keep coming up

    1. Android-based but modified & 'de-Googled', like I think #LineageOS, #CalyxOS, #GrapheneOS, #ShiftOS

    2. 'Classic' #Linux, like #SailfishOS, #UbuntuTouch, #PostmarketOS (postmarketos.org)

    3. Linux as an Android app. Like #NOMoneDesktop (desktop.nomone.com; video: youtube.com/watch?v=JqFpzI-FsU0)

    Hopefully the #JollaPhone with sailfishos.org will have thrived by the time I have to replace my phone

  32. @postmarketOS Love FOSS and don't trust Google, but I don't really get the criticism @thibaultamartin . They are still releasing code and accepting modifications, IIUC, just on a different cadence. Also, if the governance becomes intolerable, couldn't AOSP be forked? I'm sure I'm missing something, but we've got a huge ecosystem at stake, and I don't see good FOSS players like #calyxos or #iode or #eos making plans to switch.
  33. Does Android's SafetyNet actually make it safer for apps to run?

    @cybersecurity

    Currently have a #complaint at #kifid (instititute for complaints against financial service providers in the Netherlands) against #revolut because it doesn't work on #degoogled phones. They claim it makes it more secure. Can anybody point me to a study or expert opinion on the #security benefits of #safetynet and how it protects #android phones?

    My inkling about googled OEM phones is this:
    - many are old
    - many aren't receiving patches anymore
    - many receive security patches late (weeks or months)

    And regarding degoogled phones:
    - they are more likely to get security patches more quickly
    - they are often maintained longer than OEM phones
    - certain ROMs #calyxos #grapheneos (to a certain degree #eos) are actually more secure than stock OEMs due to either
    * security focus
    * faster security patches
    * being limited to relockable bootloaders

  34. The #FOSDEM FOSS on Mobile devroom schedule is out!

    fosdem.org/2026/schedule/track

    It's going to be a great day of talks on AOSP, Mobile Linux and more; covering the full stack from SoCs to app ecosystems.

    14 full length talks, 7 lightning talks, 23 speakers.

    #fosdem26 #FossOnMobile #AOSP #Android #CalyxOS #OpenHarmony #postmarketOS #Phosh #SailfishOS #Gnomeonmobile #LinuxOnMoble #MobileLinux

  35. The deadline for submitting to the FOSS on Mobile devroom, #FOSDEM26, is Monday 1st December.

    Just a few more days! Don't forget to get your submission in 📮

    It was a brilliant event last year, this year is a full day and even more topics.

    lists.fosdem.org/pipermail/fos

    #fosdem #FossOnMobile #LinuxOnMoble #MobileLinux #AsteroidOS #postmarketOS #nemomobile #aosp #pureos #phosh #mobian #calyxos #SailfishOS #ubports #PlasmaMobile

  36. I am currently researching at the FSFE for FreeYourAndroid on the topic of microG.

    If you use microG, how have you installed it? Or was it already there?

    (User app can come from F-Droid repo too)

    ---

    Ich recherchiere gerade bei der #FSFE für #FreeYourAndroid zum Thema #microG.

    Falls du es benutzt, wie hast du es installiert? Oder war es bereits da?

    #Android #Google #Privacy #PlayServices #Whatsapp #Navigation #DBNavigator #LineageOS #iodeOS #eOS #CalyxOS #CrDroid #UnifiedPush #BeaconDB

  37. Na, toll.

    Der erste Versuch mit dem #IodeOS installer mein #Fairphone4 von #CalyxOs zu befreien, scheitert schon mal:

    Ich hänge im #FastBoot fest. Jeder reboot ended im #fastboot

    Jetzt meint der installer, das handy wird nicht unterstützt :(

    Also mal die Manuellen Schritte probieren...

  38. The FOSS on Mobile devroom is returning to FOSDEM in 2026! Always an amazing experience: great talks and a brilliant audience.

    This year it's grown to a full day and all FOSS on Mobile topics, including AOSP.

    Got an interesting mobile project or topic? It's a great place to share. Submission deadline 1st December.

    lists.fosdem.org/pipermail/fos

    #fosdem #fosdem26 #FossOnMobile #LinuxOnMoble #MobileLinux #AsteroidOS #postmarketOS #nemomobile #aosp #pureos #phosh #mobian #calyxos #SailfishOS #ubports

  39. CW: longpost about grapheneos, and then i'll shut up about it

    look, i don't want to bully #grapheneos. everyone be nice! but i'm tired of staying silent while their accounts spew unchecked lies for years, so i'll just say this and then go back to ignoring it again.

    in my time working for #calyx / on #calyxos (a time which has now ended), despite graphene's claims to the contrary, i *never* saw anyone from calyx spread or encourage malice toward their project or community or harass them *at all*. if anything, due to a history of negative attention coming from their direction, calyx has long had a rule *not* to discuss their project in calyx's online spaces, but has still demonstrated respect for their OS in public, e.g. at conferences, acknowledging it's a good choice for some.

    meanwhile, there has been a steady stream of smears, accusations, and now schadenfreude from their side about calyxos. you need look no further than their official social media accounts for evidence of this; you don't need the "receipts" from me to see the malice. it's all on full display, no background knowledge or rewriting of history required to understand.

    contrary to their claims, during my time, by policy, calyx didn't even *look* at their code, let alone incorporate it (apart from some early remnants that are properly attributed, like signing scripts). in fact, with the exception of a weird, random proposal from the founder, as far as i know, calyx never even tried to interact with them whatsoever.

    anyway... 4-5 years ago, before i had even finished deciding what OS to use, i was banned from grapheneos's chat channels before even getting around to send any messages - apparently just for existing in the calyx channels - and that made my OS decision easy: i wouldn't use an OS run by folks who'd do something like that. funnily enough, if not for that ban, and subsequently learning more about their behavior, who knows? i may have used grapheneos, just ignored the community stuff, and never ended up working for calyx in the first place.

  40. so, while there were other things that influenced my decision to resign from #calyx, in the end, the biggest were the on-going outrageous behavior coming out of the engineering department, and a failure of leadership to do anything meaningful about it. although i deeply respect the #calyxos team and the many great folks at the institute, unfortunately, until/unless something is done, i cannot support calyx, and i cannot recommend donating to them right now. (9/9)

  41. none of this even delves into the #calyx engineering director's endless gaslighting, predictable derailing of discussions and decision-making, hoarding of access and information, attempts to delay / sabotage the revival of #calyxos, and apparent eagerness to direct $10,000's of member donations toward goods and services from the warmongering likes of AWS and thales. those would warrant threads of their own. (8/9)

  42. some may think, "i don't mind if #calyx moves my name, email, address, etc to vultr. it's not like it's AWS" - or "this is why i never share any personal info that i can't afford to be leaked anyway". but in my mind, given that calyx has hosted its own services for years - VPN, tor exit nodes, #calyxos release server, etc - i think people have come to expect this and to hold them to a higher standard for data handling and transparency. it's your data. shouldn't you know who has it? (7/9)

  43. "My reading of the privacy policy is different from yours."

    i want to elaborate on why i left #calyx / #calyxos. (everything in this thread is my opinion or interpretation.)

    while there were many factors, the breaking points for me were a non-consensual transfer of members' personal information to a third-party server, a total lack of notification, and a ridiculous defense. the following messy posts will continue my perspective and recollection of this particular event. (1/9)

  44. @mason

    allegedly, and from my perspective as a former calyxos employee (i do not represent them)...

    the founder was the keeper of the signing keys, and has stated this publicly. when he separated from the institute (which is a whole other story), he didn't give the signing keys to the institute in a timely manner, if at all. although there was no evidence that the keys had been compromised or accessed from outside the organization, there *was* reason to believe that they had not always been handled in a secure manner (which is yet another whole other story). also, because these were key *files*, and probably not even protected by passphrases (but i don't know), copies were always *possible*.

    the OS team decided to only release updates signed with *fully* trusted keys going forward, that were not subject to unauthorized copies. the OS team has been working on a hardware security module-based solution for signing. the exception to this was one last update to inform users about this situation, to the extent permitted by comms folks. this was facilitated by eventual cooperation from the founder.

    that being said, i do not myself believe that there is any actual risk today associated with using a build signed with these older keys, apart from it not having the latest updates. but i also support switching to new keys that are better safeguarded, and i can't guarantee there wouldn't be a risk associated with these older keys in the future.

    there is more to know as well, but too much to write here. still, it is false to say that the calyxos team doesn't want you to know this.

    source: i worked on #calyxos while all this was happening. i no longer work for #calyx. and this is all just alleged, based on what i experienced and was told. i never signed an NDA 🙃