| View previous topic :: View next topic |
| Author |
Message |
ppwaskie
n00b
Joined: 10 Sep 2015
Posts: 12
|
 Posted: Tue Jan 26, 2016 8:09 am Post subject: [SOLVED]Unable to get Plattan Bluetooth headphones working |
 |
|
Hi all. I have a pair of Plattan ADV Wireless Bluetooth headphones that I've been trying to get working with Linux. The headphones are pairing successfully, but it appears the headphones are being identified as a keyboard by bluetoothd. I've gone through the Gentoo Bluetooth setup, and the Gentoo Bluetooth Headset setup, and haven't had any success.
The headphones have an input panel on the left ear, where a user can tap or swipe to send commands like Pause, Play, etc. This is where I think the identification is tripping up.
I'm using bluez5. Here's all the info I can think of that would be relevant. Any help is much appreciated, and I can do my best to provide additional info. I've also tried this on two different machines, an Intel NUC, and a Samsung Ultrabook. Same results.
| Code: |
[bluetooth]# info 5C:EB:68:2C:19:A8
Device 5C:EB:68:2C:19:A8
Name: Plattan ADV Wireless
Alias: Plattan ADV Wireless
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
|
From /var/log/messages after connecting the headset:
| Code: |
Jan 25 23:49:41 pj-ultrabook bluetoothd[3722]: /org/bluez/hci0/dev_5C_EB_68_2C_19_A8/fd0: fd(21) ready
Jan 25 23:49:41 pj-ultrabook kernel: input: 5C:EB:68:2C:19:A8 as /devices/virtual/input/input14
Jan 25 23:49:41 pj-ultrabook gdm-x-session[3791]: (II) config/udev: Adding input device 5C:EB:68:2C:19:A8 (/dev/input/event12)
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (II) config/udev: Adding input device 5C:EB:68:2C:19:A8 (/dev/input/event12)
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (**) 5C:EB:68:2C:19:A8: Applying InputClass "evdev keyboard catchall"
Jan 25 23:49:41 pj-ultrabook gdm-x-session[3791]: (**) 5C:EB:68:2C:19:A8: Applying InputClass "evdev keyboard catchall"
Jan 25 23:49:41 pj-ultrabook gdm-x-session[3791]: (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 16 paused 1
Jan 25 23:49:41 pj-ultrabook gdm-x-session[3791]: (II) systemd-logind: releasing fd for 13:76
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 33 paused 0
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (II) Using input driver 'evdev' for '5C:EB:68:2C:19:A8'
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (**) 5C:EB:68:2C:19:A8: always reports core events
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (**) evdev: 5C:EB:68:2C:19:A8: Device: "/dev/input/event12"
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (--) evdev: 5C:EB:68:2C:19:A8: Vendor 0 Product 0
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (--) evdev: 5C:EB:68:2C:19:A8: Found keys
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (II) evdev: 5C:EB:68:2C:19:A8: Configuring as keyboard
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input14/event12"
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (II) XINPUT: Adding extended input device "5C:EB:68:2C:19:A8" (type: KEYBOARD, id 13)
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (**) Option "xkb_rules" "evdev"
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (**) Option "xkb_model" "pc104"
Jan 25 23:49:41 pj-ultrabook gdm-x-session[4089]: (**) Option "xkb_layout" "us"
|
Last edited by ppwaskie on Tue Jan 26, 2016 9:24 pm; edited 1 time in total |
|
| Back to top |
|
 |
ppwaskie
n00b
Joined: 10 Sep 2015
Posts: 12
|
| Posted: Tue Jan 26, 2016 4:31 pm Post subject: |
|
|
Some additional info from poking around last night:
It appears to me this is actually Pulseaudio causing the issues. I have two instances of pulseaudio running, one through GDM, the other through my user:
| Code: |
gdm 3933 1 0 09:18 ? 00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
pjw 4130 1 0 09:18 ? 00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
|
The problem is with the headphones paired, I still don't see the audio sink from the bluetooth headset show up in pacmd. This leads me to believe that pulseaudio isn't properly detecting the bluetooth headset once it connects, or can't create the new sink/source for some reason. Nothing is leaping out at me in /var/log/messages either.
The modules though for Pulseaudio are loaded for bluetooth auto-discovery:
| Code: |
$ pacmd list-modules
[...]
index: 8
name: <module-bluetooth-policy>
argument: <>
used: -1
load once: yes
properties:
module.author = "Frédéric Dalleau"
module.description = "When a bluetooth sink or source is added, load module-loopback"
module.version = "7.1"
index: 9
name: <module-bluetooth-discover>
argument: <>
used: -1
load once: yes
properties:
module.author = "João Paulo Rechi Vita"
module.description = "Detect available Bluetooth daemon and load the corresponding discovery module"
module.version = "7.1"
index: 10
name: <module-bluez5-discover>
argument: <>
used: -1
load once: yes
properties:
module.author = "João Paulo Rechi Vita"
module.description = "Detect available BlueZ 5 Bluetooth audio devices and load BlueZ 5 Bluetooth audio drivers"
module.version = "7.1"
|
I'm at a loss why this isn't working properly. Any input or suggestion is very welcome. |
|
| Back to top |
|
|
ppwaskie
n00b
Joined: 10 Sep 2015
Posts: 12
|
| Posted: Tue Jan 26, 2016 9:23 pm Post subject: |
|
|
I finally solved this. It was the issue with GDM starting an extra instance of pulseaudio, and taking the Bluetooth audio with it. The suggested way I intiially found to disable this didn't work, this is what worked for me:
| Code: |
# cat ~gdm/.config/pulse/client.conf
autospawn = no
daemon-binary = /bin/true
|
Add that file to that path with those contents, and at least restart X/GDM. I rebooted since it takes about 2 seconds to reboot, and it's working beautifully now. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Multimedia
