#DeGoogled #Linux #opensource OS's phone's ...
Do we have any update on #faceunlock on:
#e/os/ #Murena #Graphene #LineageOS #CalyxOS #CopperheadOS #iodé #BRAXME #SilentOS #unpluggedOS #AboveOs #VollaOS #UbuntuTouch #OmniROM #paranoidandroid #sailfishos #jollaOS #oniroproject #liberux #FreePhone
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:
https://antyweb.pl/google-zamyka-androida-dluzej-poczekamy-na-aktualizacje
@rl_dane I've been wondering the same. The iPhone I used before I switched to a custom ROM over 2.5 years ago is still in my drawer. Supposed to be my travel phone that still gets updates but I'd hate to go back. Wait and see, I guess. Darn Google! #android #foss #calyxos #grapheneos
From what I've read up to now, Google is very busy to save their arse. Google is Keeping Pixel phone sources now to it self, because there a chances that Google will be hacked up and divided up in smaller companies which will have to compete with each other, just like that process Ma Bell phone Company in the 1960s Of The last century
Do you remember the phrase?
We don't have to
We don't want to
We're the f%cking phone company!
Why would you be so masochistical and go to a totalitarian controlled ecosystem?
Just use your Android as you are used to and hack the vanilla Operating System in a manner that it is usable and enjoyable to you
On apple you will be torturing yourself and you will be paying them premium for crappy Hardware
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 released Android 16 to AOSP - but without Pixel device-specific source code
RIP Pixel in AOSP
https://gitlab.com/CalyxOS/calyxos/-/issues/3328
#Android #AOSP #CalyxOS
For the first time I flashed a phone with #CalyxOS from another CalyxOS phone using @calyxos 's web installer ( https://install.calyxos.org/ ). No additional laptop was necessary. Quite a step from the first times we flashed phones at the @fsfe in 2012. Thanks @grote for the hint to try that out!
Moto (now Lenovo) and Samsung both make amazing devices, but I won't go near 'em because they love to lock the bootloader and do petty crap like that.
Even when the models are unlockable, they aren't supported by the OSes I like.
Going with a FOSS Android OS, you lose some functionality, but you also lose a TON of the planned obsolescence.
I had my Pixel 4a 5G on stock android for about a year, and it started getting slow. I switched to #CalyxOS, and it was fast as greased lightning again.
Okay internet freaky people, I have a Google Pixel 4a (Sunfish) device that's been sitting in a drawer pretty much since unboxing. I installed #grapheneos on it a month or so ago, but on first boot got a notification that the device is no longer supported. #calyxos is EOLing it in August, and their web installer doesn't support it now. #lineageos _does_ support it, but there is enough of a time investment in making it happen that I may as well consider more... outré setups.
Sooo, any recommendations? Doesn't need to be an Android variant, as long as it's #linux or #bsd under the hood and I can get a shell on it.
Google Pixel 9a is now officially supported by CalyxOS
It is now a month since I switched from a normal #android phone to one running #calyxos. While I still use #microg it is not linked with a google account anymore. I use the Aurora Store and f-droid, are more conscious which apps I install. Generally, I use less apps and more direct links via browser.
And I must say: it is great. Less notifications, less stress, less fear priming an algorithm in a wrong way.
I do not miss much. Payment via NFC and information in google maps sometimes.
@TeomaHK Nein, ich bin #iOS User und habe ein Pixel 8a als Zweitgerät. (Bevor dies zu meinem Hauptgerät werden kann, muss ich noch auf mein Diensthandy warten. Ich möchte künftig eine klare Trennung zwischen privaten und dienstlichen Apps.)
#LineageOS, #CalyxOS und #eOS könnten evtl. brauchbare Alternativen sein. Kennst du kuketz-blog.de und kuketz-forum.de? Vielleicht findest du da weitere Anregungen.
If you have a spare phone, you might want to try out a #MicroG-based OS like #CalyxOS. I can't guarantee that it'd work better, but it's a nice middle ground between no google services and "sandboxed" google services, because it's a FOSS re-implementation of the google services.
The other option would maybe be putting sandboxed google play and just the troublesome apps in a work profile, so you can turn that all off and on as you need it and contain the badness?
@thomholwerda I don't know the rest of your requirements, but I've been enjoying #CalyxOS for the last couple years. I installed it without microG.
It's frustrating how many important services and channels of communication rely on questionable tech. For example, my neighbourhood uses Meta's WhatsApp to the point where if I hadn't accessed the chat I wouldn't have had an ETA on reactivation of our hot water that was out for several days. For this purpose, I've made a slight compromise (using a different phone number). But I'd like to #AskFedi what you think my best use is on my #CalyxOS device: keeping WhatsApp in the work profile or using #WhatsApp4Web from #FDroid?
My #Pixel7Pro basically on its way, just waiting for ebay to give me a tracking link/info, but I'm now debating weither I should keep the stock, google-infested rom and have no issues, or have a big chance of facing issues with CalyxOS or GrapheneOS?
The main reason being, I'm not sure if some of my apps like banking and carrier apps, along with another app or two will work, plus the fact that I'm paying for YouTube Premium, and so on.
I don't want to have to deal with incompatibility issues, but I'm also extremely uncomfortable (paranoid maybe?) with using the stock rom, so I don't know how it'll go...
#privacy #phoneprivacy #google #googlepixel #googlephone #android #android16 #android15 #Android14 #calyxos #calyxinstitute #grapheneos #graphene_os
@schmidtisblog Ja, mit #GrapheneOS oder #CalyxOS sind die wirklich brauchbar. 🤣
Four new Motorola devices added to CalyxOS support list
