You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the onboarding screen won't continue until I enable bluetooth, which doesn't seem to be possible yet.
Whenever I use the settings to enable bluetooth it just turns off immediately.
Describe the solution you'd like.
Either just fake bluetooth being enabled when you turn it on, or add a waydroid prop persist.waydroid.fake_bluetooth which accepts a comma separated list of package names for which the system will always appear as if bluetooth is enabled.
This approach is already used for wifi with persist.waydroid.fake_wifi
Describe alternatives you've considered.
forwarding the whole bluetooth stack or adding some kind of bluetooth passthrough, but these are much more complicated.
Additional context
I suppose some stubs would need to be written to fake handle bluetooth api calls and just always return an empty list of devices, etc, looks like someone has found some relevant links to lineageOS sources etc here and here is some research into the bluetooth intent failing
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Trying to run this apk because the unifi wifi router's web app is terrible: https://apkpure.com/amplifi-wifi/com.ubnt.unifihome
But the onboarding screen won't continue until I enable bluetooth, which doesn't seem to be possible yet.
Whenever I use the settings to enable bluetooth it just turns off immediately.
Describe the solution you'd like.
Either just fake bluetooth being enabled when you turn it on, or add a waydroid prop
persist.waydroid.fake_bluetooth
which accepts a comma separated list of package names for which the system will always appear as if bluetooth is enabled.This approach is already used for wifi with
persist.waydroid.fake_wifi
Describe alternatives you've considered.
forwarding the whole bluetooth stack or adding some kind of bluetooth passthrough, but these are much more complicated.
Additional context
I suppose some stubs would need to be written to fake handle bluetooth api calls and just always return an empty list of devices, etc, looks like someone has found some relevant links to lineageOS sources etc here and here is some research into the bluetooth intent failing
The text was updated successfully, but these errors were encountered: