No keyboard on lockscreen on Pixel 9 Pro with Fossify Keyboard

Tl4W4rEtsV7HsB81Or8U

JollyRancher I wonder if rebooting into safe mode would force the grapheneos keyboard to be used in that case

JollyRancher

Something for someone to try, but I'm kinda tired of bricking and resetting my phone and have just actually started installing my apps. So that can be a test someone else runs.

I've just decided that my Owner profile will only have the default Keyboard enabled and any others that I install will be disabled for that profile.

DeletedUser5

DeletedUser370 Right. Then I remembered that wrong :(

JollyRancher

So despite Fossify Keyboard claiming that the latest release fixed this issue, it didn't.
https://github.com/FossifyOrg/Keyboard/releases/tag/1.1.0

On the plus side, Rebooting in safe mode will let you get around the issue.
Press power until the Power Off/ Restart/ Lockdown option comes up and then tap and hold the Power Off option until a box asking if you want to reboot to safe mode pops up. Go to Settings -> Apps navigate to Keyboard, disable it, restart your phone.

DeletedUser87

JollyRancher just out of curiosity: why does it have to be the Fossify keyboard? I find most of their apps to be pretty lackluster (I use the calendar from them, which is better than Etar) and I often find the alternatives offer a way better experience. I think you should check out HeliBoard or FUTO keyboard. And while I can't confirm that those will not also run you into the same issue, I find them more mature in almost every way possible.

JollyRancher

DeletedUser87

It doesn't. I just happen to (generally) like it. Then I ran into the issue and it got me curious. Currently I use HeliBoard on my owner profile.

I updated this thread because I saw that Fossify updated the Keyboard and (supposedly) fixed this exact issue. Except it turns out that they didn't.

Fossify Keyboard as your active Keyboard on Owner plus Password Unlock means that upon reboot you won't be able to use your phone at all until you boot in safe mode, log in, and disable the Fossify Keyboard.

r_dac

I'm also curious what permits one keyboard to work BFU while another does not.

On my Pixel 7, I have AOSP keyboard disabled, and instead use Florisboard and BlackBerry keyboard. I have BlackBerry set to default.

BlackBerry keyboard doesn't appear on BFU, but fortunately Florisboard does, so I have no issues unlocking the phone after boot.

Ammako

r_dac https://developer.android.com/privacy-and-security/direct-boot

Note that if a keyboard doesn't support direct boot, you get an additional warning when enabling it that "After a reboot, this app can't start until you unlock your phone", which would be your cue not to rely on that keyboard for password unlock. In OP's case though, the keyboard in question does support direct boot, but it has a bug that causes it to crash and be unusable. There's no way to really warn or prepare for that.

de0u

r_dac I'm also curious what permits one keyboard to work BFU while another does not.

It must declare and correctly implement support for Direct Boot, which includes storing critical resources in a different area which is available before the device is unlocked. It is not rocket science but it is extra code.

DeletedUser87

JollyRancher Heliboard is great and I'm glad you found a good replacement. Regarding Fossify: I don't have anything against the developer, but when you have to support such a big suite of apps, it's almost guaranteed that there will be bugs and pretty devastating ones, too! Not to mention that the update frequency suffers as well, there's often months between releases which sometimes forces you to wait for a crucial fix forever. This is why I generally prefer projects who don't want to do everything at once, but rather focus on one or two things.

Edit: I just read your Github comment:
"I can't belive this has been fixed, but not deployed for so long given how annoying this is. I'd help with the build, but in all honesty I'll just go back to my old keyboard anyway."

I think you and I both hit the nail on the head here.

JollyRancher

DeletedUser87

I didn't make a GitHub comment. I probably should considering that the currently released version, that nominally fixes this issue, doesn't actually fix said issue.

DeletedUser87

JollyRancher wait, that wasn't you? This keeps getting better and better :D
Crazy, that someone else went through the same experience and they still don't fix anything. I think that really speaks for the quality of the software.

« Previous Page