#GrapheneOS Important Statement
One of our two senior developers has been forcibly detained and conscripted to participate in a war. When they first went missing, we revoked their repository access as a precaution. We soon learned their disappearance was completely unrelated to GrapheneOS. Our priority has been keeping them safe.
We've used our available connections to try to keep them safe. There's no way to get them out of the conscription. However, they're an incredibly talented security researcher and engineer and it would be extraordinarily misguided to send them to front line combat. This seems to be understood now.
GrapheneOS development and updates have continued and will keep going. We have substantial funds available to hire multiple experienced developers. We'll need to hire multiple experienced developers to fill their big shoes. They'll hopefully be safe and when they return we'll have a bigger team.
If you're an experienced AOSP developer interested in working full time on GrapheneOS in a fully remote position, see the hiring page at:
We can pay people anywhere in the world via BTC, XMR, ETH or Wise (local bank transfers). We need people who can hit the ground running due to the current situation.
Our near term focus is going to heavily shift to Android 16 porting, maintenance and continuing to do better patching than standard Android 15 QPR2. An OEM providing us early access to Android 16 sources would help a lot and we wouldn't need to slow down new feature development nearly as much.
Replies (45)
You mean your lead developer works for the Israeli military? Great news to stop using GrapheneOS, though it would’ve been better if you had warned us about that earlier.
Which country?
Heavy.
Final
#GrapheneOS Important Statement
One of our two senior developers has been forcibly detained and conscripted to participate in a war. When they first went missing, we revoked their repository access as a precaution. We soon learned their disappearance was completely unrelated to GrapheneOS. Our priority has been keeping them safe.
We've used our available connections to try to keep them safe. There's no way to get them out of the conscription. However, they're an incredibly talented security researcher and engineer and it would be extraordinarily misguided to send them to front line combat. This seems to be understood now.
GrapheneOS development and updates have continued and will keep going. We have substantial funds available to hire multiple experienced developers. We'll need to hire multiple experienced developers to fill their big shoes. They'll hopefully be safe and when they return we'll have a bigger team.
If you're an experienced AOSP developer interested in working full time on GrapheneOS in a fully remote position, see the hiring page at:
We can pay people anywhere in the world via BTC, XMR, ETH or Wise (local bank transfers). We need people who can hit the ground running due to the current situation.
Our near term focus is going to heavily shift to Android 16 porting, maintenance and continuing to do better patching than standard Android 15 QPR2. An OEM providing us early access to Android 16 sources would help a lot and we wouldn't need to slow down new feature development nearly as much.
The whole world is full of War, it could be any country
👀
Fuck War
Guck Gov
Final
#GrapheneOS Important Statement
One of our two senior developers has been forcibly detained and conscripted to participate in a war. When they first went missing, we revoked their repository access as a precaution. We soon learned their disappearance was completely unrelated to GrapheneOS. Our priority has been keeping them safe.
We've used our available connections to try to keep them safe. There's no way to get them out of the conscription. However, they're an incredibly talented security researcher and engineer and it would be extraordinarily misguided to send them to front line combat. This seems to be understood now.
GrapheneOS development and updates have continued and will keep going. We have substantial funds available to hire multiple experienced developers. We'll need to hire multiple experienced developers to fill their big shoes. They'll hopefully be safe and when they return we'll have a bigger team.
If you're an experienced AOSP developer interested in working full time on GrapheneOS in a fully remote position, see the hiring page at:
We can pay people anywhere in the world via BTC, XMR, ETH or Wise (local bank transfers). We need people who can hit the ground running due to the current situation.
Our near term focus is going to heavily shift to Android 16 porting, maintenance and continuing to do better patching than standard Android 15 QPR2. An OEM providing us early access to Android 16 sources would help a lot and we wouldn't need to slow down new feature development nearly as much.
Which war? There are so many.
War conscription in 2025... Wow.
Final
#GrapheneOS Important Statement
One of our two senior developers has been forcibly detained and conscripted to participate in a war. When they first went missing, we revoked their repository access as a precaution. We soon learned their disappearance was completely unrelated to GrapheneOS. Our priority has been keeping them safe.
We've used our available connections to try to keep them safe. There's no way to get them out of the conscription. However, they're an incredibly talented security researcher and engineer and it would be extraordinarily misguided to send them to front line combat. This seems to be understood now.
GrapheneOS development and updates have continued and will keep going. We have substantial funds available to hire multiple experienced developers. We'll need to hire multiple experienced developers to fill their big shoes. They'll hopefully be safe and when they return we'll have a bigger team.
If you're an experienced AOSP developer interested in working full time on GrapheneOS in a fully remote position, see the hiring page at:
We can pay people anywhere in the world via BTC, XMR, ETH or Wise (local bank transfers). We need people who can hit the ground running due to the current situation.
Our near term focus is going to heavily shift to Android 16 porting, maintenance and continuing to do better patching than standard Android 15 QPR2. An OEM providing us early access to Android 16 sources would help a lot and we wouldn't need to slow down new feature development nearly as much.
Astuteness is good. Nice reading comprehension.
It means exactly that.
What is your action plan now based on that? Do you feel the fact that they revoked his access is not enough?
Mossad is in GOS, potentially.
The developer isn't Israeli, we don't have developers there, and it doesn't involve any armed conflict in the Middle East.
Not Israel? Well, that’s a bit better then 🤔 In that case, I hope the steps taken are enough.
They aren't Israeli.
any country = Israel or Ukraine
Great. Thanks for the clarification. Would have been better if you worded the post better as to avoid confusion.
Which army?
do we know where is he from?
what are they? israeli doesn't exist. just evil settlers and colonizers exist in occupied Palestine
Well, basically that could explain why I the last two weeks I have been experiencing incredibly frustrating issues with my phone and kernel crashing a bunch.
It's nothing to do with Palestine or the Gaza War and is completely unrelated.
We're avoiding directly mentioning the country or the war since we don't want to be pushed into others' political debate about military conscriptions.
You agree with the idea?
how a senior development got conscripted into war? how strange , what was happening ?
this is remote work 80h per month or more..i never been porting grapheneOS..
Which idea? That there might be a conflict of interest if lead devs are politicised? It's only logical to assume this stance.
Please just stop this unprofessional blaming. GrapheneOS is an opensource project. When there is something to blame, show the commit, which is fraudulent.
In a opensource project it does not matter, who is involved. It only matters what commits are accepted and which ones not.
The developer was conscripted due to where he was born and located.
What is about it? They have been kicked out due to legal advice and so what?
It is also written, that with non-russian email adresses, they can still contribut to the kernel.
So Linux also is still open for contributors from everywhere. Since it is no KYC process in place to propose a change in the code.
Definitely Ukraine
brutal....
fvck wars and fvck the states who wage them
Sounds russia to me.
If he were from Russia, his access would’ve been restricted back in 2022.
That doesn't make any sense, sorry. A developer is working on code that's not on your phone and their absence won't just cause random bugs out of the blue.
Some support guys ⚡️ thanks
I’ve had over 1000000 online attacks from China and Russia due to them protecting their government infrastructure in Trinidad
Shut up
Really? It couldn't happen if gos is compromised? As some are suggesting here. Don't hacked phones and devices act buggy when hacked and compromised?
all the *B*est 2 all /*****
GrapheneOS devs can't access your devices and each update is signed off by multiple parties working for GrapheneOS. They even removed all his access once they noticed his absence. If any code had been pushed by someone else in his name, they would've known already and disclosed as much.
If you're having issues, check the forums or see if there's a pending update you haven't installed yet. If nothing else helps, check reset options in system settings (take a backup beforehand!) - you can just reset networking or some app preferences instead of doing a full factory reset.
If people are expressing concerns I am going to wonder too. Thanks for clsrifying. Hopefully all of that is so.
I was told by GOS at some point updates happen automatically and there is nothing for me to install.
That's true, but what I wrote applies to these updates as well. Hope I could bring Sinne clarity!
GrapheneOS isn't compromised, the developer never had access to the signing infrastructure to push his own updates or code without peer review.
Hacked devices also don't need to be buggy. A hack showing signs of change or compromise to the user is a pretty terrible hack and is something an attacker would avoid. Most people targeted under an attack wouldn't even know it happens until it's too late.
If you're having issues with buggy components, or crashes, I recommend sending them to one of our support channels or emailing logs at GrapheneOS dot org. Users often don't report them directly to us despite us having open alpha/beta testing periods.
Praying for his safe return 🙏
Context at:
Final
#GrapheneOS Important Statement
One of our two senior developers has been forcibly detained and conscripted to participate in a war. When they first went missing, we revoked their repository access as a precaution. We soon learned their disappearance was completely unrelated to GrapheneOS. Our priority has been keeping them safe.
We've used our available connections to try to keep them safe. There's no way to get them out of the conscription. However, they're an incredibly talented security researcher and engineer and it would be extraordinarily misguided to send them to front line combat. This seems to be understood now.
GrapheneOS development and updates have continued and will keep going. We have substantial funds available to hire multiple experienced developers. We'll need to hire multiple experienced developers to fill their big shoes. They'll hopefully be safe and when they return we'll have a bigger team.
If you're an experienced AOSP developer interested in working full time on GrapheneOS in a fully remote position, see the hiring page at:
We can pay people anywhere in the world via BTC, XMR, ETH or Wise (local bank transfers). We need people who can hit the ground running due to the current situation.
Our near term focus is going to heavily shift to Android 16 porting, maintenance and continuing to do better patching than standard Android 15 QPR2. An OEM providing us early access to Android 16 sources would help a lot and we wouldn't need to slow down new feature development nearly as much.
