USSD Shortcuts not capturing on-screen numpad input in secondary profiles

[tsaoi]

As title says, the USSD shortcut window doesn't seem to focus the USSD numpad into the correct input section, rather it focuses on the Phone dialler input area (apologise for any terminology errors, I'm not a dev).

When entering

*#100# SEND

into stock Phone dialler keypad, the Carrier USSD shortcuts are displayed on-screen shown below.

Then I click on the entry input line (blue line shown above) and the on-screen numpad keyboard appears, displaying numbers. When entering anything via this keyboard, I see the Phone dialler keypad entry line captures the input - not the USSD input line on-screen.

When clicking CANCEL, it drops back to the Phone Dialler screen and my responses are sitting there. I note also the USSD numpad remains on the screen even after hitting CANCEL and I need to hit the "checkmark" to then exit back to the phone dialler numpad.

Therefore there is no ability to enter anything and hit "SEND" to return the USSD response.

I understand there can be workaround for USSD, but for those who don't know the commands to pre-fill

(e.g. *#100*2# to check balance)

this could be a problem.

Seems to be a keyboard focus issue?

[flawedworld]

Is this still an issue?

[tsaoi]

Yes, running latest stable SQ1A.220105.002.2022011423 and the keyboard still doesn't focus on the text input line for sending commands.

[flawedworld]

Please check if this is still an issue on the 2022042000 release

[tsaoi]

@flawedworld tested on 2022042000 and USSD works in the Owner Profile (the qwerty keyboard is shown and numbers are accepted into the USSD text input) however secondary profiles presents the 'dialpad' which still doesn't focus on the USSD section. I'm not sure how to change this dialpad view back to a normal keyboard.. using stock GrapheneOS keyboard US format.

[flawedworld]

So it's only broken in secondary profiles, not the Owner profile now?

[tsaoi]

Can confirm not working on Secondary Profile only. Owner profile working.

[thestinger]

Let us know if this is still an issue on Android 13.

[tsaoi]

Yes, this is still an issue on the Secondary Profile Android 13 (TP1A.220624.014.2022083000) There are still 2 x overlapping keypads (not keyboard as expected), but neither registers any entered responses into the text input line. Note: switching back to the Primary Profile then displays error messages from the attempted USSD MMI Code input, stating "Connection problem or invalid MMI code."

The Primary Profile USSD commands work correctly. The keyboard input is displayed and entries focus on the input line correctly.

Image of Secondary overlapping numpads below: