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
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1825821
Title:
[Nvidia Tegra] Ubuntu 16.04 : Bluetooth can't be detected by other
devices
Status in bluez package in Ubuntu:
Incomplete
Bug description:
Hi,
I am running an Ubuntu 16.04 machine. I tried to start the system
bluetooth through the following steps:
1. Ensured that bluetooth was unblocked through the command rfkill
2. Set bluetooth to powered on, agent on, default-agent and scan on through
bluetootctl
On completing these steps, Bluetooth icon shows up as active on the
system, but other devices are unable to scan it and consequently not
able to connect to it. This Ubuntu does not appear in the list of
bluetooth devices for other devices' scan.
3. I ran systemctl status bluetooth
I am getting the following errors:
nvidia@tegra-ubuntu:~$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running) since Mon 2019-04-22 15:57:21 IST; 10min ago
Docs: man:bluetoothd(8)
Main PID: 1087 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─1087 /usr/lib/bluetooth/bluetoothd
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Error adding Link Loss service
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to
register service
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to
register service
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to
register service
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Current Time Service could not
be registered
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: gatt-time-server: Input/output
error (5)
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to
register service
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to
register service
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Sap driver initialization
failed.
Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: sap-server: Operation not
permitted (1)
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: arm64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InterestingModules: rfcomm bnep bluetooth
Lspci:
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 413c:301a Dell Computer Corp.
Bus 001 Device 003: ID 413c:2113 Dell Computer Corp.
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: bluez 5.37-0ubuntu5.1
PackageArchitecture: arm64
ProcKernelCmdLine: root=/dev/mmcblk0p1 rw rootwait console=ttyS0,115200n8
console=tty0 OS=l4t fbcon=map:0 net.ifnames=0 memtype=0 video=tegrafb
no_console_suspend=1 earlycon=uart8250,mmio32,0x03100000
nvdumper_reserved=0x2772e0000 gpt tegraid=18.1.2.0.0 tegra_keep_boot_clocks
maxcpus=6 androidboot.serialno=0323117055596
bl_prof_dataptr=0x10000@0x277240000 sdhci_tegra.en_boot_part_access=1
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4
Tags: xenial
Uname: Linux 4.4.38-tegra aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy sudo video
_MarkForUpload: True
hciconfig:
hci0: Type: BR/EDR Bus: UART
BD Address: 00:04:4B:8D:2F:05 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:794 acl:0 sco:0 events:52 errors:0
TX bytes:2128 acl:0 sco:0 commands:52 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2019-03-21T12:36:43.871783
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825821/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
