Public bug reported: 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]: <warn> Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: <info> (/ril_1): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: <info> (/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]<MAGNETIC> 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.000000]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [ 0.000000]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [ 0.000000]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 ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: rtm14 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1387949 Title: power cycling BT device caused phone to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1387949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
