nrfconnect dfu fail on andriod after paired

[Brian Qin]

Hi, 

I used sdk11 and sd130 at a 51822 project, it is required to be paired with a key for both andriod and ios, everything is fine but the dfu on andriod, I used nrfconnect to test dfu, for IOS it is always ok, but andriod always failed after it is paired, and always ok if it set to not paired, the error code on nrfconnect is always GATT INVALID HANDLE.  

brain.

[Vidar Berg]

Hi Brian,

Please check if "keep bond information" is enabled in nrf connect -> settings -> DFU options. It should be by default. 

[Brian Qin]

I checked the keep bond information was enabled, but the same:

 IOS it is always ok(after paired), but andriod always failed after it is paired, and always ok if it set to not paired

[Vidar Berg]

I was unable to reproduce this issue with the following setup:

• SDK 11 bootloader and hear rate example extended with buttonless dfu support
• nRF connect v.4.18.0 on Android
• Paired phone with peripheral before initiating DFU from the hrs example 

The GATT INVALID HANDLE error indicates that the phone is not doing a re-discovery of the attribute table upon entering DFU mode. I'd suggest to debug the bootloader to check if it sends the service changed indication from dfu_transport_ble.c::service_change_indicate(). E.g., check if  m_ble_peer_data_valid is true and if sd_ble_gatts_service_changed() returns NRF_SUCCESS.-