#614 fixed the issue in, I think, Beta 2. I noticed Beta 4 is out recently, the last intended one before full release, so we should test the fix there and then again on the stable release once it’s out.
Users of the last release have reported two issues with dialler integration on Android 17, and we’ll want to make sure both are fixed (if possible). The one is the issue I think was fixed in #614, which is that users get a “Dialler integration not available on your OS” message.
The other issue is that icons for things like muting or enabling speakerphone, etc. are missing when starting a call from the Phone app. I don’t know if there’s anything we can do about that or if that might have been fixed with the other work. Anyway, we’ll want to check to see if this behaves better in the pre-release and whether we can do anything else to make it better.
A user provided this note:
Re: the dialer bug where buttons don’t appear, it seems to be reproducible by going to the dialer → dialing or pasting a number → calling → selecting Cheogram. In my case it’s a phone contact. If I go to the contacts tab of the dialer app, and choose the contact, then opt to call from there, the voicemail/numpad/etc buttons appear. I haven’t checked from the contacts app yet
#614 is still fixed in the latest .1 release afaict.
I only somewhat reproduced the other issues in a non-owner account on GrapheneOS/Android 17 on a Pixel 6. GrapheneOS seems to intentionally prevent non-owner accounts from ever getting to the “Enable calling accounts” screen, which is required for dialler integration. I didn’t flash an old release or build an old release to run in an emulator, so I’m not sure whether this behaviour is new. If GrapheneOS used to allow calling account management from a non-owner account, it makes sense to me that enabling it while it works, then a newer release disabling something in there could result in weird behaviour in the dialler app, but I didn’t actually reproduce so I’m not actually sure. Either way, I think it’s pretty safe to say we don’t expect dialler integration to work from non-owner accounts and it’s out of our control; if someone is having this issue with Cheogram Android installed to a non-owner account, see whether moving it to the owner account resolves it.
If this issue is occurring when Cheogram Android is installed to the owner account, I guess I need more info about their particular setup because mine works just fine with both latest stable release and latest commit on main.