Dear Bluez advertising-api developers, I got a problem with the advertising-api. It seems to be impossible to make an iBeacon advertisement with the api. I know it can be done with my bluetooth module because it is possible with the hcitool*. An iBeacon sends the following at the start of an advertisement: 0x0201061aff4c000215. With the advertising-api I am able to advertise a big part of the iBeacon(with the manufacturer data property): 0x1AFF4C0002155E2B092544064DFEB06D66D7AFB0F84C59659D46AC If I modify the bluetooth config(/etc/bluetooth/main.conf) setting "ControllerMode = le" it will add 0x020104 to the packet(this is the closest I got to an iBeacon): 0x0201041AFF4C0002155E2B092544064DFEB06D66D7AFB0F84C59659D46AC However I can't make the api advertise the following(the most important part at the start of the advertisement(0x020106) can't be done): 0x0201061AFF4C0002155E2B092544064DFEB06D66D7AFB0F84C59659D46AC I have tried all properties of the advertising-api, none of them seem to be able to add "0x020106" at the start of the advertisement. To summarize, my question is: Can you modify the dbus advertising-api of Bluez so that it is possible to advertise an iBeacon? Greetings, Marco * hcitool example: ############################ 02 01 06 1A FF 4C 00 02 15 # Apple's fixed iBeacon advertising prefix hcitool -i hci0 cmd 0x08 0x0008 1E 02 01 1A 1A FF 4C 00 02 15 FB 0B 57 A2 82 28 44 CD 91 3A 94 A1 22 BA 12 (Source: https://en.wikipedia.org/wiki/IBeacon)
