Private Space user is the best place for apps like this, but with Envoy installed in the private user option the bluetooth doesn’t connect. This IS possible as I have it elsewhere. I’d give you more exhaustive testing but it’s likely you just haven’t explored this yet.
1 Like
Thanks for the report. Could you share some details on phone make, model, OS number etc and I’ll test this when I’m back from Easter break on Tuesday.
I have a feeling that @Jack might have also tested this, but not 100%.
1 Like
pixel 9 pro stock current
Thanks for the extra info. I’ve made a ticket to discuss and track this internally (ENV-2918).
@biscuits When you say ‘it is possible as you have it elsewhere’, can you provide specifics of what you’re able to do?
I’ve had a bit of a dig into this. The short version: Google explicitly says in their Private Space help article that “you should not use private space for apps that need to provide you with functionality in the background when your private space is locked.” Private Space locks aggressively and stops every app in the profile the moment it does, which is a bad match for QuantumLink. The BLE session gets killed whenever the space locks, so even if pairing succeeds once it won’t stay reliable.
What Google doesn’t document is whether active BLE pairing is additionally restricted while the space is unlocked. We’ll do some testing on that front (cc @Jack )
Either way, the official guidance from Google is that Private Space isn’t the right place for apps like Envoy that need a live hardware connection, so for now I’d recommend running Envoy in your main profile when you need to talk to Prime.
Simply that I can use Bluetooth within apps, within the secure user space. I have other wallets and apps happily in there, including banking apps. This obviously does cover the gnarly cases like this and I would struggle to find a matched example that isn’t simply “bluetooth works”.
Send and receive content over Bluetooth from private space apps
- You can send content over Bluetooth from private space apps: Shared content and metadata doesn’t reveal the existence of private space.
App controlled outbound bluetooth things are ok, but….
I can readily believe this is at some level an inhibited feature somehow. I use the same ‘account’ in both. Mainly its just to slow down my doom scrolling and provide some plausible deniability on a load of apps I would sooner not have surface day to day. There’s a decent chance I would just spin up a new device rather than have foundation apps on my daily phone, because, obviously really, but my MAIN use for the device is actually the key management and 2FA side (pending the FIDO2 implementation) so this would be a shame.
1 Like