[Bug 1287240] Re: Racy issue on first run after flash
This seems to of gone away so I'm marking it invalid ** Changed in: bluetooth-touch (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287240] Re: Racy issue on first run after flash
I'm reflashing 214 to confirm that 214 reliably shows bluetooth, upgrading seems to show bluetooth with no issues. ** Description changed: Using ubuntu-device-flash --channel=devel-proposed --device=mako/flo --bootstrap I see no bluetooth most times on the initial boot of the device. This was first spotted on Mako r217 and reproduced on flo I then took flo back to r214 and Bluetooth showed up fine. From 215 on it became flakey. + + Running adb reboot seems to fix it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287240] Re: Racy issue on first run after flash
So I have reflashed r214 and bluetooth shows up with no issues again. I'm now updating from 214 to 218 to ensure that it still shows up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287240] Re: Racy issue on first run after flash
root@ubuntu-phablet:/# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287240] Re: Racy issue on first run after flash
218 has no bluetooth logs to follow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287240] Re: Racy issue on first run after flash
root@ubuntu-phablet:/# getprop | grep hci [ro.qualcomm.bt.hci_transport]: [smd] [init.svc.hciattach]: [stopped] [bluetooth.hciattach]: [true] This is from my mako rather than flo but seeing the same issue on no bt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287240] Re: Racy issue on first run after flash
** Attachment added: new syslog with bt up after reboot https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+attachment/4005307/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287240] Re: Racy issue on first run after flash
After reboot commands for comparison: root@ubuntu-phablet:/# getprop | grep hci [ro.qualcomm.bt.hci_transport]: [smd] [init.svc.hciattach]: [stopped] [bluetooth.hciattach]: [true] root@ubuntu-phablet:/# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287240] Re: Racy issue on first run after flash
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+attachment/4005302/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287240 Title: Racy issue on first run after flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1287240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
