Collected issues for firmware version 0.9.11. #147

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

Ahoj,

this is a collection of issues I see with firmware version 0.9.11 on LilyGo T-Deck Plus:

Newly discovered issues:

  • Map: Tapping on a repeater does open the popup with repeater name, time since last heard and distance only in zoom levels 1..10 and zoom levels 12..13.
    ISSUE: In zoom level 11, and from zoom level 14 onwards that does not open.
    (When I now purged almost all contacts, it also works in zoom levels 11 and 14+.)

  • Map: According to release notes:

    MAP marker double-tap behavior: double-tapping the same ByteID marker opens that contact directly in Contact Detail.

    That works really unreliably for me. Too fast tapping is not recognised, too slow of course also not, it is difficult to find the correct tapping speed.
    Suggestion: No double tapping at all. Single tap opens the info box as it currently does, and tapping into the info box opens the details. This actually is also what I would expect from a user interface.

  • Room/ repeater login issue: After flashing 0.9.11, I could log in to a room server, and post there. Then I could log in to my repeater (zero-hop) as admin. I went to the CLI, issued one command, got a response. Further commands did not get any response anymore. From this point on, I also could not re-login to that repeater or any room server. Even over a reboot, I still cannot log in to the repeater or any room server that worked previously.

    • Addendum, one day later: Need to investigate further: Could now "login" to a room to at least see the messages.
    • Can not not reproduce anymore (log in now works again), so I remove the issue from the list.
  • Mgmt → Contacts → AutoAdd Max Hops: The value shown in the overview screen is one less than the value input via the Edit button. This is confusing, and unclear which actually is the true value.

  • Mgmt -> WiFi: When entering a password before entering an SSID, password in the overview is shown as "(not set)", although it is saved: When entering the SSID, the previously entered password appears as set.

  • Keyboard backlight stays on even after timeout when switched on via <alt>+<b>

  • Scan for nearby repeaters: According to release notes:

    Mgmt → Advert → Scan Neighbor Repeaters now shows an Add button only for repeaters not yet in Contacts, and tapping a repeater row opens Contact Detail instead of adding on name/row tap.

    For repeaters which were discovered via the "scan" feature, only the 1-byte prefix of the hash is known (no full advert is sent via this functionality). In firmware version 0.9.10, those repeaters could be added with an "Add" button. Now they cannot. It is not clear weather they cannot because there is at least one repeater with the same prefix already in the contacts list or not; when I tap a so-discovered repeater it only says "no key" and not a more verbose message like "repeater(s) with that prefix already in contact list: [list of multiple repeaters with that prefix]".

Issues already observed in version 0.9.10 or older versions:

For completeness: Issues I experienced in version 0.9.10 (or older) which I was not yet able to test:

Regards!

Ahoj, this is a collection of issues I see with firmware version 0.9.11 on LilyGo T-Deck Plus: #### Newly discovered issues: * <del>Map: Tapping on a repeater does open the popup with repeater name, time since last heard and distance only in zoom levels 1..10 and zoom levels 12..13.</del> <del>ISSUE: In zoom level 11, and from zoom level 14 onwards that does _not_ open.</del> *(When I now purged almost all contacts, it also works in zoom levels 11 and 14+.)* * Map: According to [release notes](https://github.com/dabeani/meshcore/releases/tag/v0.9.11): > *MAP marker double-tap behavior: double-tapping the same ByteID marker opens that contact directly in Contact Detail.* That works really unreliably for me. Too fast tapping is not recognised, too slow of course also not, it is difficult to find the correct tapping speed. Suggestion: No double tapping at all. Single tap opens the info box as it currently does, and tapping _into the info box_ opens the details. This actually is also what I would expect from a user interface. * <del>Room/ repeater login issue: After flashing 0.9.11, I could log in to a room server, and post there. Then I could log in to my repeater (zero-hop) as admin. I went to the CLI, issued one command, got a response. Further commands did not get any response anymore. From this point on, I also could not re-login to that repeater or any room server. Even over a reboot, I still cannot log in to the repeater or any room server that worked previously.</del> - Addendum, one day later: Need to investigate further: Could now "login" to a room to at least _see_ the messages. - ***Can not not reproduce anymore (log in now works again), so I remove the issue from the list.*** * `Mgmt` → `Contacts` → `AutoAdd Max Hops`: The value shown in the overview screen is one less than the value input via the `Edit` button. This is confusing, and unclear which actually is the true value. * `Mgmt` -> `WiFi`: When entering a password before entering an SSID, password in the overview is shown as "`(not set)`", although it is saved: When entering the SSID, the previously entered password appears as set. * [Keyboard backlight stays on even after timeout when switched on via `<alt>`+`<b>`](https://github.com/dabeani/meshcore/issues/111#issuecomment-4112624936) * Scan for nearby repeaters: According to [release notes](https://github.com/dabeani/meshcore/releases/tag/v0.9.11): > *`Mgmt` → `Advert` → `Scan Neighbor Repeaters` now shows an Add button only for repeaters not yet in Contacts, and tapping a repeater row opens Contact Detail instead of adding on name/row tap.* For repeaters which were discovered via the "scan" feature, only the 1-byte prefix of the hash is known (no full advert is sent via this functionality). In firmware version 0.9.10, those repeaters could be added with an "Add" button. Now they cannot. It is not clear weather they cannot because there is at least one repeater with the same prefix already in the contacts list or not; when I tap a so-discovered repeater it only says "*no key*" and not a more verbose message like "*repeater(s) with that prefix already in contact list: \[list of multiple repeaters with that prefix\]*". #### Issues already observed in version 0.9.10 or older versions: * Map: As in firmware version 0.9.10, after a reboot all nodes still get a green-ish colour. According to [this description](https://github.com/dabeani/meshcore/issues/71#issuecomment-3840370131), green means 0 hop, but definitely not all the repeaters have zero hop. [Here is the original report for firmware 0.9.10](https://github.com/dabeani/meshcore/issues/71#issuecomment-3977517112), except for that in 0.9.11 now instead of the squares the first byte of the ID is shown, the colours are the same. * Map: As in firmware version 0.9.10, I still have on the map one repeater coloured in Purple, Magenta or Pink/Magenta (I cannot say which colour it is exactly), but I have a 0-hop login to it and in the "Contacts" screen when I tap on ot to see the details it says `Route: Direct`. According to [this description](https://github.com/dabeani/meshcore/issues/71#issuecomment-3840370131), it should be coloured in green. [Here is the original report for firmware version 0.9.10](https://github.com/dabeani/meshcore/issues/71#issuecomment-3973776870). * Room and channel messages are still [not saved over a reboot](https://github.com/dabeani/meshcore/issues/61). * Text input: [Still cannot input characters not on the T-Deck's hardware keyboard. An optional on-screen keyboard that can be opened on request would be really helpful](https://github.com/dabeani/meshcore/issues/84). * [In messages screen, at the top: Channels within their boxes which would be partly visible are not rendered at all; they abruptly appear as soon as they would fit fully on the screen. At the bottom they just "normally" scroll out of screen; and in the "Contacts" screen they normally scroll at the top as well](https://github.com/dabeani/meshcore/issues/137#issuecomment-4114401108). * "[Received messages are not save after reboot](https://github.com/dabeani/meshcore/issues/61)". * "[Contacts list looses almost all last heard timestamps, then they reappear and for few contacts they are wrongly displayed (but correctly sorted).](https://github.com/dabeani/meshcore/issues/141)". * "[Some usernames are not rendered correctly: Just as `<-->`, and then "username: " followed behind in the normal text view.](https://github.com/dabeani/meshcore/issues/131)". #### For completeness: Issues I experienced in version 0.9.10 (or older) which I was not yet able to test: * "[Tapping the screen on the "Contacts" tab makes some contact transiently changing their colour.](https://github.com/dabeani/meshcore/issues/102)", * <del>[\[T-Deck\] Sent messages do not synchronise between Companion app and T-Deck." (sub-issue doubled messages with 63 hops)](https://github.com/dabeani/meshcore/issues/98#issuecomment-4016387912),</del> *seems to be fixed*, * [not all settings are saved to SD card](https://github.com/dabeani/meshcore/issues/22#issuecomment-3936726562), * if [room server messages can be copied to clipboard now](https://github.com/dabeani/meshcore/issues/104#issuecomment-3941404828). Regards! <!-- github-sync-id:4123183767 -->
adam closed this issue 2026-10-27 15:41:04 +01:00
Author
Owner

Newly discovered issues:

If you prefer that I open an individual issue report for each new issue, @dabeani, please tell and I will do so and close this "collected issues" thread instead.

Regards!

> #### *Newly discovered issues:* If you prefer that I open an individual issue report for each new issue, @dabeani, please tell and I will do so and close this "collected issues" thread instead. Regards! <!-- github-comment-id:4133655293 -->
Author
Owner
  • Room/ repeater login issue: After flashing 0.9.11, I could log in to a room server, and post there. Then I could log in to my repeater (zero-hop) as admin. I went to the CLI, issued one command, got a response. Further commands did not get any response anymore. From this point on, I also could not re-login to that repeater or any room server. Even over a reboot, I still cannot log in to the repeater or any room server that worked previously.

Can not reproduce this issue anymore (log in now works again), so I treat it as a non-issue now.

> * *<del>Room/ repeater login issue: After flashing 0.9.11, I could log in to a room server, and post there. Then I could log in to my repeater (zero-hop) as admin. I went to the CLI, issued one command, got a response. Further commands did not get any response anymore. From this point on, I also could not re-login to that repeater or any room server. Even over a reboot, I still cannot log in to the repeater or any room server that worked previously.</del>* Can not reproduce this issue anymore (log in now works again), so I treat it as a non-issue now. <!-- github-comment-id:4136885515 -->
Author
Owner
  • Map: Tapping on a repeater does open the popup with repeater name, time since last heard and distance only in zoom levels 1..10 and zoom levels 12..13.
    ISSUE: In zoom level 11, and from zoom level 14 onwards that does not open.

When I purged almost all contacts this now does work also in zoom levels 11 and 14+.

> * Map: Tapping on a repeater does open the popup with repeater name, time since last heard and distance only in zoom levels 1..10 and zoom levels 12..13. > ISSUE: In zoom level 11, and from zoom level 14 onwards that does _not_ open. When I purged almost all contacts this now does work also in zoom levels 11 and 14+. <!-- github-comment-id:4235088285 -->
Author
Owner

I did split out the "Newly discovered issues" into individuals reports (#167, #168, #169, #170, #171) and so closing this "collected issues" thread.

I did split out the "Newly discovered issues" into individuals reports (#167, #168, #169, #170, #171) and so closing this "collected issues" thread. <!-- github-comment-id:4235211495 -->
Author
Owner

For completeness: Issues I experienced in version 0.9.10 (or older) which I was not yet able to test:

This one seems to be fixed.

> #### *For completeness: Issues I experienced in version 0.9.10 (or older) which I was not yet able to test:* > > * *\[&hellip;\]* > * *[[T-Deck] Sent messages do not synchronise between Companion app and T-Deck." (sub-issue doubled messages with 63 hops)](https://github.com/dabeani/meshcore/issues/98#issuecomment-4016387912),* > * *\[&hellip;\]* This one seems to be fixed. <!-- github-comment-id:4245039390 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#147