This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BT Mouse re-connection issue with Lenovo NB T470

Hi ,

Our customer use nRF52832 to design the mouse. Currently they had problem to do the connection with Lenovo T470 after power cycling (POWER OFF and  Then POWER ON)

In order to make issue easy , we ask customer to use SDK15.2  BLE_Periphrial HID mouse example to verify the issue.

What we observer was the nRF52832 was advertising but the T470 was not response it (never had us  connection indication). 

The window version of T470 was as bellowing

We had record the log by Ellisys sniffer 

52832 nRF5_mouse with T470.btt

Did you have ever see such kind of behavior

BR

Brian Chang

Parents
  • Hi Brian,

    It is not related to the key distribution that you refer to.

    The difference between the "old" Logitech mouse (BTv4.1) you are testing and the "new" SDK mouse example, is that the new BLE softdevice (BTv5.0) support privacy.

    We contacted Microsoft after having some connection issues with windows 10 units last summer.

    What we notice is that after bonding and disconnect, then windows 10 behaves differently based on a characteristic that reside on the peripheral side (Central Address Resolution). Microsoft confirmed there was an issue where Windows 10 were assuming privacy would be enabled for some devices and thus failed to program both the IRK resolution AND the device’s static address to their controller’s offloaded capabilities. This prevented Windows 10 to reconnect. This issue was patched in Windows 10 update.

    Please update Windows 10 to confirm this fixes their issue.

    Best regards,
    Kenneth

Reply
  • Hi Brian,

    It is not related to the key distribution that you refer to.

    The difference between the "old" Logitech mouse (BTv4.1) you are testing and the "new" SDK mouse example, is that the new BLE softdevice (BTv5.0) support privacy.

    We contacted Microsoft after having some connection issues with windows 10 units last summer.

    What we notice is that after bonding and disconnect, then windows 10 behaves differently based on a characteristic that reside on the peripheral side (Central Address Resolution). Microsoft confirmed there was an issue where Windows 10 were assuming privacy would be enabled for some devices and thus failed to program both the IRK resolution AND the device’s static address to their controller’s offloaded capabilities. This prevented Windows 10 to reconnect. This issue was patched in Windows 10 update.

    Please update Windows 10 to confirm this fixes their issue.

    Best regards,
    Kenneth

Children
No Data
Related