arc: bluetooth: Expose missing advertise data.

device/bluetooth/dbus/bluetooth_device_client.cc

Index: device/bluetooth/dbus/bluetooth_device_client.cc
diff --git a/device/bluetooth/dbus/bluetooth_device_client.cc b/device/bluetooth/dbus/bluetooth_device_client.cc
index 70930894f235a09b2ee81449e984a668606c3837..4e1a1f81c3dd44238bfde8446b4aca78fa0a53d3 100644
--- a/device/bluetooth/dbus/bluetooth_device_client.cc
+++ b/device/bluetooth/dbus/bluetooth_device_client.cc
@@ -202,9 +202,12 @@ BluetoothDeviceClient::Properties::Properties(
   RegisterProperty(bluetooth_device::kModaliasProperty, &modalias);
   RegisterProperty(bluetooth_device::kRSSIProperty, &rssi);
   RegisterProperty(bluetooth_device::kTxPowerProperty, &tx_power);
+  RegisterProperty(bluetooth_device::kManufacturerDataProperty,
+                   &manufacturer_data);
   RegisterProperty(bluetooth_device::kServiceDataProperty, &service_data);
   RegisterProperty(bluetooth_device::kServicesResolvedProperty,
                    &services_resolved);
+  RegisterProperty(bluetooth_device::kFlagsProperty, &flags);

[ortuno, 2016/10/14 00:15:10]

I might be missing something but I don't see this property in the BlueZ docs. Is
it done in an internal BlueZ patch? If so can you mention it in the description?
What's the plan for upstreaming it? Does this break Linux?

rkc: Are you OK with Chrome OS and Linux implementations starting to work
differently.

[Rahul Chaturvedi, 2016/10/17 20:41:21]

I've asked Opal to upstream the patch to BlueZ. I would prefer Linux and Chrome
OS to work similarly; that being said, that won't always be possible. Certain
features we add purely for Chrome OS will just not work on Linux.

[puthik_chromium, 2016/10/17 23:30:32]

I sent it to upstream
http://marc.info/?l=linux-bluetooth&m=147674326322110&w=2
http://marc.info/?l=linux-bluetooth&m=147674326522113&w=2
http://marc.info/?l=linux-bluetooth&m=147674326322111&w=2

 }
 
 BluetoothDeviceClient::Properties::~Properties() {}