Describe the bug
Keyboard input issues in v0.9.12: Typing is laggy and only registers characters sporadically (every few seconds). This issue is not present in v0.9.11, where everything worked fine.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
0.9.12
To Reproduce
Everywhere with Keyboard inputs.
Additional context
nothing
**Describe the bug**
Keyboard input issues in v0.9.12: Typing is laggy and only registers characters sporadically (every few seconds). This issue is not present in v0.9.11, where everything worked fine.
**Which device are you using**
LilyGO T-Deck Plus
**Which Firmware are you using**
0.9.12
**To Reproduce**
Everywhere with Keyboard inputs.
**Additional context**
nothing
<!-- github-sync-id:4324640836 -->
Hmm maybe... in Messages the first Keystroke will appear direktly and then only every few seconds again. but in other fields in the settings like name etc. the problem is directly present.
Hmm maybe... in Messages the first Keystroke will appear direktly and then only every few seconds again. but in other fields in the settings like name etc. the problem is directly present.
<!-- github-comment-id:4318535185 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
Keyboard input issues in v0.9.12: Typing is laggy and only registers characters sporadically (every few seconds). This issue is not present in v0.9.11, where everything worked fine.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
0.9.12
To Reproduce
Everywhere with Keyboard inputs.
Additional context
nothing
Is this a duplicate of #186, or another issue?
Hmm maybe... in Messages the first Keystroke will appear direktly and then only every few seconds again. but in other fields in the settings like name etc. the problem is directly present.
this is the same issue as #186 and should be fixed in v0.9.12.1!
If this has been fixed, then please close this, @thelizard84 or @dabeani.
Issue is fixed