adam/meshcore
1
0 Fork 0
mirror of https://github.com/dabeani/meshcoreterm.git synced 2026-10-31 10:11:57 +01:00
Code Issues 97 Packages Projects Releases Wiki Activity

Long uptime issue?: Random device UI freezes for 1..2 seconds. #236

New Issue
Closed
opened 2026-10-27 15:45:15 +01:00 by adam · 6 comments
adam commented 2026-10-27 15:45:15 +01:00
Owner
Copy link
Copy source

Describe the bug

I sometimes -- and it seems with v0.9.11 and v0.9.12 it increased -- observe transient device freezes which last 1..2 seconds.

Best observable when the "frequency busy" inticator is lit and stays lit for ~2 seconds or so.

EDIT: Also observable that the device is just not responding to touches. It happens increasingly mostly after I have sent a (direct?) message, and randomly regardless of what I do.

ADDENDUM: After a reboot thinks worked quick again. I had an uptime of more than 14 days. So it could be related with something going rogue the longer the uptime is?

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using

v0.9.12

Regards!

**Describe the bug** I sometimes -- and it seems with v0.9.11 and v0.9.12 it increased -- observe transient device freezes which last 1..2 seconds. Best observable when the "frequency busy" inticator is lit and stays lit for ~2 seconds or so. EDIT: Also observable that the device is just not responding to touches. It happens increasingly mostly after I have sent a (direct?) message, and randomly regardless of what I do. [ADDENDUM](https://github.com/dabeani/meshcoreterm/issues/236#issuecomment-4430616614): After a reboot thinks worked quick again. I had an uptime of more than 14 days. So it could be related with something going rogue the longer the uptime is? **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** v0.9.12 Regards! <!-- github-sync-id:4351140925 -->
adam closed this issue 2026-10-27 15:45:15 +01:00
adam commented 2026-10-27 15:45:16 +01:00
Author
Owner
Copy link
Copy source

Addendum: I currently especially have it when dealing with DMs:

  • When opening DM chat,
  • when opening details of a DM,
  • after sending a DM.

Very annoying, since sometimes I even have to wait for ~5 seconds until the device reacts again on touchscreen taps.

Addendum: I currently _especially_ have it when dealing with DMs: * When opening DM chat, * when opening details of a DM, * after sending a DM. Very annoying, since sometimes I even have to wait for ~5 seconds until the device reacts again on touchscreen taps. <!-- github-comment-id:4355518442 -->
adam commented 2026-10-27 15:45:17 +01:00
Author
Owner
Copy link
Copy source

Seems to get worse the more DMs I have.

Seems not to be the case with channel messages.

Seems to get worse the more DMs I have. Seems _not_ to be the case with channel messages. <!-- github-comment-id:4356095779 -->
adam commented 2026-10-27 15:45:17 +01:00
Author
Owner
Copy link
Copy source

Seems to get worse the more DMs I have.

Seems not to be the case with channel messages.

And now it slowly starts in channel message view as well. Much less prominent than DMs, though, although there are far more channel messages.

> Seems to get worse the more DMs I have. > > Seems _not_ to be the case with channel messages. And now it _slowly_ starts in channel message view as well. Much less prominent than DMs, though, although there are far more channel messages. <!-- github-comment-id:4366432023 -->
adam commented 2026-10-27 15:45:18 +01:00
Author
Owner
Copy link
Copy source

Does in case of those freezes the internal "Companion" firmware continue to run and can receive messages, send ACKs, and so on?, or is on those freezes the internal companion firmware also frozen?

Does in case of those freezes the internal "Companion" firmware continue to run and can receive messages, send ACKs, and so on?, or is on those freezes the internal companion firmware also frozen? <!-- github-comment-id:4421463833 -->
adam commented 2026-10-27 15:45:19 +01:00
Author
Owner
Copy link
Copy source

After a reboot thinks worked quick again. I had an uptime of more than 14 days. So it could be related with something going rogue the longer the uptime is?

After a reboot thinks worked quick again. I had an uptime of more than 14 days. So it could be related with something going rogue the longer the uptime is? <!-- github-comment-id:4430616614 -->
adam commented 2026-10-27 15:45:19 +01:00
Author
Owner
Copy link
Copy source

Closing for now, since it might have been resolved in v0.9.12.3.

Closing for now, since it might have been resolved in v0.9.12.3. <!-- github-comment-id:4604423317 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#236