bluetooth: android: register for adapter on/off events.

chrome/android/java/src/org/chromium/chrome/browser/BluetoothChooserDialog.java

Index: chrome/android/java/src/org/chromium/chrome/browser/BluetoothChooserDialog.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/BluetoothChooserDialog.java b/chrome/android/java/src/org/chromium/chrome/browser/BluetoothChooserDialog.java
index a0e07a2451c5771c1cb59a3229b862b7a9fe7eff..278005106028ea09114826105fe8fe00390a5840 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/BluetoothChooserDialog.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/BluetoothChooserDialog.java
@@ -321,6 +321,14 @@ public class BluetoothChooserDialog
     }
 
     @CalledByNative
+    private void notifyAdapterTurnedOn() {
+        mItemChooserDialog.clear();

[Ted C, 2016/02/26 17:50:35]

unless this line can somehow call closeDialog(), the native pointer check on the
next line can never be non-zero as this method is explicitly marked as called by
native.

[scheib, 2016/02/26 20:23:47]

Done.

+        if (mNativeBluetoothChooserDialogPtr != 0) {
+            nativeRestartSearch(mNativeBluetoothChooserDialogPtr);

[Ted C, 2016/02/26 17:50:35]

Why not have the native side just call this method right after calling
notifyAdapterTurnedOn?

[scheib, 2016/02/26 20:23:47]

Done.

+        }
+    }
+
+    @CalledByNative
     private void notifyDiscoveryState(int discoveryState) {
         switch (discoveryState) {
             case DISCOVERY_FAILED_TO_START: {