GrapheneOS
Calling Accounts reverting
Calling Account Make Calls With preference in the Dialer is not sticking after a reboot. The setting reverts to default SIM.
I'm running GrapheneOS on a 5a but from what I have been hearing, the issue is not unique to my model.
This issue was reported a couple of years ago and looks like it was resolved, but seemingly came back. https://github.com/GrapheneOS/os-issue-tracker/issues/622
From what I'm told, this should be the patch needed: https://android-review.googlesource.com/c/platform/frameworks/opt/telephony/+/2022115
+1 for this. Useful VoIP phone apps like Cheogram (which connects to the jmp.chat service) integrate with the system dialer. Setting up a permanent calling account makes it so you make calls over the internet and avoid using the SIM card. This adds privacy as calls using VoIP bridge out to the cellular network from one origin, instead of the tower closest to you.
Because of a bug in AOSP, these calling accounts get reset with every reboot. This can cause a user to make a call using the default calling account / sim card, which could ruin an attempt at keeping separate calling identities using GrapheneOS.
I know myself and the XMPP / Cheogram / JMP chat community would be very grateful if this bug could be fixed. I would say there are more than a hundred users that are using GrapheneOS + Cheogram / JMP. This would be an important fix!
Thank you.
+1 This has been a pain since I started using Cheogram on my Android last year. After every reboot, I often forget I have to re-fix this setting because of 'the bug'.
Perhaps has something to do with:
- https://github.com/GrapheneOS/platform_packages_services_Telephony/blob/d27bef55e3bc81449df7cb08d1470018861314fa/src/com/android/phone/settings/PhoneAccountSettingsFragment.java#L202-L212
- https://github.com/GrapheneOS-Archive/platform_packages_services_Telecomm/blob/1032b7f7fd9a73dfb1062e69ed2dd43d8c089cc8/src/com/android/server/telecom/TelecomServiceImpl.java#L117-L148
I would like to see this resolved. Especially if you are privacy focused, primarily use a VOIP account, if you reboot your phone your first call will auto go over the SIM card in the device.
+1
I'd be curious what others are doing to work around this ... removing Cheogram from caller accounts and just using the clumsy Cheogram interface? Unfortunately "ask me first" won't persist either.
Reports from most users have been that this is resolved as of Android 14
GrapheneOS has had Android 14 in the stable channel since October 10th and is based on Android 14 QPR1 now. Are people still having the issue? It's possible they fixed it in an APEX mainline update. APEX mainline releases have more changes than what's included in AOSP monthly/quarterly releases, unfortunately. We aren't currently building and shipping the APEX mainline updates since it would be quite a complex mess (Google Play system updates is the branding for their builds).
We probably will start shipping the APEX mainline updates but we have no timeline for it. It's going to be a real pain to deal with dozens of modules, each with their own AOSP tags, where we need to have our changes applied for building them. They also aren't designed to be built into the OS so you have to ship them out-of-band. The initial OS boot has the AOSP OS variant of the APEXes rather than the mainline ones, and the same thing applies after factory reset. It would be so much cleaner if they included all the changes in monthly updates, or at least quarterly ones.
@singpolyma @thestinger Whoa. I just tested this again this morning and it does indeed seem to be working as desired. I believe it was not working as recently as a few days ago. Perhaps a recent GOS change fixed it? This is huge! (Once issue #2871 is resolved on the Cheogram side).
I'm on 2023121200. I set "Make calls with" to a Cheogram calling account and restarted my device. The "Make calls with" has reverted to my device's eSIM.
Not fixed.
Whoa. I just tested this again this morning and it does indeed seem to be working as desired. I believe it was not working as recently as a few days ago. Perhaps a recent GOS change fixed it? This is huge! (Once issue #2871 is resolved on the Cheogram side).
virtuousvector How did you test? 1) Android phone app -> set "ask every time" -> it works 2) reboot phone 3) see that it is set to SIM rather than "ask every time"
@dm17 That's different than setting it to something specific. Does it remember if you set it to another option?
@dm17 That's different than setting it to something specific. Does it remember if you set it to another option?
I haven't tried that but I will some time - I just have no use for one or the other; just both ("ask every time"). Thanks.
@dm17 That's different than setting it to something specific. Does it remember if you set it to another option?
Ahhh. Now, I set it to a specific calling account, closed the dialer app, and rebooted my device. It still says "Make calls with" the specific account.
So it sounds like the reset only happens with "Ask every time." Can you confirm @dm17 ?
Edit:
Wait... but... I tested the same thing earlier this morning if I didn't lie in my own post. Hmm.
I just tried with the specific non-SIM calling account as well. For me both "ask every time" and selecting the specific calling account: both reset on reboot. The SIM account is always selected after a reboot.
I've never not had to go in and re-select it in the ~4 years of using GrapheneOS.
I only have two calling accounts right now, one physical SIM and one Cheogram account. (Wondering out loud if the quantity and type of calling accounts plays a role. I know that would be weird.)
Here is what I just did:
- Change calling account from "ask" to cheogram.
- Restart
- Calling account has reverted to SIM.
- Change calling account from SIM to "ask."
- Restart
- Calling account has reverted to SIM.
- Change calling account to Cheogram.
- Restart
- Calling account has persisted on Cheogram.
(And I also did this a few more times but saw the same pattern).
Here's a weird thought ... Something DEFINITELY changed for me recently. And the other relevant thing I changed recently was disabling my original SIM card, experimenting with a new ESIM, then disabling the ESIM and re-enabling the original SIM. But my Cheogram account -- established AFTER the original SIM -- stayed on the whole time. Is it possible that the only time it will persist on a non-SIM calling account is when there is a non-SIM account that has been continuously connected for longer? Let's call it tenure? Will it only persist a non-SIM option if that option has a longer tenure than any active SIMs?
Confirming it still reverts for me as well, regardless of whether I default any of my calling accounts or set it to Ask First. The only time it did not revert for me is when I had two SIM (physical and eSIM) simultaneously, then it stuck on Ask First. I assume maybe the privileged eSIM was able to override it or something but I honestly have no idea.
EDIT: In case it's helpful, I have an eSIM currently and 3 Cheogram calling accounts. No physical SIM.
I still am having this issue. Is there any possibility of adding in this patch?
https://android-review.googlesource.com/c/platform/frameworks/opt/telephony/+/2022115
For me "Make Calls With" consistently reverts back to the SIM when I toggle my SIM with "Turn off" then "Turn On" under Network & Internet, SIMs. This happens regardless if "Make Calls With" is set to my Cheogram account or "Ask First"
This seems to have been fixed in a recent update. "Ask First" has stuck over the last several reboots for me.
Just to make sure it's actually finished – @thestinger did you close this because of anecdotal account or can we trace a specific commit that fixed?
It's closed because it's confirmed to be fixed by the person who opened it in the first place.
@rbreslow We do not know which commits fix upstream bugs in general unless we had to find it backport it, or cases we fixed it ourselves and then the upstream change comes along and conflicts. It's not a reasonable thing for us to find. This also isn't an Android issue tracker and Android issues which impact more than GrapheneOS should be filed in the Android issue tracker instead. We assumed this was a Dialer app issue rather than a core OS issue but that assumption may have been wrong and it appears that it somehow got fixed via OS changes. The reason we kept this issue open is because the stock Pixel OS doesn't use the Dialer app so we can't expect it to be handled upstream. If this bug happened on the stock Pixel OS, It could have been closed as soon as we got that confirmation, because we do are not trying to fix all Android issues.
Got it, thanks for that context.
I will report back if I encounter the calling account being reset on my end.