OS VERSION: 22.214.171.124
HARDWARE: Xperia 10 but probably N/A
UI LANGUAGE: PL
REGRESSION: kind of
While having alphanum password, user may lost access to device if keyboard will get broken.
nothing except the phone itself
STEPS TO REPRODUCE:
- setup alphanumeric encryption password
- break keyboard in a way that it won’t display/work at all
example, in console do:
dconf write /sailfish/text_input/active_layout '"en-missing.qml"' dconf write /sailfish/text_input/enabled_layouts '["en-missing.qml"]'
- remove fingerprint login
- reboot device
- during boot enter password using keyboard from top left corner to enter password to unlock
- once the phone will fully boot up, click keyboard in top left corner to enter password to unlock
keyboard will be shown
ok, this is just a hypothetical scenario which came to my mind just now cause my keyboard is broken but I didn’t change encryption pw to alphanum. If i would do that, I’d be locked out of my device.
Somehow on the first unlock screen, the one during boot the keyboard is showing. The second one which is available after the phone boot up fully, is not showing.
Based on this, it seems we still need some additional handling or a backup keyboard so users won’t end up in this situation when the first keyboard during boot is fine and the second after fully but is broken.