Hi Yunnan, > Thanks for your reply. I think kernel should support scan response > because I am able to set different local name in scan rsp using hci > socket instead of Dbus API. Have you ever post your patch or sample > code in this thread or any other place? May I have a try on your > patch? It would be doable and useful to put Local name change as > property, like include tx power, so that we can set it in scan rsp > when enabling advertisement. have you actually checked that local name is supported via advertising instances. The Read Advertising Features mgmt command is pretty clear in its description that support for adding local name in scan response is optional. The command is also pretty clear in that if that flag is given, the local name is managed via the kernel and can only be modified via Set Local Name mgmt command. If you want to use any other name in scan response, you need to not specify that flag. Using raw HCI sockets is like packet injection. That does not count. Also you will never make that work correctly since you essentially by-passing the kernel and programming the hardware directly. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
