** Tags removed: ubuntu-touch
** Tags added: bluez-touch
** Changed in: bluez (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Tags added: ubuntu-touch
--
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/1419877
Title:
[bluetooth] krillin advertized as type "computer"
Status in Canonical System
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
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/1419877
Title:
[bluetooth] krillin
** Changed in: bluez (Ubuntu)
Status: In Progress => Fix Committed
--
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/1419877
Title:
[bluetooth] krillin advertized as
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => Fix Committed
** Changed in: canonical-devices-system-image
Milestone: None => ww40-2015
** Changed in: canonical-devices-system-image
This can get rather serios if remote device doesn't allow connection
with specific types of device like my carkit. It doesn't want to connect
with my krillin device as it has a wrong device type (being a laptop)
set.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
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/1419877
Title:
[bluetooth] krillin
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.
Fixing just the device class is pretty easy but we should bind this
somehow to the type of device we're running on. For tablets/phone that
doesn't make a difference but having a more general solution in place
which lets bluez determine the type of device on startup would be
optimal.
--
You
** Changed in: bluez (Ubuntu)
Status: Confirmed => In Progress
--
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/1419877
Title:
[bluetooth] krillin advertized as type
This is a matter of defining the right class in
/etc/bluetooth/main.conf. There are some generators out there like http
://bluetooth-pentest.narod.ru/software/bluetooth_class_of_device-
service_generator.html
For me it looks like 0x73020C would be what we should set as our COD:
Major Service
the bluez config mentions that only major and minor are used, so maybe
0x00020c then...
--
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/1419877
Title:
[bluetooth] krillin
The type from the Class defined in the configuration, default is
0x000100 for Computer, 0x40020C would correspond to a smartphone
instead. It doesn't seem we can change it from the settings/client side
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
13 matches
Mail list logo
