-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unlock with no pin set doesn't let you interact with the screen #142
Comments
The same problem happens on the rM2. The tarnish log is filled with this message
The full resume log is:
|
It's safe to ignore this error: ddvk/remarkable2-framebuffer#37 |
Hi, sorry, how does one set a PIN after having already gone through setup? (I am also having the "can't interact with the screen after unlock" problem on 2.1.2, at least I think it's 2.1.2, the packages.zip file still contains packages numbered 2.1.1 but I figured that was a mistake) I tried just running |
systemctl stop tarnish
rm /home/root/.config/Eeems/decay.conf
systemctl start tarnish Thanks for alerting me about forgetting to update the version number on v2.1.2, I'll get a new build with the updated version number ASAP. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should unlock properly
Version Information:
Additional Information
You can work around this by using the left button hold action.
The text was updated successfully, but these errors were encountered: