Having WiFi enabled and online map tile download enabled, scrolling to an area & zoom level which triggers a download locks the device with status message tile download ... and Loading map... in the lower left corner of the map, and nothing happening.
WebUI still responsive.
After two minutes I force powered-off the device to regain access.
Was not the case with firmware version v0.9.12: There the download worked.
**Describe the bug**
Having WiFi enabled and online map tile download enabled, scrolling to an area & zoom level which triggers a download locks the device with status message `tile download ...` and `Loading map...` in the lower left corner of the map, and nothing happening.
WebUI still responsive.
After two minutes I force powered-off the device to regain access.
Was _not_ the case with firmware version v0.9.12: There the download worked.
SD card as primary storage, because [otherwise the map itself would not display and stall the device](https://github.com/dabeani/meshcoreterm/issues/292).
**Which device are you using**
LilyGO T-Deck Plus
**Which Firmware are you using**
v0.9.12.3
Regards!
<!-- github-sync-id:4573920441 -->
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
Having WiFi enabled and online map tile download enabled, scrolling to an area & zoom level which triggers a download locks the device with status message
tile download ...andLoading map...in the lower left corner of the map, and nothing happening.WebUI still responsive.
After two minutes I force powered-off the device to regain access.
Was not the case with firmware version v0.9.12: There the download worked.
SD card as primary storage, because otherwise the map itself would not display and stall the device.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12.3
Regards!
I'm having this issue as well. Though sometimes if I long press another tab, it will unfreeze.
me to, under 0.9.12.3
Seems to be fixed in v0.9.14.