Private Space blocks apps from creating new Bluetooth connections

beach

I think I've discovered an interesting property of private spaces. It appears that apps in Private Space can connect to existing (saved) Bluetooth devices, but they can not create/establish new Bluetooth connections.

I discovered this as I have several toys that require apps from the Google Play Store, and since I switched to Graphine OS to live a de-googled life, that is a problem. My solution is/was an owners profile that is google free, then put GPS in Private Space.

Two of the toys are a OneWheel and an ODBII adapter. They both require the app establish the Bluetooth connection, you can not add the device via the phones Bluetooth pairing functionality. When neither would work from Private Space I created another user profile, Google, and installed a VPN, GPS, and both apps there.

The OneWheel app is required to establish every connection to the OneWheel, and it does not leave the OneWheel as a Saved Bluetooth device in the phones Bluetooth connections. No matter what I have tried, I can not get the app to connect to the OneWheel from Private Space, but it works fine from the Google user profile.

The ODBII adapter requires it's app to establish a connection, but it does leave the ODBII adapter in the phones Saved Bluetooth devices. Once I connected to the Adapter once from the Googe user profile, I then locked, End Session, and went back to the Owner profile and unlocked Private Space. Now the ODBII adapter connects with no issue, as the Bluetooth setup is now in the Saved Bluetooth devices for the phone.

I know Private Space is new, does anyone know if this behavior is by design?
Has anyone else experienced this?
Or should I be able to connect to my OneWheel from Private Space?
If nothing else, I wanted to document this for anyone else coming across it.

eko

I just ran into the same issue with connecting the Sidus Audio App to a Deity audio recorder.
In this case I was lucky because the Sidus app does not require google play, and I ended up installing it in the GrapheneOS main user profile.
But in the GrapheneOS private space, the app did not discover the audio device via Bluetooth.
Of course it could be an alternative to have an additional user profile for such BT apps if I would really not want them in my main user. But I also see no reason why the private space should refuse to allow BT pairing. Ideally GrapheneOS could implement central control over the private space, to allow BT pairing, sharing system clipboard etc.

hemlockiv

Have you tried using a Work Profile (e.g. via Shelter app) instead of Private Space for this purpose? Work profile and Private space are basically identical features, both creating a second isolated userspace profile that is accessible from the owner profile. Both can be locked with a password, and all apps in the profile can be killed together.

Don't think I've ever had an issue creating Bluetooth connections from work profile, though!