Thanks for the report. If you could send us a device, we can try to repro the issue. 

Where should we send it?

Hi John, we can also purchase the device through your website. Do you have a code we can use? 

Hi John,

It would be really helpful if you can help with providing the following information:
1) The setup steps, such as webpage or plugin if there is any, for reproducing the issue.
2) Feedback reports when you observe the issue.
The key combination is Alt + Shift + i. In the summary of feedback report, please include "mcchou@, rjahagir@" as the first line and describe the detailed steps that you took before seeing this issue. Feel free to include your own observation as well.

Thanks in advance!

1. The steps are provided in the initial report. Please advise me on where you are having difficulty with the instructions.
2. I sent a feedback report as requested but there probably isn't much to see there as the issue is that it isn't detecting the device.

I have attached a html file which I have been using to debug some of the web bluetooth issues.

If you get hold of a PL1 device, turn it on and press 'Connect' on the provided html file it probably won't show up (on a Chromebook). If it does, then click 'Remove Event Listener and Disconnect' and then press 'Connect' again and it won't show up.

I am under the impression that your team has a PocketLab device now although I am not sure if you have a PocketLab 1 which is the only device you see this issue on. If not then maybe we can arrange something?

I have actually found a work around which has been deployed in https://pocketlab-web-dev.herokuapp.com where 

1. On requestDevice I have removed the services filter and added all used services as optionalServices
2. Always call removeEventListener when possible
3. Call stopNotifications before enabling any sensors after a reconnect (the device would be detected without this step but the operation to start sensors would always fail)

Deleted: webbluetooth_test.html 3.0 KB

webbluetooth_test.html 3.0 KB View Download

Hi john@zode64.com,

Can you help with enabling BT logging level (see the instructions below) before reproducing the restarting issue?

0) Enable Bluetooth debug logging by adding "-d" flag in file
/usr/bin/start_bluetoothd.sh and reboot for the log level to take effect.
  To be more specific "-d" should be added at this line:
/usr/libexec/bluetooth/bluetoothd ${BLUETOOTH_DAEMON_OPTION}
--nodetach "-d"

1) Enable Chrome logging by adding flags in /etc/chrome_dev.conf
  --vmodule=*blue*=3 --log-level=0

2) Reboot to make sure the flags are picked up by chrome and bluetoothd.

Please file a feedback report with mcchou@ and josephsih@ mentioned in the issue description after producing the issue. Thanks.
Once you filed a feedback report, can you mentioned the account used during the repro so that we can search for the report?

I have looked into this. Device is most definitely discovered when doing a normal scan in bluez and in newblue. Issue *must* be in chrome's webbluetooth code. sending to rkc@ to look into further. Proof follows:


> HCI Event: LE Meta Event (0x3e) plen 15                      [hci0] 20.539797
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Public (0x00)
        Address: D4:F5:13:4A:0D:61 (OUI D4-F5-13)
        Data length: 3
        Flags: 0x05
          LE Limited Discoverable Mode
          BR/EDR Not Supported
        RSSI: -47 dBm (0xd1)
> HCI Event: LE Meta Event (0x3e) plen 43                      [hci0] 20.541079
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Scan response - SCAN_RSP (0x04)
        Address type: Public (0x00)
        Address: D4:F5:13:4A:0D:61 (OUI D4-F5-13)
        Data length: 31
        Name (complete): MS-PL-HW10-FW10-0001
        Slave Conn. Interval: 0x0050 - 0x0320
        TX power: 0 dBm
        RSSI: -48 dBm (0xd0)

FWIW, when I used an APP running in ARC++ to scan nearby devices a while back, the device list was usually smaller than what I got by scanning in "hcitool lescan" in chrome os.

James now owns connectivity in Chrome OS UI, over to him.