>runs only on Google hardware and communicates with Google servers (gstatic) by default Why exactly is this supposed to be the holy grail of de-Googling?
>>109152686>Yet another anti-grapheneOS brainlet misconception thread.I don't even use the OS, this is retarded. People posting these shit have to be bots, right?
What better way to flag and honeypot privacy-conscious people?
>>109152698they are probably glowies doing fearmongering microcampaign
>>109152686>and communicates with Google servers (gstatic) by defaultI doesn't and that one schizo claiming it in this thread is no proof of anything.
>>109152703It does seem like an organised campaign. But on the other hand i can't imagine why anyone would campaign on /g/ instead of tik tok or somewhere less dead.
>>109152703>glowies want to fearmonger you away from Google hardwareRetard of the year award.
>>109152709nvmd, apparently it doeshttps://grapheneos.social/@GrapheneOS/116811567684278477
>>109152722I love how they heavily criticize competing projects making inaccurate claims in their marketing about being degoogled and private, while their own FAQ flat out lies about the connections the OS makes by default.https://grapheneos.org/faq#default-connections
>>109152741This seems to have been an honest mistake and it took a while for them to find the (complex) reason why this happened. They are already working on a solution (which is to distribute one file via their own servers instead of gstatic). All things considered, this is a pretty irrelevant connection (just a regular http get request for a binary file). Also, go cry about it you little faggot, if you can't stand criticism, maybe you should stop using pajeet tier ROMs which actually do knowingly lie about their privacy features.
>>109152717Try finding critical content about Graphene somewhere on the internet. The only thing I found was a blog post, though I had to use Yandex to find it. Criticism of Graphene is being systematically buried and hidden. Isn't that strange?
>>109152757>Criticism of Graphene is being systematically buried and hidden. Isn't that strange?There is literally, not figuratively, literally - a 900k views YouTube video on that topic, dealing with the schizo lolcow developer. If you were unable to find this video, maybe you just didn't look hard enough. Also, there is no substantial criticism that would apply to the project itself. They continuously went the extra mile, submitted upstream patches to Android with security improvements and regularly listen to user feedback when it comes to hardening the OS even further. It is the only serious Android ROM out there and the reason why it only works on AOSP reference phones is because no other manufacturer can be bothered to follow Googles guidelines on bootloader security.
>>109152752>honest mistakethen why did they never apologized? why didn't they update the FAQ? why did they tried to sweep the issue under the rug, while being known since months? why do they say, they just make the proxy service, just so people "feel better"?https://grapheneos.social/@GrapheneOS/116813168121504197
>>109152686>Why exactly is this supposed to be the holy grail of de-Googling?Because Sgt. Shanzes from the Eglin Airforce Base says so.Why would the government employed shill from the internet defense force lie?
>>109152772>dealing with the schizo lolcow developer.It’s nothing but spectacle on a personal level. Gossip, not substantive technical criticism. But technical criticism is what really matters, not tabloid bullshit.I am talking about real criticism, not eceleb drama.
spyware or not, graphene is the only android custom rom to support verified boot out of the box while also delivering updates on timeit's not perfect but it's still the best
>>109152774Because they literally just download a certificate file from a Google CDN, as do a gazillion other FOSS projects that will never tell you about how they deliver their assets. Google gains no information from this download, it does not hurt anyone in any way and the only thing a proxy will do is make GrapheneOS know about this single download instead of Google. >"t-they need to apologize!!!"What are you, like 12?
>>109152772nta, but most public criticism you find against GrapheneOS is about the schizo dev or starts with:>GrapheneOS is the most secure holy OS we all should use, BUT...and ends with>but nevertheless, you should use GrapheneOSThat's because they are either scared from the schizo dev sending his herd of shills to trash talk you, or they honestly believed that goypehene would have been good, but found a flaw and are in delusion about it and cope.Just look into this thread how immediately everybody who is slightly cricial about goyphene gets attacked. There is literally a post here >>109152752 claiming "they lied by mistake". How fucking dumb is this?When the goyphene idiots pushed that Google Titan blackbox chip, it should have been over. You can write essays about why that is a no-go with plenty of examples of those Google chips fucking up.
The biggest problem was their response the original thread was made in january and devs replied several times but it was to try and dismiss the post. There's also retards saying a degoogled phone connecting to google is a non issue and you should be thankful for it.Extremely hostile reception imagine if it was actually critical and the reporter was blown off by a dev or harassed by their fanboys and told to shut up and be thankful.
>>109152791>I am talking about real criticism, not eceleb drama.There is none, it's a close to perfect operating system if your focus is on mobile device security and privacy. That's why all criticism on /g/ has to revolve around a Jewish conspiracy and the fact that they only run on Google phones ( see this faggot for example >>109152810 )
>>109152793The scenario that verified boot protects you against is a scenario where a glowfag could have simply read your secrets from the Google Titan chip instead and do whatever they want without having to flash a new ROM.
>>109152820>Source: I made it up
<you know, i think that storing your secrets in a proprietary google chip that can be accessed from outside the OS is kinda shady>WTF, FUCK OFF WITH THIS NON-TECHNICAL CRITICISM, IT IS CLOSE TO PERFECT<you know, they said they make no requests to Google, but here they make requests to Google>WTF, AGAIN YOU WITH YOUR NON-TECHNIGAL ARGUMENTS, THIS REQUEST IS PERFECTLY FINE AND A NONE-ISSUE, BUT WE STILL ARE GOING TO REPLACE THIS NON-ISSUE AND SEND THE REQUEST TO OUR AMAZON AWS INSTANCE EVEN THOUGHT ITS NOT AN ISSUE AND IT WAS A MISTAKE ANYWAYok
>>109152833>SourceThe fact that Googles Titan Security Key could literally be clones wireless over bluetooth.
>>109152820sorry bro, i cant sleep while knowing that anyone can just take my phone, boot into fastboot and do whatever they want with my data
>>109152840then why do you use a phone that provides access to a proprietary chip over fastboot that stores all your encryption keys?
>>109152840>and do whatever they want with my dataThey can't do that if it's encrypted, doesn't matter if you have verified boot or not.
>>109152847name me 5 phones that don't have proprietary black box chips
>>109152884how convenient, what a honest post, ignoring the two additional conditions of:>stores all your encryption keys>accessibly over fastboot
>>109152699They run Signal on it so no worries lmao
>>109152891>>109152884sorry, i forgot to mention:>can even be flashed over fastboot, while the OS isn't even booted, lol
>>109152820glowfags could create a verified malicious ROM as well. Verified boot does exactly nothing against the entity that's holding the keys for that verification.
Goyphene doesn't consider google, three letter agencies or the government as your enemy.So the argument, that glowfags have an easier time getting into a goyphene Pixel, than into other phones, just bounces off from them.In fact, goyphene produces the perfect phone for CIA stooges on missions in foreign countries:>less network traffic going out>if the stooge gets captured, the foreign government has a hard time getting into it (most likely not at all)>but your own glowfags can (through both verified boot and Google Titan backdoor), so you can keep the stooge under your control and stop him from becoming a Snowden>if the foreign government pressures google or the US into getting access, they have plausible deniability and can pretend that they can't
>>109152686The 24/7 counter signalling is definitely interesting.
Graphene team desperately needs to put Micay into a fucking cage with 24/7 surveillance for their project's sake.
I don't care. I just updated mine to Android 17. Keep posting the same shit so pixel and motorola won't get a price increase.
>>109152722Yup, and it will be removed in the next release!>>109152774>why did they never apologized>why do they say, they just make the proxy servicePlease learn to speak english, Sameer.Even better than writing 13 paragraphs about why they are very sorry, they are going to fix the problem. They sure did sweep that one under the rug, responding, making 15 Twitter posts, replying to tens of people about the issue, and doing what people wanted. Fuck off.>>109153003>Google Titan backdoorOh yeah all those backdoors everyone knows about. Please post those here, since everyone loves to talk about how Google phones are absolutely FILLED with backdoors, despite never actually linking to anything showing it.>>109152810>claiming "they lied by mistake".Did you even read the post you are quoting? Not once in their post do they use the word "lie". They aren't "claiming" that, you illiterate bastard.>You can write essays about why that is a no-go with plenty of examples of those Google chips fucking up.Please do, and post here. I would love to hear all about that. I can't find much about that online.In the last grapheneOS thread there were posters complaining about grapheneOS that didn't even know GPS is one-way. I wonder how many of those posters are in this thread?
if grapheneOS wasn't a honeypot and was a real threat to glowies they wouldn't allow it to exist, let alone have a commercial partnership with Moto LMFAO
>>109153719Correct. In the US you are served with a secret gag order like lavabit for tailored access. Obviously this is a honeypot from the start but anyone with a brain knows that they would be served this order otherwise.
>>109152752then edgy is my account still suspended for bringing it to their attention?
>>109152772>>109153804>>109152752then why* is my account still suspended for bringing it to their attention?
>>109152796then why is my account still suspended for asking about this?
>>109153804>>109153810>>109153819can we see your post? did it contain any wrong information/inflamatory speech? what account was it? what was the official reason? where was it posted? wrong thread? can the post still be seen in the thread?
>>109152810No asshole. Most "public criticisms" of GrapheneOS are NOT criticisms AT ALL, but innocent and interested people asking genuine in-good-faith questions and getting LABELED as antagonizers and criticizers of GrapheneOS.Again, why is my account still suspended when all I did was ask if this currently discussed issue is being addressed in the new update?
>>109153510Turns out I am the illiterate bastard, the post does say OTHER roms are lying, and does use the word lie. But does not say grapheneOS "lied by mistake".
>>109153831
>>109153831GrapheneOS is full of passive-aggressive homosexuals. That's just a fact.
you do not need to use graphene, linux kernel nowdays supports phones..you can vibe code your own ios like environment for linux phone with fancy animations, you dont even need plasma or gnome mobile or phosh or whateverits not that hard
>>109153510>Oh yeah all those backdoors everyone knows about. Please post those hereThe Google Titan security chip could be cloned over bluetooth.Then the Google Titan M1 had a whole report written about how to hijack it by very sophisticated motivated researches... the researches didn't get a proper bounty payment from Google, so their effort didn't pay of, and so nobody will ever try to find the backdoor in M2.And always note that you don't even need a backdoor within its firmware at all time, if you can flash it via fastboot. They can simply have a different firmware and throw it on it when they want to hijack it. They have that capability.You may claim that Google is just full off utterly incompetent drooling monkeys, who produce such bugs, but the more likely explanation is that they are backdoors. And for our purposes, it doesn't matter at all whether its incompetency or malice, the end result of usable exploits to hijack a system, is the same.
>>109153831Why? Why all the sissy behavior? Literally acting like fucking women? This is why I used to beat them up in school. Absolute fucking faggot little bitches who deserve to be beaten
>>109153913this is why faggots get punched in the back of the head when they least expect it.
>>109153913"Unsubstantiated" while just posting facts about the connections GrapheneOS makes and showing their inaccurate claims in their FAQ. They just don't like or tolerate any criticism, even when it's genuine.
>>109152686I wonder who is behind these retarded anti-Graphene slop threads. Are you from Cellebrite, NSO Group or some other Israeli spyware company?
>>109153854i dont see any reason why this would be removed. however, if you posted >>109153865 immediately after in the same thread after getting no responses, i can understand if someone would mistake it for spam. in this thread you have already made 3 back to back posts saying the same thing. did you have a similar behavior in the thread? were you flooding it with back to back posts, or not waiting for replies? again, not sure of the full situation here.i also cannot find either of these chunks of text in this thread: https://discuss.grapheneos.org/d/36765-grapheneos-version-2026062300-released. were they deleted?>GrapheneOS is full of passive-aggressive homosexuals. That's just a fact.>Why? Why all the sissy behavior? Literally acting like fucking women? This is why I used to beat them up in school. Absolute fucking faggot little bitches who deserve to be beateni hope you didnt go using this language in the thread as well.
>>109153936The very same groups GrapheneOS is marketing to.
>>109153939>hurrr move the goal postKILL YOURSELF YOU STUPID FUCKING HOMO. remember, when you least expect it, faggot! BAM!!! Right in the faggot girly mouth
>>109153950i can completely understand why they would ban you from the GrapheneOS discussion forum.
>>109153939>There must be a reason whyliterally running damage control and putting up disqualifiers as to why GrapheneOS homos were right and justified, as if every and anything they say and do are above reproach and criticism.>>109153957what I showed that was all that i posted. you can move the goal post like the homo you are, all you want. It won't change the facts. Trying to disqualify after the facts. KYS
>>109153957that bitch ass girly mouth of yours will be all red
>>109152686they partner up with motorola right nowhttps://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/
>>109153940Please explain like i'm retarded, because that makes no fucking sense, anon.
>>109153936>don't you dare criticize GrapheneOS, you must be <insert government psyop group here>OP just mentions a connection GrapheneOS makes of which they claim in their documentation they don't. You probably never read their socials, because they go after other android distributions much harder when they make inaccurate claims. Them banning people mentioning this justifies the criticisms even more.
>>109153982NTA but it's obvious. The people who are flashing phones with OS branded for "privacy" are the same people are going to need to get transparent explanations and not bans for "4chan trolling". Obviously this is a big deal by the mere accusation and not responding properly shows only malice.
>>109153957wait wait wait are you literally trying to retroactively apply his interactions here with you to what GrapheneOS trannies did to his account? KEK>something must be wrong with YOU because the GrapheneOS Gods don't behave that way without justifiable cause.>you must have done somethinghe's right all of you need to be made to line up and face the wall.
>>109153982GrapheneOS devs, employees, marketers and shills all need to be paid, somehow. The model is and will always be PROFIT FIRST. The entire GrapheneOS model is to market to government agencies and state department personnel TO MAKE MONEY. This doesn't mean the product is placebo or fake [necessarily]. It means their target audience are not who we think. This is why it has to be airtight.
GrapheneOS makes money from user donors, such as, Jack Dorsey and Vitalik Buterin and grants from Matt Odell and Ben Price [OpenSats] (both backed by Jack Dorsey).
>>109154069>are you literally trying to retroactively apply his interactions here with you to what GrapheneOS trannies did to his account?no, but it's crazy how much you extrapolated from that incredibly short reply.what likely happened:he posted >>109153854 and after getting no replies quickly posted >>109153865. just a guess though, since there is no way to see/verify anything about these posts. timestamps, replies, etc are all stripped from these screenshots, and i can't exactly pull up the account to see all the posts they made. the posts themselves can't be found on the thread that is named at the bottom of >>109153854 (that being https://discuss.grapheneos.org/d/36765-grapheneos-version-2026062300-released/). so, really hard for me to rule for or against grapheneOS's moderation team.i can agree it is pretty annoying/suspicious that they would remove these posts from their release announcement discussion, given that's where a lot of users are going to, especially those very interested in the project that would have cause for alarm when they see such a message. that is to say, it would be bad PR for the grapheneOS project to leave either of these posts up.i could also understand this post being offtopic, given that this issue has it's own thread, and the release thread isn't exactly the best place to put this. as for being unsubstantiated? well, depending on the time zone, it looks like this moderation email was sent AFTER an official reponse to the situation was made in https://discuss.grapheneos.org/d/30985-downloads-app-contacts-gstaticcom. so, while the posts themselves could be seen as "unsubstantiated" (as they do not cite anything), and the quote could have been copied directly from /g/, the claims themselves are admitted true in another thread by the official grapheneOS account. as for if the information itself is fabricated? again, it's not, as the grapheneOS account earlier admits.1/2
>>109154069however, i will say i believe i understand why they would remove such posts. from a moderator's perspective:a post has been made that is entirely a quote, but contains no citations for who the quote is from, which has been posted not in a thread about the specific issue, when a thread for the issue already exists. when the poster doesn't get enough replies, they post "how come no one is discussing this?", cluttering up the release thread. that's probably reason enough for the moderation team to get the posts themselves deleted.mods could also be acting maliciously and trying to sweep this issue under the rug, or maybe they're just faggots with girly faggot mouthes. which explanation makes more sense to you?2/2
>>109154308>>109154322>what likely happenedThat's EXACTLY what you're doing.
>>109154322I believe anon bcuz this is widespread and commonplace with GrapheneOS trannies yeah they are girly mouthed little faggots
>>109154335>>what likely happenedyou're right. let me correct that.what DID happen:>>109153854 copied text directly off of /g/ and pasted it mindlessly into an unrelated thread, and when he didnt get any replies off his post (since the issue was already solved, and an official response already existed) he got so butthurt he made >>109153865 to try and bait more responses to his reduntant issue. once the mods banned him for spamming garbage, he became insanely butthurt and went on to spam this thread with>>109153865>>109153913>>109153923>>109153950>>109153970>>109153975mentioning "faggots" in every post, because he got tormented by homosexuals in school, and now they live rent free in his head.of course, he can't refute any of this, because it's exactly what happened :^)
>>109154494that's NOT what I did. I copied and pasted what was said on kuketz. why are you lying?
>>109154494>>109154069What a fucking creep
>>109152703It's definitely organized. Every single fucking time that something actually works, shills come out of the woodwork.
>>109154514>Why? Why all the sissy behavior? Literally acting like fucking women? This is why I used to beat them up in school. Absolute fucking faggot little bitches who deserve to be beaten>this is why faggots get punched in the back of the head when they least expect it.>remember, when you least expect it, faggot! BAM!!! Right in the faggot girly mouth>you can move the goal post like the homo you are>that bitch ass girly mouth of yours will be all redyeah, what a creep.
>>109154590but he's right tho
>>109154590he called you a faggot and that means GrapheneOS troons age in the right got it kys
>>109154590>>109154494>>109154322>>109154308jfc what a mind funeral
>>109152686Try talking about this issue on reddit or X. You will be (shadow)banned immediately.
>>109152741Let's place a bet: will GrapheneOS correct its misleading FAQ?
>>109155404They won't. They have never admitted any wrongdoing. They'll just replace the gstatic connection with their own proxy in the next update and that's it. Probably won't even put it in their change log.
>>109154584sour grapes or feds.make your call
>>109152717Because on tiktok you need to push lots of content to get people into it. Here a fed just needs to post one thread per day and his quota is exceeded.
>>109153854what is being conveyed by the client device download manager to gstatic? is it telemetry/usage logs?
>>109158085no. it's simply a request to download a file. a certificate transparency log. no private information is being conveyed.
>>109159528Even if no content or account data is transmitted, Google sees the user's IP address and the exact timestamp with every request. If the smartphone retrieves these lists, for instance, whenever the charging cable is connected (as described in the article), Google could theoretically use the IP address to determine when the user is at home and charging their device.https://www.kuketz-blog.de/grapheneos-warum-android-eine-verbindung-zu-gstatic-com-aufbaut/
>>109159528Even if static GET requests leak no personal data, the gstatic.com connection allows Google to track and correlate your IP address over time. Because it happens while charging, it maps your daily routine and locations on the exact same servers used for global tracking.
>>109159669>>109159684Yet GrapheneOS will only remove it to make users "feel better". Just install your apps from the google play store to be secure and stop complaining.
>>109152686>>109152698>>109152699>>109152703>>109152709what phones not backdoored though
We did it reddit
>>109159669it's not only when charging. and you assume the IP doesn't change. Google can do very little with the metadata they do get from the connection.>>109159684how can they track and correlate your IP address? they get no unique identifier. they won't know it's the same device on subsequent connections.
>>109159919nah, a win would be if it would get removed completely>we make requests to our Amazon AWS instance instead of Google now
>>109160203that would break apps
>>109160189Even without a device ID, Google can track you because your IP address acts as a temporary identifier that stays static for days. They can instantly cross-reference this IP with your active Google accounts, browser sessions, or Google Fonts used on other devices in your household. Furthermore, because the connection happens while charging, the recurring combination of exact timing and geolocation creates a distinct behavioral pattern that maps your daily routine.
>>109160203One toggle to disable it. Widevine provisioning (DRM) is much worse, and that can't be disabled. The same goes for attestation key provisioning.
>>109160755It doesn't happen every time you are charging, and also not continously. The tracking potential from these connections is near zero. At most all they know is that one charging process (of many) of an Android phone (not a specific one) in that network started at a certain time. And even the starting cannot be certain, as the phone may have started charging without internet connection.The biggest issue you could com up with is them cross-referencing those pings with other tracking data they get from the same IP. Guess what: that other tracking would be your real problem.
why are you concerned, that the holy grail of privacy is connecting with google servers by default?https://grapheneos.social/@GrapheneOS/116813168121504197
try to talk about this issue on reddit. they censor everything. weird.https://www.reddit.com/r/opsec/comments/1uirtnd/grapheneos_undocumented_google_connections_and/
>>109163522you don't belong herealso that post is full of misinformation
>>109163522https://archive.ph/I77NcINSANE CENSORSHIP ON REDDITtry it yourself. they will delete everyting.
>>109163577broken link? https://archive.ph/I77Nc
>>109152717>i can't imagine why anyone would campaign on /g/ instead of tik tokDo tiktok users even know what GrapheneOS is?
