My life with two phones was short-lived. It was not practical. I decided to go all in with #GrapheneOS and #Pixel 6a. I'll be giving the Samsung Galaxy S22 to someone else in the family and using the Pixel 6a for the next half of the year. If it's okay, I'll get a Pixel 10 and install GrapheneOS on it. If not, I'll humbly go back to Samsung and get the S25.

BTW it is interesting to find that I can live with a used phone for €120.

in reply to Ondřej Pokorný

@ondra 1) because S22 cannot run GrapheneOS, so I had to get a Pixel to try it out and of course, I couldn't just ditch the previous phone when I had no idea if I could live with GOS as an OS for my only phone.
2) I'm fine with it short-term, but it only has 128 GB of storage which I'm sure will run out of in a few months. Other things such as wireless charging or higher frame rates would be welcome, too, but not too crucial.

I'm not happy about giving money to Google, but I'd rather give them my money for the device (Pixel+GOS) than giving them my data (another OEM partner's phone+Google Android).

in reply to Jiří Eischmann

That's why I'd like to skip AOSP altogether. Especially when Graphene already talks about a desktop version. Mobile apps on desktop isn't the future of convergence I want.

I'm deliberately avoiding mobile-app-only services and am not watching movies or gaming on a phone. And I need just a little space for some offline data. So a Pixel-level camera on any Linux phone would probably be all I need.
Wireless charging wastes about half of energy, BTW. Also overheats my 6 Pro. :)

in reply to Ondřej Pokorný

@ondra I've got OnePlus 6 with PostmarketOS and while I like the OS, it's just too limiting for me. A secure Android device that is not a Google data miner is fine by me.
I know that wireless charging wastes energy, but the phone's annual consumption is roughly 0.03% of our top-roof solar system. I can live with it. Also my wireless charger has a cooling system, so no overheating problem.
in reply to Ilkka Tengvall

@ikkeT the corp tools generally work. If a customer invites you to their Teams or whatever, you install Teams and can enter the call. The device enrollment into Google accounts at Red Hat doesn't work. So if someone invites you to an internal Meet call, it's a problem. I'm pretty sure there is some way to open a meet link in the browser and it will work just fine, but Meet resists quite a lot.
If the phone is really important for your work, just go for something that is officially supported. I really need to just check Slack, email and calendar on my phone and that's it. I can live without the rest.
in reply to Jimmy Sjölund

@jimmysjolund a long or short story? :)
You can find the long one on my blog. It's in Czech, but a translator should translate it just fine: blog.eischmann.cz/2025/03/07/g…

The short story is that the only things that don't work for me are Google Pay and our enterprise device enrollment in the work profile.
Flashing the phone with GOS is fairly straightforward. Matter of 15 minutes if you know the routine.


GrapheneOS: Android pro lehce paranoidní uživatele

Pokud chcete mobilní telefon, který je bezpečný, opravdu respektuje vaše soukromí, zároveň nechcete přijít o populární aplikace, bez kterých už se dnes těžko obejdete, může vám současný trh přijít jako výběr mezi kompromisy. Podíval jsem se tedy na systém, který o sobě tvrdí, že jimi netrpí.

#Android #bezpečnost #Google #GrapheneOS #mobil #Pixel #soukromí

blog.eischmann.cz/2025/03/07/g…
(reakce na tento příspěvek se může zobrazit jako komentář pod článkem)