When in Mgmt → Global I have Primary Disk set to Internal, when I then go to Map, the device barely reacts and is barely usable at all (usually have to reboot to be able to get out of the Map screen), and no map tiles are displayed, only the grid which usually is displayed when there are no tiles. The nodes are also displayed.
When I switch Primary Disk to SD Card, then Map works fine.
**Describe the bug**
This seems somewhat inverse to #273:
When in `Mgmt` → `Global` I have `Primary Disk` set to `Internal`, when I then go to `Map`, the device barely reacts and is barely usable at all (usually have to reboot to be able to get out of the `Map` screen), and no map tiles are displayed, only the grid which usually is displayed when there are no tiles. The nodes are also displayed.
When I switch `Primary Disk` to `SD Card`, then `Map` works fine.
**Which device are you using**
LilyGO T-Deck Plus
**Which Firmware are you using**
v0.9.12.3
Regards!
---
*Duplicate: #309.*
<!-- github-sync-id:4574126988 -->
Reproduction confirmed on LilyGo T-Deck Plus, v0.9.12.3, Primary Disk = Internal
Adding some additional diagnostic findings that may help isolate the cause:
Symptoms:
Map tab hangs on entry; navigation to other tabs (Contacts, Messages, Mgmt) is severely sluggish or unresponsive
No tile background rendered — only the grid and node markers
Requires reboot to recover
Isolation tests:
Local Tiles OFF, Network Tiles OFF → map is blank but UI is fully responsive; tab switching is instant
Local Tiles OFF, Network Tiles ON → map renders from network; UI is fully responsive
Local Tiles ON, Network Tiles OFF → severe freeze; device barely usable
Local Tiles ON, Network Tiles ON → partial improvement vs. local-only, but still noticeably sluggish
This pattern suggests the SD card tile reads are blocking the UI thread synchronously, while network tile fetches use an async path that doesn't block. The freeze severity scales with how many tiles the map tries to load on entry.
Confirmed not the cause:
SD card is FAT32, 32GB
Tile structure is correct: z/x/y.png at SD root /tiles/
Primary Disk is set to Internal in Mgmt → Global
Tested with SD card confirmed writable (key file save to SD succeeded)
Workaround: Setting Primary Disk → SD Card resolves it (as noted by others above), but is undesirable for users who want settings in internal NVS with tiles on SD.
**Reproduction confirmed on LilyGo T-Deck Plus, v0.9.12.3, Primary Disk = Internal**
Adding some additional diagnostic findings that may help isolate the cause:
**Symptoms:**
- Map tab hangs on entry; navigation to other tabs (Contacts, Messages, Mgmt) is severely sluggish or unresponsive
- No tile background rendered — only the grid and node markers
- Requires reboot to recover
**Isolation tests:**
- **Local Tiles OFF, Network Tiles OFF** → map is blank but UI is fully responsive; tab switching is instant
- **Local Tiles OFF, Network Tiles ON** → map renders from network; UI is fully responsive
- **Local Tiles ON, Network Tiles OFF** → severe freeze; device barely usable
- **Local Tiles ON, Network Tiles ON** → partial improvement vs. local-only, but still noticeably sluggish
This pattern suggests the SD card tile reads are blocking the UI thread synchronously, while network tile fetches use an async path that doesn't block. The freeze severity scales with how many tiles the map tries to load on entry.
**Confirmed not the cause:**
- SD card is FAT32, 32GB
- Tile structure is correct: `z/x/y.png` at SD root `/tiles/`
- Primary Disk is set to Internal in Mgmt → Global
- Tested with SD card confirmed writable (key file save to SD succeeded)
**Workaround:** Setting Primary Disk → SD Card resolves it (as noted by others above), but is undesirable for users who want settings in internal NVS with tiles on SD.
<!-- github-comment-id:4748270870 -->
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
This seems somewhat inverse to #273:
When in
Mgmt→GlobalI havePrimary Diskset toInternal, when I then go toMap, the device barely reacts and is barely usable at all (usually have to reboot to be able to get out of theMapscreen), and no map tiles are displayed, only the grid which usually is displayed when there are no tiles. The nodes are also displayed.When I switch
Primary DisktoSD Card, thenMapworks fine.Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12.3
Regards!
Duplicate: #309.
Reproduction confirmed on LilyGo T-Deck Plus, v0.9.12.3, Primary Disk = Internal
Adding some additional diagnostic findings that may help isolate the cause:
Symptoms:
Isolation tests:
This pattern suggests the SD card tile reads are blocking the UI thread synchronously, while network tile fetches use an async path that doesn't block. The freeze severity scales with how many tiles the map tries to load on entry.
Confirmed not the cause:
z/x/y.pngat SD root/tiles/Workaround: Setting Primary Disk → SD Card resolves it (as noted by others above), but is undesirable for users who want settings in internal NVS with tiles on SD.