weird characters returned losing all my contacts #155

Closed
opened 2026-10-27 15:41:24 +01:00 by adam · 7 comments
Owner

Describe the bug
Using the app ok this morning switched it on this afternoon all the contacts have become unusable being replaced with weird characters and weird buttons on the right side? ive rebooted the app multiple times but looks like a full re install again.

Which device are you using
LilyGO T-Deck Plus

Which Firmware are you using

0.9.11
To Reproduce

Steps to reproduce the behavior:
its like this from switch on and has done this same thing 4 times before now got photos

Additional context
Not the first time this has happened maybe the dev could give us an insight as to why this keeps happeneing

Image
Image
Image

**Describe the bug** Using the app ok this morning switched it on this afternoon all the contacts have become unusable being replaced with weird characters and weird buttons on the right side? ive rebooted the app multiple times but looks like a full re install again. **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** 0.9.11 **To Reproduce** Steps to reproduce the behavior: its like this from switch on and has done this same thing 4 times before now got photos **Additional context** Not the first time this has happened maybe the dev could give us an insight as to why this keeps happeneing ![Image](https://github.com/user-attachments/assets/58efb733-6f14-4db1-b3f2-7d49b9637249) ![Image](https://github.com/user-attachments/assets/681a37f1-9fbb-4cd5-b9d2-447957c7735b) ![Image](https://github.com/user-attachments/assets/813a8cc5-f60a-4d01-af53-7ec5fffefe99) <!-- github-sync-id:4153687883 -->
adam closed this issue 2026-10-27 15:41:25 +01:00
Author
Owner

Uah, thats weird. Will have a look i to it. Thank you for the informations.

Uah, thats weird. Will have a look i to it. Thank you for the informations. <!-- github-comment-id:4147514197 -->
Author
Owner

Uah, thats weird. Will have a look i to it. Thank you for the informations.

Indeed it is, and did report this before but had no photos to back up my claim!

looking forward to the next release as there seems to be quite a few bugs reported by people

> Uah, thats weird. Will have a look i to it. Thank you for the informations. Indeed it is, and did report this before but had no photos to back up my claim! looking forward to the next release as there seems to be quite a few bugs reported by people <!-- github-comment-id:4147974160 -->
Author
Owner

left the t deck a few days reset it with a fresh install of 0.9.11 and within 6 hours and 40 favourited contacts they all went corrupt again! exactly the same as in the pictures. so have fully reset the application again and my switch on auto add of repeaters only without favouriting ? just trying different things but find it super weird

left the t deck a few days reset it with a fresh install of 0.9.11 and within 6 hours and 40 favourited contacts they all went corrupt again! exactly the same as in the pictures. so have fully reset the application again and my switch on auto add of repeaters only without favouriting ? just trying different things but find it super weird <!-- github-comment-id:4156277506 -->
Author
Owner

Improved in v0.9.12

  • GUI: contacts could become garbled/corrupted after malformed contact updates or persisted non-terminated names
    • Contact update command parsing now enforces the full minimum frame length before decoding, rejecting truncated payloads instead of ingesting garbage bytes
    • Contact names loaded from frames and storage are now explicitly null-terminated to prevent string overrun into adjacent contact fields
    • Discovered-contact cache updates now use bounded copy for names, preventing overflow that could corrupt contact row state and right-side badges/actions
    • Persisted contact route lengths are sanitized on load so invalid values no longer destabilize contact rendering/state
Improved in v0.9.12 - **GUI: contacts could become garbled/corrupted after malformed contact updates or persisted non-terminated names** - Contact update command parsing now enforces the full minimum frame length before decoding, rejecting truncated payloads instead of ingesting garbage bytes - Contact names loaded from frames and storage are now explicitly null-terminated to prevent string overrun into adjacent contact fields - Discovered-contact cache updates now use bounded copy for names, preventing overflow that could corrupt contact row state and right-side badges/actions - Persisted contact route lengths are sanitized on load so invalid values no longer destabilize contact rendering/state <!-- github-comment-id:4185372048 -->
Author
Owner

Improved in v0.9.12

* **GUI: contacts could become garbled/corrupted after malformed contact updates or persisted non-terminated names**
  
  * Contact update command parsing now enforces the full minimum frame length before decoding, rejecting truncated payloads instead of ingesting garbage bytes
  * Contact names loaded from frames and storage are now explicitly null-terminated to prevent string overrun into adjacent contact fields
  * Discovered-contact cache updates now use bounded copy for names, preventing overflow that could corrupt contact row state and right-side badges/actions
  * Persisted contact route lengths are sanitized on load so invalid values no longer destabilize contact rendering/state

Thank you for the uipdate and look forward to the next update

> Improved in v0.9.12 > > * **GUI: contacts could become garbled/corrupted after malformed contact updates or persisted non-terminated names** > > * Contact update command parsing now enforces the full minimum frame length before decoding, rejecting truncated payloads instead of ingesting garbage bytes > * Contact names loaded from frames and storage are now explicitly null-terminated to prevent string overrun into adjacent contact fields > * Discovered-contact cache updates now use bounded copy for names, preventing overflow that could corrupt contact row state and right-side badges/actions > * Persisted contact route lengths are sanitized on load so invalid values no longer destabilize contact rendering/state Thank you for the uipdate and look forward to the next update <!-- github-comment-id:4185388399 -->
Author
Owner

Can #141 be related?

Can #141 be related? <!-- github-comment-id:4209052266 -->
Author
Owner

And what actually does the TEL badge mean?, when is it supposed to make sense?

And what actually does the `TEL` badge mean?, when is it supposed to make sense? <!-- github-comment-id:4294663187 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#155