Assigned
Status Update
No update yet.
Comments
pa...@gmail.com
Also this bug report:
https://issuetracker.google.com/issues/148487283
specifically in post #18 and #21 shows this was easily proved to be a bug. This bug is marked as "Won't fix - infeasible", which makes no sense.
If this bug is really fixed, please respond and I can chase the nrf connect app devs to see if they are missing something.
I am testing this on a Pixel 6 using nrf connect
specifically in post #18 and #21 shows this was easily proved to be a bug. This bug is marked as "Won't fix - infeasible", which makes no sense.
If this bug is really fixed, please respond and I can chase the nrf connect app devs to see if they are missing something.
I am testing this on a Pixel 6 using nrf connect
vi...@google.com
Thanks for your request. We will investigate this issue and see if we can implement the behavior you've requested.
Description
Android on Pixel phones still does not allow for scanning of Coded PHY long range on Primary. This breaks the Bluetooth spec and makes all Pixel phones useless regarding advertising extension long range. This works fine on a Samsung phones (and a whole list of other phones).
This is easy to reproduce using the nfr connect App. Place the scanner into bluetooth LE coded phy only mode and you will never see an advertising extension.
Some links:
Bluetooth LE Scanner does not support Coded Phy
Marked as assigned, but nothing has happened in almost 3 years
3013872: Fix handling for coded and all supported PHY
Marked as merged and would have assummed this is in Android 16 beta 2
2942289: Plumb PHY settings down to native layer
Marked as merged and would have assummed this is in Android 16 beta 2
This bug has been reported 3 year ago, and has not been fixed. I don't know why this has happened, but developers really need this...
Any update would be appreciated.