This topic is temporarily closed for at least 4 hours due to a large number of community flags.
1 Like
11 Likes
This topic was automatically opened after 8 days.
This topic is temporarily closed for at least 4 hours due to a large number of community flags.
1 Like
This topic was automatically opened after 4 days.
This topic is temporarily closed for at least 4 hours due to a large number of community flags.
2 Likes
This topic was automatically opened after 18 days.
Let’s get this topic on topic again 
It will be interesting to see what is Huawei doing with their Harmony OS 5 since they are now doing something similar to SFOS - OS made from scratch, not based on android and running android apps in container + microG for google services. If they want to keep their user-base they will have to really nail the android emulation.
As far as SFOS is concerned it all boils down to what kind of deal they can make with their partner that provides appsupport (SeaFrix, i believe they are called?)
OR waydroid will become more mature over time and we will just switch over. It’s waiting game at this point, I’m afraid
6 Likes
You mean stop flagging others posts and the topic stops being locked?
I wish this from day one 
1 Like
I wanted to post this here since I’m doing some research. The proxmox guys cetainly have a mechanism for making bluetooth devices available to lxc containers.
the main issue with the approach is that you’d create a situation where the host/sfos could lose the ability to use bluetooth while the container is using it. Would probably cause a host of pain
EDIT: relevant kernel patch: [PATCH] net/bluetooth: make bluetooth socket can be created in net namespace
13 Likes
This is OK for many of the bluetooth android apps that cause big problems if you can’t occaisionally use them
e.g lock boxes, configuration apps, etc. These are apps where you can be screwed if you can’t make it work when you have to.
Losing your SFOS headphone connection while you unlock a post box, or rent a scooter is not a show stopper. This would work for me.
14 Likes
It is possible to do the same for NFC?
3 Likes
It is possible to make Bluetooth work in AAS in 5.x. Problem is that it is either or. You can have AAS controlling Bluetooth or SFOS, but not both at the same time. I had to have my smartwatch connected to Android only app via Bluetooth and managed to make it work in AAS under C2.
8 Likes
Would you mind to write a how-to?
2 Likes
Enable Developer Tools enable SSH remote access and connect to C2 via SSH:
Go to root:
$ devel-su
Stop AAS if running from SFOS settings menu.
Stop bluetooth and bluebinder services:
[root@JollaC2 defaultuser]# systemctl stop bluetooth
[root@JollaC2 defaultuser]# systemctl stop bluebinder
[root@JollaC2 defaultuser]# systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
Active: inactive (dead) since Sun 2025-06-01 19:08:39 BST; 27s ago
[root@JollaC2 defaultuser]# systemctl status bluebinder
● bluebinder.service - Simple proxy for using android binder based bluetooth through vhci.
Loaded: loaded (/usr/lib/systemd/system/bluebinder.service; disabled; vendor preset: enabled)
Active: inactive (dead) since Sun 2025-06-01 19:08:56 BST; 19s ago
Restart C2 Android Bluetooth HAL:
[root@JollaC2 defaultuser]# /system/bin/stop vendor.bluetooth-1-1
[root@JollaC2 defaultuser]# /system/bin/start vendor.bluetooth-1-1
Edit the Appsupport lybhybris config file so we can passthrough C2 Bluetooth HAL inside AAS LXC container:
vi /opt/appsupport/etc/appsupport.conf.d/10-hybris.conf
Find Proxies= part of the config:
# Some hybris specific values
...
Proxies=android.hardware.graphics.allocator@4.0::IAllocator,android.hardware.graphics.allocator@3.0::IAllocator,android.hardware.graphics.allocator@2.0::IAllocator/default
Proxies=android.hardware.power@1.3::IPower,android.hardware.power@1.2::IPower,android.hardware.power@1.1::IPower,android.hardware.power@1.0::IPower/default
Proxies=android.hardware.camera.provider@2.4::ICameraProvider/legacy/0
Add new line after last Proxies= and save the file
Proxies=android.hardware.camera.provider@2.4::ICameraProvider/legacy/0
#Add this line below
Proxies=android.hardware.bluetooth@1.1::IBluetoothHci,android.hardware.bluetooth@1.0::IBluetoothHci/default
Start AAS from SFOS settings menu.
Once it is running go back to root shell and enable AAS Android Bluetooth package:
[root@JollaC2 defaultuser]> appsupport-attach pm enable com.android.bluetooth
Package com.android.bluetooth new state: enabled
Under SFOS AAS Settings Tap 5 times on “Android version 13” on the same page to open AAS Android settings.
Under Connected devices-> Pair new device you should see ‘Device name’ as ‘Spreadtrum BT’ and see scan list of BT available devices.
64 Likes
Very impressive! Have you tried NFC too?
Edit: and that of course requires another phone than the C2, so i guess not?
2 Likes
Does this work on Sony Xperia XA2 too?
I do not have any other android device - only C2, so I cannot test.
What i don’t get about the statement about Bluetooth. Wether you can use Android or SFOS. Is this not the same situstion as with telephone network, wifi, NFC, they are all usable wether by Android or SFOS, but we can use them at the same time on both OSes. So what would be the particularity of the Bluetooth connection, compared to the other interfaces…