[Touch-packages] [Bug 1479445] Re: IN CAR: Signal Strength not shown in car display
It did. -- 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/1479445 Title: IN CAR: Signal Strength not shown in car display Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez package in Ubuntu RTM: New Bug description: STEPS: Requirement: DUT with active sim and car that supports Bluetooth phones (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Check the console display for the strength of signal EXPECTED: I expect the display to show a similar strength to that on the phone ACTUAL: The signal strength is always at 0% however the display does show the Network connected to so there is some sort of feedback via bluetooth that there is a connection. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Ananda: Can you please provide more details about what is not working and which exact steps you're performing with your Ubuntu phone? Also please provide logs with debug mode enabled. See https://wiki.ubuntu.com/DebuggingBluetooth for details how to enable this. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Mark: That is good to hear. My suspection now is that it's either a problem with the BT chipset firmware or something in in-kernel bluetooth management layer as the Meizu has a newer kernel than the BQ device (Meizu: 3.10, BQ: 3.4). -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
See https://bazaar.launchpad.net/~ubuntu- branches/ubuntu/wily/bluez/wily/view/head:/audio/telephony-ofono.c#L1346 for details. -- 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/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
The cause for this is that with the deprecation of HAL we also dropped battery query support from BlueZ and never brought it back. We need to interface BlueZ correct with upowerd so we can send out the correct battery level. -- 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/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479445] Re: IN CAR: Signal Strength not shown in car display
This comes from the fact that our BlueZ version still relies on an older API version of ofono as we have implemented. It listens for changes to a SignalStrength property on the org.ofono.NetworkRegistration interface which doesn't exist. The propery is named just Strength these days. See https://bazaar.launchpad.net/~ubuntu- branches/ubuntu/wily/bluez/wily/view/head:/audio/telephony-ofono.c#L922 and https://github.com/rilmodem/ofono/blob/master/doc/network- api.txt#L127 for more details. -- 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/1479445 Title: IN CAR: Signal Strength not shown in car display Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: STEPS: Requirement: DUT with active sim and car that supports Bluetooth phones (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Check the console display for the strength of signal EXPECTED: I expect the display to show a similar strength to that on the phone ACTUAL: The signal strength is always at 0% however the display does show the Network connected to so there is some sort of feedback via bluetooth that there is a connection. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Andriopoulos: Did you reboot after you executed the steps mentioned on https://wiki.ubuntu.com/Process/Merges/TestPlan/ubuntu-system- settings#Bluetooth-1 ? Those things will only be effective when you reboot so the relevant services get restarted (you could restart them manually but to keep the system in a sane state it's better to reboot). The log you attached doesn't has any bluetooth debug messages in it. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445376] Re: A2DP skips when conneted to handsfree device
Can someone who experience this problem here follow the steps on https://wiki.ubuntu.com/Process/Merges/TestPlan/ubuntu-system- settings#Bluetooth-1 so that we get logs files with debugging for bluetooth components enabled to further analyze what the problem here is? ** 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/1445376 Title: A2DP skips when conneted to handsfree device Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: When I connect my Aquaris E4.5 to my car's handsfree device (Funkwerk Ego Flash) via Bluetooth I experience a skipping problem when playing sound files through A2DP. Half a second for each second there is a pause. The rest of that half second seems to clear a buffer which results in extra fast audio. To illustrate, listening to a podcast I would expect to hear something like bla bla bla. However, what I do get to hear sounds more like flapflapflap - pause - flapflapflap - pause - When I connect my Aquaris to my A2DP speakers at home, the audio is perfect. Also, handsfree telephony in my car works like a charm. So I guess it's just the combination of A2DP while connected to the handsfree device which causes the trouble. In the past I've used several phones with the Funkwerk device (always with handsfree *and* A2DP functionality) including an N900 running Maemo. There have never been any problems with those. OS build number 21 KRILIN01A-S15A_BQ_L100EN_2021_150410 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Andriopoulos: I have some questions to the log file you attached: * Did you power off Bluetooth at some point through the UI? * You say calls but I only see one call being made in that log file. Can you please describe the exact steps you performed after you powered on your phone? * What is the exact model of the Car you're using? From the log you attached it looks like the HCI controller signals us that the Bluetooth device wents down so bluez is just reacting on incoming events and brings everything else also down: Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_added() /ril_1/voicecall01 Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() /ril_1/voicecall01 Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() state dialing Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() cli 6944* (number removed) Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() Multipary False Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() CALL_STATUS_DIALING Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.h:telephony_update_indicator() Telephony indicator callsetup 0-2 Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_network_property_changed() in handle_registration_property_changed(), the property is Strength Jul 31 19:39:10 ubuntu-phablet bluetoothd[854]: message repeated 2 times: [ audio/telephony.c:handle_network_property_changed() in handle_registration_property_changed(), the property is Strength] Jul 31 19:39:11 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() path /ril_1/voicecall01 Jul 31 19:39:11 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() property State Jul 31 19:39:11 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() State alerting Jul 31 19:39:11 ubuntu-phablet bluetoothd[854]: audio/telephony.h:telephony_update_indicator() Telephony indicator callsetup 2-3 Jul 31 19:39:12 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_network_property_changed() in handle_registration_property_changed(), the property is Strength Jul 31 19:39:17 ubuntu-phablet bluetoothd[854]: message repeated 2 times: [ audio/telephony.c:handle_network_property_changed() in handle_registration_property_changed(), the property is Strength] Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() path /ril_1/voicecall01 Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() property State Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() State disconnected Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_free() /ril_1/voicecall01 Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.h:telephony_update_indicator() Telephony indicator callsetup 3-0 Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_removed() /ril_1/voicecall01 [...] Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: plugins/mgmtops.c:mgmt_event() cond 1 Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: plugins/mgmtops.c:mgmt_event() Received 10 bytes from management socket Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: plugins/mgmtops.c:mgmt_new_settings() hci0 new settings Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: src/adapter.c:adapter_remove_connection() Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: audio/manager.c:state_changed() /org/bluez/854/hci0 powered off Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: audio/telephony.c:telephony_exit() Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: audio/telephony.c:modem_removed() /ril_1 Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: audio/headset.c:telephony_deinit() Telephony deinitialized Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: Adapter /org/bluez/854/hci0 has been disabled Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: src/adapter.c:set_mode_complete() This pretty much looks to me like problems in the lower communication layers (HCI, ..) and need more investigation. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a
[Touch-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type computer
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 -- 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: New 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1162781] Re: bluez package out of date, 5.23 is available in debian sid/jessie
We're actively working on getting this done and BlueZ 5.23 is being prepared and should soon appear in wily. There is a ppa already which has all necessary packages for vivid and wily (see https://launchpad.net /~ubuntu-desktop/+archive/ubuntu/transitions). If you want to help us testing those feel free to do so and report any problems. The Touch side of Ubuntu will be updated later too. -- 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/1162781 Title: bluez package out of date, 5.23 is available in debian sid/jessie Status in bluez package in Ubuntu: Triaged Bug description: Looks like there have been a lot of improvements to bluez since the 4.x series. Would be nice to get the latest release pulled in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Pat: Thanks for the pointer. @Mark: How should reverse engineering help here? Its simply an interoperability issue and we're using completely different software than Android does. However the interface to the BT chip is standardized so no need to reverse anything here. We need to find out where exactly this bug is and what we can do for it. Before we don't know that we can't start any coding. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482688] [NEW] Bluez reports quoted hostname
Public bug reported: At least on touch devices BlueZ reports a quoted hostname like Aquaris E4.5 Ubuntu Edition which is then send over to other devices including the quotes. bluetoothd[6402]: plugins/adaptername.c:set_pretty_name() Setting name 'Aquaris E4.5 Ubuntu Edition' for device 'hci0' bluetoothd[6402]: plugins/mgmtops.c:mgmt_set_name() index 0, name Aquaris E4.5 Ubuntu Edition BlueZ reads the hostname from /etc/machine-info on startup which has the following set PRETTY_HOSTNAME=Aquaris E4.5 Ubuntu Edition Code in BlueZ needs to be changed to ignore the quotes from the value. ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: In Progress ** Tags: bluetooth ** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Simon Fels (morphis) ** Changed in: bluez (Ubuntu) Status: New = 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/1482688 Title: Bluez reports quoted hostname Status in bluez package in Ubuntu: In Progress Bug description: At least on touch devices BlueZ reports a quoted hostname like Aquaris E4.5 Ubuntu Edition which is then send over to other devices including the quotes. bluetoothd[6402]: plugins/adaptername.c:set_pretty_name() Setting name 'Aquaris E4.5 Ubuntu Edition' for device 'hci0' bluetoothd[6402]: plugins/mgmtops.c:mgmt_set_name() index 0, name Aquaris E4.5 Ubuntu Edition BlueZ reads the hostname from /etc/machine-info on startup which has the following set PRETTY_HOSTNAME=Aquaris E4.5 Ubuntu Edition Code in BlueZ needs to be changed to ignore the quotes from the value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1482688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482688] Re: Bluez reports quoted hostname
Fix in https://code.launchpad.net/~morphis/bluez/unquote-hostname -- 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/1482688 Title: Bluez reports quoted hostname Status in bluez package in Ubuntu: In Progress Bug description: At least on touch devices BlueZ reports a quoted hostname like Aquaris E4.5 Ubuntu Edition which is then send over to other devices including the quotes. bluetoothd[6402]: plugins/adaptername.c:set_pretty_name() Setting name 'Aquaris E4.5 Ubuntu Edition' for device 'hci0' bluetoothd[6402]: plugins/mgmtops.c:mgmt_set_name() index 0, name Aquaris E4.5 Ubuntu Edition BlueZ reads the hostname from /etc/machine-info on startup which has the following set PRETTY_HOSTNAME=Aquaris E4.5 Ubuntu Edition Code in BlueZ needs to be changed to ignore the quotes from the value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1482688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Mark: You can. Follow https://wiki.ubuntu.com/DebuggingBluetooth to generate logs with debugging statements and then please attach them here. But please check those for any private data before or send them to me by private mail. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484980] Re: AVRCP support for Ubuntu Phone
** Tags added: bluetooth -- 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/1484980 Title: AVRCP support for Ubuntu Phone Status in bluez package in Ubuntu: Confirmed Bug description: Hey! I bought a bluetooth headphone, but the volume, next and previous track buttons don't work with my Ubuntu Phone, because it doesn't support AVRCP. So please implement this feature. :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1484980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479445] Re: IN CAR: Signal Strength not shown in car display
It should. -- 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/1479445 Title: IN CAR: Signal Strength not shown in car display Status in Canonical System Image: New Status in bluez package in Ubuntu: Triaged Bug description: STEPS: Requirement: DUT with active sim and car that supports Bluetooth phones (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Check the console display for the strength of signal EXPECTED: I expect the display to show a similar strength to that on the phone ACTUAL: The signal strength is always at 0% however the display does show the Network connected to so there is some sort of feedback via bluetooth that there is a connection. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Peter: Address book download isn't really implemented today. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Simon: Really? Then I just didn't found the pointers in the code ... -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475608] Re: bluetooth dual sim
@seb128 Yeah this is really related. As Alfsono already said the selection of the modem device is currently not deterministic and needs to be tweaked in order to be reliable. -- 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/1475608 Title: bluetooth dual sim Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: Hi, I have a BQ phone with 2 SIM-cards. When connected to my handsfree-set (built-in radio set Opel), it shows the provider of my 2nd SIM. When someone phones me on SIM 1, it doesn't go to the hands-free set. But I when I answer the phone (while still connected with BT), I cannot hear the other person, nor does he hear me. Calls on SIM 2 are working as expected. Regards, Carl To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506988] Re: Update ofono.override plugin excludes ( -P ) for bluez5
** Changed in: lxc-android-config (Ubuntu RTM) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1506988 Title: Update ofono.override plugin excludes ( -P ) for bluez5 Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu RTM: Fix Committed Bug description: The ofono upstart override file includes an updated exec line for ofono with a different set of plugins excluded vs. the upstart job shipped as part of the ofono package. The '-P' argument is a comma-separated list of plugins to exclude at startup. ofono internally uses g_pattern_match_simple to process this list, which means the patterns are glob-style, and support the wildcard '*' and '?' characters per https://developer.gnome.org/glib/2.28/glib-Glob-style-pattern- matching.html The upstart job shipped in the archive's ofono package specifies a single plugin to exclude, 'ril', which is the device plugin used on touch devices only. Note, this job should also probably exclude the 'rildev' plugin as well. As such, we probably should change the upstart job to specify "-P ril*". The current excludes list in the overlay PPA is: -P stktest,provision,sap,udev,dun,smart,hfp 'stktest' can be removed as it's only included in the builtin_modules list if ofono is built with MAINTAINER_MODE defined. 'dun' can be removed as there's no plugin with that name. Note, for bluez5, we've added "dun_gw_bluez5" to the list. We should just combine the two and specify "dun*". 'sap' ( SIM Access Profile ) can be removed when we land bluez5, as it's only defined if ofono is built against bluez4. 'smart' isn't doing anything by itself, as the plugin is really named "smart_messaging". 'udev' only prevents the original udev plugin from loading, it doesn't prevent udevng from being loaded. This should probably be changed to "udev*" to prevent problems on a device where a collision might occur between the udev plugins and the rildev plugin. So, the recommended command line once we land bluez5 should be: exec ofonod -P provision,udev*,dun*,smart*,hfp_bluez5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511029] Re: Audio gets confused when playing from source after playing from playlist
** Changed in: media-hub (Ubuntu) Status: Invalid => New ** Changed in: media-hub (Ubuntu RTM) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1511029 Title: Audio gets confused when playing from source after playing from playlist Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: New Status in qtmultimedia-opensource-src package in Ubuntu: New Status in media-hub package in Ubuntu RTM: New Bug description: Can be reproduced using silo 4 as of today. How to reproduce: 1. Go to the Tracks department on the My Music scope 2. Press the Play icon on song 1 3. Go to preview of song 2 (by clicking anywhere except on the Play icon) 4. Play song 2 from the preview (by pressing the small play icon at the bottom) 5. Notice how song 1 is playing instead of song 2 After this lots of things break but probably related to the same issue To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: BLE pairing fail
@pitti: Yes, they implemented it to allow us to replace our hack udev rule (https://bazaar.launchpad.net/~bluetooth/bluez/ubuntu/view/head:/debian/50 -bluetooth-hci-auto-poweron.rules) with that. "that some distributions " includes Ubuntu. -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505241] Re: Phone did not suspend
The wakeup source hold here "MT662x" is the combo connectivity chip responsible for WiFi/BT/GPS. @Pat: Can you describe a bit more what you did with the device before this happened or what it was connected to? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone did not suspend Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: Confirmed Bug description: Noticed a quick batter drain, no idea what was keeping it awake all day and night. MX4 running proposed 136 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398193] Re: The bluetooth headset can not control the video playback
Nothing we have to change on media-hub just need to enable bluez to forward those events to media-hub. Will come with bluez5. ** Changed in: media-hub (Ubuntu) Status: Confirmed => Invalid ** Changed in: media-hub (Ubuntu RTM) Status: New => Invalid -- 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/1398193 Title: The bluetooth headset can not control the video playback Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in media-hub package in Ubuntu: Invalid Status in media-hub package in Ubuntu RTM: Invalid Bug description: [Preconditions] 1.The DUT pair with bluetooth headset [Procedures] 1.Play a video using the mediaplayer-app 2.Play/pause video by bluetooth headset [Expect results] The bluetooth headset can play/pause video [Actual results] The bluetooth headset can not control the video playback. [Reproduce] Always To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398193] Re: The bluetooth headset can not control the video playback
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => In Progress ** 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/1398193 Title: The bluetooth headset can not control the video playback Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in media-hub package in Ubuntu: Confirmed Status in media-hub package in Ubuntu RTM: New Bug description: [Preconditions] 1.The DUT pair with bluetooth headset [Procedures] 1.Play a video using the mediaplayer-app 2.Play/pause video by bluetooth headset [Expect results] The bluetooth headset can play/pause video [Actual results] The bluetooth headset can not control the video playback. [Reproduce] Always To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505241] Re: Phone does not suspend
** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1505241 Title: Phone does not suspend Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: In Progress Bug description: I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior According to the logs they are not able to suspend due to active wakeup sources. (I am running a BT test kernel on the MX4 3.10.35+) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505241] Re: Phone does not suspend
Worth to mentioned but doesn't prove anything yet: When turning bluetooth off Nov 13 06:06:18 ubuntu-phablet kernel: [60938.696811] [HCI-STP][I]hci_stp_close:hdev(0xd91de000) Nov 13 06:06:18 ubuntu-phablet kernel: [60938.696829] [HCI-STP][I]hci_stp_flush:done Nov 13 06:06:18 ubuntu-phablet kernel: [60938.696841] Flush type = 0 Rx Queue Nov 13 06:06:18 ubuntu-phablet kernel: [60938.696856] BT OFF >>sec=1447394778, usec=940213 Nov 13 06:06:18 ubuntu-phablet kernel: [60938.710524] BT OFF <>sec=1447394778, usec=953871 Nov 13 06:06:18 ubuntu-phablet kernel: [60938.710541] [HCI-STP][I]hci_stp_close:WMT turn off BT OK! Nov 13 06:06:18 ubuntu-phablet kernel: [60938.742769] [CONN-MD-DFT][I]conn_md_thread:no msg queued in msg queue... Nov 13 06:06:35 ubuntu-phablet kernel: [60955.707955] PM: suspend entry 2015-11-13 06:06:35.951294414 UTC Nov 13 06:06:35 ubuntu-phablet kernel: [60955.707976] PM: Syncing filesystems ... done. Nov 13 06:06:35 ubuntu-phablet kernel: [60955.732748] Freezing user space processes ... Nov 13 06:06:35 ubuntu-phablet kernel: [60955.733966] active wakeup source: MT662x Nov 13 06:06:35 ubuntu-phablet kernel: [60955.733995] Nov 13 06:06:35 ubuntu-phablet kernel: [60955.734010] Freezing of tasks aborted after 0.001 seconds (24 tasks refusing to freeze, wq_busy=0): Nov 13 06:06:35 ubuntu-phablet kernel: [60955.734051] Nov 13 06:06:35 ubuntu-phablet kernel: [60955.734060] Restarting tasks ... done. Nov 13 06:06:35 ubuntu-phablet kernel: [60955.736030] msdc: 0,mmc_schedule_delayed_work ret= 1 Nov 13 06:06:35 ubuntu-phablet kernel: [60955.736098] PM: suspend exit 2015-11-13 06:06:35.979446414 UTC Nov 13 06:06:35 ubuntu-phablet kernel: [60955.736116] WQ warning! work (try_to_suspend, c0eaab2c) execute more than 1 sec, time: 635923103499 ns So suspend still fails even if BT is turned off. -- 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/1505241 Title: Phone does not suspend Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: In Progress Bug description: I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior According to the logs they are not able to suspend due to active wakeup sources. (I am running a BT test kernel on the MX4 3.10.35+) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505241] Re: Phone does not suspend
I tried to reproduce this with two MX4: - First one running rc-proposed, the newer kernel with upgraded bluetooth stack and bluez4. - Second one running rc-proposed, the newer kernel with upgraded bluetooth stack and bluez5. Pat was running the first combination. I saw similar kernel suspend aborts due to the wakeup source MT662x being still active but not such a huge battery drain as Pat had. My battery only lost around 15-20% in ~20h where I just plugged it into my laptop for a few min to fetch a recent syslog in between. The rest of the time the phone was just laying around being paired and connect to a bluetooth device, being connected to a WiFi network and got a GPS fix before I turned the screen off. Statistics look like this: Resume wakeup causes: EINT, 909 100.00% Suspend failure causes: tasks freezer abort 536 99.81% devices failed to suspend 1 0.19% Suspends: 588 suspends aborted (39.28%). 909 suspends succeeded (60.72%). total time: 10361.993895 seconds (87.08%). minimum: 0.400780 seconds. maximum: 74.526359 seconds. mean: 11.399333 seconds. mode: 14.00 seconds. median: 13.158011 seconds. Time between successful suspends: total time: 1537.561435 seconds (12.92%). minimum: 0.897107 seconds. maximum: 11.649660 seconds. mean: 1.693350 seconds. mode: 1.00 seconds. median: 1.030588 seconds. ** Attachment added: "syslog-mx4-bluez5-new-kernel-reproduced" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4517989/+files/syslog-mx4-bluez5-new-kernel-reproduced -- 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/1505241 Title: Phone does not suspend Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: In Progress Bug description: I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior According to the logs they are not able to suspend due to active wakeup sources. (I am running a BT test kernel on the MX4 3.10.35+) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505241] Re: Phone does not suspend
Disabling WiFi as next step lets the device suspend (but being woken up by EINT shortly afterwards again). -- 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/1505241 Title: Phone does not suspend Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: In Progress Bug description: I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior According to the logs they are not able to suspend due to active wakeup sources. (I am running a BT test kernel on the MX4 3.10.35+) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390532] Re: [Bluetooth] Attempt to pair using default pin of 0000 before prompting the user
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Importance: Undecided => Medium
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Triaged => Invalid
** Tags added: after-bluez5
--
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/1390532
Title:
[Bluetooth] Attempt to pair using default pin of before prompting
the user
Status in bluez package in Ubuntu:
In Progress
Status in ubuntu-system-settings package in Ubuntu:
Invalid
Bug description:
Per the design at https://wiki.ubuntu.com/Bluetooth#phone
If the device is of a type that usually has the PIN “” (a headset,
keyboard, or mouse), Ubuntu should try this first. If that doesn’t
work, or for any other kind of device, a ‘PIN for “{headset name}”’ or
‘Passkey for “{headset name}”’ dialog should appear, with a
PIN/passkey field that uses a number-based keyboard.
It is not clear whether the input field should still display
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1390532/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505241] Re: Phone does not suspend
Generally I see aborted suspends because of the MT662x wakeup source also on rc-proposed with its current kernel but not in such a high frequency as Pat or I saw them before. -- 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/1505241 Title: Phone does not suspend Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: In Progress Bug description: I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior According to the logs they are not able to suspend due to active wakeup sources. (I am running a BT test kernel on the MX4 3.10.35+) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505241] Re: Phone does not suspend
** Changed in: bluez (Ubuntu) Status: New => In Progress ** 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/1505241 Title: Phone does not suspend Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: In Progress Bug description: I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior According to the logs they are not able to suspend due to active wakeup sources. (I am running a BT test kernel on the MX4 3.10.35+) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
** Tags added: after-bluez5 -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421249] Re: bluetooth can not be enabled sometimes (when booting with flight mode on being one case)
The case where we reboot with flight mode being enable is still valid. I did some further analysis on this as I stumbled upon this again during my current BlueZ 5 work and the underlaying problems goes down to the kernel. The bluetooth driver we have on krillin isn't implemented as a module but is initialized by a subsystem it uses. It now turns out that this is bound to the WiFi driver being initialized too. If WiFi doesn't get enabled at boot time the Bluetooth driver can proceed providing a HCI device and we end up without any Bluetooth functionality. Needs further investigation on the kernel side what we can do to work around this. ** Tags added: krillin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1421249 Title: bluetooth can not be enabled sometimes (when booting with flight mode on being one case) Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: Triaged Status in urfkill package in Ubuntu: Triaged Bug description: The bluetooth indicator and the bluetooth page in system settings sometimes won't turn on bluetooth until after a reboot. What I expect to happen is that if bluetooth is off in the indicator/system settings and I tap the switch, the switch will go green and in a moment the bluetooth indicator will show up and bluetooth is enabled. When bluetooth is on, I expect to go into the indicator/system settings and turn the switch off, the switch will go gray and the bluetooth indicator will hide and bluetooth is disabled. I expect this to work whenever I want while the phone is on. Sometimes, this does not work. For example, yesterday I disabled bluetooth at some point in the evening and later I went to sleep. When I woke up, I tried to turn it on via the indicator and also system settings and it wouldn't turn on. In the indicator, the switch moves to the green position briefly, then moves back to gray (the bluetooth indicator remains hidden and bluetooth is disabled). In system settings, the switch will stay green, but the bluetooth indicator remains hidden and bluetooth is disabled. If I leave system settings and come back, the the switch is now in the off position. /var/lib/urfkill/saved-states has: [BLUETOOTH] soft=false prev-soft=false bluetoothd is confirmed to be running before and after using the indicator and system settings when bluetooth cannot be enabled. Workaround: reboot the phone and bluetooth will be enabled. Note: this is not new behavior-- I'm only reporting it now (partly because I thought it was fixed for a while, but that might have been because I was rebooting a lot at the time) $ system-image-cli -i current build number: 194 device name: mako channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-02-11 15:34:27 version version: 194 version ubuntu: 20150211.1 version device: 20150116 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506340] [NEW] Multimedia audio is routed for half of a second through HFP SCO after call has ended
Public bug reported: When playing audio through A2DP and a call comes in, gets accepted and finishes after some time the multimedia audio will start again after the call but is played for half of a second either through the phone speaker or HFP SCO channel rather than only being played again through A2DP as it was before the call. This happens with BlueZ 4.x and 5.x and is related to how we handle the audio routing setup currently. The telepathy-ofono service currently switches the different ports, sinks, sources and profiles of our PulseAudio elements to enable everything needed to do a voicecall and to switch things back correctly once the voicecall is done. The issue described above is the result of either a incorrect sequence of enabling/disbling things or bound to timing issues when the switching is done. We need to do some more analysis on the routing in PulseAudio and how telepathy-ofono does things. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth bluez5 ** Also affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- 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/1506340 Title: Multimedia audio is routed for half of a second through HFP SCO after call has ended Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: When playing audio through A2DP and a call comes in, gets accepted and finishes after some time the multimedia audio will start again after the call but is played for half of a second either through the phone speaker or HFP SCO channel rather than only being played again through A2DP as it was before the call. This happens with BlueZ 4.x and 5.x and is related to how we handle the audio routing setup currently. The telepathy-ofono service currently switches the different ports, sinks, sources and profiles of our PulseAudio elements to enable everything needed to do a voicecall and to switch things back correctly once the voicecall is done. The issue described above is the result of either a incorrect sequence of enabling/disbling things or bound to timing issues when the switching is done. We need to do some more analysis on the routing in PulseAudio and how telepathy-ofono does things. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1499789] Re: BLUEZ5: Connecting a keyboard shows no pin popup
** Summary changed: - BLUEZ5: Connecting a keyboard shows no pip popup + BLUEZ5: Connecting a keyboard shows no pin popup -- 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/1499789 Title: BLUEZ5: Connecting a keyboard shows no pin popup Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: You can not connect to a pin required keyboard as the dialogue is not shown. This means that the device for all intents and purposes looks to be connected, but if you disconnect from it you can not reconnect and the device doesn't actually type anything because although it looks connected it actually isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1499789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1501825] Re: Bq Aquaris e5 HD bluetooth problem
We will release a fully updated bluetooth stack soon to the images and this hopefully improves this interoperability issue. If not we will take further actions from there. -- 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/1501825 Title: Bq Aquaris e5 HD bluetooth problem Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: I hawe bq Aquaris e5 hd problem conect bluetooth with caraudio Clarion on Nissan Tiida. Pairing takes place in order. Near the radio display Conect fail and disconnected cell phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1501825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494230] Re: Audio is not routed to A2DP sink when connected
** Changed in: bluez (Ubuntu) Status: New => Invalid ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: pulseaudio (Ubuntu) Status: New => 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/1494230 Title: Audio is not routed to A2DP sink when connected Status in Canonical System Image: New Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Committed Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed. * Pair/connect A2DP sink device * Play any audio -> Audio is not played on A2DP sink and also not on speakers To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1499789] Re: BLUEZ5: Connecting a keyboard shows no pin popup
** Changed in: bluez (Ubuntu) Status: New => 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/1499789 Title: BLUEZ5: Connecting a keyboard shows no pin popup Status in Canonical System Image: New Status in bluez package in Ubuntu: In Progress Bug description: You can not connect to a pin required keyboard as the dialogue is not shown. This means that the device for all intents and purposes looks to be connected, but if you disconnect from it you can not reconnect and the device doesn't actually type anything because although it looks connected it actually isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1499789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic
** Tags removed: bluez5 ** Tags added: after-bluez5 -- 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/1499858 Title: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic Status in bluez package in Ubuntu: Confirmed Bug description: sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link Loss service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service could not be registered sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: Input/output error (5) sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free handles to register service sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver initialization failed. sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation not permitted (1) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.34-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 25 16:37:42 2015 InstallationDate: Installed on 2015-07-26 (61 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) InterestingModules: rfcomm bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:6C:01:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0 TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1499858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494242] Re: Try to auto connect devices when user enables bluetooth
** Changed in: canonical-devices-system-image 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/1494242 Title: Try to auto connect devices when user enables bluetooth Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: When bluetooth gets enabled by the user we should try to connect all devices we're currently paired with and which are marked as trusted. This will help to improve the user experience that the user will get his configured devices connected right away. Android does this similar. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1499789] Re: BLUEZ5: Connecting a keyboard shows no pin popup
** Branch linked: lp:~morphis/ubuntu-system-settings/bluez5-support ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: canonical-devices-system-image 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/1499789 Title: BLUEZ5: Connecting a keyboard shows no pin popup Status in Canonical System Image: New Status in bluez package in Ubuntu: In Progress Bug description: You can not connect to a pin required keyboard as the dialogue is not shown. This means that the device for all intents and purposes looks to be connected, but if you disconnect from it you can not reconnect and the device doesn't actually type anything because although it looks connected it actually isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1499789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Changed in: ofono (Ubuntu) Assignee: (unassigned) => Tony Espy (awe) ** Tags added: bluez5 -- 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/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: In Progress Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375766] Re: Phone gives wrong capabilities over bluetooth
Can you please elaborate a bit more on what you think doesn't work? I am not sure I fully understand what you describe as bug here. -- 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/1375766 Title: Phone gives wrong capabilities over bluetooth Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: USED SW: current build number: 73 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-09-30 14:12:10 version version: 73 version ubuntu: 20140930 version device: 20140925-6623bf1 version custom: 1411735617 TEST STEPS: 1. Play music in iphone 4S 2. Connect krillin to iphone by bluetooth EXPECTED RESULT Connection is established without extra side effects ACTUAL RESULT: Krillin starts to play the music which is listened in iphone. Theory: Presumably krillin is broadcasting wrong bluetooth capablities To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1375766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506774] Re: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (without linux-image-extra*)
We could just bind this to the condition if /sys/class/bluetooth is available or not. So a ... ConditionPathIsDirectory=/sys/class/bluetooth -- 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/1506774 Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (without linux-image-extra*) Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in bluez source package in Vivid: New Status in bluez source package in Wily: Confirmed Bug description: Bluez installation fails on vivid and wily without linux-image-extra* because BT kernel modules are unavailable. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Thu Oct 15 22:06:50 2015 DuplicateSignature: package:bluez:5.35-0ubuntu1:subprocess installed post-installation script returned error exit status 1 Ec2AMI: ami-0f6e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: cpu10-ram10-disk10-ephemeral20 Ec2Kernel: aki-022a Ec2Ramdisk: ari-022a ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: bnep bluetooth Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.10.2ubuntu1 SourcePackage: bluez Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.3 dmi.sys.vendor: OpenStack Foundation hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1506774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506988] Re: Update ofono.override plugin excludes ( -P ) for bluez5
** Branch linked: lp:~morphis/lxc-android-config/bluez5-support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1506988 Title: Update ofono.override plugin excludes ( -P ) for bluez5 Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu RTM: In Progress Bug description: The ofono upstart override file includes an updated exec line for ofono with a different set of plugins excluded vs. the upstart job shipped as part of the ofono package. The '-P' argument is a comma-separated list of plugins to exclude at startup. ofono internally uses g_pattern_match_simple to process this list, which means the patterns are glob-style, and support the wildcard '*' and '?' characters per https://developer.gnome.org/glib/2.28/glib-Glob-style-pattern- matching.html The upstart job shipped in the archive's ofono package specifies a single plugin to exclude, 'ril', which is the device plugin used on touch devices only. Note, this job should also probably exclude the 'rildev' plugin as well. As such, we probably should change the upstart job to specify "-P ril*". The current excludes list in the overlay PPA is: -P stktest,provision,sap,udev,dun,smart,hfp 'stktest' can be removed as it's only included in the builtin_modules list if ofono is built with MAINTAINER_MODE defined. 'dun' can be removed as there's no plugin with that name. Note, for bluez5, we've added "dun_gw_bluez5" to the list. We should just combine the two and specify "dun*". 'sap' ( SIM Access Profile ) can be removed when we land bluez5, as it's only defined if ofono is built against bluez4. 'smart' isn't doing anything by itself, as the plugin is really named "smart_messaging". 'udev' only prevents the original udev plugin from loading, it doesn't prevent udevng from being loaded. This should probably be changed to "udev*" to prevent problems on a device where a collision might occur between the udev plugins and the rildev plugin. So, the recommended command line once we land bluez5 should be: exec ofonod -P provision,udev*,dun*,smart*,hfp_bluez5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506988] Re: Update ofono.override plugin excludes ( -P ) for bluez5
** Changed in: lxc-android-config (Ubuntu RTM) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1506988 Title: Update ofono.override plugin excludes ( -P ) for bluez5 Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu RTM: In Progress Bug description: The ofono upstart override file includes an updated exec line for ofono with a different set of plugins excluded vs. the upstart job shipped as part of the ofono package. The '-P' argument is a comma-separated list of plugins to exclude at startup. ofono internally uses g_pattern_match_simple to process this list, which means the patterns are glob-style, and support the wildcard '*' and '?' characters per https://developer.gnome.org/glib/2.28/glib-Glob-style-pattern- matching.html The upstart job shipped in the archive's ofono package specifies a single plugin to exclude, 'ril', which is the device plugin used on touch devices only. Note, this job should also probably exclude the 'rildev' plugin as well. As such, we probably should change the upstart job to specify "-P ril*". The current excludes list in the overlay PPA is: -P stktest,provision,sap,udev,dun,smart,hfp 'stktest' can be removed as it's only included in the builtin_modules list if ofono is built with MAINTAINER_MODE defined. 'dun' can be removed as there's no plugin with that name. Note, for bluez5, we've added "dun_gw_bluez5" to the list. We should just combine the two and specify "dun*". 'sap' ( SIM Access Profile ) can be removed when we land bluez5, as it's only defined if ofono is built against bluez4. 'smart' isn't doing anything by itself, as the plugin is really named "smart_messaging". 'udev' only prevents the original udev plugin from loading, it doesn't prevent udevng from being loaded. This should probably be changed to "udev*" to prevent problems on a device where a collision might occur between the udev plugins and the rildev plugin. So, the recommended command line once we land bluez5 should be: exec ofonod -P provision,udev*,dun*,smart*,hfp_bluez5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506774] Re: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (without linux-image-extra*)
Great! -- 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/1506774 Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (without linux-image-extra*) Status in bluez package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Won't Fix Status in bluez source package in Vivid: New Status in bluez source package in Wily: Fix Committed Bug description: Bluez installation fails on vivid and wily without linux-image-extra* because BT kernel modules are unavailable. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Thu Oct 15 22:06:50 2015 DuplicateSignature: package:bluez:5.35-0ubuntu1:subprocess installed post-installation script returned error exit status 1 Ec2AMI: ami-0f6e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: cpu10-ram10-disk10-ephemeral20 Ec2Kernel: aki-022a Ec2Ramdisk: ari-022a ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: bnep bluetooth Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.10.2ubuntu1 SourcePackage: bluez Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.3 dmi.sys.vendor: OpenStack Foundation hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1506774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506774] Re: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (without linux-image-extra*)
There is nothing we can do from bluez side. If the kernel interface we need to do *any* work is not available we can't do anything else but fail. The "bluetooth" module needs to be loaded or the kernel compiled with CONFIG_BT=y rather than CONFIG_BT=m. Is there any reason not to compile bluetooth support directly into the kernel? Any driver can still be loaded as module but the subsystem should be always available. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: bluetooth -- 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/1506774 Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (without linux-image-extra*) Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Status in bluez source package in Wily: Confirmed Status in linux source package in Wily: New Bug description: Bluez installation fails on vivid and wily without linux-image-extra* because BT kernel modules are unavailable. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Thu Oct 15 22:06:50 2015 DuplicateSignature: package:bluez:5.35-0ubuntu1:subprocess installed post-installation script returned error exit status 1 Ec2AMI: ami-0f6e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: cpu10-ram10-disk10-ephemeral20 Ec2Kernel: aki-022a Ec2Ramdisk: ari-022a ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: bnep bluetooth Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.10.2ubuntu1 SourcePackage: bluez Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.3 dmi.sys.vendor: OpenStack Foundation hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1506774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323837] Re: Sim toolkit is not available on UT
Some code we can base our work on is in https://github.com/meego-tablet- ux/meego-app-satk However we need to be able to process requests from STK in the background to push notifications or other requests. We maybe can put in a small plugin into ofono which triggers this when the STK agent should be triggered but is suspended or not available. As a further note: I talked with Tony (awe) a week ago and he said from the ofono side there should be nothing left to do for STK support. @Tony: Can you confirm that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1323837 Title: Sim toolkit is not available on UT Status in Canonical System Image: New Status in Ubuntu UX: New Status in ofono package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ /SIM-Toolkit While a lot of those addons are completely crap and useless, the SIm toolkit is sometimes used by some phone provider to set your sim card to roaming mode when you are abroad which makes it a must have. For the moment i need to borrow a second phone put my sim card in it, go to the Sim-toolkit, enable my sim card for roaming and put the sim card back in my UT to get my phone working while i am abroad. I need to do the same when i go back home. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1323837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505213] [NEW] Multiple bluetooth audio devices break audio routing
Public bug reported: When connecting multiple bluetooth audio devices the audio routing doesn't behave as it should. When multiple devices are connected which support A2DP for example we have to * Pick one which becomes the active one * When the active one disappears (disconnected, out-of-range) we need to pick the next one and set it as the active Right now the result is not constant when connecting multiple devices: * bluez and PA (mainly PA) try to setup all devices not respecting if one is already active * when disconnecting the active one the previously not-active one doesn't become active and stays unused Also we need to check if telepathy-ofono takes always the right audio card from PA to setup the audio routing for voicecalls. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Affects: telepathy-ofono (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Tags: after-bluez5 bluetooth ** Tags removed: bluez5 ** Tags added: after-bluez5 ** Description changed: When connecting multiple bluetooth audio devices the audio routing doesn't behave as it should. When multiple devices are connected which support A2DP for example we have to * Pick one which becomes the active one * When the active one disappears (disconnected, out-of-range) we need to pick the next one and set it as the active Right now the result is not constant when connecting multiple devices: * bluez and PA (mainly PA) try to setup all devices not respecting if one is already active * when disconnecting the active one the previously not-active one doesn't become active and stays unused + + Also we need to check if telepathy-ofono takes always the right audio + card from PA to setup the audio routing for voicecalls. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: telepathy-ofono (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: pulseaudio (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/1505213 Title: Multiple bluetooth audio devices break audio routing Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: When connecting multiple bluetooth audio devices the audio routing doesn't behave as it should. When multiple devices are connected which support A2DP for example we have to * Pick one which becomes the active one * When the active one disappears (disconnected, out-of-range) we need to pick the next one and set it as the active Right now the result is not constant when connecting multiple devices: * bluez and PA (mainly PA) try to setup all devices not respecting if one is already active * when disconnecting the active one the previously not-active one doesn't become active and stays unused Also we need to check if telepathy-ofono takes always the right audio card from PA to setup the audio routing for voicecalls. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396700] Re: Indicator needs to be updated to bluez5
Work for the vivid stable overlay is in https://code.launchpad.net/~morphis/indicator-bluetooth/merge-with- wily/+merge/269332 which will be landed with https://requests.ci- train.ubuntu.com/#/ticket/242 together with all other BlueZ 5 bits ** Changed in: indicator-bluetooth (Ubuntu RTM) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: indicator-bluetooth (Ubuntu RTM) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1396700 Title: Indicator needs to be updated to bluez5 Status in Canonical System Image: In Progress Status in indicator-bluetooth package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu RTM: In Progress Bug description: See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for details To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1396700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494225] Re: Call audio is not routed to headset with HFP
This is fixed now and working with silo 43 and 52. ** Changed in: media-hub (Ubuntu) Status: New => Invalid ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: bluez (Ubuntu) Status: New => Fix Committed ** Changed in: pulseaudio (Ubuntu) Status: New => 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/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: New Status in bluez package in Ubuntu: Fix Committed Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Committed Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505692] [NEW] Show connected Bluetooth profiles in settings application
Public bug reported: Right now the user doesn't have any way to find out on which Bluetooth profiles he is connected. The only thing he knows from the settings app or the bluetooth indicator is that he is connected in some way with a remote bluetooth device. Android for example allows you to select for what you want to use a known and auto connectable bluetooth device. For example it lists: * phone audio * media audio * contact sharing where each of those points is an alias for one or more profiles (phone audio: HFP/HSP, media-audio: A2DP AVCTP .., contact-sharing: PBAP). We should at minimum list the profiles the user is connected to at the moment in the settings application on the device information page. On a next level we could implement a allow/deny preference for a device or something similar. ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Tags: after-bluez5 bluetooth ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New -- 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/1505692 Title: Show connected Bluetooth profiles in settings application Status in Ubuntu UX: New Status in bluez package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: Right now the user doesn't have any way to find out on which Bluetooth profiles he is connected. The only thing he knows from the settings app or the bluetooth indicator is that he is connected in some way with a remote bluetooth device. Android for example allows you to select for what you want to use a known and auto connectable bluetooth device. For example it lists: * phone audio * media audio * contact sharing where each of those points is an alias for one or more profiles (phone audio: HFP/HSP, media-audio: A2DP AVCTP .., contact-sharing: PBAP). We should at minimum list the profiles the user is connected to at the moment in the settings application on the device information page. On a next level we could implement a allow/deny preference for a device or something similar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1505692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448472] Re: I can not connect phone with bluetooth with Lexus 400 RX 400H
** Tags added: after-bluez5 bluetooth -- 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/1448472 Title: I can not connect phone with bluetooth with Lexus 400 RX 400H Status in bluez package in Ubuntu: Expired Bug description: Both are detected each other but the connection is not done so I cantón not registre the phone un the car To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1448472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504057] Re: Bluetooth icon should turn blue when there's traffic happening
This gets a bit tricky when you want to define what actual "traffic" you want to indicate. Just count HCI frames on the link doesn't make sense as those don't mean anything goes to a remote device. This should be more or less happen on a per-profile level. When a profile becomes connected this needs to be indicated somehow. I've pushed support for this yesterday upstream (see http://article.gmane.org/gmane.linux.bluez.kernel/64957). This is something we could reflect in the indicator details or in the settings app. The indicator icon should only reflect that bluetooth is turned on and that we're connected. IMHO putting more details into this tiny icon just overloads it with too much details. The other part is for the special use case of a profile. Indicating that we're playing music is really up to the sound indicator. If you want a clearer indicator where your audio goes to than this needs to be reflected in the sound indicator too. We don't have the option for the user right now to switch between speaker, earphone or bt audio when playing music. A2DP currently gets the highest priority here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1504057 Title: Bluetooth icon should turn blue when there's traffic happening Status in Canonical System Image: New Status in Ubuntu UX: New Status in indicator-bluetooth package in Ubuntu: New Bug description: The Bluetooth icon in the panel is currently an outline icon when Bluetooth is turned on but nothing is connected, it will turn to the filled icon when something connects. Additionally it would be useful if the icon would turn blue when there is actual traffic happening. This is something I've been used to from previous phones and it helps greatly to identify the state of the connection. For instance, the Music player playing music to a Bluetooth headset would be immediately visible when you've put the headset away already and forgot to stop the music player. Also, it causes bug reports of failed connections to be more detailed as this gives details to the developer whether the connection failed when establishing the ACL link or if something failed after a profile has been connected already. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1504057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504057] Re: Bluetooth icon should turn blue when there's traffic happening
** Tags added: after-bluez5 bluetooth -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1504057 Title: Bluetooth icon should turn blue when there's traffic happening Status in Canonical System Image: New Status in Ubuntu UX: New Status in indicator-bluetooth package in Ubuntu: New Bug description: The Bluetooth icon in the panel is currently an outline icon when Bluetooth is turned on but nothing is connected, it will turn to the filled icon when something connects. Additionally it would be useful if the icon would turn blue when there is actual traffic happening. This is something I've been used to from previous phones and it helps greatly to identify the state of the connection. For instance, the Music player playing music to a Bluetooth headset would be immediately visible when you've put the headset away already and forgot to stop the music player. Also, it causes bug reports of failed connections to be more detailed as this gives details to the developer whether the connection failed when establishing the ACL link or if something failed after a profile has been connected already. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1504057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505241] Re: Phone does not suspend
QA did a test run and measure power usage on an MX4 device. Results are stored at http://people.canonical.com/~platform-qa/power- results/?Chttp://people.canonical.com/~platform-qa/power- results/?C=M;O=D=M;O=D Test run number is 166. According to QA they don't show anything significant difference to normal runs. -- 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/1505241 Title: Phone does not suspend Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: In Progress Bug description: I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior According to the logs they are not able to suspend due to active wakeup sources. (I am running a BT test kernel on the MX4 3.10.35+) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@joihap: Does the car gets listed under Connect automatically when detected on your phone? If yes that is a good indicator that the car got at least paired. What happens then if you connect the car manually? -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@JoiHap: At the time you called bluez-list-devices what was the state of the entry in the settings app? As the output reports the car as being paired / trusted / connected which is what we want. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
We now have two things mixed in here. 1. Device doesn't connect directly after it got paired in the UI and needs a second user step to get connected 2. A keyboard doesn't reconnect after it turned off or the using device went to sleep First problem needs fixes in ubuntu-system-settings which I have at https://code.launchpad.net/~morphis/ubuntu-system-settings/fix-device- actions Second problem requires to backport fixes from upstream bluez to correctly enable the reconnect mode of HID devices. ** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Simon Fels (morphis) ** 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: New Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does attempt to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
I tried to reproduce this under similar conditions with a headset as I don't have access to any carkit at the moment but didn't had success. There are two possible reasons for this: * the device doesn't get disconnect any stays connected as device for bluez * the device disconnects properly but the upper stack (telepathy-ofono, telephony-service, pulseaudio) doesn't recognize this correctly I will try to get this reproduced next week with my own carkit at home. Tiago also mentioned there was a major rework of the code part in telepathy-ofono recently (ota6?) handling these things. He will attach a package without this rework included to let us verify if this is the reason for the behavior we see here or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1487889 Title: After disconnnecting from car bluetooth, audio is still routed to bluetooth Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: New Bug description: MX4 r96 This has been happening fro a few weeks Phone automatically connects to the car, you don't have to make or receive a call Leave the car and disconnect Place a call The audio starts out using the phone as expected, after a few seconds the audio switches to bluetooth You can manually change the audio in the UI This happens until you reboot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
Fixes for 1. and 2. are in Silo 009 and 059. Wily should be not affected as we already landed bluez5 there. @Daniel: If you want to test get and install packages from silo 059 in your vivid desktop installation. -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does attempt to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@JoiHap: Can you describe a bit more what you experience? So I need answers for the following quesitons: * Does the connection not happen directly after you paired the device successfully? * Please check with /usr/bin/bluez-list-devices if you car is paired. Optimal would be if you can attach the output here. Instructions for debugging steps are at https://wiki.ubuntu.com/DebuggingBluetooth. Informations for how to get into a device with adb shell are on https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/ We're going to land two fixes for bluetooth in rc-proposed soon. I will update here when they are landed so you guys can see if that improves the situation. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows Aquaris E4.5 Ubuntu Edition and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489327] [NEW] Upgrade kernel bluetooth stack to 4.2-rc7
Public bug reported: [Impact] [Test Case] [Regression Potential] [Other Info] ** Affects: linux-flo (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Affects: linux-mako (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Package changed: apparmor (Ubuntu) = linux-mako (Ubuntu) ** Also affects: linux-flo (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-flo (Ubuntu) Assignee: (unassigned) = Simon Fels (morphis) ** Changed in: linux-mako (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1489327 Title: Upgrade kernel bluetooth stack to 4.2-rc7 Status in linux-flo package in Ubuntu: New Status in linux-mako package in Ubuntu: New Bug description: [Impact] [Test Case] [Regression Potential] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-flo/+bug/1489327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490520] Re: WiFi network is not listed by NM but listed by the kernel driver
** Description changed: - I wanted to connect my local WiFi network today but didn't found it in - the UI. I then manually triggered a + I wanted to connect my local WiFi network today (device was off before + and may have slept) but didn't found it in the UI. I then manually + triggered a $ sudo iwlist wlan0 scan on the command line which directly found my WiFi network whereas NetworkManager still didn't listed it. After power cycling WiFi the network was listed again on the UI. This is on Ubuntu Touch and mako: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 227 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-08-28 09:13:42 version version: 227 version ubuntu: 20150828 version device: 20150819 version custom: 20150828 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1490520 Title: WiFi network is not listed by NM but listed by the kernel driver Status in network-manager package in Ubuntu: Incomplete Bug description: I wanted to connect my local WiFi network today (device was off before and may have slept) but didn't found it in the UI. I then manually triggered a $ sudo iwlist wlan0 scan on the command line which directly found my WiFi network whereas NetworkManager still didn't listed it. After power cycling WiFi the network was listed again on the UI. This is on Ubuntu Touch and mako: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 227 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-08-28 09:13:42 version version: 227 version ubuntu: 20150828 version device: 20150819 version custom: 20150828 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1490520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490520] Re: WiFi network is not listed by NM but listed by the kernel driver
AP is 2.4G, WPA-PSK secured and it's SSID is not hidden. Will add more details once I get this reproduced. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1490520 Title: WiFi network is not listed by NM but listed by the kernel driver Status in network-manager package in Ubuntu: Incomplete Bug description: I wanted to connect my local WiFi network today (device was off before and may have slept) but didn't found it in the UI. I then manually triggered a $ sudo iwlist wlan0 scan on the command line which directly found my WiFi network whereas NetworkManager still didn't listed it. After power cycling WiFi the network was listed again on the UI. This is on Ubuntu Touch and mako: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 227 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-08-28 09:13:42 version version: 227 version ubuntu: 20150828 version device: 20150819 version custom: 20150828 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1490520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479442] Re: IN CAR: Previous Calls log is not shown in the car display
** 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/1479442 Title: IN CAR: Previous Calls log is not shown in the car display Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT a list of previous calls and a car that support bluetooth phones (Skoda Superb 2013 in my case) 1. Connect DUT to the car 2. In the car menu navigate to previous calls log EXPECTED: I expect to see a list of past calls similar to those I see on the phone itself ACTUAL: Car shows no previous calls log at all VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** 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/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Triaged Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490520] [NEW] WiFi network is not listed by NM but listed by the kernel driver
Public bug reported: I wanted to connect my local WiFi network today but didn't found it in the UI. I then manually triggered a $ sudo iwlist wlan0 scan on the command line which directly found my WiFi network whereas NetworkManager still didn't listed it. After power cycling WiFi the network was listed again on the UI. This is on Ubuntu Touch and mako: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 227 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-08-28 09:13:42 version version: 227 version ubuntu: 20150828 version device: 20150819 version custom: 20150828 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "nm-network-not-listed.log" https://bugs.launchpad.net/bugs/1490520/+attachment/4455027/+files/nm-network-not-listed.log ** Description changed: I wanted to connect my local WiFi network today but didn't found it in the UI. I then manually triggered a $ sudo iwlist wlan0 scan on the command line which directly found my WiFi network whereas NetworkManager still didn't listed it. + + After power cycling WiFi the network was listed again on the UI. This is on Ubuntu Touch and mako: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 227 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-08-28 09:13:42 version version: 227 version ubuntu: 20150828 version device: 20150819 version custom: 20150828 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1490520 Title: WiFi network is not listed by NM but listed by the kernel driver Status in network-manager package in Ubuntu: New Bug description: I wanted to connect my local WiFi network today but didn't found it in the UI. I then manually triggered a $ sudo iwlist wlan0 scan on the command line which directly found my WiFi network whereas NetworkManager still didn't listed it. After power cycling WiFi the network was listed again on the UI. This is on Ubuntu Touch and mako: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 227 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-08-28 09:13:42 version version: 227 version ubuntu: 20150828 version device: 20150819 version custom: 20150828 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1490520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type "computer"
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 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
@Pat: I tried to reproduce this today but didn't had success. A few more questions: 1. With "Leave the car and disconnect" you mean the phone automatically disconnects as it goes out of range or do you actively disconnect the car? 2. How long did you wait to place the call after you left the car? You saw you were disconnect from the car (through the indicator)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1487889 Title: After disconnnecting from car bluetooth, audio is still routed to bluetooth Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: New Bug description: MX4 r96 This has been happening fro a few weeks Phone automatically connects to the car, you don't have to make or receive a call Leave the car and disconnect Place a call The audio starts out using the phone as expected, after a few seconds the audio switches to bluetooth You can manually change the audio in the UI This happens until you reboot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type "computer"
** 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 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type "computer"
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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@JoiHap: Can you test this again with the latest rc-proposed image? -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484980] Re: AVRCP support for Ubuntu Phone
>From what jhodap told me the sound indicator might be the one responsible for this. ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid ** Also affects: indicator-sound Importance: Undecided Status: New ** No longer affects: indicator-sound ** Package changed: bluez (Ubuntu) => canonical-devices-system-image ** Changed in: canonical-devices-system-image Status: Invalid => Confirmed -- 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/1484980 Title: AVRCP support for Ubuntu Phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Bug description: Hey! I bought a bluetooth headphone, but the volume, next and previous track buttons don't work with my Ubuntu Phone, because it doesn't support AVRCP. So please implement this feature. :) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1484980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491484] Re: Anker keyboard doesn't send key events to krillin
After some more analysis the BT HID stack in the krillin kernel seems to be horrible broken. We will not going to fix but replace this pretty soon with a complete new bluetooth stack which will be based on an recent upstream kernel (4.2). We have to wait until this is done until we have a solution for this bug. However just conencting a keyboard should be possible once the mentioned kernel fix is merged and published, it will just not allow you to enter anything. -- 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/1491484 Title: Anker keyboard doesn't send key events to krillin Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Bug description: I have an Anker BT keyboard which seems to work fine on the Nexus 4 with Android, but when I use it with Krillin and Ubuntu it doesn't seem to receive keypresses. In fact I have used a hack boot.img to get it to even connect. The exact model is : http://www.amazon.co.uk /Compact-Wireless-Bluetooth-Keyboard- Rechargeable/dp/B00PIMRCFG/ref=sr_1_2?ie=UTF8=1441209196=8-2=anker+bluetooth+keyboard phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 08:01:15 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489109] Re: system freezing with bluetooth sony vaio mouse
Sounds good. There were some bluetooth bug fixes between 4.1 and 4.2 so good chance that this solved your problem. Closing this bug for now. ** Changed in: bluez (Ubuntu) Status: New => 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/1489109 Title: system freezing with bluetooth sony vaio mouse Status in bluez package in Ubuntu: Fix Released Bug description: Hello, I am testing Ubuntu-gnome 15.10... For this, I installed Wily in my notebook Sony VAIO SVS151290. I bought this notebook already with a Vaio integrated bluetooth mouse from Sony. While I used the Vivid I could use the mouse normally but after I did a fresh install of Wily, I began to realize that Ubuntu started to freeze completely, so that I am forced to shut down the notebook for it to return to work. Ctrl+Alt+F'n' does not work, 'Caps Lock' does not work,' Num Lock' does not work ... the computer stay completely paralyzed showing the frozen screen with content that was running just before freezing. At first I thought it was some crash that could be linked to the new kernel 4.1.0-3, but then one day, I had to put the mouse to recharge and I noticed that the Ubuntu worked normally throughout all the day. From there I started doing some tests and found that the crash only occurs when I use the Sony VAIO mouse... If I do not to connect the mouse and use only the touchpad, everything works normally without freezing. Every new update of Wily I've been redoing the tests but so far, the freezing is still occurring. Thank you very much! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluetooth 5.33-0ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 26 15:06:12 2015 InstallationDate: Installed on 2015-07-30 (27 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150728) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation SVS151290X PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic root=UUID=5b11d9d8-e0cc-462f-a2c0-72e8af1ae050 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0081C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0081C8:bd09/18/2012:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS151290X dmi.product.version: C60BKPK7 dmi.sys.vendor: Sony Corporation hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:3A:53:C1 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:2707 acl:0 sco:0 commands:48 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1489109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492368] Re: Calls made through car bluetooth drop out
Which phone is this? It would be also quite helpful if you can provide some more verbose debug logs. To do that follow https://wiki.ubuntu.com/DebuggingBluetooth and reproduce the problem. Afterwards attach the syslog file here or shared privately with me if you mind pushing it here. -- 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/1492368 Title: Calls made through car bluetooth drop out Status in bluez package in Ubuntu: New Bug description: Calls made through car bluetooth connection always drop out after about 3 minutes. The phone becomes unusable and I have to hold the power button for 15 seconds to reboot it. Car is Skoda Octavia. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492361] Re: Battery status wrong in car bluetooth display
*** This bug is a duplicate of bug 1479438 *** https://bugs.launchpad.net/bugs/1479438 ** This bug has been marked a duplicate of bug 1479438 IN CAR: Battery levels not shared via bluetooth for in car experience -- 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/1492361 Title: Battery status wrong in car bluetooth display Status in bluez package in Ubuntu: New Bug description: When my BQ Aquaris is connected to my car (SkodaOctavia) the car display console always shows a fully charged battery. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492441] Re: Cannot connect to 1byone bluetooth keyboard (after successfully pairing)
When connecting a device doesn't work this normally means that there is no handler for the profiles bluez tries to connect with. "Connecting with a bluetooth device" means "Connecting with a profile". When you enter "connect " in bluetoothctl bluez will go through all profiles the remote devices provides, looking for an handler for this profile (either in bluetoothd or in another service like pulseaudio for A2DP/HFP) and if a handler is found it will be to connect with that profile. Can you do the following: $ sudo systemctl stop bluetooth $ sudo bluetoothd -n -d in another terminal $ bluetoothctl # connect and then attach the output of bluetoothd here? -- 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/1492441 Title: Cannot connect to 1byone bluetooth keyboard (after successfully pairing) Status in bluez package in Ubuntu: New Bug description: I own a 1byone bluetooth keyboard/touchpad combo device. I'm using wily. I have managed to successfully pair it (the UI did not work for this -- bug 1492443). But doing it via the console did pair it: $ bluetoothctl [NEW] Device 08:73:00:13:CC:45 1byone Keyboard [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# pair 08:73:00:13:CC:45 Attempting to pair with 08:73:00:13:CC:45 [CHG] Device 08:73:00:13:CC:45 Connected: yes [agent] PIN code: 420005 [CHG] Device 08:73:00:13:CC:45 Modalias: usb:v04E8p7021d011B [CHG] Device 08:73:00:13:CC:45 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 Paired: yes Pairing successful [CHG] Device 08:73:00:13:CC:45 Connected: no [CHG] Device 60:03:08:C9:C0:87 RSSI: -59 [CHG] Device 60:03:08:C9:C0:87 RSSI: -48 [CHG] Device 60:03:08:C9:C0:87 RSSI: -60 [CHG] Device 60:03:08:C9:C0:87 RSSI: -48 etc, etc (kept outputting RSSI bits every now and then) OK. So it paired. (which means it's not bug 1490347) But now I can't connect. You can see above that it says "Connected: no". If I go to the Bluetooth panel in System Settings, its "Connection" switch is set to Off and disabled. But it otherwise seems to be successfully paired. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 4 15:16:58 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (967 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=0719ea95-7c02-4d0a-a969-1ba285c420f2 ro quiet splash vt.handoff=7 SourcePackage: bluez SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to wily on 2013-01-31 (945 days ago) dmi.bios.date: 12/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0CK86J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/03/2012:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0CK86J:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:FB:58:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:19494 acl:0 sco:0 events:721 errors:0 TX bytes:3449 acl:0 sco:0 commands:234 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492892] Re: Implement standalone bluetooth agent handler
** Tags added: bluez5 -- 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/1492892 Title: Implement standalone bluetooth agent handler Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: Currently the settings app registers an agent instance against BlueZ which can only be triggered when the application is currently active. To provide a better user experience we need a different place to implement the agent to have it running in the background all the time. indicator-bluetooth sounds like a suitable component for this but we need to sort out how we present the different user interface screens (trusted helper, notifications, units8, ). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1492892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Nephilim1973: No, we can't "learn" anything here from Android. We have a completely different bluetooth stack which you can't compare with the Android one. Config files in /etc/bluetooth/*.conf don't help. Those problems are at other layers. > Why the BT handling is so different between Touch and Desktop ? There are quite a lot differences: * different BT chip * different UI handlers * newer kernel with updated Bluetooth stack We're currently working quite hard to update the bluetooth stack on Touch (which dates back to 2012) to a newer, more stable and reliable one. Can't give any timeline yet but it will happen soon. What I really need is a log of bluetoothd in debug mode. See https://wiki.ubuntu.com/DebuggingBluetooth for details. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492892] [NEW] Implement standalone bluetooth agent handler
Public bug reported: Currently the settings app registers an agent instance against BlueZ which can only be triggered when the application is currently active. To provide a better user experience we need a different place to implement the agent to have it running in the background all the time. indicator- bluetooth sounds like a suitable component for this but we need to sort out how we present the different user interface screens (trusted helper, notifications, units8, ). ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu-system-settings (Ubuntu) => canonical- devices-system-image ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** 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/1492892 Title: Implement standalone bluetooth agent handler Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: Currently the settings app registers an agent instance against BlueZ which can only be triggered when the application is currently active. To provide a better user experience we need a different place to implement the agent to have it running in the background all the time. indicator-bluetooth sounds like a suitable component for this but we need to sort out how we present the different user interface screens (trusted helper, notifications, units8, ). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1492892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492891] [NEW] Implement standalone bluetooth agent handler
Public bug reported: Currently the settings app registers an agent instance against BlueZ which can only be triggered when the application is currently active. To provide a better user experience we need a different place to implement the agent to have it running in the background all the time. indicator- bluetooth sounds like a suitable component for this but we need to sort out how we present the different user interface screens (trusted helper, notifications, units8, ). ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth -- 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/1492891 Title: Implement standalone bluetooth agent handler Status in bluez package in Ubuntu: New Bug description: Currently the settings app registers an agent instance against BlueZ which can only be triggered when the application is currently active. To provide a better user experience we need a different place to implement the agent to have it running in the background all the time. indicator-bluetooth sounds like a suitable component for this but we need to sort out how we present the different user interface screens (trusted helper, notifications, units8, ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
@Pat: You had any success in reproducing this again? -- 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/1487889 Title: After disconnnecting from car bluetooth, audio is still routed to bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in telephony-service package in Ubuntu: New Bug description: MX4 r96 This has been happening fro a few weeks Phone automatically connects to the car, you don't have to make or receive a call Leave the car and disconnect Place a call The audio starts out using the phone as expected, after a few seconds the audio switches to bluetooth You can manually change the audio in the UI This happens until you reboot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493351] [NEW] Playing music/videos in browser doesn't respect silent mode
Public bug reported: If playing music or a youtube video doesn't respect a currently enabled silent mode. Found on: current build number: 234 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-09-08 12:21:37 version version: 234 version ubuntu: 20150908 version device: 20150819 version custom: 20150908 ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1493351 Title: Playing music/videos in browser doesn't respect silent mode Status in webbrowser-app package in Ubuntu: New Bug description: If playing music or a youtube video doesn't respect a currently enabled silent mode. Found on: current build number: 234 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2015-09-08 12:21:37 version version: 234 version ubuntu: 20150908 version device: 20150819 version custom: 20150908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1493351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493386] Re: IN CAR: SIM2 calls cann not be routed via car audio
The used SIM card for HFP is currently picked randomly depending on which modem device in ofono turns up first. See https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1418040 for more details on this. However this needs to be reworked to support incoming calls from two SIM cards rather than just one. Outgoing calls should still be done through the default one. -- 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/1493386 Title: IN CAR: SIM2 calls cann not be routed via car audio Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth phone support (Seat Alhambra 2012 in my case) 1. Connect the Aquaris to the car (with two SIM cards, car kid shows the provider of the 2nd SIM card in the display) 2. From the second device call the number of SIM1 3. Phone & car sound rings and call can be taken 4. From the second device call the number of SIM2 5. Phone does ring but car kit not. 6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone directly or using the car kit) 7. Normal behaviour with in car phone & audio system 8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible dialling from the phone) 9. No sound on the phone, no microphone support EXPECTED: I expect that calls from SIM2 can be taken and performed as from SIM1 ACTUAL: SIM2 seems not to work when phone is connected to blue tooth of car whereby SIM1 works flawlessly VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
** Tags added: after-bluez5 bluetooth -- 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/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Triaged Status in ofono package in Ubuntu: Triaged Status in telephony-service package in Ubuntu: Triaged Status in telephony-service package in Ubuntu RTM: Triaged Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493386] Re: IN CAR: SIM2 calls cann not be routed via car audio
This should be fixed as soon as we have landed bluez5. ** Tags added: after-bluez5 bluetooth -- 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/1493386 Title: IN CAR: SIM2 calls cann not be routed via car audio Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth phone support (Seat Alhambra 2012 in my case) 1. Connect the Aquaris to the car (with two SIM cards, car kid shows the provider of the 2nd SIM card in the display) 2. From the second device call the number of SIM1 3. Phone & car sound rings and call can be taken 4. From the second device call the number of SIM2 5. Phone does ring but car kit not. 6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone directly or using the car kit) 7. Normal behaviour with in car phone & audio system 8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible dialling from the phone) 9. No sound on the phone, no microphone support EXPECTED: I expect that calls from SIM2 can be taken and performed as from SIM1 ACTUAL: SIM2 seems not to work when phone is connected to blue tooth of car whereby SIM1 works flawlessly VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491484] Re: Anker keyboard doesn't send key events to krillin
Kernel fix for this is submitted and waiting for review. -- 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/1491484 Title: Anker keyboard doesn't send key events to krillin Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Bug description: I have an Anker BT keyboard which seems to work fine on the Nexus 4 with Android, but when I use it with Krillin and Ubuntu it doesn't seem to receive keypresses. In fact I have used a hack boot.img to get it to even connect. The exact model is : http://www.amazon.co.uk /Compact-Wireless-Bluetooth-Keyboard- Rechargeable/dp/B00PIMRCFG/ref=sr_1_2?ie=UTF8=1441209196=8-2=anker+bluetooth+keyboard phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 08:01:15 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491484] Re: Anker keyboard doesn't send key events to krillin
This comes down to a critical problem in the krillin kernel where two HID drivers conflict at startup time and the BT never gets loaded which ends up with the userland side never being able to create a BT HID input device. ** Changed in: bluez (Ubuntu) Status: New => In Progress ** Also affects: bluez Importance: Undecided Status: New ** Project changed: bluez => canonical-devices-system-image ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: canonical-devices-system-image 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. https://bugs.launchpad.net/bugs/1491484 Title: Anker keyboard doesn't send key events to krillin Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Bug description: I have an Anker BT keyboard which seems to work fine on the Nexus 4 with Android, but when I use it with Krillin and Ubuntu it doesn't seem to receive keypresses. In fact I have used a hack boot.img to get it to even connect. The exact model is : http://www.amazon.co.uk /Compact-Wireless-Bluetooth-Keyboard- Rechargeable/dp/B00PIMRCFG/ref=sr_1_2?ie=UTF8=1441209196=8-2=anker+bluetooth+keyboard phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 08:01:15 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout
>From what I hear from the Mir/UI guys this is something which isn't implemented yet on their side. BlueZ itself doesn't have any control over this as its just exposing an input device which is then configured and used by the UI. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Invalid -- 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/1491340 Title: Bluetooth keyboard is configured with wrong keyboard layout Status in bluez package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: Phone: Meizu MX4 (15.04 r4) OS Language: German What you expected to happen: When connecting a Bluetooth keyboard I expect that the keyboard layout is the same as the keyboard hardware key layout (German) or that it is possible to change the keyboard layout in the Bluetooth setting for the connected Bluetooth device. What happened instead: The Bluetooth keyboard worked, but wasn't set to German key layout. In the Bluetooth device setting I couldn't find any option to change the Bluetooth keyboard key layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout
** Summary changed: - wrong keyboard layout + Bluetooth keyboard is configured with wrong keyboard layout ** Tags added: bluetooth -- 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/1491340 Title: Bluetooth keyboard is configured with wrong keyboard layout Status in bluez package in Ubuntu: New Bug description: Phone: Meizu MX4 (15.04 r4) OS Language: German What you expected to happen: When connecting a Bluetooth keyboard I expect that the keyboard layout is the same as the keyboard hardware key layout (German) or that it is possible to change the keyboard layout in the Bluetooth setting for the connected Bluetooth device. What happened instead: The Bluetooth keyboard worked, but wasn't set to German key layout. In the Bluetooth device setting I couldn't find any option to change the Bluetooth keyboard key layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type "computer"
** 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 "computer" Status in Canonical System Image: New Status in bluez package in Ubuntu: In Progress 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Just add-apt-repository doesn't work as the priority of a silo is below the regular archive so those things aren't pulled in. At best you use the citrain command line tool for this. However if you're installing a silo you will put your device into unsupported state and have to reflash to avoid any problems on OTA upgrade. See https://wiki.ubuntu.com/citrain/LandingProcess#Command-Line_Tool for how to install the citrain tool. Then it is simple as this: $ citrain device-upgrade 43 Wait a bit and the device will go through a reboot. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491988] Re: 15.10: Multiple Bluetooth controllers not found
Can you please do the following to generate a more verbose output: $ sudo systemctl stop bluetooth $ MGMT_DEBUG=1 sudo bluetoothd -n -d &> bluetoothd-multiple-adapters.log In another terminal: $ bluetoothctl [bluetooth]# list Please add all output here and attach the file bluetoothd-multiple- adapters.log ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1491988 Title: 15.10: Multiple Bluetooth controllers not found Status in bluez package in Ubuntu: Incomplete Bug description: $ hcitool dev Devices: hci100:10:7A:4D:15:33 hci000:1F:3A:E0:0A:AF $ hcitool -i hci1 scan Scanning ... 00:0A:95:4B:BD:C2 Apple Wireless Keyboard $ sudo systemctl restart bluetooth $ journalctl -u bluetooth | grep adapter_service_add Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: src/adapter.c:adapter_service_add() /org/bluez/hci0 $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard [bluetooth]# list Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484980] Re: AVRCP support for Ubuntu Phone
>From BlueZ side we provide an input device which already reports the necessary key events we now only need someone to use them. -- 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/1484980 Title: AVRCP support for Ubuntu Phone Status in bluez package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu: New Bug description: Hey! I bought a bluetooth headphone, but the volume, next and previous track buttons don't work with my Ubuntu Phone, because it doesn't support AVRCP. So please implement this feature. :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1484980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Also a test with a latest rc-proposed image and silo 22 (https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-022/) would be great from someone who experience problems here. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
