-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dory] Bluetooth does not turn on #129
Comments
I just flashed the latest nightly on dory and I can not reproduce your issue. Please provide more information such as:
Possibly related: AsteroidOS/meta-smartwatch#47 |
I have just build a dory image and the Bluetooth is working for me too. |
Actually, last night, I have shutdown my watch and this morning, this morning, I have the same issue, as described in AsteroidOS/meta-smartwatch#47
Nothing special in dmesg about Bluetooth:
|
|
Thanks @jrtberlin I have replaced the 8 seconds sleep by 20 seconds, reboot and Bluetooth worked! |
Great to hear! Still is is just a workaround (and we don't know if that fixes it for @FurryFan2003) would be great to get to the bottom of it and find out what it actually depends on and define it in the unit. |
Hi Everyone, I am new to all this, and am trying this OS on my old LG G. I too have been having the problem that bluetooth is not turning on. I believe that I tried the @jrtberlin's fix that I changed: ExecStartPre=/bin/sleep 8 to ExecStartPre=/bin/sleep 20 in /lib/systemd/system/patchram.service. Is that what I was suppose to do? If so, it did not help. Any other suggestions? |
On a fresh nightly this seems to have worked for me so far as well |
I know this is ultra late but even with the latest nightly (14-Aug-2021 11:57) bluetooth is still busted for me |
For me bluetooth has been a non issue since the fix. Also flashed the latest nightly and Bluetooth still working fine every time |
Tested recent dory nightly and found no BT issues. Solved. |
Bluetooth doesnt work at all and the toggle for it sometimes crashes the entire OS
The text was updated successfully, but these errors were encountered: