You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently using a OnePlus Nord N10 5G and I can confirm it works well for scanning, advertising (primary & secondary), and connecting all using Coded PHY (using the nRF Connect Android app).
The issue I am running into is I'm not able to scan only Coded PHY advertisements (primary + secondary). According to the Android API documentation, you can set the PHY used for scanning to be: 1M + Coded PHY, 1M only, or Coded only. However, I am still receiving non-Coded PHY advertisements even when I set the Phy to Coded PHY using the .setPhy(BluetoothDevice.PHY_LE_CODED) during the setting of the Scan Settings.
Here's the code I modified in the app (in ScannerViewModel.java):
How about you set report delay to 0?
Edit: You're using scanner compat with disabled hardware batching, so delays are emulated by the library... This will not help.
So I guess there's nothing that can be done. It's how the phone behaves... Did you try other phones?
I have not tried other phones. I only have a Pixel 4a and I believe that does not support scanning for extended advertisements. In your testing, have you tried scanning for Coded PHY only?
I am currently using a OnePlus Nord N10 5G and I can confirm it works well for scanning, advertising (primary & secondary), and connecting all using Coded PHY (using the nRF Connect Android app).
The issue I am running into is I'm not able to scan only Coded PHY advertisements (primary + secondary). According to the Android API documentation, you can set the PHY used for scanning to be: 1M + Coded PHY, 1M only, or Coded only. However, I am still receiving non-Coded PHY advertisements even when I set the Phy to Coded PHY using the .setPhy(BluetoothDevice.PHY_LE_CODED) during the setting of the Scan Settings.
Here's the code I modified in the app (in ScannerViewModel.java):
Is this an issue with the API? or am I doing something wrong?
The text was updated successfully, but these errors were encountered: