[Kernel-packages] [Bug 1185572] Re: 8086:0116 i915 GPU hang
I have not seen a hang now for over a month, currently running kernel 3.11.0-4-generic NP900X3A Samsung Series 9 Notebook -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1185572 Title: 8086:0116 i915 GPU hang Status in “linux” package in Ubuntu: Incomplete Bug description: System hangs several times a day kernel: [ 9712.125611] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung 3.8.0-22-generic, raring ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-22-generic 3.8.0-22.33 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pat1662 F pulseaudio Date: Wed May 29 15:56:40 2013 HibernationDevice: RESUME=UUID=e17c3e9f-0df9-4a7a-b645-a914ee60b915 InstallationDate: Installed on 2011-10-11 (596 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) MachineType: SAMSUNG ELECTRONICS CO., LTD. 90X3A MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-22-generic root=UUID=938a96e5-704a-4af4-b445-1acda4e6d888 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-22-generic N/A linux-backports-modules-3.8.0-22-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-26 (33 days ago) dmi.bios.date: 05/20/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 05HL dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 90X3A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr05HL:bd05/20/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn90X3A:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn90X3A:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 90X3A dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1185572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1234361] Re: Bluetooth panel not getting scan results
Needs a bluez package change to create the /var/lib/bluetooth folder in the image at install time. ** Changed in: bluez (Ubuntu) Importance: Undecided = High ** Changed in: bluez (Ubuntu) Status: New = Confirmed ** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1234361 Title: Bluetooth panel not getting scan results Status in “bluez” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: Mako running build 76 The scan does not detect the bluetooth headset. hcitool scan does find it Scanning ... 00:18:16:20:00:FE RF-MAB2 10:40:F3:7E:12:B1 ubuntu-0 bt-monitor output is (note the Name and Alias and the Glib assertion) [Adapter: ubuntu-phablet-0 (98:D6:F7:31:C6:A6)] Device found: [00:18:16:20:00:FE] (bt-monitor:4149): GLib-GObject-CRITICAL **: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed Name: (null) Alias: 00-18-16-20-00-FE Address: 00:18:16:20:00:FE Icon: audio-card Class: 0x240404 LegacyPairing: 0 Paired: 0 RSSI: -58 bt-monitor on desktop: [Adapter: pat-samsung-0 (88:53:2E:1B:4C:D3)] Device found: [00:18:16:20:00:FE] Name: RF-MAB2 Alias: RF-MAB2 Address: 00:18:16:20:00:FE Icon: audio-card Class: 0x240404 LegacyPairing: 1 Paired: 0 RSSI: -48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1234361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273629] Re: HSP fails on Ubuntu Touch [Bluetooth headset does not work]
** Tags added: avengers-3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1273629 Title: HSP fails on Ubuntu Touch [Bluetooth headset does not work] Status in “bluez” package in Ubuntu: In Progress Bug description: When on Ubuntu Touch, HSP consistently fails to route any audio to the paired audio device. bluez-test-device create BT address bluez-test-audio connect BT address The above should create and pair a detected (in discoverable mode) bluetooth device, by default setting it up for HSP. The following excerpt from syslog on my mako shows the issue, with a bluetooth headset device failing to bring up HSP -- pulseaudio can acquire the first transport, but never release it: Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:start_inquiry() hci0 length 8 Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: Discovery session 0x41f77f98 with :1.132 activated Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_ref() 0x41f77f98: ref=1 Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() hci0: new state 1 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_remove() Discovery session 0x41f77f98 with :1.132 deactivated Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_remove() Stopping discovery Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:hciops_stop_discovery() index 0 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:hciops_stop_inquiry() hci0 Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() hci0: new state 0 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/adapter.c:create_device() 00:1A:7D:54:32:8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_create_device() 00:1A:7D:54:32:8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:device_create() Creating device /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=1 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:device_set_temporary() temporary 1 Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=2 Jan 28 09:47:54 ubuntu-phablet kernel: [ 3389.758613] l2cap_sock_connect: failed -115 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:conn_complete() status 0x00 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_version_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_features_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:remote_name_information() hci0 status 0 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:device_probe_drivers() Probing drivers for 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/manager.c:serial_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 1108--1000-8000-00805f9b34fb Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/port.c:create_serial_device() Registered interface org.bluez.Serial on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: serial/manager.c:serial_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 111e--1000-8000-00805f9b34fb Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: input/manager.c:headset_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=3 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: input/device.c:input_device_new() Registered interface org.bluez.Input on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:btd_device_ref() 0x41f936e8: ref=4 Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/device.c:audio_device_register() Registered interface org.bluez.Audio on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/manager.c:handle_uuid() Found Headset record Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/headset.c:headset_init() Registered interface org.bluez.Headset on path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: audio/manager.c:handle_uuid() Found Handsfree record Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: src/device.c:device_set_temporary() temporary 0 Jan 28 09:47:55 ubuntu-phablet
[Kernel-packages] [Bug 1329532] [NEW] irq errors then a system restart on ubuntu touch
Public bug reported: Mako running build 79 Linux ubuntu-phablet 3.4.0-5-mako #28-Ubuntu SMP PREEMPT Fri Mar 28 15:20:22 UTC 2014 armv7l armv7l armv7l GNU/Linux The syslog has the following messages for around 15 mins prior to the shutdown Jun 12 17:05:28 ubuntu-phablet kernel: [19089.868943] irq errorIrq Jun 12 17:05:28 ubuntu-phablet kernel: [19089.869370] vfe32_irq: image master 0 bus overflow Jun 12 17:05:28 ubuntu-phablet kernel: [19089.869614] vfe32_irq: image master 1 bus overflow Jun 12 17:05:28 ubuntu-phablet kernel: [19089.880479] irq errorIrq Jun 12 17:05:28 ubuntu-phablet kernel: [19089.880907] vfe32_irq: violation interrupt Jun 12 17:05:28 ubuntu-phablet kernel: [19089.881151] vfe32_process_error_irq: violationStatus = 0x10 ... Jun 12 17:17:36 ubuntu-phablet kernel: [19818.403538] vfe32_irq: image master 1 bus overflow Jun 12 17:17:36 ubuntu-phablet kernel: [19818.421117] irq errorIrq Jun 12 17:17:36 ubuntu-phablet kernel: [19818.421453] vfe32_irq: violation interrupt Jun 12 1Jun 12 17:17:55 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=719 x-info=http://www.rsyslog.com;] start Jun 12 17:17:55 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Jun 12 17:17:55 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 104 Jun 12 17:17:55 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 101 Jun 12 17:17:55 ubuntu-phablet rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ] Jun 12 17:17:55 ubuntu-phablet kernel: [0.00] Booting Linux on physical CPU 0 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ricardo Salveti (rsalveti) Status: Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1329532 Title: irq errors then a system restart on ubuntu touch Status in “linux” package in Ubuntu: Incomplete Bug description: Mako running build 79 Linux ubuntu-phablet 3.4.0-5-mako #28-Ubuntu SMP PREEMPT Fri Mar 28 15:20:22 UTC 2014 armv7l armv7l armv7l GNU/Linux The syslog has the following messages for around 15 mins prior to the shutdown Jun 12 17:05:28 ubuntu-phablet kernel: [19089.868943] irq errorIrq Jun 12 17:05:28 ubuntu-phablet kernel: [19089.869370] vfe32_irq: image master 0 bus overflow Jun 12 17:05:28 ubuntu-phablet kernel: [19089.869614] vfe32_irq: image master 1 bus overflow Jun 12 17:05:28 ubuntu-phablet kernel: [19089.880479] irq errorIrq Jun 12 17:05:28 ubuntu-phablet kernel: [19089.880907] vfe32_irq: violation interrupt Jun 12 17:05:28 ubuntu-phablet kernel: [19089.881151] vfe32_process_error_irq: violationStatus = 0x10 ... Jun 12 17:17:36 ubuntu-phablet kernel: [19818.403538] vfe32_irq: image master 1 bus overflow Jun 12 17:17:36 ubuntu-phablet kernel: [19818.421117] irq errorIrq Jun 12 17:17:36 ubuntu-phablet kernel: [19818.421453] vfe32_irq: violation interrupt Jun 12 1Jun 12 17:17:55 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=719 x-info=http://www.rsyslog.com;] start Jun 12 17:17:55 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Jun 12 17:17:55 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 104 Jun 12 17:17:55 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 101 Jun 12 17:17:55 ubuntu-phablet rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ] Jun 12 17:17:55 ubuntu-phablet kernel: [0.00] Booting Linux on physical CPU 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1329532] Re: irq errors then a system restart on ubuntu touch
I had several apps up in the background including the camera -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1329532 Title: irq errors then a system restart on ubuntu touch Status in “linux” package in Ubuntu: Incomplete Bug description: Mako running build 79 Linux ubuntu-phablet 3.4.0-5-mako #28-Ubuntu SMP PREEMPT Fri Mar 28 15:20:22 UTC 2014 armv7l armv7l armv7l GNU/Linux The syslog has the following messages for around 15 mins prior to the shutdown Jun 12 17:05:28 ubuntu-phablet kernel: [19089.868943] irq errorIrq Jun 12 17:05:28 ubuntu-phablet kernel: [19089.869370] vfe32_irq: image master 0 bus overflow Jun 12 17:05:28 ubuntu-phablet kernel: [19089.869614] vfe32_irq: image master 1 bus overflow Jun 12 17:05:28 ubuntu-phablet kernel: [19089.880479] irq errorIrq Jun 12 17:05:28 ubuntu-phablet kernel: [19089.880907] vfe32_irq: violation interrupt Jun 12 17:05:28 ubuntu-phablet kernel: [19089.881151] vfe32_process_error_irq: violationStatus = 0x10 ... Jun 12 17:17:36 ubuntu-phablet kernel: [19818.403538] vfe32_irq: image master 1 bus overflow Jun 12 17:17:36 ubuntu-phablet kernel: [19818.421117] irq errorIrq Jun 12 17:17:36 ubuntu-phablet kernel: [19818.421453] vfe32_irq: violation interrupt Jun 12 1Jun 12 17:17:55 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=719 x-info=http://www.rsyslog.com;] start Jun 12 17:17:55 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Jun 12 17:17:55 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 104 Jun 12 17:17:55 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 101 Jun 12 17:17:55 ubuntu-phablet rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ] Jun 12 17:17:55 ubuntu-phablet kernel: [0.00] Booting Linux on physical CPU 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1329532] Re: irq errors then a system restart on ubuntu touch
cant run apport-collect on the phone ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1329532 Title: irq errors then a system restart on ubuntu touch Status in “linux” package in Ubuntu: Confirmed Bug description: Mako running build 79 Linux ubuntu-phablet 3.4.0-5-mako #28-Ubuntu SMP PREEMPT Fri Mar 28 15:20:22 UTC 2014 armv7l armv7l armv7l GNU/Linux The syslog has the following messages for around 15 mins prior to the shutdown Jun 12 17:05:28 ubuntu-phablet kernel: [19089.868943] irq errorIrq Jun 12 17:05:28 ubuntu-phablet kernel: [19089.869370] vfe32_irq: image master 0 bus overflow Jun 12 17:05:28 ubuntu-phablet kernel: [19089.869614] vfe32_irq: image master 1 bus overflow Jun 12 17:05:28 ubuntu-phablet kernel: [19089.880479] irq errorIrq Jun 12 17:05:28 ubuntu-phablet kernel: [19089.880907] vfe32_irq: violation interrupt Jun 12 17:05:28 ubuntu-phablet kernel: [19089.881151] vfe32_process_error_irq: violationStatus = 0x10 ... Jun 12 17:17:36 ubuntu-phablet kernel: [19818.403538] vfe32_irq: image master 1 bus overflow Jun 12 17:17:36 ubuntu-phablet kernel: [19818.421117] irq errorIrq Jun 12 17:17:36 ubuntu-phablet kernel: [19818.421453] vfe32_irq: violation interrupt Jun 12 1Jun 12 17:17:55 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=719 x-info=http://www.rsyslog.com;] start Jun 12 17:17:55 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Jun 12 17:17:55 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 104 Jun 12 17:17:55 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 101 Jun 12 17:17:55 ubuntu-phablet rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ] Jun 12 17:17:55 ubuntu-phablet kernel: [0.00] Booting Linux on physical CPU 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301990] Re: Samsung N9 Kernel panic
** Attachment added: bottom of screen https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301990/+attachment/4063358/+files/image20140403_0004.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1301990 Title: Samsung N9 Kernel panic Status in “linux” package in Ubuntu: New Bug description: kernel paniced several times resulting in a hard lockup requiring hardware reset to power down I suspect its related to pairing an Apple magic trackpad over bluetooth Samsung N90x3A linux-image-3.13.0-20-generic version 3.13.0-20.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301990] [NEW] Samsung N9 Kernel panic
Public bug reported: kernel paniced several times resulting in a hard lockup requiring hardware reset to power down I suspect its related to pairing an Apple magic trackpad over bluetooth Samsung N90x3A linux-image-3.13.0-20-generic version 3.13.0-20.42 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: Screen with trace https://bugs.launchpad.net/bugs/1301990/+attachment/4063357/+files/image20140403_0003.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1301990 Title: Samsung N9 Kernel panic Status in “linux” package in Ubuntu: New Bug description: kernel paniced several times resulting in a hard lockup requiring hardware reset to power down I suspect its related to pairing an Apple magic trackpad over bluetooth Samsung N90x3A linux-image-3.13.0-20-generic version 3.13.0-20.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301990] Re: Samsung N9 Kernel panic
*** This bug is a duplicate of bug 1252874 *** https://bugs.launchpad.net/bugs/1252874 I had not paired the trackpad for many months. Looks like a dupe of bug #1252874 ** This bug has been marked a duplicate of bug 1252874 Kernel panic shortly after pairing Apple Magic Touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1301990 Title: Samsung N9 Kernel panic Status in “linux” package in Ubuntu: New Bug description: kernel paniced several times resulting in a hard lockup requiring hardware reset to power down I suspect its related to pairing an Apple magic trackpad over bluetooth Samsung N90x3A linux-image-3.13.0-20-generic version 3.13.0-20.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1352778] Re: bluetooth does not stay off (aka setting does not persist across reboot)
*** This bug is a duplicate of bug 1296114 *** https://bugs.launchpad.net/bugs/1296114 ** This bug has been marked a duplicate of bug 1296114 Bluetooth is always enabled after reboot even if it was disabled ** Tags removed: rtm14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1352778 Title: bluetooth does not stay off (aka setting does not persist across reboot) Status in “bluez” package in Ubuntu: New Bug description: If I disable bluetooth, and reboot the phone, bluetooth is enabled again. Outcome: - a surprised user. - increased and unnecessary battery drain. - increased phone attack surface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1352778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380567] Re: Music plays through device's loudspeaker when incoming call received with BT headset connected
** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1380567 Title: Music plays through device's loudspeaker when incoming call received with BT headset connected Status in “bluez” package in Ubuntu: New Bug description: krillin ubuntu-rtm/14.09-proposed build 101 SUMMARY: With a Bluetooth headset connected and listening to music, the ring tone and music will both play through device loudspeaker when an incoming call is received. STEPS: 1) Pair and connect the Bluetooth headset 2) Play music through headset 3) Receive an incoming call EXPECTED RESULT: The device should remain silent (as is behaviour for wired headset). The music should pause. The ring tone should play through the headset. ACTUAL RESULT: The music and the ring tone both play through the device's loudspeaker. The ring tone also plays through the headset (as expected). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1380567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1412543] Re: udev bridge fails to get events from kernel (missing FHANDLE)
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1412543 Title: udev bridge fails to get events from kernel (missing FHANDLE) Status in the base for Ubuntu mobile products: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-flo package in Ubuntu: Fix Released Status in linux-mako package in Ubuntu: Fix Released Status in linux-manta package in Ubuntu: Fix Released Bug description: current build number: 70 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2015-01-19 14:11:13 version version: 70 version ubuntu: 20150119 version device: 20150116 version custom: 20150119 Noticed that sometimes upstart is not receiving kernel events, which caused bad side effects at the usb event logic we have in ubuntu touch. Basically I noticed that /etc/init/android-usb-state.conf fails to send the connected/disconnected events during some reboots when testing MTP. Looking a bit further, I saw that not only these events are missing, but every udev related ones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1412543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1277765] Re: big delay when pressing speakerphone icon on N4
I am still experiencing this. I usually need to press the button several times and it can take as long as 15 to 20 secs to be usable. ** Changed in: dialer-app Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1277765 Title: big delay when pressing speakerphone icon on N4 Status in Dialer app for Ubuntu Touch: Confirmed Status in alsa-lib package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in telepathy-ofono package in Ubuntu: Fix Released Bug description: On Nexus 4, when on an active call, pressing the speaker phone icon does nothing for a few seconds and then it switches. We should toggle the icon immediately upon press even if it takes the backend a while to respond so the user has instant feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1277765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1400827] Re: BlueZ crashing when connecting input channel to a keyboard
need for convergence work ** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww05-2015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1400827 Title: BlueZ crashing when connecting input channel to a keyboard Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez package in Ubuntu RTM: In Progress Bug description: On the phone, pairing a keyboard makes BlueZ crash when connecting the input channel (either by calling org.bluez.Input.Connect() on D-Bus or by pressing some keys on the keyboard to make the keyboard open the channel. In order to pair a keyboard with an Ubuntu phone, you need to either apply this branch to ubuntu-system-settings [1] or do it manually with bluez-simple-agent and dbus-send/qdbus. [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1400827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1400827] Re: BlueZ crashing when connecting input channel to a keyboard
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1400827 Title: BlueZ crashing when connecting input channel to a keyboard Status in the base for Ubuntu mobile products: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez package in Ubuntu RTM: In Progress Bug description: On the phone, pairing a keyboard makes BlueZ crash when connecting the input channel (either by calling org.bluez.Input.Connect() on D-Bus or by pressing some keys on the keyboard to make the keyboard open the channel. In order to pair a keyboard with an Ubuntu phone, you need to either apply this branch to ubuntu-system-settings [1] or do it manually with bluez-simple-agent and dbus-send/qdbus. [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1400827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1419874] Re: krillin bluetooth discoverability enabled on boot
** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Michael Frey (mfrey) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419874 Title: krillin bluetooth discoverability enabled on boot Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: New Bug description: Using krillin rtm 228, the device is discoverable/can be paired -o over bluetooth directly after boot (don't even need to unlock the greeter). That seems like somewhat a security (and use extra power as well) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1419874] Re: krillin bluetooth discoverability enabled on boot
** Tags added: battery ** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww09-2015 ** Changed in: bluez (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419874 Title: krillin bluetooth discoverability enabled on boot Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: New Bug description: Using krillin rtm 228, the device is discoverable/can be paired -o over bluetooth directly after boot (don't even need to unlock the greeter). That seems like somewhat a security (and use extra power as well) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1419874] Re: krillin bluetooth discoverability enabled on boot
After closing app from the BT panel cat /var/lib/bluetooth/B8\:64\:91\:48\:1D\:FE/config name Aquaris E4.5 Ubuntu Edition pairable yes onmode discoverable mode discoverable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419874 Title: krillin bluetooth discoverability enabled on boot Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: New Bug description: Using krillin rtm 228, the device is discoverable/can be paired -o over bluetooth directly after boot (don't even need to unlock the greeter). That seems like somewhat a security (and use extra power as well) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1419874] Re: krillin bluetooth discoverability enabled on boot
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419874 Title: krillin bluetooth discoverability enabled on boot Status in the base for Ubuntu mobile products: Fix Released Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in bluez package in Ubuntu RTM: Fix Released Status in ubuntu-system-settings package in Ubuntu RTM: Fix Released Bug description: Using krillin rtm 228, the device is discoverable/can be paired -o over bluetooth directly after boot (don't even need to unlock the greeter). That seems like somewhat a security (and use extra power as well) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1419874] Re: krillin bluetooth discoverability enabled on boot
approving for the ota due to battery life impact ** Changed in: canonical-devices-system-image Milestone: ww09-2015 = ww13-ota -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419874 Title: krillin bluetooth discoverability enabled on boot Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in bluez package in Ubuntu RTM: New Status in ubuntu-system-settings package in Ubuntu RTM: New Bug description: Using krillin rtm 228, the device is discoverable/can be paired -o over bluetooth directly after boot (don't even need to unlock the greeter). That seems like somewhat a security (and use extra power as well) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1426272] Re: vivid-proposed/krillin - Phone reboots spontaneously
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided = Critical ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww13-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1426272 Title: vivid-proposed/krillin - Phone reboots spontaneously Status in the base for Ubuntu mobile products: Confirmed Status in linux package in Ubuntu: Triaged Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 It happened up to 3 times a day, the phone reboots with no apparent reason. syslog doesn't work on the phone but /proc/last_kmsg shows the following message: [ 793.598710]systemd-logind[16120]: Failed to start user service: Unknown unit: user@0.service [ 793.606282]systemd-logind[16120]: Failed to start user service: Unknown unit: user@32011.service [ 806.517752]systemd-logind[16242]: Failed to start user service: Unknown unit: user@0.service [ 806.521333]systemd-logind[16242]: Failed to start user service: Unknown unit: user@32011.service [ 809.797251]Restarting system. [ 809.797336][c0015404] (unwind_backtrace+0x0/0x104) from [c07db344] (dump_stack+0x20/0x24) [ 809.797366][c0015404] (unwind_backtrace+0x0/0x104) from [c07db344] (dump_stack+0x20/0x24) [ 809.797396][c07db344] (dump_stack+0x20/0x24) from [c0014110] (handle_IPI+0xf4/0x250) [ 809.797424][c07db344] (dump_stack+0x20/0x24) from [c0014110] (handle_IPI+0xf4/0x250) [ 809.797452][c0014110] (handle_IPI+0xf4/0x250) from [c00085bc] hdo_IPI+0x18/0x1c) [ 809.797477][c0014110] (handle_IPI+0xf4/0x250) from [c00085bc] (do_IPI+0x18/0x1c) [ 809.797502][c00085bc] (do_IPI+0x18/0x1c) from [c07eb9f4] (__irq_svc+0x34/0xc8) [ 809.797529][c00085bc] (do_IPI+0x18/0x1c) from [c07eb9f4] (__irq_svc+0x34/0xc8) [ 809.797686][c07eb9f4] (8e1fac dc+0x34/0xc8) from [c000f178] (78 20070013 [ 809.797718][c07eb9f4] (__irq_svc+0x34/0xc8) from [c000f178] (default_idle+0x2c/0x40) [ 809.797747][c000f178] (default_idle+0x2c/0x40) from [c000f5a0defcpu_idle+0xb0/0x10c) [ 809.797775][c000f178] (default_idle+0x2c/0x40) from [c000f5a0] (cpu_idle+0xb0/0x10c) [ 809.797804][c000f5a0] (cpu_idle+0xb0/0x10c) from [c07d8448] (secondary_start_kernel+0x1cc/0x1e8) [ 809.797834][c000f5a0] (cpu_idle+0xb0/0x10c) from [c07d8448] (secondary_start_kernel+0x1cc/0x1e8) [ 809.797863][c07d8448] (secondary_start_kernel+0x1cc/0x1e8) fromsecondary_start0x807d7d8c) [ 809.797889][c07d8448] (secondary_start_kernel+0x1cc/0x1e8) from [807d7d8c] (0x807d7d8c) [ 809.797915][c07d8448] (secondary_start_kernel+0x1cc/0x1e8) from [807d7d8c] (0x807d7d8c) [ 809.797964][c07db344] (dump_stack+0x20/0x24) from [c0014110] (handle_IPI+0xf4/0x250) [ 809.798009][c0014110] (handle_IPI+0xf4/0x250) from [c00085bc] (do_IPI+0x18/0x1c) [ 809.798056][c00085bc] (do_IPI+0x18/0x1c) from [c07eb9f4] (__irq_svc+0x34/0xc8) [ 809.798218][c07eb9f4] (__irq_svc+0x34/0xc8) from [c000f178] (default_idle+0x2c/0x40) [ 809.798269][c000f178] (default_idle+0x2c/0x40) from [c000f5a0] (cpu_idle+0xb0/0x10c) [ 809.798319][c000f5a0] (cpu_idle+0xb0/0x10c) from [c07d8448] (secondary_start_kernel+0x1cc/0x1e8) [ 809.798365][c07d8448] (secondary_start_kernel+0x1cc/0x1e8) from [807d7d8c] (0x807d7d8c) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447761] Re: Car bluetooth shows no signal
reassigning to bluez for attention. The signal and battery level functions are not yet supported ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Importance: Undecided = High ** Changed in: bluez (Ubuntu) Status: New = Confirmed ** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1447761 Title: Car bluetooth shows no signal Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: My BQ Aquaris bluetooth connection seems to work ok in my Skoda Octavia but it never shows a signal level. It is also misreporting the battery status as it constantly shows fully charged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1447761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1445376] Re: A2DP skips when conneted to handsfree device
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1445376 Title: A2DP skips when conneted to handsfree device Status in the base for Ubuntu mobile products: 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
** Tags added: connectivity -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: New 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww28-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Pat McGowan (pat-mcgowan) ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in the base for Ubuntu mobile products: Confirmed Status in bluez package in Ubuntu: New 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
** Changed in: canonical-devices-system-image Milestone: ww28-2015 = ww34-2015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in the base for Ubuntu mobile products: 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479442] Re: IN CAR: Previous Calls log is not shown in the car display
** Changed in: canonical-devices-system-image Milestone: None = ww40-2015 ** Tags added: bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479442 Title: IN CAR: Previous Calls log is not shown in the car display Status in Canonical System Image: New Status in bluez package in Ubuntu: New 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Tags added: bluetooth ** Changed in: canonical-devices-system-image Milestone: None = ww40-2015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479445] Re: IN CAR: Signal Strength not shown in car display
** Changed in: canonical-devices-system-image Milestone: None = ww40-2015 ** Tags added: bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
** Changed in: bluez (Ubuntu) Importance: Undecided = High ** Changed in: bluez (Ubuntu) Assignee: (unassigned) = Simon Fels (morphis) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479445] Re: IN CAR: Signal Strength not shown in car display
Seb if you get a silo let me know I can test -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@simo Address book download is implemented and works for me on a BMW, it generally only takes a few seconds after connection -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Yeah we have the obexd plugin installed and it should just work A similar bug filed at https://bugs.launchpad.net/ubuntu/+source/obexd/+bug/1459369 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1205404] Re: WARNING: at /build/buildd/linux-mako-3.4.0/net/wireless/scan.c:590 cfg80211_bss_update+0x384/0x4f8()
** No longer affects: touch-preview-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1205404 Title: WARNING: at /build/buildd/linux-mako-3.4.0/net/wireless/scan.c:590 cfg80211_bss_update+0x384/0x4f8() Status in linux-mako package in Ubuntu: Incomplete Bug description: Image: 20130726.1 Device: Nexus 4 The full console log is at https://jenkins.qa.ubuntu.com/job/saucy- touch-mako-smoke-webbrowser-app-autopilot/25/console Normally this test run should take only 13 minutes or so, but it took about an hour before getting canceled. During this run, autopilot seemed to be progressing, but we saw a lot of errors like: Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728093] [ cut here ] Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728154] WARNING: at /build/buildd/linux-mako-3.4.0/net/wireless/scan.c:590 cfg80211_bss_update+0x384/0x4f8() Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728185] Modules linked in: Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728277] [c0015504] (unwind_backtrace+0x0/0xec) from [c0890a7c] (dump_stack+0x20/0x24) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728368] [c0890a7c] (dump_stack+0x20/0x24) from [c00713bc] (warn_slowpath_common+0x5c/0x74) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728429] [c00713bc] (warn_slowpath_common+0x5c/0x74) from [c0071400] (warn_slowpath_null+0x2c/0x34) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728490] [c0071400] (warn_slowpath_null+0x2c/0x34) from [c0859aa8] (cfg80211_bss_update+0x384/0x4f8) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728521] [c0859aa8] (cfg80211_bss_update+0x384/0x4f8) from [c0859d20] (cfg80211_inform_bss_frame+0x104/0x17c) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728612] [c0859d20] (cfg80211_inform_bss_frame+0x104/0x17c) from [c05b5278] (wlan_hdd_cfg80211_inform_bss_frame+0x1d8/0x204) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728673] [c05b5278] (wlan_hdd_cfg80211_inform_bss_frame+0x1d8/0x204) from [c05b5454] (hdd_cfg80211_scan_done_callback+0x1b0/0x358) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728765] [c05b5454] (hdd_cfg80211_scan_done_callback+0x1b0/0x358) from [c062b7c4] (csrScanCallCallback+0x38/0x64) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728826] [c062b7c4] (csrScanCallCallback+0x38/0x64) from [c062d614] (csrReleaseScanCommand+0x5c/0xb8) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728887] [c062d614] (csrReleaseScanCommand+0x5c/0xb8) from [c062f494] (csrScanSmeScanResponse+0x17c/0x1c4) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.728948] [c062f494] (csrScanSmeScanResponse+0x17c/0x1c4) from [c062f51c] (csrScanningStateMsgProcessor+0x40/0x80) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.729009] [c062f51c] (csrScanningStateMsgProcessor+0x40/0x80) from [c0631188] (csrMsgProcessor+0x88/0x130) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.729070] [c0631188] (csrMsgProcessor+0x88/0x130) from [c0611f38] (sme_ProcessMsg+0x4ac/0x56c) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.729162] [c0611f38] (sme_ProcessMsg+0x4ac/0x56c) from [c06856ac] (VosMCThread+0x4f4/0x690) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.729223] [c06856ac] (VosMCThread+0x4f4/0x690) from [c0091824] (kthread+0x9c/0xac) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.729284] [c0091824] (kthread+0x9c/0xac) from [c000f2b4] (kernel_thread_exit+0x0/0x8) Jul 26 14:38:03 ubuntu-phablet kernel: [ 688.729345] ---[ end trace 3de3e530dd65d0f6 ]--- (Full console log is in the link above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1205404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
** Changed in: canonical-devices-system-image Assignee: Pat McGowan (pat-mcgowan) = John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode
** Description changed: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. + + Boot with bluetooth disabled + Turn on flight mode + turn off flight mode + Bluetooth gets enabled + + See bug #1421249 for related symptoms ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1488170 Title: Bluetooth initiated after quitting airplane mode Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in urfkill package in Ubuntu: Confirmed Bug description: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. Boot with bluetooth disabled Turn on flight mode turn off flight mode Bluetooth gets enabled See bug #1421249 for related symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479449] Re: IN CAR: Bluetooth connected but ring happens through the DUT and not the Bluetooth audio
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479449 Title: IN CAR: Bluetooth connected but ring happens through the DUT and not the Bluetooth audio Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: DUT, a second device, a car with bluetooth phone support (Skoda Supberb 2013 in my case) 1. Connect the DUT to the car 2. From the second device call the car 3. The ringer starts EXPECTED: I expect all audio to come through the car speakers ACTUAL: The ringer is routed through the loud speaker of the phone not the car audio 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/1479449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479453] Re: IN CAR: Bluetooth is connected but occasionally a call comes in and there is no audio on bluetooth
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) ** Changed in: canonical-devices-system-image Milestone: None => backlog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479453 Title: IN CAR: Bluetooth is connected but occasionally a call comes in and there is no audio on bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: STEPS: Requirements: DUT, a second device and a car that supports bluetooth phones (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Receive multiple calls EXPECTED: I expect the call audio to always be routed through the car audio and be audible ACTUAL: After a number of calls all of a sudden you can accept the call but you get no audio from the call at all, the mic is still working as expected. 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/1479453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1432788] Re: Race in vivid means sometimes bluetooth is no available
** Changed in: canonical-devices-system-image Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1432788 Title: Race in vivid means sometimes bluetooth is no available Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: New Bug description: STEPS: 1. Flash a fresh image of vivid on a krillin device 2. Check if bluetooth is on 3. Reboot EXPECTED: I always expect bluetooth to be on ACTUAL: Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how ever it wouldn't connect to anything. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1432788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1445376] Re: A2DP skips when conneted to handsfree device
** Changed in: canonical-devices-system-image Status: New => Incomplete ** Changed in: canonical-devices-system-image Assignee: Canonical Phone Foundations (canonical-phonedations-team) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1445376 Title: A2DP skips when conneted to handsfree device Status in Canonical System Image: Incomplete 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
** Changed in: canonical-devices-system-image Milestone: None => backlog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499789] Re: BLUEZ5: Connecting a keyboard shows no pin popup
** Changed in: canonical-devices-system-image Milestone: backlog => ww02-2016 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1499789 Title: BLUEZ5: Connecting a keyboard shows no pin popup Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
** Changed in: canonical-devices-system-image Milestone: ww46-2015 => ww02-2016 ** Tags added: bluez5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1487889 Title: After disconnnecting from car bluetooth, audio is still routed to bluetooth Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Changed in: canonical-devices-system-image Milestone: ww46-2015 => ww02-2016 ** Changed in: bluez (Ubuntu) Status: Invalid => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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: In Progress Status in ofono package in Ubuntu: In Progress Status in ofono package in Ubuntu RTM: Fix Committed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479442] Re: IN CAR: Previous Calls log is not shown in the car display
** Changed in: canonical-devices-system-image Milestone: ww46-2015 => ww02-2016 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
@Julia yes there could be a bug still on BQ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425290] Re: Reading from /sys/devices/system/cpaccess/cpaccess0/cp_rw crashes the Nexus 4
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1425290 Title: Reading from /sys/devices/system/cpaccess/cpaccess0/cp_rw crashes the Nexus 4 Status in Canonical System Image: Confirmed Status in linux-mako package in Ubuntu: Confirmed Bug description: I noticed that my Nexus 4 crashed while doing a grep "1" -r / in an adb shell as user phablet. After narrowing it down, it looks like I can reliably crash my device by just doing a cat /sys/devices/system/cpaccess/cpaccess0/cp_rw as a normal user. After doing it about three times, all aspects of the device still work as expected, but it no longer identifies itself via USB, not even when in recovery mode. This might be a different issue, but it has never happened before, so I do think it might have been caused by the crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1513059] Re: Blue-tooth: Can't hear other party with first call after connecting to car-kit
** Also affects: bluez (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 Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1513059 Title: Blue-tooth: Can't hear other party with first call after connecting to car-kit Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: When I connect my BQ 4.5 to my car-kit (Nokia CK-7W) and want to make a call I can see that a connection has been made. The time starts ticking, however I can't hear the other party. But they can hear me. If I then hang up and call again everything works fine. We can hear each other well, but when the call is finished my radio stays in Tel- Mute, music is not coming back. Not even after several minutes. The only way to get my radio back is by switching off the blue-tooth on my phone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1513059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473936] Re: [wishlist] Sharing files via bluetooth
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Wishlist ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1473936 Title: [wishlist] Sharing files via bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Hello, I think that there should be possibility to share files (especially photos/videos by gallery app) via bluetooth by share button. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1506340] Re: Multimedia audio is routed for half of a second through HFP SCO after call has ended
** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1506340 Title: Multimedia audio is routed for half of a second through HFP SCO after call has ended Status in Canonical System Image: Confirmed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505213] Re: Multiple bluetooth audio devices break audio routing
** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505213 Title: Multiple bluetooth audio devices break audio routing Status in Canonical System Image: Confirmed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469444] Re: Lack of functionality on the car bluetooth connection
Note that many of these are covered in other reports and are due to be supported once Bluez5 upgrade is done. The phone book support has been working for some time so file a specific bug if it is not. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1469444 Title: Lack of functionality on the car bluetooth connection Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: BQ Aquaris E4.5 provides only basic functionality when connected via a bluetooth to Range Rover Evoque car system. It can only reply to calls and call numbers inserted manually from a dial pad on the car panel. There is no support to the phone contacts, no last 10 calls (in/out) list, no indication of GPRS/3G signal strength and no access to the music collection on the phone. All this functionality is available on the same car with Blackberry 10 smartphone, iPhone 5 and even old Nokia. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1469444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475608] Re: bluetooth dual sim
*** This bug is a duplicate of bug 1418040 *** https://bugs.launchpad.net/bugs/1418040 ** This bug has been marked a duplicate of bug 1418040 Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1475608 Title: bluetooth dual sim Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Status in telepathy-ofono package in Ubuntu: Confirmed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501825] Re: Bq Aquaris e5 HD bluetooth problem
** Changed in: canonical-devices-system-image Status: New => Incomplete ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1501825 Title: Bq Aquaris e5 HD bluetooth problem Status in Canonical System Image: Incomplete 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
r25 is ota6 ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499789] Re: BLUEZ5: Connecting a keyboard shows no pin popup
** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Milestone: None => backlog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1499789 Title: BLUEZ5: Connecting a keyboard shows no pin popup Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot
** Changed in: canonical-devices-system-image Status: New => Incomplete ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1387949 Title: power cycling Emerson EM229 headset caused phone to reboot Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Confirmed Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593] mag_context_obj ok--->hwm_obj->early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1375766] Re: Phone gives wrong capabilities over bluetooth
** Changed in: canonical-devices-system-image Status: New => Incomplete ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type "computer"
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419877 Title: [bluetooth] krillin advertized as type "computer" Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Fix Committed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492368] Re: Calls made through car bluetooth drop out
** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1492368 Title: Calls made through car bluetooth drop out Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed 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/canonical-devices-system-image/+bug/1492368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492892] Re: Implement standalone bluetooth agent handler
** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1492892 Title: Implement standalone bluetooth agent handler Status in Canonical System Image: Confirmed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1494230] Re: Audio is not routed to A2DP sink when connected
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Milestone: None => ww02-2016 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1494230 Title: Audio is not routed to A2DP sink when connected Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1494225] Re: Call audio is not routed to headset with HFP
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Milestone: None => ww02-2016 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1494242] Re: Try to auto connect devices when user enables bluetooth
** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: None => backlog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1494242 Title: Try to auto connect devices when user enables bluetooth Status in Canonical System Image: Confirmed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Changed in: canonical-devices-system-image Milestone: ww40-2015 => ww46-2015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479442] Re: IN CAR: Previous Calls log is not shown in the car display
** Changed in: canonical-devices-system-image Milestone: ww40-2015 => ww46-2015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
Using the new bluetooth stack I have not seen this issue again on arale fastboot flash boot boot-arale-newer-bt-stack-1.img fastboot reboot Now verify that the kernel is really what it should be: $ sudo dmesg | grep Bluetooth [0.198808] Bluetooth: Core ver 2.20 [0.198863] Bluetooth: HCI device and connection manager initialized [0.19] Bluetooth: HCI socket layer initialized [0.198910] Bluetooth: L2CAP socket layer initialized [0.198965] Bluetooth: SCO socket layer initialized [0.867176] Bluetooth: RFCOMM TTY layer initialized [0.867213] Bluetooth: RFCOMM socket layer initialized [0.867248] Bluetooth: RFCOMM ver 1.11 [0.867277] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [0.867293] Bluetooth: BNEP filters: protocol multicast [0.867319] Bluetooth: BNEP socket layer initialized [0.867336] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [0.867361] Bluetooth: HIDP socket layer initialized and that the hci0 device is up $ hciconfig hci0 hci0: Type: BR/EDR Bus: UART BD Address: 38:BC:1A:1F:7E:96 ACL MTU: 1021:8 SCO MTU: 244:4 UP RUNNING PSCAN RX bytes:716 acl:0 sco:0 events:43 errors:0 TX bytes:1475 acl:0 sco:0 commands:43 errors:0 Then continue to use your device as normal. ** Changed in: canonical-devices-system-image Milestone: ww40-2015 => ww46-2015 ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress ** No longer affects: telephony-service (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1487889 Title: After disconnnecting from car bluetooth, audio is still routed to bluetooth Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Lets see what Bluez5 brings ** Changed in: canonical-devices-system-image Milestone: ww40-2015 => backlog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479442] Re: IN CAR: Previous Calls log is not shown in the car display
** Changed in: canonical-devices-system-image Importance: Undecided => Wishlist ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
syslog after turning bluetooth off and on again ** Attachment added: "syslog.2" https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1487889/+attachment/4460667/+files/syslog.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
yes syslog during the event http://pastebin.ubuntu.com/12329857/ pactl list http://paste.ubuntu.com/12329778/ bluez-list-devices http://paste.ubuntu.com/12329831/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1487889/+attachment/4460643/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
turning off bluetooth does not remove the car bt from pactl list -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1419877] Re: [bluetooth] krillin advertized as type "computer"
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Fix Committed ** Changed in: canonical-devices-system-image Milestone: None => ww40-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1419877 Title: [bluetooth] krillin advertized as type "computer" Status in Canonical System Image: Fix Committed 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1501281] Re: Frequent freezes on 15.04 with kernel 3.19.0-29+
I have also gone several days without a freeze, Samsung with all Intel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501281 Title: Frequent freezes on 15.04 with kernel 3.19.0-29+ Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Incomplete Bug description: I am experiencing systematic freezes since my kernel was automatically upgraded to 3.19.0-29. Same problem happens if I use kernel 3.19.0-30. If I use kernel 3.19.0-28 it does not freeze any more. Behaviour is described with more details at http://askubuntu.com/questions/679212/frequent-freezes-on-15-04-with- kernel-3-19-0-29 and at http://askubuntu.com/questions/673767/frequent-freezes ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrea 3174 F pulseaudio /dev/snd/pcmC0D0p: andrea 3174 F...m pulseaudio /dev/snd/controlC0: andrea 3174 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 30 12:45:03 2015 HibernationDevice: RESUME=UUID=7f029a53-8d17-4db1-b66f-d131578efe68 InstallationDate: Installed on 2010-04-15 (1993 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) IwConfig: eth2 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=5d76a02d-2ed2-484a-81da-3cf5ce0ab3fb ro crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-30 (153 days ago) dmi.bios.date: 04/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd04/18/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521737] Re: Cannot enable bluetooth
Log reports Dec 1 09:25:00 ubuntu-phablet bluetoothd[744]: Not enough free handles to register service so we may have new FH leaks ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Pat McGowan (pat-mcgowan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1521737 Title: Cannot enable bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: MX4 running propsoed 181 with debug enabled kernel Paired to car and saw signal strength indicated Left car, renetered car and noticed not paried and BT disabled in the indicator tried to enable, 1 min later it resets to disabled Bluetoothd is no longer running there was a previous crash file in /var/crash see syslog attached /var/lib/urfkill/saved-states: [BLUETOOTH] soft=false prev-soft=false /var/log/upstart/bluetooth-touch.log start: Unknown job: bluetooth-touch-arale Reboot and bt is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
Log with debugging kernel, pretty high fail to suspend rate Suspends: 262 suspends aborted (38.93%). 411 suspends succeeded (61.07%). total time: 7293.604631 seconds (84.86%). minimum: 0.319212 seconds. maximum: 1359.032827 seconds. mean: 17.745997 seconds. mode: 6.00 seconds. median: 6.060202 seconds. Time between successful suspends: total time: 1300.874846 seconds (15.14%). minimum: 0.80 seconds. maximum: 308.381052 seconds. mean: 3.172865 seconds. mode: 1.00 seconds. median: 1.186014 seconds. ** Attachment added: "syslog" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4528129/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521737] Re: Cannot enable bluetooth
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1521737/+attachment/4528176/+files/syslog ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Description changed: MX4 running propsoed 181 with debug enabled kernel Paired to car and saw signal strength indicated Left car, renetered car and noticed not paried and BT disabled in the indicator tried to enable, 1 min later it resets to disabled Bluetoothd is no longer running see syslog attached + + /var/lib/urfkill/saved-states: + [BLUETOOTH] + soft=false + prev-soft=false + + /var/log/upstart/bluetooth-touch.log + start: Unknown job: bluetooth-touch-arale ** Description changed: MX4 running propsoed 181 with debug enabled kernel Paired to car and saw signal strength indicated Left car, renetered car and noticed not paried and BT disabled in the indicator tried to enable, 1 min later it resets to disabled Bluetoothd is no longer running + there was a previous crash file in /var/crash + see syslog attached /var/lib/urfkill/saved-states: [BLUETOOTH] soft=false prev-soft=false /var/log/upstart/bluetooth-touch.log start: Unknown job: bluetooth-touch-arale ** Description changed: MX4 running propsoed 181 with debug enabled kernel Paired to car and saw signal strength indicated Left car, renetered car and noticed not paried and BT disabled in the indicator tried to enable, 1 min later it resets to disabled Bluetoothd is no longer running there was a previous crash file in /var/crash see syslog attached /var/lib/urfkill/saved-states: [BLUETOOTH] soft=false prev-soft=false /var/log/upstart/bluetooth-touch.log start: Unknown job: bluetooth-touch-arale + + Reboot and bt is enabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1521737 Title: Cannot enable bluetooth Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: MX4 running propsoed 181 with debug enabled kernel Paired to car and saw signal strength indicated Left car, renetered car and noticed not paried and BT disabled in the indicator tried to enable, 1 min later it resets to disabled Bluetoothd is no longer running there was a previous crash file in /var/crash see syslog attached /var/lib/urfkill/saved-states: [BLUETOOTH] soft=false prev-soft=false /var/log/upstart/bluetooth-touch.log start: Unknown job: bluetooth-touch-arale Reboot and bt is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521737] [NEW] Cannot enable bluetooth
Public bug reported: MX4 running propsoed 181 with debug enabled kernel Paired to car and saw signal strength indicated Left car, renetered car and noticed not paried and BT disabled in the indicator tried to enable, 1 min later it resets to disabled Bluetoothd is no longer running there was a previous crash file in /var/crash see syslog attached /var/lib/urfkill/saved-states: [BLUETOOTH] soft=false prev-soft=false /var/log/upstart/bluetooth-touch.log start: Unknown job: bluetooth-touch-arale Reboot and bt is enabled ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Simon Fels (morphis) Status: New ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1521737 Title: Cannot enable bluetooth Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: MX4 running propsoed 181 with debug enabled kernel Paired to car and saw signal strength indicated Left car, renetered car and noticed not paried and BT disabled in the indicator tried to enable, 1 min later it resets to disabled Bluetoothd is no longer running there was a previous crash file in /var/crash see syslog attached /var/lib/urfkill/saved-states: [BLUETOOTH] soft=false prev-soft=false /var/log/upstart/bluetooth-touch.log start: Unknown job: bluetooth-touch-arale Reboot and bt is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
I think I long ago added a bug on that, when plugged in to a charger we should certainly suspend, its not an active USB data connection so we should not hold the wakelock in that case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
syslog with phone plugged in and charging for several hours, then unplugged, then charging again. All raidios on but did not connect to BT. suspend-blocker is no longer able to parse the log output so unsure the suspend success. ** Attachment added: "syslog" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4532794/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
Latest log Suspend blocking wakelocks: None Resume wakeup causes: EINT, 170 98.84% CLDMA_MD1 0.58% CLDMA_MD, 1 0.58% Suspend failure causes: tasks freezer abort 783 99.87% devices failed to suspend 1 0.13% Time between successful suspends: Interval (seconds) FrequencyCumulative Time (Seconds) 0.250 -0.499 1 0.59% 0.42 0.02% 0.500 -0.999 66 38.82% 61.81 2.23% 1.000 -1.999 63 37.06% 94.71 3.42% 2.000 -3.999 18 10.59% 41.06 1.48% 4.000 -7.999 15 8.82% 87.16 3.15% 8.000 - 15.999 0 0.00% 0.00 0.00% 16.000 - 31.999 1 0.59% 16.47 0.60% 32.000 - 63.999 0 0.00% 0.00 0.00% 64.000 - 127.999 0 0.00% 0.00 0.00% 128.000 - 255.999 4 2.35% 634.54 22.92% 256.000 - 511.999 1 0.59% 261.71 9.45% 512.000 - 1023.999 0 0.00% 0.00 0.00% 1024.000 - 2047.999 1 0.59%1570.61 56.73% Duration of successful suspends: Interval (seconds) FrequencyCumulative Time (Seconds) 0.250 -0.499 3 1.75% 1.13 0.04% 0.500 -0.999 0 0.00% 0.00 0.00% 1.000 -1.999 10 5.85% 12.97 0.48% 2.000 -3.999 17 9.94% 48.77 1.81% 4.000 -7.999 91 53.22% 514.08 19.12% 8.000 - 15.999 11 6.43% 122.08 4.54% 16.000 - 31.999 9 5.26% 212.36 7.90% 32.000 - 63.999 22 12.87%1165.36 43.35% 64.000 - 127.999 8 4.68% 611.53 22.75% Suspends: 789 suspends aborted (82.19%). 171 suspends succeeded (17.81%). total time: 2688.280289 seconds (49.27%). minimum: 0.365635 seconds. maximum: 124.066354 seconds. mean: 15.720937 seconds. mode: 6.00 seconds. median: 6.060716 seconds. Time between successful suspends: total time: 2768.483611 seconds (50.73%). minimum: 0.424609 seconds. maximum: 1570.606069 seconds. mean: 16.285198 seconds. mode: 1.00 seconds. median: 1.247488 seconds. ** Attachment added: "syslog" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4533267/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
With the latest kernel with fix for temperature controller reports things are much improved. Resume wakeup causes: EINT,2903 94.47% CLDMA_MD 85 2.77% CLDMA_MD, 85 2.77% Suspend failure causes: tasks freezer abort 113 99.12% devices failed to suspend 1 0.88% 254 suspends aborted (7.83%). 2988 suspends succeeded (92.17%). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
** Changed in: canonical-devices-system-image Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Won't Fix 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
Device part 20160106-6a15a0b ** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Won't Fix 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
** Changed in: canonical-devices-system-image Status: Fix Released => Fix Committed ** Changed in: canonical-devices-system-image Milestone: None => ww02-2016 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Won't Fix 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
logs from dec 9 seem to have a lot of good data ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard
** Attachment added: "bluetoothd.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+attachment/4545874/+files/bluetoothd.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1531925 Title: bluetoothd crash with BTLE keyboard Status in bluez package in Ubuntu: New Bug description: Trying to pair this device and bluetoothd crashed on my Wily laptop and the N4 running latest proposed build number: 107 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu-pd last update: 2016-01-07 11:30:20 version version: 107 version ubuntu: 20160107 version device: 20150911 version custom: 20150929-2-vivid The device is a Logitech keyboard with an integrated trackpad. Device DF:08:A9:A0:13:91 Name: K830 Alias: K830 Appearance: 0x03c1 Icon: input-keyboard Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) RSSI: -43 The device would come and go in the devices list from bluetoothctl A manual scan would bring it back I then tried to manually pair and it failed with Failed to pair: org.freedesktop.DBus.Error.NoReply On the latop dmesg reports [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473936] Re: [wishlist] Sharing files via bluetooth
*** This bug is a duplicate of bug 1511525 *** https://bugs.launchpad.net/bugs/1511525 ** This bug has been marked a duplicate of bug 1511525 Can't transfer file using bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1473936 Title: [wishlist] Sharing files via bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Hello, I think that there should be possibility to share files (especially photos/videos by gallery app) via bluetooth by share button. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
My test MX4 did suspend reasonably over a period of several hours, trying my daily driver now -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519718] Re: Screen doesn't change after connecting a BT mouse and no cursor displayed.
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1519718 Title: Screen doesn't change after connecting a BT mouse and no cursor displayed. Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: ~$ system-image-cli -i current build number: 177 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-11-25 11:02:09 version version: 177 version ubuntu: 20151124 version device: 20151019-6d4a3ab version custom: 2015-918-8-52 Reproduce steps: Setup:Bluetooth mouse set to discovery mode. Step 1.Unlock the phone. Step 2.Swipe down the Bluetooth indicator. Step 3.Tap on Bluetooth settings. Step 4.Wait a moment for the device to appear in the list. Step 5.App switches to the device page, tap on connect. Actual result:Screen doesn't change after connecting a BT mouse and no cursor displayed. Expected result:App switches to Windowed mode and turns back to the Main Setting page for Bluetooth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
On my MX4 after half a day of use Suspends: 6826 suspends aborted (99.53%). 32 suspends succeeded (0.47%). Battery dropped 50% overnight -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505241] Re: Phone does not suspend
** Attachment added: "syslog" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4525282/+files/sl3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1505241 Title: Phone does not suspend Status in Canonical System Image: In Progress 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496756] Re: Nexus 7 devices which ship with android 5 need revised storage drivers
** Also affects: linux-flo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-flo in Ubuntu. https://bugs.launchpad.net/bugs/1496756 Title: Nexus 7 devices which ship with android 5 need revised storage drivers Status in Canonical System Image: Confirmed Status in linux-flo package in Ubuntu: New Bug description: It appears some Nexus 7 devices are shipping with a new MMC storage system, and so will not boot current phablet flo kernels To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode
** Changed in: canonical-devices-system-image Milestone: None => ww02-2016 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1488170 Title: Bluetooth initiated after quitting airplane mode Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in urfkill package in Ubuntu: Confirmed Bug description: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. Boot with bluetooth disabled Turn on flight mode turn off flight mode Bluetooth gets enabled See bug #1421249 for related symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518418] Re: devices need governor tuning for best performance
** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => ww02-2016 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Thomas Voß (thomas-voss) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1518418 Title: devices need governor tuning for best performance Status in Canonical System Image: Confirmed Status in linux-flo package in Ubuntu: New Status in linux-mako package in Ubuntu: New Bug description: spawned from bug 1513450 as well as some investigation by tvoss devices need to be tuned to utililze the interactive governor; available method employed by android/apple is to switch to interactive when the device is picked up (sensor) or screen is unblanked this actually applies to all devices, but i could only find/link our reference device projects. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1519007] Re: Ringtone not played on the speaker
** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1519007 Title: Ringtone not played on the speaker Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Test case. - Pair with a Bluetooth speaker. - Make a call to the device. Expected result. - A ringtone or wait sound is played on the speaker. Actual result. - Only the phone plays the ringtone. current build number: 186 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1519007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
** Also affects: turbo Importance: Undecided Status: New ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: New Status in bluez package in Ubuntu: New Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1586302] Re: Bluetooth and other issues connecting to Bluetooth speaker
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags added: bluetooth ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1586302 Title: Bluetooth and other issues connecting to Bluetooth speaker Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Aquaris E4.5 @ OTA 10.1 Attempting to connect to EasyAcc Bluetooth Speaker (https://www.amazon.co.uk/EasyAcc-Portable-Rechargeable-Bluetooth- Microphone/dp/B00JK6MQEI/ref=sr_1_3?ie=UTF8=1464297589=8-3=easyacc) Phone finds speaker and connects (no pin required). Audio is heard from the speaker for 1 second, then stops. The volume control stills says audio is routed to bluetooth speaker, but no sound output. Bluetooth cannot then be turned off (button appears to function to “off” position , but bluetooth remains active and button returns to “on” position after exactly 30 seconds) Attempting to switch to flight mode – the button “greys out” for 30 seconds, then appears as “on”. Wifi is disconnected but mobile network connections are still active. Switching off the bluetooth speaker has no effect, the phone still appears to be connected to it. Attempting to restart does not work – The phone switches off and does not restart. Hard reset is required to get the phone to boot again. Also if the phone is powered off, it will not restart until a hard reset is performed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
