Can't access the device after setting an invalid PIN
Describe the bug Can't access the device after setting an invalid PIN
To Reproduce Steps to reproduce the behavior:
- Open a terminal (SSH is recommended, as you will lose access to oxide without it)
- Run xdg-settings set pin 'abcd' (abcd is just an example, it can be everything that isn't a 4 digits number)
- Put it in stand-by and resume it
- Every pin will be wrong
Expected behavior It should skip the lockscreen and - possibly - show an error
Version Information:
- Device: reMarkable 2
- OS: 2.15.1.1189
- Version: 2.6
This is both a feature and a bug. I don't limit what a pin can be set to, because you could replace the lockscreen with something else that supports a different length value, or alphanumerics. The bug here is that the default lockscreen should just recognize an invalid pin and treat it the same as no pin, with a warning notification.
For anybody who has encountered this, you can follow the instructions here to reset your pin: https://oxide.eeems.codes/faq.html#how-do-i-change-my-pin-after-i-ve-set-it