I am encountering a problem with the DFU process in my Android application. Specifically, when I stop scanning for the device or disconnect during the middle of the DFU process, the expected callbacks onError or onAbort in the DFU service listener are not triggered. Consequently, the DFU service fails to disconnect properly. This issue becomes evident when I attempt to rescan for the device and initiate the DFU process again, as it does not start as expected.
The figure below illustrates the issue that interrupts the DFU
The notification displayed in the interface below indicates an ongoing process. However, the notification remains active for an extended period and does not lead to a disconnection as expected.
Version
2.2.x
Ask the question
I am encountering a problem with the DFU process in my Android application. Specifically, when I stop scanning for the device or disconnect during the middle of the DFU process, the expected callbacks onError or onAbort in the DFU service listener are not triggered. Consequently, the DFU service fails to disconnect properly. This issue becomes evident when I attempt to rescan for the device and initiate the DFU process again, as it does not start as expected.
The figure below illustrates the issue that interrupts the DFU
The notification displayed in the interface below indicates an ongoing process. However, the notification remains active for an extended period and does not lead to a disconnection as expected.
Relevant log output
No response