Closed Avamander closed 3 years ago
Just managed to make it happen again, so I'm pretty sure it's an issue.
I can confirm this with 0.9.0, failed DFU update makes the watch unreachable unless I reboot it.
Also, I get very frequent failures when uploading a DFU, which get better if I turn off wifi on my phone which is doing the uploading. I had about 5-6 consecutive failures before turning wifi off, after which it worked on the second try. Having at least 5 m of distance from my router is a prerequisite for successful flashing as well.
I've also encountered this issue on 0.9.0, but don't recall having the issue on 0.10.0 or with the RC3 bootloader.
I can do further testing and confirm.
https://github.com/JF002/Pinetime/releases/tag/0.13.0 was released, we'll have to see if that fixed it.
https://github.com/JF002/Pinetime/releases/tag/0.13.0 was released, we'll have to see if that fixed it.
I have not had this issue since 0.13.0. Could be because OTA failures are rare now, but I think it is fixed
Since either 0.13 or 0.14 I haven't haven't had this issue either...
Prithee closeth this issue for the issue doesnt exist anymore!
With pleasure :)
I think I just stumbled upon a state where a DFU update fails, it returns to the main screen, but I couldn't establish a Bluetooth connection any more. Rebooting the watch fixed it.
This needs investigation because it's very bad with sealed PineTimes