here is a proof of concept script+systemd unit ... http://paste.ubuntu.com/24537569/ using this setup i have properly working BT after boot *if* the bluez snap is in --devmode
my proposal forward would be to: - ship a similar script inside the bluez package - make it a daemon so we get a systemd unit for it - ship an interface connection for pi-bluetooth in bluez' snapcraft.yaml the script allows for adding other hardware to the case statement for other boards we encounter ... indeed with the "pi3:pi-bluetooth" approach we have in place now this means that the bluez snap now needs to define all possible interfaces for all boards in the snapcraft.yaml to allow hciattach access to the different tty devices on different boards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674509 Title: Unable to find bluetooth device on RPi3 running Ubuntu Core 16 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1674509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
