BT_ADDR not updated

BT_ADDR not updated

[Randy Yates]

This question is regarding bluez 5.2:
 
i'm changing bt addr "on-the-fly" via a vendor-specific hcitool 
command but the bluetoothctl is not seeing the new address, even 
after a hciconfig hci0 reset

however i do see the new address via "hcitool dev", so it's 
getting changed in the device

is there some bug in bluez updating the device address on a reset?
-- 
Randy Yates
Digital Signal Labs
http://www.digitalsignallabs.com

Re: BT_ADDR not updated

[Johan Hedberg]

Hi Randy,

On Sat, Feb 16, 2013, Randy Yates wrote:
> This question is regarding bluez 5.2:
> 
> i'm changing bt addr "on-the-fly" via a vendor-specific hcitool
> command but the bluetoothctl is not seeing the new address, even
> after a hciconfig hci0 reset
> 
> however i do see the new address via "hcitool dev", so it's getting
> changed in the device
> 
> is there some bug in bluez updating the device address on a reset?

The address is assumed to stay unchanged from the moment that the
existence of the controller is presented to user space, i.e. there is no
event through which user space would be notified of changes to its
address. If your hardware requires this kind of initialization (e.g. if
it doesn't have a proper address from the start) the best place for
writing the address would probably be the HCI driver's initialization
routine.

Johan