10-29-2022, 05:36 PM
(10-29-2022, 04:39 PM)Tim Curtis Wrote:(10-29-2022, 04:24 PM)bitlab Wrote: @Tim Curtis I just also runned into this problem:
[pi4 / m8.2.2 / k 5.15.61]
- Didn't not use bluetooth
- Disabled integrated bluetooth adapter in the system menu
- Reboot
- No moode ui after (`moodeutl -l` was also hanging at show bluetooth feature in worker.php)
My workarround was disabling bluetooth feature to allow moode correct:
Code:moodeutl -A rm 16384
Can it be that there is some unwanted condition that can be triggered?
Thats always a possibility. I'll investigate later today.
Did you have Bluetooth ON in Renderer Config?
Yep that is it
The condition:
Turn off the Integrated Bluetooth adapter in the system menu, while Bluetooth was on in the rendering menu.
The result:
moode will not boot anymore (hang at startup).
No way the resolve the issue from the gui, because it isn't running.
Workarround:
Use a ssh session (not the web one, that isn't available) to disable the bluetooth feature.
After restart with `moodeutl -r` you can disable the Bluetooth render. and enable the bluetooth feature again.