Comment 15 for bug 1825821

Hi Daniel,

Thank you for your quick response. Yes, the computer (an embedded device board on which the said Ubunutu is running) already had Discoverable set to on (yes) by default. So I did not explicitly set it via your command. But, just I applied the command. Even now there is no change as to the detectability. Please see the terminal output below

Another point I just noticed (before running the command) is that if I am really close to the ubuntu device, then intermittently my android phone detects it, but then I have to be absurdly close (literally keep my phone right next to to the device).

***This was never the case**** and I suspect the issue mentioned in my original post - "Not enough free handles to register service".

[bluetooth]# show
Controller 00:04:4B:8D:2F:05
 Name: tegra-ubuntu
 Alias: tegra-ubuntu
 Class: 0x200000
 Powered: yes
 Discoverable: yes
 Pairable: yes
 UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
 UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
 Modalias: usb:v1D6Bp0246d0525
 Discovering: no
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:04:4B:8D:2F:05 Discovering: yes
[NEW] Device 46:72:B0:23:5F:BD 46-72-B0-23-5F-BD