The fix for this has landed in RTM: ubuntu-system-settings
(0.3+14.10.20140909~rtm-0ubuntu1).
It is now available in the proposed RTM image; so I'll mark this as Fix
Released.
** Changed in: bluez (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are
I also tried with: https://launchpad.net/~mathieu-tl/+archive/ubuntu/nv-
build/+build/6332014
But no change in result.
--
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/1364008
Title:
Cann
output from hcitool inq:
12:1F:83:05:03:B4 clock offset: 0x264cclass: 0x240414
--
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/1364008
Title:
Cannot pair with Altavoz Vivaldi B
Hmm, this didn't include the information I expected. Here's a different
command to use, again with the speaker in range:
hcitool inq
You should get a list of all the devices in range and their class, etc.;
the class information is what I need.
In the meantime, I'll dig in the code and make sure
Yes, this device does pair and work with the desktop successfully as
'audio device' type. See below for info from hcitool:
BD Address: 12:1F:83:05:03:B4
Device Name: Avrha Vivaldi
LMP Version: 2.0 (0x3) LMP Subversion: 0x2
Manufacturer: Accel Semiconductor Ltd. (74
Could this be tested on an Ubuntu desktop? I'd like to know what type
this device is saying it is; we already support most speakers as "Other"
audio devices, we support Headphones, Handsfree, etc.
Once connected, you should be able to figure out the state of the device
with the following command:
Note that this speaker is from the BQ store, so should work as a
priority
** Changed in: bluez (Ubuntu)
Importance: High => Critical
--
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/13640
7 matches
Mail list logo
