-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Long hold of middle button will crash tbeam if there's no screen. #1646
Comments
Mine goes to AP mode, that is the long press action right? //\ E S H T /\ S T / C ??:??:?? 0 booted, wake cause 0 (boot count 1), reset_reason=reset ??:??:?? 26 Starting (Forced) WIFI AP: ssid=meshtasticAdmin, ok=1 |
Maybe the crash is trying to enable wifi while paired with bluetooth? I can't reproduce with a standalone device either |
I wonder if his AXP chip is fried |
There's an order of operation. Middle button will only activate wifi if it's held down within the first (about) quarter second of boot. Middle button won't activate wifi otherwise. |
There is a crash if you wait before the long press meshtastic --noproto ELF file SHA256: 0000000000000000 Backtrace: 0x401f2af0:0x3ffd5670 0x400f4c93:0x3ffd5690 0x400dc433:0x3ffd56b0 0x400dd645:0x3ffd56e0 0x400f6086:0x3ffd5700 0x400f60f6:0x3ffd5720 0x400dd535:0x3ffd5740 0x400d56ae:0x3ffd5760 0x400f6f31:0x3ffd5780 0x400dd88c:0x3ffd57b0 0x4012c01d:0x3ffd57d0 Rebooting... rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) //\ E S H T /\ S T / C ??:??:?? 0 booted, wake cause 0 (boot count 1), reset_reason=reset ??:??:?? 34 Starting (Forced) WIFI AP: ssid=meshtasticAdmin, ok=1 |
After the initial crash if you are still holding the button it goes into AP mode |
Bug: Long hold of middle button will crash tbeam if there's no screen. This is on 1.3.39.
100% reproducible.
The text was updated successfully, but these errors were encountered: