[Touch-packages] [Bug 1924623] Re: Bluetooth headset pairing issue (HOCO ES32 PLUS)

2023-02-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1924623

Title:
  Bluetooth headset pairing issue (HOCO ES32 PLUS)

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is
  visible and in pairable mode, but after running:

  bluetoothctl

  [bluetooth]# show
  Controller 04:33:C2:AA:17:60 (public)
   Name: mykyt
   Alias: mykyt
   Class: 0x001c010c
   Powered: yes
   Discoverable: yes
   DiscoverableTimeout: 0x
   Pairable: yes
   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
   UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
   UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
   UUID: Vendor specific   (5005--1000-8000-0002ee01)
   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
   UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
   Modalias: usb:v1D6Bp0246d0535
   Discovering: yes
  Advertising Features:
   ActiveInstances: 0x00
   SupportedInstances: 0x05
   SupportedIncludes: tx-power
   SupportedIncludes: appearance
   SupportedIncludes: local-name
   SupportedSecondaryChannels: 1M
   SupportedSecondaryChannels: 2M
   SupportedSecondaryChannels: Coded

  i get:

  Failed to pair: org.bluez.Error.AuthenticationTimeout

  or

  Failed to pair: org.bluez.Error.AuthenticationCanceled

  or

  Failed to pair: org.bluez.Error.Failed

  I tried every single solution i was able to find for similar problems,
  including changing controller mode to bredr, reinstalling pulseaudio,
  unblocking rfkill, checking if my device is in pairable mode, using
  blueman and so on.

  The fact is, bluetooth is working on my laptop (I can connect to my
  phone and my other bluetooth headset MEIZU EP51) and also my headset
  HOCO ES32 PLUS is working and is able to connect to my phone and my
  other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04.

  I really hope you can help me. Please tell me if you need more information 
and I will provide it.
  Thank you!
  --

  lsb_release -rd

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  apt-cache policy bluez

  bluez:
    Installed: 5.53-0ubuntu3
    Candidate: 5.53-0ubuntu3
    Version table:
   *** 5.53-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  --

  Expected behavior:

  After turning on bluetooth and clicking on device name in settings ->
  bluetooth device is connecting and pairing successfully.

  Current behavior:

  Pairing fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 00:28:19 2021
  InstallationDate: Installed on 2020-08-27 (231 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Swift SF314-57G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2020
  dmi.bios.release: 1.14
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 

[Touch-packages] [Bug 1924623] Re: Bluetooth headset pairing issue (HOCO ES32 PLUS)

2021-04-15 Thread Daniel van Vugt
** Summary changed:

- Bluetooth headset pairing issue
+ Bluetooth headset pairing issue (HOCO ES32 PLUS)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1924623

Title:
  Bluetooth headset pairing issue (HOCO ES32 PLUS)

Status in bluez package in Ubuntu:
  New

Bug description:
  I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is
  visible and in pairable mode, but after running:

  bluetoothctl

  [bluetooth]# show
  Controller 04:33:C2:AA:17:60 (public)
   Name: mykyt
   Alias: mykyt
   Class: 0x001c010c
   Powered: yes
   Discoverable: yes
   DiscoverableTimeout: 0x
   Pairable: yes
   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
   UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
   UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
   UUID: Vendor specific   (5005--1000-8000-0002ee01)
   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
   UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
   Modalias: usb:v1D6Bp0246d0535
   Discovering: yes
  Advertising Features:
   ActiveInstances: 0x00
   SupportedInstances: 0x05
   SupportedIncludes: tx-power
   SupportedIncludes: appearance
   SupportedIncludes: local-name
   SupportedSecondaryChannels: 1M
   SupportedSecondaryChannels: 2M
   SupportedSecondaryChannels: Coded

  i get:

  Failed to pair: org.bluez.Error.AuthenticationTimeout

  or

  Failed to pair: org.bluez.Error.AuthenticationCanceled

  or

  Failed to pair: org.bluez.Error.Failed

  I tried every single solution i was able to find for similar problems,
  including changing controller mode to bredr, reinstalling pulseaudio,
  unblocking rfkill, checking if my device is in pairable mode, using
  blueman and so on.

  The fact is, bluetooth is working on my laptop (I can connect to my
  phone and my other bluetooth headset MEIZU EP51) and also my headset
  HOCO ES32 PLUS is working and is able to connect to my phone and my
  other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04.

  I really hope you can help me. Please tell me if you need more information 
and I will provide it.
  Thank you!
  --

  lsb_release -rd

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  apt-cache policy bluez

  bluez:
    Installed: 5.53-0ubuntu3
    Candidate: 5.53-0ubuntu3
    Version table:
   *** 5.53-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  --

  Expected behavior:

  After turning on bluetooth and clicking on device name in settings ->
  bluetooth device is connecting and pairing successfully.

  Current behavior:

  Pairing fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 00:28:19 2021
  InstallationDate: Installed on 2020-08-27 (231 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Swift SF314-57G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2020
  dmi.bios.release: 1.14
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.14
  dmi.modalias: