The referenced LXD related discussion on problems with bluetooth within container is about seven years old. Maybe the related defitiencies within the linux kernel have been modernized by now?
Anyway. In the LXD issue tracker this issue was closed in may 2017 and a reasonable workaround was pointed out that makes use of libusb’s userlevel bluetooth stack in conjunction with the usb device type.
So maybe there could be a comparable solution in our case with alien dalvik? Having to plug a USB BT dongle into the phones USB-C in order to rent e-scooters or set up solar inverters surely would be a no issue at all. It would indeed remove one of the bigger pain points 
2 Likes
This will be a showstopper for me for using Jolla and I would have to say goodbye to Sailfish, even though I have been there from the very beginning.
1 Like
There is a patch which was not merged:
https://lore.kernel.org/lkml/20170814071640.289327-1-fupan.li@windriver.com/
+1 for the feature request.
I finally found today, what is causing me so much trouble and making me carry around second phone with android that pairs to all those apps that run well on SFOS app support, but for some strange reason do not pair with the devices because of which I have them. This is it.
Could you explain it in detail. I’m interested, but I don’t understand what you mean.
He means that he did not realize the lack of the feature “Bluetooth in App Support” before he read this thread, after months of trying to connect devices
I’ve linked these before, but for the sake of stirring curiousity:
First, docker specific, but docker uses the kernels cgroups foo:
LXC specific
No idea how far any of this gets us since I have no idea how jolla sets up lxc for the android layer.
4 Likes
I remembered this feature, a few years after stopping using sailfish os due to that exact feature missing (public buses are using it, their app is no longer locked so bad that i couldn’t use it, but the bluetooth is a must) and someone here was nice enough (lunatic, that just doesn’t understand, that some features are a must - due to the external factors forcing you, not using buses due to sailfish is just a deal breaker) to pushed me into it.
Nice to see my decision was correct, now I am happy Pixel and GrapheneOS user, while I hate google and would be happy with alternative and would prefer sailfish but not with company that is so badly ignoring users needs.
For, 5 years.
You are just not getting it, sailfish, although technologically better, than android, is not a market leader, rather market follower and critical features of android, affecting real life usage, are something that should be top priority, not pushed to the side, even if it means hiring someone who can do it.
I no longer think that this project has any future. Not due technology, due to bad management and priorities.
1 Like
@stiray I understand your issue, thats why I have an android phone in my bag if I have to use bluetooth/bank software. But did you see: Potential Bluetooth Support in the Android App Support (AAS) - #206 by rdomschk ? The bluetooth issue could be solved for you?
You are so right. What sense does SF make for us all, when you cannot buy a bus ticket?
3 Likes