0.9.12 Key / event lagging on T-Deck #186

Closed
opened 2026-10-27 15:42:55 +01:00 by adam · 17 comments
Owner

Describe the bug
Significant hardware key lag in 0.9.12 (after 0.9.11)

Which device are you using
LilyGO T-Deck

Which Firmware are you using
0.9.12

To Reproduce
Steps to reproduce the behavior:

  1. Go to room
  2. Try typing message
  3. Note that after the first key press there is significant lag in event processing

Additional context
Sorry this report is sparse. Admittedly I would try a clean / -merged install to see if the issue is still reproduced. I will update this bug report as time allows; however, T-Deck users may want to be aware of this issue.

**Describe the bug** Significant hardware key lag in 0.9.12 (after 0.9.11) **Which device are you using** LilyGO T-Deck **Which Firmware are you using** 0.9.12 **To Reproduce** Steps to reproduce the behavior: 1. Go to room 2. Try typing message 3. Note that after the first key press there is significant lag in event processing **Additional context** Sorry this report is sparse. Admittedly I would try a clean / -merged install to see if the issue is still reproduced. I will update this bug report as time allows; however, T-Deck users may want to be aware of this issue. <!-- github-sync-id:4297366091 -->
adam closed this issue 2026-10-27 15:42:55 +01:00
Author
Owner

Thank you very much, had to redesign the message stream for the webui and it could be that there are issues remaining. Tested some scenarios, but roomserver stuff is not really used by me, but, let me know and i will try my best to fix (if its not a general issue).

Thank you very much, had to redesign the message stream for the webui and it could be that there are issues remaining. Tested some scenarios, but roomserver stuff is not really used by me, but, let me know and i will try my best to fix (if its not a general issue). <!-- github-comment-id:4283185707 -->
Author
Owner

Hi. Same issue here. Lag making the device unusable with the keyboard. Issue with typing messages, changing device name, etc. Screen keyboard is working fine.

I've erased flash and flashed - merged file twice and issue still present.

Hi. Same issue here. Lag making the device unusable with the keyboard. Issue with typing messages, changing device name, etc. Screen keyboard is working fine. I've erased flash and flashed - merged file twice and issue still present. <!-- github-comment-id:4283711665 -->
Author
Owner

same here also sending messages that i know ive typed but only half the words

same here also sending messages that i know ive typed but only half the words <!-- github-comment-id:4283755486 -->
Author
Owner

I also had a long lag when I was composing a message to a public channel, the on screen symbolic keyboard was on, and I pressed "OK". It took so long that I actually thought of rebooting, but after several tens of seconds it finally did it's job.

I also had a long lag when I was composing a message to a public channel, the on screen symbolic keyboard was on, and I pressed "OK". It took so long that I actually thought of rebooting, but after several tens of seconds it finally did it's job. <!-- github-comment-id:4291584131 -->
Author
Owner

Yeah, something is VERY broken with the keyboard processing in the latest release. I'm trying to give this a go on my T-Deck but I can't even setup the radio settings. Pressing backspace might delete the previous char, it might not? Repeatedly pressing it eventually it will show up, but it's actually, unuseable.

This is a complete blocker to using the OS on the latest version. Based on this bug alone I can't use 0.9.12, and I really like the look and feel of this OS.

0.9.11 works just fine.

T Deck Plus

Yeah, something is VERY broken with the keyboard processing in the latest release. I'm trying to give this a go on my T-Deck but I can't even setup the radio settings. Pressing backspace might delete the previous char, it might not? Repeatedly pressing it eventually it will show up, but it's actually, unuseable. This is a complete blocker to using the OS on the latest version. Based on this bug alone I can't use 0.9.12, and I *really* like the look and feel of this OS. 0.9.11 works just fine. T Deck Plus <!-- github-comment-id:4312473829 -->
Author
Owner

Let me know if you have this issue with or without SDCard inserted!

Let me know if you have this issue with or without SDCard inserted! <!-- github-comment-id:4312836309 -->
Author
Owner

Let me know if you have this issue with or without SDCard inserted!

I had the card in today. Will try tomorrow without it.

> Let me know if you have this issue with or without SDCard inserted! I had the card in today. Will try tomorrow without it. <!-- github-comment-id:4312967043 -->
Author
Owner

another information would be good, in Mgmt / Messages -> "Save Msgs for" what value is entered on the right side?

another information would be good, in Mgmt / Messages -> "Save Msgs for" what value is entered on the right side? <!-- github-comment-id:4314398478 -->
Author
Owner

i had the lagging only once (but several tens of seconds then), at the
beginning of using v0.9.12. Maybe it took time to set stuff up on SD
card? If so, a busy message explaining "doing SD card IO" would be
helpful, for stuff that cannot be done in background.

i had the lagging only once (but several tens of seconds then), at the beginning of using v0.9.12. Maybe it took time to set stuff up on SD card? If so, a busy message explaining "doing SD card IO" would be helpful, for stuff that cannot be done in background. <!-- github-comment-id:4314830035 -->
Author
Owner

another information would be good, in Mgmt / Messages -> "Save Msgs
for" what value is entered on the right side?

Just for your information: I now have 365 days.

Can it be infinite?

> another information would be good, in Mgmt / Messages -> "Save Msgs > for" what value is entered on the right side? Just for your information: I now have 365 days. Can it be infinite? <!-- github-comment-id:4314833549 -->
Author
Owner

T-Deck Plus, 4GB SD card.

Have just flashed my device from 0.9.11 to 0.9.12 without an SD card inserted and the same behaviour is present.

It may be a touch less laggy, but it's still not really useable.

Save Msgs for is set to 3 days.

This is a fresh flash. I did not "Eraze Flash" before I flashed the device.

=====

I then did a fresh flash of 0.9.12 with "Eraze Flash" via the MC flasher, and the device got stuck in a constant reboot loop. Still no SD card inserted.

Reverted to 0.9.11 and still the same behaviour. Constant reboot loop.

===

The only way I got the device to come back was to flash Ripple with a clean "Eraze Flash".

===

After it booted on ripple, I flashed 0.9.12 with no "Eraze Flash" and no SD card inserted still and got stuck on the "Loading..." screen. I assume it got stuck because it couldn't access the SD card. Just sits there and hangs.

Inserting the SD card the device and it booted, keyboard still basically unuseable. Multiple presses to get it to register a char.

===

The SD card still had some data on it from previous attempts of other firmwares - I assumed this would be OK as it would be in a different directory, it also had all my map tiles on it. I erazed all the data on the SD card and tried again.

After clearing the SD card still no change. 0.9.12 the keyboard is unuseable at all.

===

Just to test, I removed the SD card, formatted it (fat32) and again tried a fresh flash with "Eraze Flash" and 0.9.12, no sd card inserted, same reboot loop. No change after inserting the SD card.

The only way to get the device to behave was to flash with Ripple and then flash with your firmware 0.9.11. I could not get the device to boot after an "Eraze flash" with any of your firmware variants, and nothing I did made the keyboard useable on 0.9.12

Over to you.

T-Deck Plus, 4GB SD card. Have just flashed my device from 0.9.11 to 0.9.12 without an SD card inserted and the same behaviour is present. It may be a *touch* less laggy, but it's still not really useable. Save Msgs for is set to 3 days. This is a fresh flash. I did not "Eraze Flash" before I flashed the device. ===== I then did a fresh flash of 0.9.12 with "Eraze Flash" via the MC flasher, and the device got stuck in a constant reboot loop. Still no SD card inserted. Reverted to 0.9.11 and still the same behaviour. Constant reboot loop. === The only way I got the device to come back was to flash Ripple with a clean "Eraze Flash". === After it booted on ripple, I flashed 0.9.12 with no "Eraze Flash" and no SD card inserted still and got stuck on the "Loading..." screen. I assume it got stuck because it couldn't access the SD card. Just sits there and hangs. Inserting the SD card the device and it booted, keyboard still basically unuseable. Multiple presses to get it to register a char. === The SD card still had some data on it from previous attempts of other firmwares - I assumed this would be OK as it would be in a different directory, it also had all my map tiles on it. I erazed all the data on the SD card and tried again. After clearing the SD card still no change. 0.9.12 the keyboard is unuseable at all. === Just to test, I removed the SD card, formatted it (fat32) and again tried a fresh flash with "Eraze Flash" and 0.9.12, no sd card inserted, same reboot loop. No change after inserting the SD card. The only way to get the device to behave was to flash with Ripple and then flash with your firmware 0.9.11. I could not get the device to boot after an "Eraze flash" with any of your firmware variants, and nothing I did made the keyboard useable on 0.9.12 Over to you. <!-- github-comment-id:4317230602 -->
Author
Owner

Any further update on this at all?

Any further update on this at all? <!-- github-comment-id:4334149634 -->
Author
Owner

I will update you as soon as i found the issue for this. Still, i try my best to improve and fix issues 🤗.

I will update you as soon as i found the issue for this. Still, i try my best to improve and fix issues 🤗. <!-- github-comment-id:4338180060 -->
Author
Owner

anyone of you who would like to test this before i start to release it, surprisingly on my device it was working already before - but seems like there are different HW versions in the wild of the TDeck...?

(hopefully) fixed in v0.9.12.1:

  • T-Deck Plus keyboard: keep the hardware keyboard in byte-stream mode while draining input, using only idle-time modifier sampling for Alt+S and global Alt+L lock/unlock, restoring responsive backspace/text entry (after 0.9.12 introduced key/event lag) (#186).
anyone of you who would like to test this before i start to release it, surprisingly on my device it was working already before - but seems like there are different HW versions in the wild of the TDeck...? (hopefully) fixed in v0.9.12.1: - T-Deck Plus keyboard: keep the hardware keyboard in byte-stream mode while draining input, using only idle-time modifier sampling for `Alt+S` and global `Alt+L` lock/unlock, restoring responsive backspace/text entry (after 0.9.12 introduced key/event lag) (#186). <!-- github-comment-id:4339138490 -->
Author
Owner

For me it was while trying to configure the radio, basically unuseable.

I'll see if I can find the release and flash it and give you some feedback.

Edit: Where do I find 0.9.12.1 ?

For me it was while trying to configure the radio, basically unuseable. I'll see if I can find the release and flash it and give you some feedback. Edit: Where do I find 0.9.12.1 ? <!-- github-comment-id:4340673361 -->
Author
Owner

Write me a mail, then i will send it to you 👍.

Write me a mail, then i will send it to you 👍. <!-- github-comment-id:4350003048 -->
Author
Owner

Tested. Issue resolved for me in 0.9.12.1. Nice work!

Tested. Issue resolved for me in 0.9.12.1. Nice work! <!-- github-comment-id:4560789078 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#186