BT Mouse re-connection issue with Lenovo NB T470

[Brian Chang]

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

[Kenneth]

Hello,

Make sure they have updated Windows 10 to the latest release. Type 'winver' to check version.

https://docs.microsoft.com/en-us/windows/windows-10/release-information 

There was an issue a year ago that prevented Windows 10 to reconnect in some cases, but this has since been fixed.

Best regards,
Kenneth

[Brian Chang]

Kenneth,

Lenovo said the Logitech mouse could be reconnect correctly so they do not accept to upgrade the window version was only solution

I attached the Logitech sniffer log

MX Anywhere 2S with T470_2.btt

I fund the different between the log of our SDK sample code / customer code with Logitech's log.

The sign bit field of Initiator Key Distribution  was set.

So bonding procedure was different.

However , in our code , if we set sign bit field , there will be an error happen.

How can we do to achieve the same secure configuration with Logitech????

It was very urgent since the project was going to do DVT status.

Thanks

BR

Brian 

[Kenneth]

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

[Brian Chang]

Hi Kenneth ,

Thanks for your support 

We fund out the issue version was 1709 and solve at 1803.

There was an  issue at Lenovo T470 NoteBook.

BR

Brian 

[Brian Chang]

Hi Kenneth,

sorry to open the case again.

Since the Lenovo was not recognized the issue was coming from Microsoft and ask for the bug relatted link。 

So I was trying to  link the issued date。You mention that team find the problem and report at last summer（2018 June to August）

So probably that was not fix at the 1803

I check the window update log

https://support.microsoft.com/en-ca/help/4467682/windows-10-update-kb4467682

Is it as same as fix the ble random address feature as above link?

Brian