Robert Braxman has published another video spreading blatant misinformation about GrapheneOS in order to promote his highly insecure products and services. In addition to many false technical claims and fabrications about our team, he's falsely claiming the project is dying.
Gianmarco Gargiulo reshared this.
Kuketz-Blog π‘
in reply to GrapheneOS • • •GrapheneOS reshared this.
No Twitter
in reply to Kuketz-Blog π‘ • • •@kuketzblog
What do you all think of Privacy on iOS? Should the average user care? Rob Braxman has made me too skeptical about iOS and MacOS devices, on privacy front.
What I am really sure about those devices is that Apple does have some backdoors, but they don't implement mass surveillance, and avg. user shouldn't worry.
Ofcourse, GOS is god in security.
What do you all think of Privacy on iOS?
GrapheneOS
in reply to No Twitter • • •@Notsoanonymous @kuketzblog Apple products and services are certainly far more private, secure and trustworthy than Braxman's products and services. That's not a high bar.
> What I am really sure about those devices is that Apple does have some backdoors
There's no evidence of that. On the other hand, Braxman's products/services have had actual legitimate backdoors in their code including fake end-to-end encryption where the server has access to the keys. There are people who covered this.
GrapheneOS
in reply to GrapheneOS • • •@Notsoanonymous @kuketzblog
> What do you all think of Privacy on iOS?
iPhones are far more secure than the vast majority of Android devices. Only Pixels are currently competitive with them.
iOS is far more secure than nearly all options. Stock Pixel OS and AOSP itself aren't far behind iOS but iOS is at least a bit ahead. GrapheneOS greatly improves security. iOS has areas it does better even than GrapheneOS, but we think GrapheneOS is more secure overall especially against real exploits.
GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •We have a thread already debunking this recent line of attack on GrapheneOS at grapheneos.social/@GrapheneOS/β¦. GrapheneOS quickly provided the June security patches, was ported to Android 16 and is working with a major Android OEM. It's not dying and we haven't said or implied it is.
GrapheneOS
2025-06-21 13:48:22
GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •More privacy and security experts should address Braxman's inaccurate content along with the products and services he sells.
social.tchncs.de/@kuketzblog/1β¦
Braxman has repeatedly sold people fake end-to-end encryption messaging, etc. The companies working with him are scammers too.
Kuketz-Blog π‘
2025-07-09 17:28:59
GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •Oblomov reshared this.
GrapheneOS
in reply to GrapheneOS • • •Oblomov reshared this.
GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •Our initial official production release of Android 16 was made on June 30th after an experimental release the day before which had major issues:
grapheneos.org/releases#202506β¦
Most users already considered that fully functional and very stable. Most early testers were happy with it.
GrapheneOS releases
GrapheneOSNomadicCore
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •There were no Pixel Update Bulletin security patches for July 2025 so we took an extra day to polish things up further and GrapheneOS based on Android 16 reached our Stable channel today.
Due to requesting and receiving help, we're much better off than we were before Android 16.
GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •Useful information on Braxman's products and services from a security researcher (founder of DivestOS):
forum.f-droid.org/t/brax2-alteβ¦
Highly insecure, ancient hardware running a closed source fork of the end-of-life Android 10 which did NOT receive basic security patches and updates.
Brax2 alternatives?
F-Droid ForumGrapheneOS
in reply to GrapheneOS • • •thereisnoanderson
in reply to GrapheneOS • • •Ozzelot
in reply to GrapheneOS • • •Florian
in reply to GrapheneOS • • •tinyocean
in reply to GrapheneOS • • •Not sure if this is the right place to ask but how will you handle the battery update for the 6a?
Did you push the one for 4a?
GrapheneOS
in reply to tinyocean • • •@tinyocean
> Not sure if this is the right place to ask but how will you handle the battery update for the 6a?
We'll ship it and perhaps figure out how to display a notification to users about it with the option to disable the safety feature. People should get the battery replaced though.
> Did you push the one for 4a?
No, since it was end-of-life for ages already and they didn't properly release it. We highly discourage people using end-of-life devices.
tinyocean
in reply to GrapheneOS • • •I assume that includes a check if the device is affected?
I tried my IMEI but it seems that I am not eligible for free repair. Not sure if that means I am safe or screwed over.
GrapheneOS
in reply to tinyocean • • •tinyocean
in reply to GrapheneOS • • •Thanks, I guess that means I am safe and I can keep using it till EOL in 2027?
Sorry that I ask again but will the battery only be limited for the affected users or for everyone? Will you just include a warning for everyone and you need to manually confirm if you can disable the safety feature at your own risk? Or does the update from google contain a list of affected devices / detects the battery origin and unaffected users don't need to do anything
GrapheneOS
in reply to tinyocean • • •@tinyocean
> Thanks, I guess that means I am safe and I can keep using it till EOL in 2027?
We aren't fully sure, but when we add the planned feature you'll only get a warning if you have a problematic battery. Their code only activates the change when the battery is from the problematic supplier so we can do the same with a warning. We could also tell people their battery is NOT one of the problematic ones. We haven't fully decided what to do about this yet and don't have resources to spare.
HL
in reply to GrapheneOS • • •Tizian γγγ£γγ£γ’γΌγ³γ
in reply to GrapheneOS • • •SomeAnoTooter
in reply to GrapheneOS • • •Miguel Torrellas
in reply to GrapheneOS • • •Eskuero
in reply to GrapheneOS • • •GrapheneOS
in reply to Eskuero • • •Eskuero
in reply to GrapheneOS • • •"Otherwise, be prepared for the final release of GrapheneOS to be today. It's up to the people who have this access to decide if they want the project to go on after today."
is very clear language not open for interpretations
GrapheneOS
in reply to Eskuero • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •@eskuero Show the whole conversation including the edits we quickly made to the initial messages. Why are you using a cropped screenshot and twisting the wording we used in a way which contradicts us very clearly explaining it would take far more work than expected? We also did receive additional support compared to what we expected to have. Our call for help was at least partially answered.
It's now a month later after we successfully ported to Android 16 a couple weeks earlier...
GrapheneOS
in reply to GrapheneOS • • •Eskuero
in reply to GrapheneOS • • •This is the only second message I got which still said you would not be able to do it without help from a partner access.
The rest you deleted already since I just scroll all way back to june 10th and it's all gone.
Do not take this as an attack because it's far from my intention but the message on day one was worrying, what happened later was great and I'm happy about it
GrapheneOS
in reply to Eskuero • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS Mastodon
grapheneos.socialGrapheneOS
in reply to GrapheneOS • • •Eskuero
in reply to GrapheneOS • • •I didn't falsely accuse you of anything. You said on day one that the project would not be able to continue without help. I doubt I was the only one that thought the project was close to death.
I don't care about Braxman I don't know him and I haven't watched his video, don't relate me to him.
GrapheneOS
in reply to Eskuero • • •@eskuero
> I didn't falsely accuse you of anything.
You falsely accused us of lying in our thread.
> You said on day one that the project would not be able to continue without help.
We received more help than we had at the time.
> I doubt I was the only one that thought the project was close to death.
That is what happens when a state forcibly conscripts our lead developer when we already lack the resources we need, and then a port we were worried about is made much harder than expected.
GrapheneOS
in reply to GrapheneOS • • •@eskuero We never said GrapheneOS was being discontinued and or that we were going to stop working on it.
Do you realize how hard it is to have the person who did 95% of code review and 90% of the ports conscripted into a military and sent to basic training with nearly 0 contact with us for 45 days?
We desperately needed help and made that clear before Android 16 was released. We were not yet receiving enough help at that time.
Following the posts we made, we received more help and funding.
GrapheneOS
in reply to GrapheneOS • • •@eskuero It is not June 10. It is July 3. Our first production build based on Android 16 was made on June 30. Prior to that, we publicly explained how things were going in several long threads.
We made it clear we were going to be able to complete the port very shortly after June 10 after we received additional help and support.
Why is a dire situation on June 10 where we said we need help to continue being misrepresented as GrapheneOS being discontinued or struggling now, after we got help?
orestis987
in reply to GrapheneOS • • •It seems to me also that Braxman maybe is a scammer but right now you are doing what Braxman accuses your community, which means hurrahing people (@eskuero)
The content of the screenshot is undeniable that express the danger of last day. It is common sense and despite how many times you answer and deny it, it won't change.
At least be honest and admit your mistake on how you expressed it.
GrapheneOS
in reply to orestis987 • • •@orestis987 @eskuero
> If that screenshot is true then indeed this message is very worrying about the next day..
It has been altered from what was actually said by removing most of what was said.
> but right now you are doing what Braxman accuses your community, which means hurrahing people
We've done no such thing. You can choose between removing this reply with a blatant lie about us or being permanently banned. You should do it before replying to us again or we're just banning you.
GrapheneOS
in reply to GrapheneOS • • •@orestis987 @eskuero
> The content of the screenshot is undeniable that express the danger of last day.
Removing most of what was said and presenting something out of context while lying about what was said is dishonest manipulation and making false claims. Referring back to it weeks or months later while pretending it's current is even worse.
> It is common sense and despite how many times you answer and deny it, it won't change.
It is a lie which you are perpetuating.
orestis987
in reply to GrapheneOS • • •I think you are very offensive to me as well to @eskuero.
I brought it back in order to defense him since I saw that. I don't spread a lie, I didn't claim the screenshot was true, and I think neither @eskuero had an intention to accuse you.
Maybe something I got wrong about @eskuero post, and apologize.
But threating someone to recall or otherwise banned is not the way to grow your community.
In a community I think we should be equal and respect each other. Don't we?
GrapheneOS
in reply to orestis987 • • •@orestis987 We haven't said or done anything offensive to either you or @eskuero. You came here to make hostile posts towards us based on false claims about us including from Braxman. You're no longer welcome to contact us or participate in our community.
> In a community I think we should be equal and respect each other. Don't we?
It's you who is being toxic and disrespectful. You appear to have come here to concern troll. Please avoid contacting us again or participating in our community.
User
in reply to GrapheneOS • • •GrapheneOS
in reply to User • • •@userj @eskuero He isn't being sent to combat and he'll hopefully be discharged and able to work on GrapheneOS again soon. We're in active communication with him via a cellular connection. He's currently in limbo and not really tasked with any actual assignment so he has some time to help.
Corruption is very widespread in the country but that doesn't mean he can get out of it with money. There's widespread knowledge of his situation and that he's a talented security researcher and developer.
GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •User
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •@eskuero If you want to keep following us and participating in our community, then we expect you to remove the false accusation and extreme misrepresentation you made at mstdn.io/@eskuero/114824540277β¦. Is that really the hill you want to die on with us? We have no issue forgiving it if you retract it. We did not lie in our thread. Posting about how dire things were prior to June 10 and on June 10 including that we needed significantly more help to continue in no way contradicts anything we said...
Eskuero
2025-07-09 17:50:39
GrapheneOS
in reply to GrapheneOS • • •Okuna
in reply to GrapheneOS • • •Okuna
in reply to GrapheneOS • • •GrapheneOS
Unknown parent • • •GrapheneOS features overview
GrapheneOSOkuna
in reply to GrapheneOS • • •But I have to admit, that he is good presenting and selling his ideas. Like a lot of populists there are a few things correct but then mixed with lies or misinformation or populism. So I can sort of understand that people fall for him and his lies.
I am not as smart or well educated in IT Security matters, but I read a lot. I try a lot. I think I am usually very well informed. But I have never heard of BraX3 or 2 or anything like this. No one buys his phones, so he has to actβ¦ π((
SmarTekk
in reply to GrapheneOS • • •GrapheneOS
Unknown parent • • •GrapheneOS
Unknown parent • • •GrapheneOS
Unknown parent • • •orestis987
in reply to GrapheneOS • • •Hello @GrapheneOS
I am considering buying a pixel 9 and install GrapheneOS, for privacy.
I believe also that Braxman is scummer although when I watched his videos I almost get convinced. Have you considered to argument back on those accusations in order to dissolve his arguments?
For example, watching some of his videos I have the following concerns:
[to be continiued in next comment]
GrapheneOS
in reply to orestis987 • • •@orestis987
> Have you considered to argument back on those accusations in order to dissolve his arguments?
We've debunked his claims about GrapheneOS multiple times. He publishes inaccurate privacy content filled with fabrications for a living and we do not have time to go through all of his content and find all of the places he lies about GrapheneOS, let alone responding to all of it.
Many privacy and security experts have debunked his claims and exposed him as a charlatan already.
orestis987
in reply to orestis987 • • •-Why Pixel? Just because of TM2 chip? As Braxman claim, is there any chip on harware that can identify you to Google?
- Why you choose Vanadium as secure browsing? Vanadium is a chronium variant, which chronium is developed by google. Why don''t you prefer duckduckgo browser for example?
For now These are my questions, and may come up more. Nowadays internet is full of "experts" and you don't know who is telling the truth
As community I believe you should argument back with technical details!
GrapheneOS
in reply to orestis987 • • •@orestis987
> Why Pixel? Just because of TM2 chip?
They're the only devices meeting our security and update requirements. See grapheneos.org/faq#future-deviβ¦. There's a requirement for a decent secure element with the AOSP APIs, not the Titan M2.
> As Braxman claim, is there any chip on harware that can identify you to Google?
No, it's a fabrication.
> Why you choose Vanadium as secure browsing?
It's our privacy and security hardened browser project based on the most secure mainstream browser.
GrapheneOS Frequently Asked Questions
GrapheneOSGrapheneOS
in reply to GrapheneOS • • •@orestis987
> Vanadium is a chronium variant, which chronium is developed by google.
Irrelevant.
> Why don''t you prefer duckduckgo browser for example?
DuckDuckGo's Android browser app is a WebView-based browser which means it's a Chromium-based browser. However, it has crippled privacy and security compared to a proper Chromium-based browser. WebView isn't meant for a fully featured browser app including not having per-site isolation yet and being missing important privacy features.
GrapheneOS
in reply to GrapheneOS • • •@orestis987
> Nowadays internet is full of "experts" and you don't know who is telling the truth
Braxman is quite obviously a charlatan and widely exposed as such by actual experts.
> you should argument back with technical details
We provide an enormous amount of technical details. What we don't do is spend a large amount of time watching and responding to a serial fabricator attacking us every day.
If you want to participate in our community, stop peddling false attacks on GrapheneOS.