Google’s latest flagship smartphone raises concerns about user privacy and security. It frequently transmits private user data to the tech giant before any app is installed. Moreover, the Cybernews research team has discovered that it potentially has remote management capabilities without user awareness or approval.
Cybernews researchers analyzed the new Pixel 9 Pro XL smartphone’s web traffic, focusing on what a new smartphone sends to Google.
“Every 15 minutes, Google Pixel 9 Pro XL sends a data packet to Google. The device shares location, email address, phone number, network status, and other telemetry. Even more concerning, the phone periodically attempts to download and run new code, potentially opening up security risks,” said Aras Nazarovas, a security researcher at Cybernews…
… “The amount of data transmitted and the potential for remote management casts doubt on who truly owns the device. Users may have paid for it, but the deep integration of surveillance systems in the ecosystem may leave users vulnerable to privacy violations,” Nazarovas said…
You can’t say no to Google’s surveillance
Yes you can: https://grapheneos.org/
So what phones do you all have?
Pixel 7 pro with GrapheneOS.
Pencil with graphite
stone and chisel
Oooga booga
the one guy on lemmy with calyxos
Fairphone 5
not a phone just a literal block of graphene
Pixel 7 Pro with GrapheneOS
pixel 6a with graphene os
Pixel 8a with graphene
pixel 7a with crdroid
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.
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.
Can’t speak to what others are saying about Graphene but Calyx is amazing if you prefer a FOSS-centric option but still want GMS/GSF compatibility. Bootloader relocking is a requirement for their devices.
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.
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.
Other OSs let you lock the bootloader too. I know that iodéOS and CalyxOS do, for example.
As well as all the other security features offered by Pixels, like the Titan M2 secure element, which securely stores encryption keys and makes brute-force attacks basically impossible.
It’s my understanding that Graphene has security as its main goal, not privacy, though it’s also quite private.
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.
@RubberElectrons @multi_regime_enjoyer its not actually fully open source, it uses a lot of closed-source libraries, and its not as battle-tested as google’s official one so there really isn’t a reason to use it
Just about all of your identifying data is stripped out by the framework before interacting with Google at all: https://github.com/microg/GmsCore/wiki/Google-Network-Connections
That alone makes it an important tool. I’m not too worried about memory exploits as I don’t really install apps, but it’s an important feature in graphene’s toolkit.
For most people who want an Android alternative that’s open source but don’t have time to fiddle with it, calyxOS seems like a good solution. It just works out of the box.
GrapheneOS
Do they have passkeys yet
Edit: passkeys support. Last year when I checked they didn’t support pass keys yet.
Yes, @oranki@lemmy.world wrote a great article about that: https://oranki.net/posts/2024-07-10-passkeys-on-grapheneos/
Thank you! Idk why I was down voted, I appreciate it. I did a bunch of research on grapheneos last year around this time and it wasn’t supported yet.
Yeah there’s also a relevant post on the GrapheneOS forum where this was discussed in detail, but I can’t find it anymore
No worries, ya I looked into it about a year ago when I was seeing if I could make the switch, glad there is support now.
What does that even mean? It’s not the function of an OS to have passkeys.
Grapheneos didn’t support pass keys last year when I checked, so you couldn’t use them at all. There was some APIs broken/missing between the OS to browser comms so you couldn’t use 3rd party apps for pass keys, like proton or bit warden. I have been actively experimenting and adopting passkeys and didn’t want to revert. It sounds like there is support now though, so I will give it a try soon.
I’m not sure because I’m on a OnePlus device running a lineage OS.
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.
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.
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.
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.
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.
what use cases do you have in mind that require root access?
Ownership.
Nah. The only thing root does is massively decrease security. To actually own your phone, you need to install a proper, FOSS, private and secure OS in the first place. Pixels are great, because they support GrapheneOS.
I own my Pixel 8 Pro. No root. GrapheneOS. So, your logic is therefore flawed.
okay cool but what are you specifically using system or systemless root for now?
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.
You still have to trust their black box Titan security chip that’s only in Pixels, that they pinky promised to open source but never did.
You will have to inevitably trust someone somewhere for every phone, unfortunately. At least the Titan has been tested in the real world, and it’s not like it’s phoning home on it’s own or anything.
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
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.