Thread 105926291

This OS is just so great. Can't wait for the end of 2026 when they will have their own GrapheneOS phone.

I don't understand why /g/ is full of "Anti-GrapheneOS" just because this is only compatible with Google phones. It's not GrapheneOS's fault if all other smartphones are trash.

Source of the screen : https://eylenburg.github.io/android_comparison.htm

Because it's creator is a massive faggot and blowed me off 2 nights ago

>>105926291 (OP)
>I don't understand why /g/ is full of "Anti-GrapheneOS" j
Contrarianisms on g and baiting

>>105926291 (OP)
It's wrong to be French.

>>105926291 (OP)
Just make something like whonix but to run in any phone, otherwise its DOA

>>105926291 (OP)
Because the concept is fundamentally flawed. Even if GrapheneOS is secure, the FUCKING GOOGLE HARDWARE is the true problem!

>>105926742
1) It's the same for every phone.
2) GrapheneOS will have their own phone at the end of 2026.
3) The chip will be Open Source on the Pixel 10 (check OpenTitan)

>>105926291 (OP)
what retard made that table? How are google play services a plus? It should be highlighted in red.
These kinds of tables would only trick genuine monkeys.

>>105926814
The compatibility is a plus for people that wants it. Obviously it's not installed by default.

>>105926291 (OP)
>they will have their own GrapheneOS phone.
Wow, that's really cool, I'm happy for them! Maybe I'll even buy it.

>>105926742
Unless you're running a PC from the 90s that you got from a pawn shop 15 years ago, paid cash while wearing a disguise, you're going to run into the same problem on any and every hardware.

>>105926420
Sorry to hear he didn't want to top you.

>>105926742
>negative technical understanding
>germ
Every time. Just stop Hans, you can't even build the best cars anymore, you knuckle dragging cavemen never figured out any technology beyond the 90s.

>>105926814
>How are google play services a plus? It should be highlighted in red.
Being able to easily install sandboxed GPS is the best way possible since it's opt-in and you still have the option of availability

>>105926291 (OP)
pixel phones are overpriced even on the second hand market (sellers know that you can install a third party os on it and will jack up prices accordingly). Just get a cheap new phone instead of keeping old hardware that relies on bootleg software.

Graphene has so many fucking shills and fanboys. Even the linked page is a bunch of bullshit "um aksshually everything else is bloated", how nigga. LineageOS comes with a music app and a dialer. Graphene ships with "secure messenger" CIA plant bullshit. Its the defacto brainlet ROM.

>>105926291 (OP)
Did Louis Rossman have legitimate reason to scorn GrapheneOS? I trust that guy and if he says your OS is trash not worth installing, I can believe it.

>>105927866
> if he says your OS is trash not worth installing

Louis Rossman never said that, he uninstalled it after a ideological beef with the main dev, nothing to do with the technology.

>>105927866
>Did Louis Rossman have legitimate reason to scorn GrapheneOS?
No he watched a video from techlore and commented positively on it, then micay complained in the DMs and louis called him a schizo and claims he could just target him specifically for some reason. This is at best influencer beef, at worst two schizos crying.

>>105927866
No. He is a pajeet that got mad because the lead dev called him out for being a little bitch.
Graphene OS is great.

>>105927830
>Graphene ships with "secure messenger" CIA plant bullshit.
wrong

>>105927830
Not to mention all of it is wrong
>network based location without GNSS
You can download an open source service that lets you do this from fdroid. See BeaconDB. Having it built in is bloat and contradicts point 2.
>Duress pin
Meme feature, exists as an app on fdroid already, no need for it to be a built in feature. Contradicts point 2.
>Android auto compatible
What does this even mean? Android auto works just fine for me on Lineage.
>PSDS/XTRA
This is a download of GPS sat position data. Irrelevant to security.
>DNS is changeable in settings on default android for years
>NTP, you can change your NTP servers on default android for years
>option to mark apps as installed from google play store
This can be done with a free app already, or an ADB command.
>exif metadata stripping for photos
This exists as an app
>metadata stripping for screenshots
Android screenshots carry no metadata, unless we count the filename which contains the date, just change the filename.

The rest of the privacy section is a bunch of pseudointellectual bullshit with no real privacy impact. "Guys google cannot know what calls I'm making because I removed the esim provider. Wait what do you mean my phone provider knows and can be audited by the FBI, noooo im so secureeeeee"
>android verified boot (AVB)
Irrelevant only protects against evil maid attacks. Unless you're a politician or billionaire, but if you are, you wouldnt be using some sperg's toy OS where he'd inject malware into on a whim to "own the billionaires".
>Hardware-based security verification
Same as AVB but rebranded so that we can add another exclusive feature to the list
>system app downgrade protection
They are in a RO partition, you cannot downgrade then without literally replacing the files.
>Hardened
Irrelevant, android apps all run in a sandbox with highly limited native interactions. None of these mean anything unless you're actively running sketchy native binaries through ADB shell.

>>105927866
I am a convinced GrapheneOS hater, but my hate is based on factual criticism of GrapheneOS. Rossman is a cool guy, but his video where he explains why he stopped using Graphene is absolut dogshit. There are tons of technical, fact based problems to criticize Graphene, but Rossman's video is is nothing more than clickbait gossip.

This video is so dissapointing, because when people are trying to find actual, technical criticism of Graphene on Youtube, they will get this brainrot gossip video instead.

I don't care about the people behind Graphene. But I do care about technical facts and the Graphene community is systematically surpressing the ACTUAL uncomfortable truth about GrapheneOS. The tech is the problem, not some bullshit gossip about their autistic devs.

>>105928160
What problem with GrapheneOS ? Your post is empty just as the guy above you that just says "muh actchually an app on F-Droid does this" while the apps on F-Droid are not even up-to-date

>>105928183
The hardware is the main problem. And the second problem is, nobody has reviewed the Graphene code.

>>105928223
>The hardware is the main problem.
As with any OS. Go live in the woods.
>And the second problem is, nobody has reviewed the Graphene code.
That's what it being FOSS is for.

>>105928146
>can disable USB-C data pins
Irrelevant as USB data has to be approved while the device is unlocked, if its not unlocked it cannot be forced to communicate
>can disable charging
For what purpose?
Both of these can simply be bypassed by booting the phone into the hardware bootloader mode (not the secondary bootloader which graphene ships with). The one thats permanently burned into the SoC. You can do whatever you want there regardless of whats going on. Dump the NAND and bruteforce the encryption on a supercomputer somewhere. Apparently modern machine learning techniques exist to determine whether the data on the device is of interest even if encrypted. They cant decrypt it but it can state that there is something suspicious about it.
>auto reboot timer for locked devices
Bootloops are actually a feature
>2factor fingerprint unlock, finger + pin afterwards.
Defeats the purpose of the biometrics. What if my finger gets damaged? The whole point pin is used as a fallback is because of this very reason.
>full patches on supported devices
What does this mean? As opposed to half patches?

This whole thing is like product boxes where they advertise a feature no one else has because its either useless or superficial, or they made it up and therefore no one else has it. How come your MSI motherboard doesnt have ASUS EzFlash™ and Gigabyte CrashFreeBios™

So long as you're not using a hyper pajeeted custom rom like Pixel experience that ships with all the google crApps or a stock rom that phones home to every intelligence agency on the planet at the same time you're good. Graphene is the qubes, tails, "i only browse through TOR" project for people who like to larp as Snowden, while still using all the social media crap to brag about it anyways. Grow up

>>105928223
The hardware is always proprietary, the Titan chip will be open on the Pixel 10, check out OpenTitan.

And they will soon make their own phone for 2026, no more Google things.

>>105928183
>apps on fdroid not updated
Duress last updated 12 months ago, works fine on android 16, what updates does it need exactly? 20 translation imports per month?
AltLocationServices last updated 3 months ago and works fine on android 16.
Quad9 last updated 3 months ago and works on 16
ScrambledExif last updated 3 months ago and works on 16
Imagepipe (automatic image changes like filenames, exif, and even edits like baked in timestamps, rotations etc) last updated 6 months ago, works on 16

What exactly isnt up to date? What exactly do these apps need? "Security", how are they currently insecure? "No updates" is such a brainlet take, think about what the updates actually contain rather than consoomslopping 200 page changelogs of code style changes and translation imports.

>>105928301
>>105928146
So should I just use stock ROM or what?

just created another info image.

>>105928416
No, any custom ROM not riddled with google slop will do. Its more a matter of shutting up Graphene shills. If you like it, use it, its better than stock, but its nothing that special either. Its advantages over other custom roms are superficial at best and usability breaking at worst.

GrapheneOS is a fine OS but their stance on stopping support for older pixels is nonsense and they go too far on security in some cases. Like do I care if google is my time server are there any security or privacy implications? Not really. I'd call that privacy theatre. Still I'd probably use it on a new pixel but on older devices use lineage

>>105926818
I want you to go on a little sidequest here buddy

Your computer or your phone, right? Figure out what processor it has.
Okay, good, now try to find out if it has open source or proprietary drives.

If its open source, you're either extremely lucky or you deliberately searched it out and paid a premium for such.

>>105926291 (OP)
Okay guys, when the pixel 10 releases I'm probably buying it, which android distro should I install on it that's secure by default and has support for the mcdonald's app or at least android auto?
Have in mind neither of those two things work in grapheneos, so that's out of the question.

>>105927866
Take a quick look at the main developer of grapheneos in the farms and you'd properly see why he had that fewd with the os.
TLDR of that thread: The dude is assmad bonkers and basically thinks everyone is ought to get him and destroy him, so if anyone ever makes a mistake portraying his distro, he'd start an online campaign to harass, defame, libel and try to character assassinate that person, which has led to basically getting thrown out of every online community he's been on and his project being pulled out of the secure android distros help group to share ideas and code.
He basically has some kind of hatred against calyxos so he'd basically harass everyone online that says that name in the same text as graphene, and in the git repos he basically argumented all day with the calyx devs to the point they had to ban his account from the git repositories.

>>105927961
Don't forget the thousands of lines of text he send rossman and how he spent weeks harassing him for making a simple comment, on a video speaking exactly about him harassing and defaming another person that made a mistake in an installation tutorial.

>>105926291 (OP)
>only works with Google devices
yeah no thanks, nice try Graphana shill

>>105928564
>partnered with Elon Musk
DOA

>>105928821
>Don't forget the thousands of lines of text he send rossman
Really? Louis only showed a few texts
>how he spent weeks harassing him
I don't remember that one either
>him harassing and defaming another person
You mean Henry who constantly claims he's a menace for not wanting to be swatted and harrassed online?
>None of this has any impact on a technological level
You're correct about th- Wait, you forgot that part? You can remember details about eceleb drama but forget the only important part? Weird...

>>105926291 (OP)
>only google phones are supported
into the trash it goes

>>105928708
>mcdonald's app or at least android auto?
>Have in mind neither of those two things work in grapheneos,
but they both work for me

>>105928792
>The dude is assmad bonkers and basically thinks everyone is ought to get him and destroy him, so if anyone ever makes a mistake portraying his distro, he'd start an online campaign to harass, defame, libel and try to character assassinate that person

This was a funny moment, when he told Mike Kuketz to help him lol

>>105926291 (OP)
The biggest problem with both Graphene and Calyx is that they're anal about only supporting "current" phones. Well, what if I want a more secure OS for an older phone that no longer gets vendor updates? That's half the goddamn reason I'd be interested in using a custom ROM in the first place.

>>105929179
This is because they are controlled opposition.

>>105929128
>Mike Kuketz
left-wing extremist btw

>>105929179
>what if I want a more secure OS for an older phone that no longer gets vendor updates?
You're free to create Graphene OS LTS if you want to do Google's work for free. Or just live with your security flaws.

>>105929214
>>105929179
So is there any real alternative besides never using a mobile phone ever again?

>>105929793
Don't let the psyops on /g/ get to you, use Graphene and proper opsec and you'll be fine no matter what your threat model is.

>>105929844
Graphene is the psyop.

>news articles get written about how Spain's police forces weren't able to access Graphene phones a few days ago
>sudden demoralization psyop campaign is underway on /g/

>>105929909
Debunk the facts about Graphene, glowie. Who controls the hardware? Who has audited Graphenes code? Tell me.

>>105929909
Please stop noticing

>>105929909
yeah and who owns the media outlets? certainly not anyone with political motives HEHEHEHE

>>105926291 (OP)
As a honeypot, since pixel phones have hardware backdoors.

>>105926742
>source: ai
lmfaooooo

>>105926291 (OP)
>I don't understand why /g/ is full of "Anti-GrapheneOS
Because YOU SHILL THIS SAME THREAD EVERY FUCKING DAY FUCK OFF

>>105930026
debunk it. i am waiting.

GrapheneOS cannot be fully trusted because it runs on Google's proprietary hardware stack, which remains a critical vulnerability. While GrapheneOS markets itself as a privacy-focused alternative, its security is undermined by the fact that it operates on devices like Google's Pixel smartphones—hardware designed and controlled entirely by Google. Unlike other OEMs, Google does not merely integrate off-the-shelf components; it designs its own processors (e.g., Tensor chips) and develops the closed-source firmware and software that power them. Other manufacturers receive binary blobs from chipmakers, which they cannot modify, but Google retains unilateral authority to embed hidden functionalities or surveillance mechanisms directly into the hardware-software ecosystem.

This means Google could inject malicious code into the processor’s firmware—code that operates independently of Android (and thus independently of GrapheneOS itself). Such malware would run at the hardware level, bypassing the operating system entirely and evading detection. If Google exploits this capability in its proprietary GApps, the same logic applies to the foundational software controlling its processors. Since GrapheneOS cannot audit or modify these closed-source components, users are left exposed to potential backdoors.

If you trust GrapheneOS on Pixel devices, you must also trust Google’s closed-source hardware stack—the very same infrastructure that could enable pervasive surveillance. In that case, there is no meaningful distinction between GrapheneOS and stock Android; both rely on Google’s opaque technology. Conversely, if you reject GApps and Google’s data harvesting, you cannot reconcile that distrust with reliance on Google’s hardware. To truly deGoogle, you must abandon devices where the manufacturer controls the silicon itself.

>>105930121
AI post

>>105930093
i dont care what an ai user says

>>105930121
Google doesn't need to do anything, the SoC already does this by default as mandated.

>>105930134
give google your money if this makes you happy. go back watching peepiedie.

>>105926291 (OP)
>perfect
>not Google Play compatible
>no option to enable screenshots in all apps
>cloudflare as fallback DNS
>can't pass full integrity check
>can't mark arbitrary apps as installed from the Play store
>doesn't support Asus, Fairphone, Motorola, Oneplus, Samsung, Sony, or Xiaomi devices, forcing you to use google hardware for support
Your image contradicts your subject

>>105930240
>SAAR BUY GOOGLE PIXEL™ VERY SECURE PHONE DO THE NEEDFUL INSTALL GRAPHENE NO HARDWARE BACKDOOR TRUST MEE SAAAAR PEWPIEDIE SAID IS GOOD

>>105930308
>SAAAR PLEASE STOP USING GRAPHMEMEOS MY MASTERS CANT CRACK IT THEY FORCE ME TO SHILL AGAINST IT NONSTOP FOR DAYS PLEASE SAAAR

>>105930331
SAAR PLEASE CONTINUE TO CONSUME MAINSTREAM MEDIA LIKE A GOOD CITIZEN AND DON'T QUESTION ANYTHING SAAR BUY GOOGLE PIXEL VERY SECURE PHONE NO BACKDOOR POLICE CAN'T CRACK IT MEDIA TOLD ME SAAR

>>105926742
it's about time that backdoored hardware is finally dealt with permanently

>>105930240
>>105930308
>>105930331
>>105930381
Okay i get it, if graphene isn't good, what is?

>>105930614
And that's how you spot he's just an idiot. If he had legitimate criticism he would have provided solutions or alternatives.

>>105930646
I was thinking of getting a used pixel 6 for it

>>105930679
Check on Graphene's website (or on sites that show how long google will support that phone). It might just be a few years so saving for a newer model might be smarter. Also check since some phones can be locked for loading new ROMs by carriers.

>>105930679
Pixel 8 and newer models have 7 years of support and memory tagging, so I would wait until you can get one for a good price.

>>105930614
here you agree that graphene isn't good
>>105930700
>>105930679
and then you fags say you still want a pixel? and not a singel one of you mentioned an alternative. I'm fucking confused.

>>105930646
Yes, I admit I am an idiot and I HAVE NO CLUE WHAT THE SOLUTION IS.

But I also know what is NOT the solution: Graphene OS.

Just because I have no solution, doesn't mean that I will have to accept a fake solution.

>>105930790
>and then you fags say you still want a pixel?
Yes because my thread model requires the best option available to me. I'm anonymity-maxxing, so I won't sit in some store with an external wifi attenna stick out of my laptop to use another store's free wifi.
>and not a singel one of you mentioned an alternative.
That's because there aren't any good alternatives to GOS if you threat model is that high but you still require mobile connectivity. It's not like you can use GOS and then all of your problems are solved but until we get better linux phones this is our best option.

>>105930837
>Yes, I admit I am an idiot and I HAVE NO CLUE WHAT THE SOLUTION IS.
To stop caring about potential hardware backdoors instead of actual ones. Is your bios completely FOSS? Did you buy a CPU without IME, PSP or Trustzone (or whatever that bs from ARM is called)? Did you actually read through all of the source code you use? Did you ensure multiple times that the compiler you use isn't malicious. Did you protect yourself from side channel attacks? Are all of your critical devices airgapped? No? Then be consistent in your approach and realize that you need to extend your trust somewhere.
>But I also know what is NOT the solution: Graphene OS.
Because big internet company likes data? ALL COMPANIES LIKE DATA. If they can easily get your data you best believe they will take it and sell it to whoever wants it. The only option you can feasibly have is that live in the woods and then you can't even do anything against being framed.
If you want to have a functional life become a target that's so hard to compromise you won't be successfully attacked. If not, enjoy your wood cabin. Don't put a standard lock on it though, they are all based of the same few designs and easily picked.

>>105930121
I wonder what Stallman would say about this text. Do you think he would agree?

>>105930945
Bro, you will not convince me to buy a Google Pixel.

>>105931149
You don't have to, all I want for you is to stop your smear campaign when all you can do is demoralize.

>>105931169
I will not stop. The Graphene cult is a bunch of liars who are trying to sell a fake solution. They portray Graphene/pixel phones as the best and most private phone ever. They are scam artists and they are doing more harm than good, because they are lulling everyone into false security. Their work is not in favor of educating people about privacy.

This is why the Graphene cult must be stopped. All they do is selling copium. And this is why I hate them.

>>105931239
>The Graphene cult is a bunch of liars who are trying to sell a fake solution
Not really. I've shown you above that there's no reason to particularly hate on GOS.
>They portray Graphene/pixel phones as the best and most private phone ever.
It currently is the best option. To disagree with this you need to provide a better option which you claim you couldn't and I doubt you suddenly can.
>And this is why I hate them.
That's your personal problem, how about you smear every single custom ROM instead? How about all hardware while we're at it?

>>105931239
>They portray Graphene/pixel phones as the best and most private phone ever.
It is. Unless you right now state something better you agree with me

>>105926291 (OP)
Seems like a honeypot because you can't turn off auto updates and they don't support fairphone.

>>105926787
> GrapheneOS will have their own phone at the end of 2026.
X

>>105932108
>they don't support fairphone.
Fairphone is garbage for hippies who want to save the planet by reducing ewaste not people who care about privacy. If Fairphone made a phone with a relockable bootloader and whatever other features it is lacking that Graphene needs it would support them.

>>105926787
>2) GrapheneOS will have their own phone at the end of 2026.
Then the devs can troon out like Kondik did with Cyanogen, and the project can finally die

>>105926291 (OP)
how? it's developed by a genuine schizo. they always produce the best software.

>>105926742
>Truth by consensus.
>Truth by AI consensus
What an absolutely fucking retard. You morons should all be beaten to death.

>>105926742
>qwen
Look at the fucking state of you

>>105928708
>I NEED the McDonald's app
Post wrist

>>105926291 (OP)
Gentoo is more secure than this, I will continue using it.

>>105932108
you can turn off auto-updates

>>105928301
I don't give a fuck about Snowden; he was a limited hangout, anyway. I don't use social media AT ALL and I don't care to brag about GrapheneOS, but, I still use it. What now?

>>105928223
>The hardware is the main problem.
Provides 0 explanation nor examples attesting to his claim. Fucking moron

>>105928223
Retard has an issue with Google pixel phone hardware. Not Graphene OS. This is the kind of retardation that keeps our friends from the opposite side of the galaxy from visiting.

>>105928430
Cerebral insufficient moron.

is graphene os using only starlink mobile and telegram messenger the ultimate glowie seething use case?

>Who controls the hardware?
Google does. Now what's this to do with GrapheneOS itself as a ROM and operating system? It running on an OPPO would make you stop being retarded? Name ONE phone that isn't developed by a major phone manufacturer that doesn't fit the description you're crying about. I'll wait. Jackass

>>105931239
Is the cult in the room with you, right now?

>>105926291 (OP)
i have a fairphone5, do you recommend any of these rom since i cant use graphene?
im more concerned about all the italian state app that are probably not going to work. I'm not luke smith and i have to use them, even if its twice a year i still need them, aso i need my banking app. Worst case i can move all the italian gov apps to my workphone.

>>105931239
>Graphene OS bad, because ALL computing devices have backdoors and to install ANY OS on ANY computing device means the OS is bad.
This retards' parents must be siblings. Hey retard. Do you suggest not using any devices whatsoever, or, that we get multiple devices, take out various components and jerry-rig them and install CalyxOS. I'll be upfront and tell you the first is much more appealing

>>105929909
KEK, this.

>>105933852
So you admit, that Graphene OS is useless. Thank you.

>>105932872
I just use it for getting the points to get free burgers and the 3,90 euros big mac promotions they do from time to time.
I barely go there like once a month tops.

>>105933884
>im more concerned about all the italian state app that are probably not going to work.
why doesnt Fairphone make a dual boot phone? pozzed google Android for pozzed apps using play integrity + calyx/lineage for daily use

>>105935228
What a colossal retard

>>105926291 (OP)
I've an issue since switching to grapheme tho, and its the battery drain. Not sure if its the OS or the pixel itself but mobile data and WiFi are battery hogs for me.

>>105935767
>What a colossal retard

Not an argument.

>>105935228
False analogy - it is not an open window, but would be akin to a secret entrance into your basement placed by the builder. If this is the dealbreaker for you, you should try creating your own fan to make your own chips, to put your own firmware on and build your own phone. Otherwise, this is not an argument at all - why trust anything not built by yourself?
>>105935792
Manifestly untrue. Graphenes code has been audits both by the community and by organizations independent of its creator. There have also been independent security audits and the devs have addressed the discovered vulnerabilities so far.

While GrapheneOS is not beyond criticism, you have failed to make a coherent argument against it, hence why I suspect some sort of mental deficiency

>>105926742
Google hardware is special compared to Samsung for example? Samsung also puts their backdoor in TEE and vendor .so files, right? What's so special with pixels?
What does "deblobbed" mean in graphene? They replaced vendor libs with the ones they built from source? I thought it's not possible?

TRUST THE INFLUENCERS

>>105935228
This is the kind of retardation only a mother child love. anon, were you dropped on your head as a child?

>>105935947
>by organizations independent of its creator.

post source

>>105936049
>Zoomer trusts LLMs to tell him what his opinion should be, but can't use a search engine

>>105926291 (OP)
I'm not buying a $1000 phone just to install unusable schizoware

>>105936008
>jeets seething
and that's a good thing, maybe one day you'll be able to poo in loo

>>105926291 (OP)
almost perfect, support non google hardware first

>>105935792
>>105935947
>>105935982
Tbh, I don't think anyone disagrees that relying on google hardware is not ideal. Until theres an OEM that allows for AVB and OEM (re)locking however, we have no better alternative. It will be interesting to see what hw solution the gos people will come up with

>>105926787
>2) GrapheneOS will have their own phone at the end of 2026.
no cap?

He has a problem with Hardware and thinks the problem is with Software and can't differentiate between hardware and software. What a fucking moron

>>105936672
Could you please explain what is the problem with pixel hardware that is not present in other smartphones?

>>105936672
Stallman would agree with him

>>105936836
Unlike other OEMs, Google’s core strength lies in monetizing user data through pervasive tracking. New Pixel devices use Google-developed chips, granting full control. Other smartphones rely on processors with proprietary software not modifiable by manufacturers. By embedding backdoors and tracking in chip firmware—irremovable and Android-independent—Google ensures undetectable surveillance, as chip software runs before Android boots and SELinux activates.

>>105936900
Even if there is a backdoor, it would still need to go through the OS to "see" what you are doing and transmit it to Google.
Plus, why bother using (and thus potentially exposing) a hardware backdoor in like 0.01% of devices, when they can just legally spy on everyone using a stock android? Makes no sense

>>105936836
Apparently only google wants your data and not the other companies that sell your data

>>105936900
Also, while this is true in general, Google is not the only OEM manufacturing its own chips. So do LG, Huawei, Xiaomi, and most importantly, Samsung. So yeah, if google are doing this, the rest are guaranteed to do it as well

>>105936952
Your assumption that a hardware backdoor "needs the OS to function" is incorrect. Chip-level firmware (like in Google’s Pixel SoCs) operates independently of Android. It runs before the OS boots and before SELinux or any Android security policies activate. This means surveillance could occur entirely outside Android’s visibility—no logs, no detection in tools like logcats, and no user control. Unlike GApps, which rely on Android to collect data, firmware-level tracking bypasses the OS entirely.

As for the "0.01%" argument: Even a small subset of devices with exploitable hardware creates a dangerous precedent. Google’s own Pixel devices (a niche but growing market) are ideal for targeted surveillance against high-value individuals (e.g., journalists, activists, or enterprise users). Why rely solely on GApps’ broad surveillance when hardware backdoors enable undetectable, irremovable spying on specific targets? Additionally, firmware vulnerabilities can persist across generations—once embedded, they’re nearly impossible to audit or patch without Google’s cooperation.

Finally, trust in hardware is foundational. If Google controls the entire stack (chips to OS), it can bypass even GrapheneOS’s security mitigations. This isn’t about "bothering" with rare devices; it’s about systemic risk. A backdoor in 0.01% of devices still proves a critical flaw: total vendor control over hardware undermines security for everyone.

>>105937052
Ask ChatGPT about Intel ME next.

>>105928564
chat is this real?
oh how bad did grafedneOS fall off

The real question I would ask is:
Is GrapheneOS vulnerable to pegasus or any sort of device dumper currently on the market?
I don't care about how theoretically secure it is, I want to know how actually secure it is against real threats .

>>105937052
But how can the firmware know about my app usage if its outside the OS environment? I'm legit asking here, as I am not sure how this works in practice.

I agree with your points about targeted surveillance, but this has nothing to do with their business model as claimed in the post above.

As for the stack being all in googles hands, this is also a valid concern, hence the antitrust proceedings against them. However, as >>105937047 says, other OEMs produce their own SoCs too. If graphene solves the problem it claims to solve, namely the OS dependence on Google, then the pixel is no more compromised than any Samsung, LG or Chinese phone

>>105937161
>Is GrapheneOS vulnerable to pegasus or any sort of device dumper currently on the market?
There have been multiple reports of police not getting into phones because of GOS. Especially the auto-turn off feature is a thorn in their eyes. There were also leaks (I believe from Cellebrite) in which the only Android phones (iPhones weren't mentioned) that couldn't be gotten into were up to date GOS phones BFU, I'm unsure about AFU.

>>105937061
He could also ask about AMD PSP and ARM TrustZone as I told him before. He had no response since he's only here to smear Graphene.

>>105937320
thanks, this is the info I was looking for
still, it's worrisome that graphene might still be vulnerable if it has already been turned on and unlocked once but yeah, the auto turn off functionality might help with that

>>105937052
>targeted surveillance against high-value individuals
There's not a phone in the world which will protect you against that, brother. If they got Bezos, they'll get you high-profile ass

>>105937355
>still, it's worrisome that graphene might still be vulnerable if it has already been turned on and unlocked once but yeah
Yeah but that's just a problem with all android phones (and seemingly all iphones) in general. Don't forget that we're talking about state-level spyware though.

>block's you're path
wat do?

>>105937726
I accept that GrapheneOS prevents me from using Google Wallet which I wouldn't use anyway and wouldn't recommend GrapheneOS to someone who considers Google wallet an essential feature for their phone but would suggest a smart watch containing Google wallet as a nigger rigged solution.

>>105937726
it doesn't block my path. X always display this Play Integrity notification, but it always works.

>>105937161
>>105937320
I think if your phone is connected to a network (e.g. cellular) the feds could MITM its requests since they have hooks into the entire US Internet grid (see https://en.m.wikipedia.org/wiki/Room_641A)

Maybe it can evade local police attempts to get it, but it will not evade the feds' omnipotent capabilities.

I personally think they can crack TLS using anything under 2048 bit DHKE, and that they don't need to because they can MITM everyone.

>>105937387
no, secure enclave on iphone works as expected, it's the titan chip that's fucked (and it's the same on gos and base pixel, unless latest model fixed it but don't think cellebrite announced how exactly they were skipping it, so pretty much safe to assume it's the same as the last leaked cellebrite docs), gos can't do shit about shit hw design

>>105937869
>I think if your phone is connected to a network (e.g. cellular) the feds could MITM its requests
That depends. Being able to read the encrypted data barely counts as a MITM. Also Room 641A is about them copying all the data from the internet and encrypting it later, it's not about live access nor phones specifically. What you also want to look into are stingrays.
>Maybe it can evade local police attempts to get it, but it will not evade the feds' omnipotent capabilities.
No, them being able to copy encrypted data won't help them much. That's why DNM admins still can operate.
>>105937869
>I personally think they can crack TLS using anything under 2048 bit DHKE
Maybe but there's still more encryption even for simple messages
>that they don't need to because they can MITM everyone.
Them having access to encrypted bytes still doesn't enable them to spy on everything you do. If they did, there would be no state secrets.

>>105937917
>no, secure enclave on iphone works as expected
Source?
>gos can't do shit about shit hw design
You mean the design that's so bad that it's better than any other android phone out there? How about you design some chips so they can finally be secure? It seems you got some knowledge literally everyone (except for apple apparently) is lacking.

>>105937943
the fucking hw chip that prevents cellebrite from breaking into your iphone after first unlock does not work on pixels, now go ahead and claim cellebrite were just false advertising or some other deflection

>>105937943
>data beneath TLS is encrypted
Maybe for Signal, and DNM clients, but the vast majority of traffic is plain text beneath TLS, and thus a MITM setup like Cloudflare will be able to see everything, minus your Signal chats (which they can copy encrypted bytes of, as you mentioned)

>>105937989
Apparently you are wrong, and gos can actually make a difference here - https://primal.net/e/nevent1qqsfyvgd7jt0sql32rt6cwm87df5jlug5mnzl37m90y9ae8j7tu74ycfmqye3

>>105929214
Makes sense.
>>105929844
Graphene is only good if you have a phone that supports it, and they refuse to support older phones.

>>105926291 (OP)
Does graphene drain my battery faster or do pixels just have shit batteries in the first place?

>>105926742
It's funny how people who post LLM screenshots don't understand that AI can be made to agree with you on anything, so you're basically posting an image of you agreeing with yourself as evidence. It should simply add nothing to your argument at worst, but it actually goes as far as weakening you rhetorically, since there is a huge overlap between AI screenshots and delusional low IQ shit on twitter and reddit.

>>105940874
both

>>105938473
>but the vast majority of traffic is plain text beneath TLS,
GPG for sensitive data

>>105936846
I couldn't give a fuck about what a jew thinks

>>105936900
>Unlike other OEMs
>Google is the only OEM that monetizes user data through pervasive tracking
are you some kind of homeless person with down syndrome who found someone's phone under a park bench and posting on here, or something?

>>105926291 (OP)
It's shit, I had a pixel and tried it out it's more bug ridden than pajeet roms, it's crazy because it only works on pixel meanwhile crdroid, lineage, paranoidaosp support phones from 12 years back and work flawlessly, do not buy pixels they are trash hw to begin with

>>105936900
Once again, the retard criticizes software while pointing out the flaw with HARDWARE. this kind of simpleton-ry is unparalleled.

>>105937052
GrapheneOS = SOFTWARE
do you not comprehend the difference to quit your gay crusade against GrapheneOS?

>>105940985
Retard states in previous thread:
>anyone who tells you they can 'isolate/protect' Android from whatever is going on on processors' level is either clueless or if a developer, a FRAUD. Whatever is going on on processor's level has been isolated by design before GOS ever existed, and it is a bad thing, because processors are hooked directly into hardware and RAM and Android doesn't know what's going on there, because it is isolated.
So, how is this an issue for GrapheneOS? In addition, this is EVERY SINGLE COMPUTING DEVICE IN EXISTENCE!
>it is a bad thing
How? Where do the problems begin, since, as you've said, is "isolated".

>>105941403
>isolated
whatever the fuck that means

>>105941147
well duh, but how am I going to implement gpg when I post on 4chan?

>>105941540
>How can I encrypt my publicly available posts

>>105926291 (OP)

If you trust GrapheneOS on Pixel devices, you must also trust Google’s closed-source hardware stack—the very same infrastructure that could enable pervasive surveillance. In that case, there is no meaningful distinction between GrapheneOS and stock Android; both rely on Google’s opaque technology. Conversely, if you reject GApps and Google’s data harvesting, you cannot reconcile that distrust with reliance on Google’s hardware. To truly deGoogle, you must abandon devices where the manufacturer controls the silicon itself.

>>105941699
What does you trusting Graphene OS look like, anon?

>>105941579
Yeah, most isn't encrypted, counter to what this anon puts forth
>>105937943

>>105942238
Both of the posts you replied to are mine.

>>105942280
That's ok

Dumb faggot refuses you provide a hypothetical scenario where he trusts Graphene OS

>>105941699
>you must abandon devices where the manufacturer controls the silicon itself.
A proud huawei owner

>>105941699
>you must abandon devices where the manufacturer controls the silicon itself.
So qualcom or whatever company makes the cpu/chipset doesn't control its hw but google does?

is this thing even alive still. how tf they making a phone now when they could barely keep their fork alive.

>>105926291 (OP)
are you guys are Google hiring?
i want to get paid for shilling phones too

>>105943861
>A proud huawei owner
oy vey this is literally another holocaust china is your enemy goy

>>105926291 (OP)
Does call recording work in the EU? This may help me convince my in-laws to finally stop using chinkware

>>105926291 (OP)
is there a country where you can still legally get a burner phone and internationally working sim card? Sadly I was too young to get one back when it was possible in my country

>>105945488
>is there a country where you can still legally get a burner phone and internationally working sim card?
Yes, even in the EU

>>105927599
no one is saying otherwise, but i would rather be the gray man than the guy wearing a ninja outfit in that case

>>105940985
while your post is true the fact remains that I can tell most of the people shitting on this post are shills. they have a certain dialogue pattern that is just as noooticable as the ai slop. everything this guy said to the AI is correct, so at worst hes a broken clock. google hardware is pozzed

And I'll go one deeper, why shoul you care that google is pozzed if everything is pozzed? while I wont pretend you can avoid backdoors the fact of the matter is google is OBJECTIVELY a front shell company for the NSA and CIA. they are not an organic business attempting to use your information as a lunch ticket but instead a socially and financially engineered weapon meant to conduct global espionage for five eyes.

At minimum when you buy from a pozzed brand google is forced to then BUY that data from them in black book form. its much cheaper to just get it. and USING graphene means that the data can be prioritized and sold because it's SPECIFICALLY known that the people using it care about privacy and so the NSA information brokers can use them to test bed their social engineering and casework.

>>105945750
>google hardware is pozzed
Specifically google hardware or all hardware?
>google is OBJECTIVELY a front shell company for the NSA and CIA.
And all chip manufacturers are easily compromised.
>organic business
We haven't had those in Big Tech for a few decades now.

>>105945760
>We haven't had those in Big Tech for a few decades now
anon there is a difference between a company that was complicit with government oversight and one that is created to be a front for the government. Pretending they are equal is retarded. Governments want to crack down on dissidents, Businesses just want to get paid. if that means they sell your data, they sell your data. Google on the other hand is in a position where having a honeypot is useful for them because it gives them a test bed of useful retards they can toy with. socially engineer, attempt to crack, snoop, spy, intercept. it's a personal sandbox for them and is loaded with satanic symbolism as is. if you insist on using them, use them. but personally I don't see a point in waving my arms up and down and saying "hey I'm a person of interest"

>>105945750
>google is forced to then BUY that data from them in black book form
Or they could just use their proprietary malware which comes pre-installed on these phones with root access, and download the data directly

>>105945815
you don't really think those companies keep that shit back doored for free do you?

>>105945822
Anon, Google play on android is not a backdoor. Its the front door google uses to legally collect your data. No need for backdoors or spy shit, you've just bought the bug and pressed 'accept'

>>105945814
>anon there is a difference between a company that was complicit with government oversight and one that is created to be a front for the government.
Correct, but from this perspective there is no difference. Both will easily give access to your data and both have backdoors built in.
>Governments want to crack down on dissidents, Businesses just want to get paid.
No, businesses want to maximize their profits. If a government decides to persecute you in a court for years and suicide all of your top managers then you will not make a profit.
>Google on the other hand is in a position where having a honeypot is useful for them because it gives them a test bed of useful retards they can toy with.
By having us install software that can't be compromised by mossad?
>socially engineer, attempt to crack, snoop, spy, intercept.
Ok, do you have any recorded case of this happening on Graphene?
>it's a personal sandbox for them and is loaded with satanic symbolism as is.
So are you avoiding the internet completely then? Do you think this isn't satanic? Why do you think demons thrive so much in this space? Why do you think porn is such a big topic on the internet? It easily enables demonic possession as does everything that abstracts us from the reality of God's Grace. Not allowing my enemies to have my data is reducing the effectiveness of their possession.
>if you insist on using them, use them. but personally I don't see a point in waving my arms up and down and saying "hey I'm a person of interest"
Oh no, they might look at me more, realize they can't any reasonable data and I both wasted government time and made myself harder to look into. The horror!

>>105945858
>Correct, but from this perspective there is no difference. Both will easily give access to your data and both have backdoors built in.
wrong
the difference was already stated multiple times glownigger, you seem to really not like that though so let me say it a 4th time
USING GRAPHENE MAKES YOU A PERSON OF INTEREST TO THEM AND THEIR TOTAL CONTROL OF THE HARDWARE MEANS THAT YOU ARE OPEN TO FURTHER ABUSE

>>105945887
>USING GRAPHENE MAKES YOU A PERSON OF INTEREST TO THEM
That has nothing to do with google being a glowasset.
>THEIR TOTAL CONTROL OF THE HARDWARE MEANS THAT YOU ARE OPEN TO FURTHER ABUSE
We already established that all hardware is fully compromised by the feds

>>105945887
Nta, but let's say gos are successful in manufacturing their own phones. What's the critique of their software then?
All I've seen so far itt is ramblings about pixels, which even when true, are true for other android phones as well.

>>105945908
>>105945902
>N-no its all the same!!!
its literally not all the same for reasons I just posted you lying glowniggers.
I posted a LAUNDRY LIST of reasons and all you've said 4 times now is "N-NUH UH!!!!"

>>105945935
>>N-no its all the same!!!
It literally is. Google (use any search engine) Intel IME, AMD PSP and ARM Trustzone.
>I posted a LAUNDRY LIST of reasons and all you've said 4 times now is "N-NUH UH!!!!"
You provided two reasons and both are completely wrong

>>105945935
Anon, I agree that Google bad. However, not one poster in the thread has offered a better alternative to the pixel phone. Secondly, all arguments here have been about the phones, not the OS itself

>>105945945
>n-no they have this trusted platform see! thats the only binary blob we promise
t. (((you)))
>you provided two reasons
I provided much more than just that,
Do you want them again? of course (((you))) do
1. Google hardware running graphene makes you a person of interest
2. controlling the data on other businesses isn't free
3. google controls the hardware on the PIXEL
4. they can anticipate and use this data more effectively, as I mentioned every single time./
5. sifting through data and fucking with people throuhg an operating system they maintain IS NOT FREE.
SILICON IS NOT FREE
6. Manpower at compromised companies is not free
which leads to 7. THE HARDWARE IS OBVIOUSLY NOT THE SAME.

>>105945956
making yourself not a person of interest to a glownigger company is a better security choice than modding your phone. an even better one is just not having one.

>>105945963
>"Please install the spyware, bro. Please its better I promise, they won't use it if you don't stand out, I swear bro, they will not spy on you if you agree to be spied on, bro"

>>105945960
>>n-no they have this trusted platform see! thats the only binary blob we promise
I'm not saying that. I'm saying that literally any processor available to you (unless you are daily driving a RISC-V processor you designed and produced yourself) has a backdoor.
>1. Google hardware running graphene makes you a person of interest
So does posting on 4chan. The feds are storing all transferred data available to them anyway. The only solution for this is to have a new physical network they can't access. Good luck with that.
>2. controlling the data on other businesses isn't free
It isn't free if they are taking the deal they can't refuse. If they refuse, the state makes more money in the end.
>3. google controls the hardware on the PIXEL
Google has control over the design and production of the hardware. You have not shown that a backdoor is even present. However, all hardware is controlled anyway. See above.
>4. they can anticipate and use this data more effectively, as I mentioned every single time./
See my previous and the first point.
>5. sifting through data and fucking with people throuhg an operating system they maintain IS NOT FREE. SILICON IS NOT FREE
Good on me that I'm not using GApps or their OS. Also the phone isn't free either.
>6. Manpower at compromised companies is not free
Correct but literally all significant companies are compromised.
>which leads to 7. THE HARDWARE IS OBVIOUSLY NOT THE SAME.
Compared to what? Hardware with openly advertised backdoors?

>>105945982
>>105945994
>I'm not saying that.
you are saying that and did say that
>. I'm saying that literally any processor available to you
irrelevant
>So does posting on 4chan.
the vast majority of this site is not comparable to the number of people who use graphene.
>It isn't free if they are taking the deal they can't refuse.
you are correct, though I suspect you intended to actually be (((wrong on purpose)))
>If they refuse, the state makes more money in the end.
capturing data and fucking with people who have data and managing data all cost money and resources, which is why you are lying like the filthiest jew when you pretend its the same as on jewgle hardware.
>(((Google has control over the design and production of the hardware. You have not shown that a backdoor is even present.))) However, all hardware is controlled anyway. See above.
the fact that you even tried to argue this briefly is all I should really have to say at this point. YOU LOST. I'm done jousting with you glowpigs who literally shit their pants over an anime website so hard you stole and ran it for 10+ years. heres to another decade of tax payer funded anime pussy on (((your))) dollar

>>105946034
Literally said "install stock android because google spies on you" and left.
>Kek

>>105946034
>you are saying that and did say that
I'm saying that literally any piece of hardware available to you right now is compromised.
>irrelevant
No, that's what I'm saying
>the vast majority of this site is not comparable to the number of people who use graphene.
Doesn't matter. You're on a list. You likely have been for a while now.
>you are correct, though I suspect you intended to actually be (((wrong on purpose)))
I'm not, I'm explaining to you why your entire logic is applicable to all hardware.
>capturing data and fucking with people who have data and managing data all cost money and resources
And who pays that? Right, the company that collects this data and then sells it for a profit.
>which is why you are lying like the filthiest jew when you pretend its the same as on jewgle hardware.
It literally is the same since the government will come out of the deal with an advantage. Either you take their little money or you get raped in court and then they give you even less money and you pay them back for them raping you.
>the fact that you even tried to argue this briefly is all I should really have to say at this point. YOU LOST.
We all lost since according to you it's impossible to have any privacy if you interact with digital devices.
>I'm done jousting with you glowpigs who literally shit their pants over an anime website so hard you stole and ran it for 10+ years. heres to another decade of tax payer funded anime pussy on (((your))) dollar
Gookmoot isn't a fed, he's just a retard. You are even worse since you, according to yourself, are on a glowsite to complain about the only phones that weren't broken into by israelis glowing.

>>105930093
every device has to depend on modern closed hardware
auditing doesn't protect you from zero-days you troglodyte

>>105945750
But the hw is "isolated". so none of this happens

>>105945960
You are a moron. Continued to sperg out about Hardware and conflates software with hardware. Blossoms Graphene OS makes a user a target and doesn't explain (ADMIT) why (probably because there's no issues with Graphene OS he can point to without highlighting and conflating with hardware). You should take steps to kill yourself

>>105926291 (OP)
Its true but 99℅ of the attacks against it boil down to "pixels are exposed because google controls the hardware and the software, buy an iphone instead"

>>105946034
YOU lost, retard. You lost at least 50 posts ago. You have absolutely nothing to provide as evidence illustrating Graphene OS is an issue.

>>105926291 (OP)
>Can't wait for the end of 2026 when they will have their own GrapheneOS phone.
What the actual fuck are you babbling about

>>105945994
>literally any processor available to you
>>105946067
>any piece of hardware available to you right now is compromised
ACKSHCHUALLY you can buy this https://pine64.org/devices/rockpro64/ and build uboot without arm trustzone and it won't compromised, maybe other their devices too

>>105937330
>AMD PSP and ARM TrustZone
isn't it the same shit?
>The PSP itself represents an ARM core (ARM Cortex-A5) with the TrustZone extension which is inserted into the main CPU die as a coprocessor.
https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor

>>105947129
>ACKSHCHUALLY you can buy this https://pine64.org/devices/rockpro64/ and build uboot without arm trustzone and it won't compromised, maybe other their devices too
And how can you guarantee that the design pine64 set forth isn't compromised in production?

>>105948158
How can you prove that design IS compromised? With other arm SOCs we know that backdoor is in trustzone, in this case there is no backdoor in that place. You build yourself a dummy trustzone binary that does nothing. Why should we suppose that there is something else?

>>105948412
>How can you prove that design IS compromised?
We couldn't prove that for Google's chips either
>With other arm SOCs we know that backdoor is in trustzone, in this case there is no backdoor in that place.
Wrong, we don't know if there is a backdoor. If we employ the same logic with pine64 (be it malicious or through external compromises)
>You build yourself a dummy trustzone binary that does nothing. Why should we suppose that there is something else?
Because we did so with google where we have no knowledge of such a backdoor existing. I don't believe pine64 would knowingly ship products with malicious chips but I would also not believe that google would use hardware backdoors when they simply could get data from all of their other products that are practically used by half the world.

so this is just pixel marketing

>>105948573
>Graphene OS showing its biggest drawback is somehow unfair

>>105948573
that site is completely pozzed since half of the columns are literally fabricated for grapheneos to get a "yes" and for everything else to get a "no"

>>105948924
>Graphene is a scam it only has features no one else has to make a comparison chart where it gets a "yes" and everything else get a "no"
Retard.

>>105948540
I thought we consider it a trustzone backdoor? Because only TEE runs whole time together with regular OS and can perform the spying we are worried about?
>The cold boot path in this implementation of the ARM Trusted Firmware is divided into five steps (in order of execution):
> Boot Loader stage 1 (BL1) AP Trusted ROM
> Boot Loader stage 2 (BL2) Trusted Boot Firmware
> Boot Loader stage 3-1 (BL31) EL3 Runtime Firmware
> Boot Loader stage 3-2 (BL32) Secure-EL1 Payload (optional)
> Boot Loader stage 3-3 (BL33) Non-trusted Firmware
I assume backdoor can only be in bl31 which is built from source for that computer? (https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/comment-page-1) And it can't be in other stages? Or you mean some other kind of backdoor?
I don't know much about this but I'm not sure that you know it either...

>>105949254
>I thought we consider it a trustzone backdoor?
My point wasn't that pine64's chip specifically got the trustzone backdoor. My point is that if we say 'Google make chip so it have backdoor' we also have to assume that pine64 or its supply chain is compromised. My argument is on a logical level about the form of the arguments, not on a technological level about minutia of the different chips offered by pine64.

>>105948540
I mean, I thought like that, correct me if I'm wrong.
In Intel and amd CPUs backdoor is some black box, while arm CPUs don't have such backdoor, but rather a framework for making backdoors, for manufacturers of single board computers / smartphones. It's implemented in hardware but manufacturer has to write code that uses that hardware and does what is required. Most manufacturers provide this code as binary and users can't find out what it does, but some manufacturers allow users to write their own code for some models. And if you buy that model and use code that doesn't spy, then it's OK. And you can relax because there's no other backdoors in arm CPUs.
Is everything correct?

>>105949342
>Google make chip so it have backdoor
Well every time I said this I meant that they don't allow you to boot it with pure trustzone payload. But before thus thread I thought that they use some default arm CPUs, if they have something very custom, then if course there could be some additional backdoor, except trustzone.

>>105949353
>And if you buy that model and use code that doesn't spy, then it's OK.
Yes but that applies to everything doesn't it?

>>105949387
>if they have something very custom, then if course there could be some additional backdoor, except trustzone.
Yes there is a possibility that the hw could be backdoored but this, again, is the case with everything. Ofc you could check every single chip you use but we got fairly legit sources that show Graphene seems to be a tough nut to crack for feds.

>>105926291 (OP)
>can't use banking apps
>can't use media apps
>can't use messenger apps
will never be useful as long as (((play integrity))) and (((remote attestation))) continue to exist

>>105949972
Skill issue

>>105950159
go live innawoords while the rest of the civilized world continues to function

>>105950193
You how my banking app functions on Graphene?

>If someone had a light use phone as a backup, without needing Google Services, is it better to stay on stock Android or use which of the other OS that claim privacy?

Micay:
>An iPhone is the next best choice for a private and secure smartphone.

Source: https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private/3

What is their definition of "privacy" ?

>>105950315
So the privacy tier list according to the Graphene leader is:

1. Graphene phone

2. Iphone

?. Stock android phone

But Iphones NEED an apple account, otherwise you can't use the device. While stock android phones don't need a Google account to function. Using no account is from a privacy perspective a big plus. Then how is an iphone supposed to be better in terms of privacy?

>>105950394
>While stock android phones don't need a Google account to function
no android phone will ever progress past the boot screen without logging into jewgle

>>105950820
I don't deny that. But what is from a PRIVACY (not security) perspective better: stock android phone without Google account or iphone with mandatory apple account?

>>105951045
what would be better is having another luigi go after google

>>105950254
I use lineage but should be similar to grapheme. Banking apps work, messengers also work. What doesn't work is government app and apps that require maps (taxi and food delivery). It's possible to make them work with installing free google play services but I don't do it because it's for faggots. Also despite that my bank app works, I don't use it and only pay with cash because banks are also for faggots.

>>105932494
this dude has a black belt, i wouldn't underestimate him

>>105926291 (OP)
why does graphene do all this meme security autism when even most workstation operating systems don't do that? you're not doing anything on your tiktok browsing device that's more important than accountants or sysadmins

>>105951227
>you're not doing anything on your tiktok browsing device that's more important than accountants or sysadmins

This is why I think it is wrong, to advertise Graphene phones as "privacy phones". Your daliy internet habits are far more important than hardening autism of everything. The conflation of security and privacy - are they doing it on purpose?

>>105951282
A phone without base level security can never be private.

>>105951394
Yes, I agree. But I would say: Privacy = Mininmizing your digital footprint. The only way to certainly minimize your digital footprint (maximizing privacy) is by generating as few as data as possible. In other words: Even with a Graphene phone you will destroy your privacy through webbrowsing, using corpo apps, etc.

This is why in regard of privacy, user behaviour is paramount, not the type of device you are using.

>>105951394
you can have both privacy and security. the only reason we currently don't have both is because kikes deliberately withhold the keys and hide all info that can keep you safe under the rug (e.g. hashes, digital signatures and certs) for the sake of convenience

>>105951282
>>105951522
It's one of the many tools available to us. Not a silver bullet but one of the things you might need for a higher threat model.

What's the best way to root Graphene?

>>105928011
Daniel Micay is a woke schizo with several personality disorders. An especially spiteful one at that. I don't want a nigger like that tinkering with my phone software.

ITT: mundane midwits with uninteresting lives larping as James Bond

>>105951652
>one of the things you might need for a higher threat model.


Where does this belief come from, that a small group of average talented hobby coders can outsmart the most powerful secret services of the world which have endless ressources and don't care about the law?

>>105951582
Kikes like Moxie Marlinspike, AKA (((Matthew Rosenfeld)))? Oy vey goyim, you can definitely trust my non-CIA-sponsored cryptography.

>>105951652
How can you speak about higher threat models if you have zero such experience? Stop larping.

>>105951809
>Where does this belief come from, that a small group of average talented hobby coders can outsmart the most powerful secret services of the world which have endless ressources and don't care about the law?
From court documents and the media who both have shown that they do not have access. Could Google, Apple or any other Big Tech firm create a more secure product? Yes. Are they interested in doing so? No.

>>105951825
Bad bait. I hope this (You) appeases you.

>>105951813
it's not just that they can decrypt your shit. they also hide keyboxes outside your control inside the chips of your phone to get it to betray you. that's the entire point of (((attestation)))

>>105951857
They have access. They use the 20$ wrench.

>>105951905
And then they got my phone, the data on it being inaccessible to them if I have it turned off. Good job.

>>105951809
>>105951867
This, google is literally omnipotent, so don't even bother with any security. they are unbeatable so definitely do not install grapheneos. Do you know they have super duper ultra advanced fingerprinting methods? Tor? lol thats owned by the government and you think google cant track you with that? so don't even think about using it for pirvacy.
makes no difference whether you use a phone with only google apps and the play store vs no ad blocker or a graphene os cutome rom with no google services, google has literally every phone chipped and tracked to measure the intensity of your breath and your heat signature even when the phone is off. How? Proof? um it's google that's all I have to say it's google they sell your data. What data? uh no ive never actually SEEN the "data" they sell but they sell your data theyre logging every keystroke, every breath you make, so it's over privacy is dead and you really shouldn't even try, they also have nano tracking bugs in the drinking water, in the water table even so no wells can keep you safe either, your body is already infested with google trackers.

>>105951945
all I'm saying is I hate (((remote attestation))) and as long as no solution is found for it, there's no point in using non-stock roms.
ps: microshit intends to do the same with its (((TPM))) bullshit. i.e. if you disable secure boot, run unsigned drivers, install programs from "untrusted" sources, etc., then programs refuse to run until you "sort that out"

>>105926291 (OP)
Glowies need something trustworthy to use personally, right?

Daily driving GrapheneOS and Qubes OS for a few years now. You can't FUD me from either!

>>105926291 (OP)
How much will this phone cost? I ain't paying more than a Pixel that is like $200 for a gen or two old.

>>105952855
I will pay $2.000,00 for a GrapheneOS phone (presuming it's close to flagship Google specs), but I won't use any other Android if you gave it to me free.

If you are pricing the hardware, you are doing it wrong. You must price the platform: If it costs $2K to ship an otherwise $1K phone equivalent, so-be-it! Better than a discounted $600 for a $150 equivalent like so many before.

>>105952845
I use Qubes for crypto shit and daily drive Graphene. Why do you daily drive Qubes? What possible use case could demand putting up with how resource heavy it is. Graphene is absolutely fine to use as a daily driver.

>>105952997
I would like to say I would do the same but I will gauge how durable it looks first. It will probably be fine but you have to consider the possibility that it is super secure and that doesn't matter because it is made of Chineseum and breaks if you look at it wrong.

I use GrapheneOS with Google Play Services turned on.

>>105949972
So far everything works. I'm using all the big corpo tracking spyware right now including multiple banking apps. The FOSS weather apps can't find my location but The Weather Channel can.

>>105953011
>What possible use case could demand putting up with how resource heavy it is.
Browsing 4chan. Do you really trust your browser not to send ~/.* up the pipe quietly?

Can you use graphene in any other phone besides pixel?

I like YouTube, I like some videos, I want to keep watching YouTube but yeah, I don't want Google.

>>105949415
>we got fairly legit sources that show Graphene seems to be a tough nut to crack for feds.
source?

>>105951945
>no android phone will ever progress past the boot screen without logging into jewgle
When does this logging in occur? You schizos makes up all kinds of shit

>>105951857
This retard literally trusts the media and the government

>>105948924
>storage scopes don't matter

>>105926291 (OP)
>create a chart with a list of grapheneos features
>check if other os' have the same features
>ignore features that other os' have but grapheneos doesn't
>"How GrapheneOS is so perfect ?"

>>105957125
sorry why are you using apps that still ask for external storage permissions
SAF is the standard and Android VILL phase out external storage