Bluetooth problems

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Noah Ferreira
Level 1
Level 1
Posts: 6
Joined: Thu Jan 20, 2022 6:30 pm

Bluetooth problems

Post by Noah Ferreira »

Hi,

I know Linux have a lot of problems with bluetooth... but, let's try..

I have a Lenovo G480 that came with no bluetooth, so I bought a USB bluetooth adapter. After that i removed blueberry and installed blueman. Here's what happens.

It can recognize y cellphone and my cellphone recognize my computer, but it won't pair.
And my JBL Go2 speaker (most important to me) it can't even recognize when searching for devices.

Any ideas?

thank you!

P.S.: OS= Linux Mint 20.3
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
kato181
Level 9
Level 9
Posts: 2564
Joined: Fri Mar 24, 2017 12:33 am
Location: Frederickton NSW

Re: Bluetooth problems

Post by kato181 »

Post the results of the following...

Code: Select all

sudo dmesg | grep -i Blue
Noah Ferreira
Level 1
Level 1
Posts: 6
Joined: Thu Jan 20, 2022 6:30 pm

Re: Bluetooth problems

Post by Noah Ferreira »

kato181 wrote: Sat Jan 22, 2022 5:20 am Post the results of the following...

Code: Select all

sudo dmesg | grep -i Blue

Code: Select all

noah@noah-Lenovo-G480:~$ sudo dmesg | grep -i Blue
[  538.011300] Bluetooth: Core ver 2.22
[  538.011345] Bluetooth: HCI device and connection manager initialized
[  538.011351] Bluetooth: HCI socket layer initialized
[  538.011353] Bluetooth: L2CAP socket layer initialized
[  538.011360] Bluetooth: SCO socket layer initialized
[  538.114352] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  538.114355] Bluetooth: BNEP filters: protocol multicast
[  538.114360] Bluetooth: BNEP socket layer initialized
[  538.176906] Bluetooth: RFCOMM TTY layer initialized
[  538.176911] Bluetooth: RFCOMM socket layer initialized
[  538.176918] Bluetooth: RFCOMM ver 1.11
Thanks
User avatar
kato181
Level 9
Level 9
Posts: 2564
Joined: Fri Mar 24, 2017 12:33 am
Location: Frederickton NSW

Re: Bluetooth problems

Post by kato181 »

Ok now try this and see what happens...

Code: Select all

In terminal type in the following...
bluetoothctl
It should respond with the following...
Agent registered.

It should be now in root..
[bluetooth]#
Type in..
scan on
Should result in..
Discovery started
It should return with..
[New] Device (eg) F0:65:DD:67:55:09 Name of bluetooth mouse

Then type..
pair F0:65:DD:67:55:09
The results should say..
Pairing Successful

Then type..
connect F0:56:DD:67:55:09
The results should say..
Connection Successful.

Then type...
trust F0:65:DD:67::55:09
They result should say..
Trust succeeded
Noah Ferreira
Level 1
Level 1
Posts: 6
Joined: Thu Jan 20, 2022 6:30 pm

Re: Bluetooth problems

Post by Noah Ferreira »

kato181 wrote: Sat Jan 22, 2022 8:19 am Ok now try this and see what happens...

Code: Select all

In terminal type in the following...
bluetoothctl
It should respond with the following...
Agent registered.

It should be now in root..
[bluetooth]#
Type in..
scan on
Should result in..
Discovery started
It should return with..
[New] Device (eg) F0:65:DD:67:55:09 Name of bluetooth mouse

Then type..
pair F0:65:DD:67:55:09
The results should say..
Pairing Successful

Then type..
connect F0:56:DD:67:55:09
The results should say..
Connection Successful.

Then type...
trust F0:65:DD:67::55:09
They result should say..
Trust succeeded
The last line didn't show as expected...

Code: Select all

noah@noah-Lenovo-G480:~$ bluetoothctl
Agent registered
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# 
User avatar
kato181
Level 9
Level 9
Posts: 2564
Joined: Fri Mar 24, 2017 12:33 am
Location: Frederickton NSW

Re: Bluetooth problems

Post by kato181 »

Ok. With the dongle connected post the results of the following..
lsusb
Noah Ferreira
Level 1
Level 1
Posts: 6
Joined: Thu Jan 20, 2022 6:30 pm

Re: Bluetooth problems

Post by Noah Ferreira »

kato181 wrote: Sun Jan 23, 2022 2:30 am Ok. With the dongle connected post the results of the following..
lsusb

Code: Select all

noah@noah-Lenovo-G480:~$ lsusb
Bus 002 Device 003: ID 5986:0295 Acer, Inc 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
User avatar
kato181
Level 9
Level 9
Posts: 2564
Joined: Fri Mar 24, 2017 12:33 am
Location: Frederickton NSW

Re: Bluetooth problems

Post by kato181 »

Code: Select all

Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
It's found the dongle alright..
Try this next and see what happens. Found it doing a search..

Code: Select all

I'm using it with a really old Acer TravelMate 2420 laptop using (out of necessity) the i386 release of Ubuntu 18.04 LTS. (Current kernel as of the time of writing is 4.15.0-106-generic. (No need to feel sympathy. This is just an old spare computer I keep in the bedroom and use occasionally.)

Bluetooth worked for me, but wasn't very reliable. I would get frequent disconnections of my Bluetooth mouse (Microsoft Bluetooth Notebook Mouse 5000).

I solved the problems completely a couple of weeks ago with the following changes in /etc/default/tlp:

# Exclude listed devices...
USB_BLACKLIST="0a12:0001"
# Bluetooth devices are excluded...
USB_BLACKLIST_BTUSB=1

(Find the appropriate lines and add the first and edit the second accordingly.)

It is likely that I don't need the specific ID-based USB_BLACKLIST command (I've not tested this) but thought I'd leave it in for safety. The second (USB_BLACKLIST_BTUSB) defaults to 0 on my system and I suspect this is the key configuration to change.

You may need to install the tlp package specifically, if it's not already installed. Don't forget to restart it after reconfiguring it.

I hope this helps.
User avatar
kato181
Level 9
Level 9
Posts: 2564
Joined: Fri Mar 24, 2017 12:33 am
Location: Frederickton NSW

Re: Bluetooth problems

Post by kato181 »

Could you also post the results of the following command..

Code: Select all

inxi -Fxpmzr
Noah Ferreira
Level 1
Level 1
Posts: 6
Joined: Thu Jan 20, 2022 6:30 pm

Re: Bluetooth problems

Post by Noah Ferreira »

kato181 wrote: Sun Jan 23, 2022 8:19 pm

Code: Select all

Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
It's found the dongle alright..
Try this next and see what happens. Found it doing a search..

Code: Select all

I'm using it with a really old Acer TravelMate 2420 laptop using (out of necessity) the i386 release of Ubuntu 18.04 LTS. (Current kernel as of the time of writing is 4.15.0-106-generic. (No need to feel sympathy. This is just an old spare computer I keep in the bedroom and use occasionally.)

Bluetooth worked for me, but wasn't very reliable. I would get frequent disconnections of my Bluetooth mouse (Microsoft Bluetooth Notebook Mouse 5000).

I solved the problems completely a couple of weeks ago with the following changes in /etc/default/tlp:

# Exclude listed devices...
USB_BLACKLIST="0a12:0001"
# Bluetooth devices are excluded...
USB_BLACKLIST_BTUSB=1

(Find the appropriate lines and add the first and edit the second accordingly.)

It is likely that I don't need the specific ID-based USB_BLACKLIST command (I've not tested this) but thought I'd leave it in for safety. The second (USB_BLACKLIST_BTUSB) defaults to 0 on my system and I suspect this is the key configuration to change.

You may need to install the tlp package specifically, if it's not already installed. Don't forget to restart it after reconfiguring it.

I hope this helps.
Sorry for taking so long to answer...

I don't have any archive named tlp in /etc/default/. Maybe its an older version that have been replaced in Mint 20.3.

Any suggestion?
Noah Ferreira
Level 1
Level 1
Posts: 6
Joined: Thu Jan 20, 2022 6:30 pm

Re: Bluetooth problems

Post by Noah Ferreira »

kato181 wrote: Sun Jan 23, 2022 8:25 pm Could you also post the results of the following command..

Code: Select all

inxi -Fxpmzr

Code: Select all

noah@noah-Lenovo-G480:~$ inxi -Fxpmzr
System:
  Kernel: 5.4.0-96-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: LENOVO product: 20149 v: Lenovo G480 serial: <filter> 
  Mobo: LENOVO model: INVALID v: 31900004WIN8 STD SGL serial: <filter> 
  UEFI [Legacy]: LENOVO v: 5ECN90WW(V8.02) date: 08/28/2012 
Battery:
  ID-1: BAT1 charge: 16.1 Wh condition: 34.5/42.8 Wh (81%) 
  model: LENOVO PABAS0241231 status: Charging 
Memory:
  RAM: total: 3.71 GiB used: 1.68 GiB (45.3%) 
  RAM Report: 
  permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Topology: Dual Core model: Intel Core i3-2328M bits: 64 type: MT MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17558 
  Speed: 798 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 846 2: 832 
  3: 825 4: 870 
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.20.13 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) 
  v: 3.3 Mesa 21.0.3 direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k5.4.0-96-generic 
Network:
  Device-1: Qualcomm Atheros AR8162 Fast Ethernet vendor: Lenovo driver: alx 
  v: kernel port: 2000 bus ID: 01:00.0 
  IF: enp1s0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: Lenovo 
  driver: ath9k v: kernel port: 2000 bus ID: 02:00.0 
  IF: wlp2s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 577.55 GiB used: 73.45 GiB (12.7%) 
  ID-1: /dev/sda vendor: Kingston model: SA400S37120GB size: 111.79 GiB 
  ID-2: /dev/sdb vendor: Seagate model: ST9500325AS size: 465.76 GiB 
Partition:
  ID-1: / size: 107.51 GiB used: 10.62 GiB (9.9%) fs: btrfs dev: /dev/sda6 
  ID-2: /boot/efi size: 475.1 MiB used: 4 KiB (0.0%) fs: vfat dev: /dev/sda1 
  ID-3: /home size: 457.45 GiB used: 62.82 GiB (13.7%) fs: ext4 
  dev: /dev/sdb1 
  ID-4: /run/timeshift/backup size: 107.51 GiB used: 10.62 GiB (9.9%) 
  fs: btrfs dev: /dev/sda6 
  ID-5: swap-1 size: 3.81 GiB used: 15.5 MiB (0.4%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 50.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
  1: deb http://dl.google.com/linux/earth/deb focal main
  Active apt repos in: /etc/apt/sources.list.d/atareao-telegram-focal.list 
  1: deb http://ppa.launchpad.net/atareao/telegram/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
  1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com una main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
  1: deb [arch=amd64] https://repo.skype.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
  1: deb https://linux.teamviewer.com/deb stable main
Info:
  Processes: 242 Uptime: 2h 21m Init: systemd runlevel: 5 Compilers: 
  gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 
User avatar
kato181
Level 9
Level 9
Posts: 2564
Joined: Fri Mar 24, 2017 12:33 am
Location: Frederickton NSW

Re: Bluetooth problems

Post by kato181 »

I see your bios is 10yrs old, so running a newer version of LM maybe your problem. Cinnamon is very resource hungry, so I would suggest booting into LM 19.3 Xfce and see if the dongle works in that version. If It does, then you may have to resort back to a earlier LM version. You could also try a boot version of LM 20 but using the Xfce desktop to see if it works.
Locked

Return to “Hardware Support”