207
GrapheneOS
this post was submitted on 03 Oct 2024
207 points (98.1% liked)
DeGoogle Yourself
8753 readers
1 users here now
A community for those that would like to get away from Google.
Here you may post anything related to DeGoogling, why we should do it or good software alternatives!
Rules
-
Be respectful even in disagreement
-
No advertising unless it is very relevent and justified. Do not do this excessively.
-
No low value posts / memes. We or you need to learn, or discuss something.
Related communities
!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml
founded 4 years ago
MODERATORS
Installing GrapheneOS removes all the Google crap.
What is the advantage over Calyx/Lineage/iode OS on compatible devices? I just don't want Google to have any of my money at all. Buying a privacy solution from them recoups their loss.
It's my understanding that Graphene has security as its main goal, not privacy, though it's also quite private.
I don't know about Calyx or Iode but Lineage doesn't allow for a locked bootloader. This is a massive security hole and without security, sooner or later, your privacy will be violated.
Currently, GrapheneOS on a newer Pixel are the only phones that Celebrite can't breach. Celebrite machines are cheap enough that the border guards and your local cops probably have one. In my country, it's the law that a cop is allowed to examine a phone during a traffic stop.
load more comments
(3 replies)
Mainly the locked bootloader that GrapheneOS offers. It's more secure, and GrapheneOS emphasizes security over all else, but privacy features are part of that security.
load more comments
(2 replies)
I like calyx, might try graphene some day. But I absolutely won't run Google's play services ala graphene. It's sandboxed, supposedly, but why run it at all?
Calyx uses microG, a much smaller, fully open source emulator of Google's services.
load more comments
(9 replies)
load more comments
(4 replies)
I know this isn't the topic here, but I really wish these researchers would unroll what all Apple harvests from Apple devices. It's quite a lot as well. Could help pop that "we're so private" myth.
You can’t say no to Google’s surveillance
Yes you can: https://grapheneos.org/
I was just wondering earlier today if Google kept the bootloader open to allow custom OS installation only because they had other hardware on the phone that would send them their information anyways, possibly through covert side channels.
Like they could add listeners for cell signals that pick up data encoded in the lower bits of timestamps attached to packets, which would be very difficult to detect (like I'm having trouble thinking of a way to determine if that's happening even if you knew to look for it).
Or maybe there's a sleeper code that can be sent to "wake up" the phone's secret circuitry and send bulk data when Google decides they want something specific (since encoding in timestamps would be pretty low bandwidth), which would make detection by traffic analysis more difficult, since most of the time it isn't sending anything at all.
This is just speculation, but I've picked up on a pattern of speculating that something is technically possible, assuming there's no way they'd actually be doing that, and later finding out that it was actually underestimating what they were doing.
I don't mean to discredit your opinion, but it is pure speculation and falls in the category of conspiracy theories. There are plenty of compelling arguments, why this is likely completely wrong:
- Google Pixels have less than 1% of the global smartphone market share, in fact, they are currently only sold in ~~12~~ (the Pixel 9 is sold in 32 countries, my bad, I had an outdated number in mind) countries around the world. Do you really think that Google would spend all the money in research, custom manufacturing, software development and maintenance to extract this tiny bit of data from a relatively small number of users? I'd say more than 90% of Pixel owners use the Stock OS anyways, so it really doesn't matter. And Google has access to all the user data on around 70% of all the smartphones in the world through their rootkits (Google Play services and framework, which are installed as system apps and granted special privileges), which lets them collect far more data than they ever could from Pixel users.
- Keeping this a secret would also immensely difficult and require even more resources, making this even less profitable. Employees leave the company all the time, after which they might just leak the story to the press, or the company could get hacked and internal records published on the internet. Since this would also require hardware modifications, it's also likely that it would get discovered when taking apart and analyzing the device. PCB schematics also get leaked all the time, including popular devices like several generations of iPhones and MacBooks.
- Lastly, the image damage would be insane, if this ever got leaked to the public. No one would ever buy any Google devices, if it was proven that they actually contain hardware backdoors that are used to exfiltrate data.
load more comments
(9 replies)
load more comments
(1 replies)
load more comments
(6 replies)
Who truly owns the device is a question that has been answered ever since Android came into being.
Ask yourself: do you have root access to YOUR phone? No you don't: Google does.
It's the so-called "Android security model", which posits that the users are too dumb to take care of themselves, so Google unilaterally decides to administer their phone on their behalf without asking permission.
Which of course has nothing to do with saving the users from their own supposed stupidity and everything to do with controlling other people's private property to exfiltrate and monetize their data.
How this is even legal has been beyond me for 15 years.
Weirdly, Pixels are actually the best Android phones for installing custom ROMs, at least out of the major manufacturers. So for me, there isn't another choice, because I can finance a Pixel, and I can't finance a Fairphone or something.
GrapheneOS is really the furthest away from Google you can get on an Android phone and it's mainly developed for Pixel.
Please read the many write-ups by developers of well regarded privacy and security ROMs, such as grapheneOS and divestOS.
Who detail in great length why root access is a bad idea, and why many apps that require root access, are just poorly developed security nightmares.
That said, I agree that it should be an option, or at least a standardized means of enabling it. As well as all bootloaders should be unlockable. But phones are more personal devices than the PC ever was, and there are good reasons NOT to push for the proliferation of standardized root access.
These writeups never managed to to convince me me that I should not be able to modify any file on my device. If the system is not able to grant this access to me, and me only, while doing it securely, than it's bad operating system, designed without my interests first on mind. I am absolutely sure that granting so-called "root access" can be done securely, as decades of almost-every-other-OS have shown.
Yes. It is the principle, everyone should be informed of the security risks, but not stripped of the root privileges they keep for themselves.
I have GrapheneOS and I know having root is not ideal and I was wondering about https://shizuku.rikka.app/ It looks like a more elegant way to have for some apps higher privileges while preserving security but I'm not sure about it so I'm thinking out loud
I will admit that I also use Shizuku, but I only enable it for short bursts when I need access for a very select number of precise use cases. Immediately afterwards, I reboot.
I also assume that if I spent any amount of time digging into it, I would realize it's a bad idea, but nothing's perfect.
And don't assume that all apps allowing Shizuku access were developed securely, or that there all developers have good intentions. Really I only use it for Swift, or if I'm really behind on my updates, I'll briefly allow Droidify access for hands off updating.
load more comments
(1 replies)
do you have root access to YOUR phone?
Yes. On a Pixel 9 Pro Fold.
Ironically, Google Pixels are among the few (US available) brands that still let you fully unlock the BL
Yes. On a Pixel 9 Pro Fold.
Not if you run the stock OS you don't.
My comment was generic. The vast majority of Android users don't unlock their bootloader and install a custom ROM. The people who do that are fringe users.
My point was that when the normal state of affairs is Google controlling YOUR property that YOU paid with YOUR hard-earned, and you have to be technically competent and willing to risk bricking your device to regain control, that's full-blown dystopia right there.
out of interest, what use cases do you have in mind that require root access?
I used to use a root based solution to block ads system wide via hosts but now I just use ublock origin in Firefox.
load more comments
(10 replies)
And this is different from Apple. Right? Right?
The only real difference is that Google pretends to be open and Apple pretends to be privacy-focused. It's the illusion of choice. They're both selling their users' data to the same people.
load more comments
(1 replies)
Yep, what radicalized me against Google was all the way back when they had bought Android and rolled out the Play Store for the first time.
I was on my first-ever phone, and yes, it did have rather limited internal storage, but then the Play Store got installed, taking up all the remaining space. I had literally around 500KB of free storage left afterwards, making it impossible to install new apps.
Couldn't uninstall the Play Store, couldn't move it to the SD-card and it didn't even fucking do anything that the Android Market app didn't do. It just took up 40MB more space for no good reason.
What's surprising about their stock ROM having tracking and phoning home? Use Grapheneos.
load more comments
(2 replies)
This doesn't seem surprising at all. Isn't that what Google Play Services is for? If you don't want it, custom ROMs are easily installed.
GrapheneOS + buy your phone from a store in-case you're allergic to PETN
It's so ironic that Pixels are the go to devices for privacy roms these days.
All this shit is probably happening at the hardware level too, with 100 different backdoors you can't remove with your megamind plan of installing a custom rom.
The silicon probably has the ability to live stream all sensor data directly to the NSA using the fanciest ML compression technology lmao.
It’s so ironic that Pixels are the go to devices for privacy roms these days.
It's so ironic it's a show-stopper for me. I'm not paying fucking Google to escape the Google dystopia. Nosiree! That's just too rich for me.
This is why I own a Fairphone running CalyxOS. Yes, I know GrapheneOS is supposedly more secure - I say supposedly because I think 95% of users don't have a threat model that justifies the extra security really. But I don't care: my number one priority is not giving Google a single cent. If it means running a less secure OS, I'm fine with that.
There's no way on God's green Earth I'm buying a Pixel phone to run a deGoogled OS. That's such an insane proposition I don't even know how anybody can twist their brain into believing this is a rational thing to do.
That's why I buy my phones used or refurbished. It's also cheaper and more environmentally friendly.
load more comments
(5 replies)
Citation needed. I get that it's healthy not to trust anyone, but with the amount of security research that goes into these devices if something like that was happening then we would know about it.
load more comments
(4 replies)
load more comments
(1 replies)
So what phones do you all have?
Pixel 7 Pro with GrapheneOS
pixel 6a with graphene os
Pixel 8a with graphene
iPhone 16 Pro Max, but Graphene does look dope.
load more comments
(7 replies)
I'd say newer Pixels have even more privacy issues than the older ones because of cloud based AI features (ugh when will the bubble finally pop?) and stuff. However the stock OS is bad for privacy in both cases so a custom ROM is a must and afaik installing it on a Pixel is not too hard. Also new Pixels seem to get custom ROMs very quickly so you don't have to wait for months or even years for someone to make one.
The Pixel 9 line had GrapheneOS avaliable a couple of days after launch. That's how fast. You order the phone, and by the time you got it, GrapheneOS was ready to replace Stock Android.
view more: next ›