meshtastic
[Feature Request]: OTA timeout
Checklist
-
[x] I have used the search function for OPEN ISSUES to see if someone else has already submitted the same feature request.
-
[x] I have also used the search function for CLOSED ISSUES to see if the feature was already implemented and is just waiting to be released, or if the feature was rejected.
-
[x] I will describe the request with as much detail as possible.
-
[x] This request contains only one single feature, not a list of multiple (related) features.
-
[x] I have read and understood the Contribution Guidelines.
-
[x] I agree to follow this project's Code of Conduct
Contact Details
No response
Feature or improvement you want
As a stop gap as we wait for potential bootloader version to be exposed, perhaps we should time out if an update stalls out at 0%, and provide user steps normally needed to recover.
Why should this be added?
No response
Screenshots / Drawings / Technical details
No response
FYI- when the update got stuck at 0%, afterwards I needed to flash over it over the USB because reset button would not help and it would not boot normally anymore. (RAK4631)
Just to make sure - when the update got stuck at 0%, afterwards I needed to flash over it over the USB because it would not boot normally anymore. Is that expected?
It's expected when you don't follow directions/heed warnings and try to flash on a bootloader that doesn't support it like you were told in the previous thread 🙄
