Hello,
I encounter an issue using GrapheneOS on my Pixel 6. I added a secondary keyboard, HeliBoard, and it currently have an issue where it would crash at startup. That's fine, I didn't disabled the AOSP keyboard for this kind of case. However, AOSP keyboard doesn't show up either. I tried multiple things :
Starting in normal mode :
- Unlocking the phone, Heliboard doesn't show up, nor does AOSP keyoard. I tried to switch the input keyboard, but it blink really fast and I'm not able to switch the keyboard. I filmed it on slow mode, and confirmed that the AOSP keyboard was in the available choices.
- Tried to click on the blinking window, but didn't manage to select the AOSP keyboard on time despite trying a lot of times.
- Going into "Emergency" then user info, I get the box saying Heliboard crashed. I can only see it's informations (which does nothing except asking me to unlock) or kill the app. Even after killing it, the AOSP keyboard doesn't show up and the switch keyboard window keep blinking.
- Attach a physical keyboard, however, my USB C port is in charge only before unlock, and bluetooth in disabled so it didn't worked well.
After searching a lot through this forum, I find a solution using Safe Mode, so I rebooted using it. I do not have the message about Heliboard this time, however, AOSP keyboard doesn't show up either. I can't change keyboard either, it does nothing.
I then stumbled upon this issue on github : https://github.com/GrapheneOS/os-issue-tracker/issues/4662
From my understanding, it seems to be an OS bug specifically in case of alphanumeric password, which is my case.
Question is : given the fact that it's open since 5 months, and reproduced by a member of GrapheneOS, can I hope for it to be fixed soon ? Do I have any other solution than to factory reset ?
To be honest, I'd rather not reset. But if it's really my only choice or wait for I don't know how many time, I'll probably do it. My last backup is a month ago, I'll loose things, but it could be worse.