emergency contacts

gungadin

Although It shaows my details, it does not list any contacts. Tried adding them a few times.

de0u

gungadin I just got around to doing this a couple of days ago, and it seems to work for me.

To view emergency contacts from the lock screen, I swipe up, press the "Emergency" button, then tap twice on the "Emergency Information" area. I added contacts but not medical details.

intelligence

Another, potentially better option, is to use the "add text on lock screen" setting. "If found, call Phil at 555-123-1234", or "any attempt to tamper with this device will trigger self destruct"

gungadin

even if I delete the medical info, it still does not add contacts. (you can add them, looks OK, but on restarting, info is lost)

de0u

gungadin This is exciting! I restarted my phone and indeed the emergency information that was previously present is now gone. I think you have found a bug. The next step is to try it on vanilla AOSP to see if it happens there. I don't have a spare device or an AOSP build handy at the moment. Hopefully somebody else can check?

de0u

gungadin Ok, more detail.

If I enter emergency contacts, restart my phone, enter my PIN, tap the power button to go back to the lock screen, then swipe up and press Emergency Info, the contacts are there.
But if I restart my phone, do NOT enter my PIN, swipe up, and press Emergency Info, it's gone. And it's gone permanently. Presumably the information can't be displayed because it's still encrypted (this is unfortunate), but that doesn't explain why failing to display it deletes it forever.

Is that what you're seeing? If so, the next step is to try it on vanilla AOSP to see if it happens there. I don't have a spare device or an AOSP build handy at the moment. Hopefully somebody else can check?

gungadin

de0u Glad I'm not alone.. I've no idea about AOSP, or how to report it as a bug.. Maybe someone else can do that? If it is three, I think it should work. Thanks for confirming it is not just me...

Nordwest

de0u Hi, I can confirm this behaviour for Pixel 6. If you open emergency contacts before unlocking the phone after restart, the emergency contacts are gone.

But that not a grapheneos bug. I found this bug years ago at my old Nokia 6.1 (2018) with Android 10, and can reproduce the bug although today. I thought, the bug has been fixed long ago, but obviously it's not.

de0u

Nordwest Thanks for the confirmation. I guess the next step would be seeing if an AOSP bug has already been filed.

de0u

de0u I guess the next step would be seeing if an AOSP bug has already been filed.

Android issue #110814301 appears to be exactly this problem. It appears that Google closed it as "Won't Fix (Obsolete)", without indicating why. That disposition suggests re-opening the bug if it's still happening (which it clearly still is). Based on the history of that issue, it seems as if submitting a video would help -- but that video would need to be based on a current vanilla AOSP build, not on GrapheneOS.

Another approach would be just fixing it and sending the fix to Google.

If anybody is filing a GrapheneOS issue (which I am not particularly suggesting), please be sure to link to the AOSP bug page and arguably to this thread.

treequell

gungadin I am not exactly clear how bug reporting works with AOSP. Happy for somebody to correct me on this.

My understanding is that users like us can't report bugs to Google.

https://developers.google.com/issue-tracker

In any case, as de0u points out, there is a bug report for this issue already. So there's no need to submit a new one.

I don't know why it's marked as obsolete, but my guess is that it's because the SOS features on stock Android are not the same as in AOSP. If recall correctly there are some additional features in stock Android. It could be that the SOS features in AOSP are not properly maintained by Google, in a similar way that Google does not maintain AOSP Keyboard properly (it has many bugs and the codebase is rotting) in favour of just focusing on GBoard.

As far as I know, the only thing you can do is submit a bug report to GrapheneOS and they can pass it upstream if they think it's appropriate. But I wouldn't hold much hope of this issue getting resolved any time soon.

If anybody has a more optimistic perspective, I'm happy to hear!

de0u

treequell In any case, as de0u points out, there is a bug report for this issue already. So there's no need to submit a new one.

If you have a Google account, you can "star" the issue. In theory if a huge number of people did that they might reconsider.

treequell As far as I know, the only thing you can do is submit a bug report to GrapheneOS and they can pass it upstream if they think it's appropriate. But I wouldn't hold much hope of this issue getting resolved any time soon.

If anybody has a more optimistic perspective, I'm happy to hear!

Interestingly, the "Show text on lock screen" feature works fine before the first unlock. So maybe the issue is just that Settings is storing the emergency-contact information the wrong way. It might be a simple fix.