Var IsMultipleAdvertisementSupported = bluetoothAdapter.IsMultipleAdvertisementSupported Var IsLePeriodicAdvertisingSupported = bluetoothAdapter.IsLePeriodicAdvertisingSupported Var IsLeExtendedAdvertisingSupported = bluetoothAdapter.IsLeExtendedAdvertisingSupported Var IsLeCodedPhySupported = bluetoothAdapter.IsLeCodedPhySupported Var IsLe2MPhySupported = bluetoothAdapter.IsLe2MPhySupported
Here's the Android code that demonstrated the capability in the Android (the actual extended advertising code is about 30 - 40 lines long), and all of the following variables returned true: The way I deduced this is that I wrote the code in Android, and broadcast advertisements using that from a Samsung 20+, and in my iPhone 12 Pro, I downloaded the nRF Connect app, and was able to receive the Bluetooth 5.0 advertisements there. Indeed there is support for BL 5.0 Extended Advertising Support in iOS. I can verify the 'will it or wont it?' questions in the original post, and answers to date: There's a new API for you to programmatically query for platform support, and this is now supported on iPhone XS and the new iPad Pro. We would scan for both legacy and extended advertisements. You can use the same scan API, scan filters. This is again transparent to your application. This is four times the amount of advertisement data that an accessory can send us today. We now support extended advertisement payloads up to 124 bytes. So, if you're developing an accessory, your accessory must also support extended advertisement with LE 2 Mbps. This means that we can scan now for the extended advertisements that I've just mentioned, but we will only scan for our extended advertisements that are transmitted in LE 2 Mbps. Core Bluetooth will support extended scan this year. Up now from 31 to 255 bytes, and the transmission rate itself can now be in LE 2 Mbps. The first is it eases the congestion on the three advertising channel by sending a smaller payload on the advertising channel, then jumping to the more spacious data channel to transmit a much larger payload. It essentially improves upon three main points for advertising. At the 2019 WWDC they claimed it could but I have yet to see an Apple device that does.Īdvertising extension is a Bluetooth 5.0 feature. I'm also curious to see if someone can comment on whether there are any devices which support extended advertising and can point to some example that shows this. Last one, maybe there are any devices which supports extended advertising.
How to do it? Is it possible by users? Or maybe anywhere in product's specification exists this information?Ĥ. I'm wondering about how to check Bluetooth bitrate in my device. What is problem with my device or framework or something else? What is caused that scanning for extended advertising is impossible using my iPad A2152?ģ.
About Core Bluetooth, is there any API which should I use to enable scanning for extended advertising? I haven't found any but I would like to be certain about its.Ģ. To sum up, I have a several questions for you.ġ. How to check if it's possible to scanning using LE 2 Mbps? It seems to me each device which supports Bluetooth 5.0 should be able to scan using LE 2 Mbps. We can see that iPad is scanning using LE 1 Mbps. Next one, I don't know about if my device is supports "LE 2 Mbps bitrate".
It is looking like software issues (with Core Bluetooth) rather than the unability by my device to scan for advertising extensions. It's strange for me why this value is set. My investigation has gone to place when I see that there are sending packets to set extended scan parameters with code "Reserved for future use". More over, I was trying to use the PacketLogger for Xcode to find out the problem. I have found an API to test if my devices support this feature and I have written code to test its. I've noticed that my device supports Bluetooth 5.0 but I can't find my BLE 5.0 peripheral using Core Bluetooth. I am trying to scan for extended advertising packets using my iPad Air (A2152).