Ubuntu
bluez package

[bluetooth] krillin advertized as type "computer"

Bug #1419877 reported by Sebastien Bacher
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
John McAleely
Canonical System Image ww40-2015 "ota7"
bluez (Ubuntu)
Fix Released
Undecided
Simon Fels

Bug Description

Using rtm 228, the device is advertized as being a "computer", it should probably be a "phone" rather?

Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Revision history for this message
Sebastien Bacher (seb128) wrote :

the bluez config mentions that only major and minor are used, so maybe 0x00020c then...

John McAleely (john.mcaleely)
tags: added: bluetooth
Revision history for this message
Simon Fels (morphis) wrote :

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 Class Positioning, Networking, Object Transfer, Audio, Telephony
Major Device Class: Phone
Minor Device Class: Smartphone

Simon Fels (morphis)
Changed in bluez (Ubuntu):
assignee: nobody → Simon Fels (morphis)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
Simon Fels (morphis) wrote :

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.

Revision history for this message
Simon Fels (morphis) wrote :

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.

Simon Fels (morphis)
Changed in bluez (Ubuntu):
status: Confirmed → In Progress
Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
assignee: nobody → John McAleely (john.mcaleely)
importance: Undecided → High
milestone: none → ww40-2015
status: New → Fix Committed
Simon Fels (morphis)
Changed in bluez (Ubuntu):
status: In Progress → Fix Committed
Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
Daniel van Vugt (vanvugt)
tags: added: ubuntu-touch
Daniel van Vugt (vanvugt)
tags: added: bluez-touch
removed: ubuntu-touch
Changed in bluez (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.