Tested the issue in Android and able to reproduce the issue. Similar behavior is observed since Chrome #60.0.3072.0

Enabled Bluetooth on device under test.

Steps Followed:
1. Launched the Chrome Browser.
2. Navigate to: chrome://bluetooth-internals.
3. From the Hamburger menu, tap on "Devices".
4. Tap on "Start Scan" button.
5. Observed that "Failed to start discovery session" message is displayed

Chrome versions tested:
60.0.3072.0, 64.0.3282.140(Stable), 66.0.3344.0(Canary)

OS:
Android 8.0.1

Android Devices:
Pixel XL

This seems to be a Non-Regression issue as same behavior is seen since M60.  Untriaged for further input's on this issue.

Please navigate to below link for log's and video--
go/chrome-androidlogs/811125

Thanks!

From screenshot #1, it seems like the adapter is off. Turning Bluetooth on should fix the scanning problem. We should probably show a dialog to turn Bluetooth on but that seems more like a feature request than a bug.

Dear ortuno@, of course, that scanning was tried with BT on... And of course, that BT address was checked with BT on too.

it's also written in #2: "Enabled Bluetooth on device under test."

Please investigate the clue of the problem if possible.

Interesting. So you are saying that in the screenshot in #1 Bluetooth was on? I don't see the Bluetooth icon in the first screenshot.

Does Chrome have the location permission? You can check it by going to https://permission.site/ and tapping location. I revoked the location permission on my device and get the same error.

> Interesting. So you are saying that in the screenshot in #1 
> Bluetooth was on? I don't see the Bluetooth icon in the first screenshot.

Screenshot_20180211-140915.png - you have BT on and there is icon

Screenshot_20180211-140723.png - screenshot was made with BT off, but bug was visible with BT on too (I mean - no correct address)

> Does Chrome have the location permission? 
> You can check it by going to https://permission.site/ 
> and tapping location. I revoked the location permission 
> on my device and get the same error.

I've enabled location permission for app in Android System settings menu and inside Chrome settings and scan doesn't return error, but BT device address is still incorrect.

This is one problem.

And second problem is that Chrome should probably ask correctly for permission for chrome://bluetooth-internals 

Current situation is just non-clear / non-logical

(and this is my end-user opinion -> like mentioned in #0 I don't know if everything is expected to be working)

The wrong address is expected: https://developer.android.com/about/versions/marshmallow/android-6.0-changes.html#behavior-hardware-id

Thx, can be this info added to page? or can be address hidden when we have Android >= 6 ?

it's obviously not critical thing, but...

1. Detect when Chrome still needs Bluetooth and location permission and inform the user.
2. Detect Android >= 6 and mark MAC address as obfuscated or hide it.