search

NordicSemiconductor / Android-nRF-Connect

Documentation and issue tracker for nRF Connect for Android.
1.35k stars 313 forks source link

choose device in dfu mode, sometimes it not connected with tab created and opend #30

Open jasonbu opened 7 years ago

jasonbu commented 7 years ago

The UI is looks like when dfu is processing. The connect/disconnect button is hidden and dfu button is also hidden. It can be fix by re-enter the scan tab and choose open Tab, and the connect/disconnect button and dfu button will appear and ready to use.

philips77 commented 7 years ago

Could you post a screenshot?

jasonbu commented 7 years ago

screenshot_2017-02-21-14-07-34-343_no nordicsemi ![Uploading Screenshot_2017-02-21-14-08-27-551_no.nordicsemi..png…]()

just like the two screenshot, it is not able to be operation without rescan and open tab

philips77 commented 7 years ago

The DFUTARG tab opens because during the DFU process your device starts to adv with address incremented by 1 so, from nRF Connect point of view, it's a new device. Also, because you have configured the GATT server in the app, it is able to detect a "new" connected device and shows it on a new tab.

There are 2 questions:

  1. Why DFU TARG has 2 first bytes of the address different? Was my statement above correct and this is the same device in different mode, or it's a coincidence?
  2. Why this tab is empty while it should show available services.

Could you also post the log you get on this and the previous tab?

jasonbu commented 7 years ago
  1. Why DFU TARG has 2 first bytes of the address different? Was my statement above correct and this is the same device in different mode, or it's a coincidence? because I chanedged the mac in application.
  2. Why this tab is empty while it should show available services. It is why i put issue here, it seems not to happen every time. when dfu two files on single file continuesly, it happen sometimes. next time, i will catch the logfile
philips77 commented 7 years ago

Hi, I managed to reproduce the issue but still didn't have time to check the cause and fix it. I'll keep it open here as a reminder.