graphenediscoverer4
Will try this setup to check whether the unknown caller can see what names I put in the emergency list
My idea was that you only save one contact in Emergency Contacts, namely the one the stranger wants to call. Then he can only see this one contact.
I came up with another idea that might solve your problem with far fewer steps (although unfortunately I can't test this myself as I don't use a SIM card - so please try it yourself):
- Get the number of the stranger
- dial the prefix + number yourself
- lock the screen by pressing the power button
- give the phone to the stranger
- I believe (but don't know exactly) that you can still press buttons on the dialer during the call (mute, loudspeaker, hang up -please also check whether you can access Home, Back, and App Overview via gestures or 3-button navigation while call is in progress - that would be counterproductive ), but the display is locked at the end of the call.
However I don't understand :
- meaning of "AFU" please ?
In BFU (before first unlock) state, the device's storage is encrypted and the user's data is not yet accessible whereas in AFU (after first unlock) decryption keys remain in memory, allowing seamless access to user data.
BFU offers a higher level of security because it ensures that the data remains encrypted and inaccessible until the user explicitly unlocks it.
The following links probably provide more and much better and accurate information about AFU, BFU and encryption:
https://grapheneos.org/faq#encryption
https://discuss.grapheneos.org/d/10108-pixel-afu-vs-bfu-security
https://discuss.grapheneos.org/d/10462-what-information-can-forensic-tools-recover-from-an-afu-gos-phone
However I don't understand :
...
- the nuance when adding the extra step of logging in a burner profile, if daily profile is locked anyway when accessing emergency dialer
You can set the data of a specific user profile to rest, e.g. via Hold Power Button> End session (does not work with the Owner Profile, only with secondary profiles) - then they are in the particularly secure BFU state mentioned above.
My suggestion with guest profile (or another secondary profile - that also would work) is aimed at the fact that you can set the particularly sensitive data of your daily driver to BFU via "End session" - that would add an additional layer of protection to your data. The call of the stranger happens all inside the guest profile.
I can't answer whether your threat level is worth this extra effort - you'll have to decide for yourself.