GrapheneOS version 2024053100 released

cdflasdkesalkjfkdfkjsdajfd With all users, and it's one for all, yes.

To make this clear to everyone:

Duress PIN/Password will work anywhere where the device credentials are requested. NOT JUST THE LOCKSCREEN.

Anywhere in the OS where the PIN/password is requested (enabling developer options, a PIN prompt to unlock an app, confirming your PIN to change the device's password, anywhere) can trigger the duress PIN.

The only exception is the SIM PIN prompt, since that's a different PIN, but we will likely extend it to that screen too, to try and avoid any confusion.

mmmm the release is in the alpha channel now, so to get the update you have to first change the release channel at Settings > System > System update > Release channel

Thankyou GOS team for this is a great update

other8026 ahhh right understood. Thanks! I'll wait then I think, everything is working well with my install and I dont want to jepodise that. I'll wait until its released into beta.

Amazing. Thank you Devs, another huge feature added.

https://grapheneos.org/donate

If you execute the duress feature, does it basically fully reset the phone back to a graphene os flash.....but also wiping the esim?

Or is it more than this ?

matchboxbananasynergy are esims wiped or only phone data? Or maybe this is configurable?

cdflasdkesalkjfkdfkjsdajfd Duress wipe also wipes eSIM, this is explained in the description of the feature when you go to set it up.

cdflasdkesalkjfkdfkjsdajfd As far as I'm aware, there are no such plans. If you're in a situation where you want to trigger a duress wipe like that, why would you want the eSIM to stay?

If you are not in a duress situation and want to wipe, just factory reset instead.

matchboxbananasynergy Sim and esim are pin protected. I use Sim and esim. Duress app is killing esim but not firing the Sim, no? What's the difference

cdflasdkesalkjfkdfkjsdajfd The difference is we can wipe the eSIM. What can the OS do for the physical SIM? Not much.

mmmm You could file a feature request with Google and ask them to produce hardware that supports the OS being able to cause the device to immediately explode. 😜

fid02 😂

GrapheneOS I'm very excited for the duress feature! What do you think about putting a little label with the duress PIN on the inside of the phone case in case some nosey person thinks they can just access ones phone?

I also read that Google is planning a Theft Detection Feature for later this year: "Theft Detection Lock is coming later this year and helps you keep your personal and financial data safe if your phone is ever snatched from you. This powerful new feature uses Google AI to sense if someone snatches your phone from your hand and tries to run, bike or drive away with it. If a theft motion is detected, it will be quickly locked down to keep your information out of the wrong hands."
Do you think it will find its way into GrapheneOS? It uses Google AI, so I'm not sure how this would work. I've been using Private Lock for some time, but it hasn't been updated for quite some time.

Clueless I'm very excited for the duress feature! What do you think about putting a little label with the duress PIN on the inside of the phone case in case some nosey person thinks they can just access ones phone?

Someone actually brought this up in our chat rooms, and I think it's a fantastic use of the feature. A phone snatcher is more likely to want to wipe the phone and sell it, which you as the owner kinda have to accept, but if they try to sign in to see if they can find anything that'll help them making more profit, there are two ways to combat the scenario:

1. The duress PIN could be a PIN that someone trying random common PINs would try. It could be a birth year that seems to be around your actual age (the thief might start guessing how old you were based on when they saw you and might trip the feature in this way), or something really common like "1234" or similar.

2. Is what you mentioned. A small sheet of paper in the phone case that contains a few dummy passwords for non-existent accounts (to add legitimacy to what's about to follow) and another entry which you can name "phone PIN" or just "PIN" if you don't want to make it too obvious. That PIN would of course be the duress PIN, which would wipe the device and any eSIMs you have, so that they can no longer try accessing any of the data on it.

Clueless I also read that Google is planning a Theft Detection Feature for later this year: "Theft Detection Lock is coming later this year and helps you keep your personal and financial data safe if your phone is ever snatched from you. This powerful new feature uses Google AI to sense if someone snatches your phone from your hand and tries to run, bike or drive away with it. If a theft motion is detected, it will be quickly locked down to keep your information out of the wrong hands."

This will be part of sandboxed Google Play. I don't imagine it'll be able to work without privileges, but it's not 100% certain. Maybe it does. There is an open issue on our tracker to implement something similar. It's something that we might look into in the future.