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 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 Image: New Status in bluez package in Ubuntu: Confirmed Bug description: Using rtm 228, the device is advertized as being a "computer", it should probably be a "phone" rather? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
