this post was submitted on 04 May 2026
198 points (99.5% liked)
Hardware
7200 readers
115 users here now
All things related to technology hardware, with a focus on computing hardware.
Some other hardware communities across Lemmy:
- Augmented Reality
- Gaming Laptops
- Laptops
- Linux Hardware
- Linux Phones
- Monitors
- Raspberry Pi
- Retro Computing
- Virtual Reality
Rules (Click to Expand):
-
Follow the Lemmy.world Rules - https://mastodon.world/about
-
Be kind. No bullying, harassment, racism, sexism etc. against other users.
-
No Spam, illegal content, or NSFW content.
-
Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.
-
Please try and post original sources when possible (as opposed to summaries).
-
If posting an archived version of the article, please include a URL link to the original article in the body of the post.
Icon by "icon lauk" under CC BY 3.0
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's ironic that arguably the best way to de-Google a phone is to get a Pixel and use GrapheneOS.
My buddy did that. Didn't read the fine print. So he either pays off the $700 phone cash or let's Google invade his life long enough for it to be paid off by monthly credits, and he can unlock the bootloader.
You're still using a platform upon which Google has an enormous influence, including making life much more difficult for projects like GrapheneOS. And I think it's only a matter of timer before they'll take more aggressive measures.
Btw, I am not saying one should or shouldn't use a Pixel with GrapheneOS.
Until the Motorola deal sees fruition, Pixels are the only way to use GrapheneOS. I don't think that using GrapheneOS makes the project more difficult.