search

meshtastic / firmware

Meshtastic device firmware
https://meshtastic.org
GNU General Public License v3.0
3.49k stars 863 forks source link

[Bug]: T-Watch S3 is looping after Wifi enabled #4981

Open 369Martin369 opened 3 weeks ago

369Martin369 commented 3 weeks ago

Category

WiFi

Hardware

T-Watch

Firmware Version

2.5.5.e18 (alpha) and 2.5.4.8d (stable)

Description

watch is looping and cannot enable wifi. tried to enable wifi to get time synced (other bug), but wifi does not work

Relevant log output

none
caveman99 commented 3 weeks ago

Please pst a serial log from the watch starting up.

369Martin369 commented 3 weeks ago

please explain me more how I can do that? Thanks @caveman99

caveman99 commented 3 weeks ago

connect an usb cable to your PC and the watch charging port, open up a command line and start meshtastic --noproto. The MEshtastic CLI needs to be installed like outlined in our documentation.

caveman99 commented 3 weeks ago

Patch doesn't fix the issue unfortunately. it now crashes in another spot.

369Martin369 commented 2 weeks ago

sorry, but my watch does no more work.... :-( cannot test.

todd-herbert commented 2 weeks ago

Logs reported via Discord:

caveman99 🇩🇪 — 2024/10/10 at 10:56 PM:

DEBUG | 09:42:12 16 WiFi-Event 5: Disconnected from WiFi access point WARN | 09:42:13 16 WiFi lost connection. Reason: 2 INFO | 09:42:14 17 [WifiConnect] Reconnecting to WiFi access point HomeNet DEBUG | 09:42:19 23 WiFi-Event 4: Connected to access point DEBUG | 09:42:19 23 WiFi-Event 7: Obtained IP address: 192.168.101.11 INFO | 09:42:19 23 Starting WiFi network services INFO | 09:42:19 23 mDNS responder started INFO | 09:42:19 23 mDNS Host: Meshtastic.local INFO | 09:42:19 23 Starting NTP time client DEBUG | 09:42:19 23 Initializing Web Server ... INFO | 09:42:19 23 Starting Secure Web Server... INFO | 09:42:19 23 Starting Insecure Web Server... INFO | 09:42:19 23 Web Servers Ready! :-)

next dead stop

I was able to reproduce the first stage of the issue with my DIY Touch-TFT node, but I can't reproduce this second stage.

That DIY device uses the older ESP32 rather than ESP32-S3. As a further experiment, I built 2.5.7.1f2d972 (current master) for Heltec Wireless Paper (an S3 device), modified to show the T-Watch screen frames. I couldn't reproduce the issue with this set-up either.

Is T-Watch S3 expected to receive an LVGL device-ui in the future? If that is the case, it might not be super important to dig too deep into fixing this one with the old screen implementation?