-
Notifications
You must be signed in to change notification settings - Fork 148
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
Bluetooth: Not starting at all #108
Comments
Hi guys, I got the same problem. The service is running just after installation, but when I try to restart the service, the "systemctl restart bluetooth"-command just hangs. After that I was able to start the bluetooth-service again and got the following status: Mai 28 09:30:41 raspicast systemd[1]: Starting Bluetooth service... After reboot, the service is stopped again. I cannot restart (hangs), but starting bluetoothd and then starting the service works. I have no idea, what this means and what to do. Any suggestions? |
Yes! This happened to me after the latest update to bluetoothd a week or so ago. I think this update did something to the order of service startup in systemd. At first I thought it was just me because I've done some customization to get bluetooth to work with snapcast. But what @bruennlein lists above are the same symptoms as I had. Here's what happened to me if you want to check to see if it's the same for you: For some reason the bthelper@ service is trying to start before the rest of the bluetooth stack and holding it up because it runs "bluetoothctl discoverable on" (as added by rpi-audio-receiver in "/etc/systemd/system/bthelper@.service.d/override.conf"). You can confirm this by running "systemctl list-jobs" after reboot. If this is the problem, you'll see something like:
"bthelper@hci0.service" is "running" (ie., hanging) and the other services are waiting for it to complete to run. This seems to be because "bluetoothctl" hangs if "bluetoothd" isn't running, instead of failing. So "bthelper@" can't complete because "bluetoothd" isn't running but "bluetoothd" can't start until "bthelper@" completes. So everything is stuck. If you are experiencing the same thing, after reboot you should be able to run "sudo systemctl stop bthelper@hciX.service" and the rest of the stack will start up properly. Then you can "sudo systemctl start bthelper@hciX.service" (for some reason "restart" just hangs). OR, you can comment out "ExecStartPost=/usr/bin/bluetoothctl discoverable on" in "/etc/systemd/system/bthelper@.service.d/override.conf", then "systemctl daemon-reload" and everything will start again at reboot. Of course, then you need to script "bluetoothctl discoverable on" somewhere else or do it manually. I don't have a spare rpi to test to see if this is a repeatable issue (and I don't want to mess with the one that's working now!), so YMMV. I also don't know/understand enough about the bluetoothd update or systemd to suggest a long-term fix for this either. Anyway, hope this helps!!! |
Hi @lostmyshape , So unfortunately, I can´t do any investigation on my system, because I already installed a fresh Rasbian. But if I get back to this project, I´ll get back to you. See you... |
Hi, When the service bluetooth is stuck, I figure out that the command
I see their are some recent changes on bthelper RPi-Distro/pi-bluetooth@ae2efde . Now, the command ( |
Hey @sebPomme looks like you encountered the same thing as me and figured out the reason why! I'm getting a new pi on Monday and can test to confirm that this happens on a fresh system before setting the pi up for my intended purpose. |
I will try to move
in |
Not sure it's a help now, but I can confirm that with the 2021-05-07 RPi OS Lite, and updates, I can replicate exactly what @sebPomme describes above. After boot, stopping @sebPomme did the changes you made fix the problem at boot? |
Thanks @sebPomme. Just tested these changes (manually added them) and everything seems to work as expected now! You are awesome! |
I think you meant bthelper@hci0.service, if I'm not mistaken. I can confirm the issue overall, but I'm not quite sure whether the With my observation it seems more likely that Have a look at
Theory 1 So this means that at the time The arch wiki then related this to the kernel module My guess at this point is, that that the initialization of the internal bluetooth chip is happening differntly than the initialization of usb hci adapters. Hence, at the time the Theory 2 Another theory I developed while digging: Maybe I'll dig even deeper if I find the time. I'm more leaning towards theory 2 vs. the initialization of the bluetooth chip itself. This would explain, why my two Raspberry Pi 2B's (using USB BT dongles) don't experience the problem while my Raspberry Pi 3 (having an onboard Bluetooth chip) does have the problem. So could all of those affected by this issue check:
EDIT: one last remark: I also did a Cheers so far, |
Can confirm @sebPomme workaround works. Thank you very much! |
Hi, I have the same problem that is described in this issue, after having installed the bluealsa module (no bluetooth device showing up, I guess bluetooth isn't starting) Could you please explain me better the steps that I need to do? In which file I need to write those things? |
Actually the diff in the linked PR (#109) describes exactly what to do where. You need to apply those changes before you execute Should it get merged soon, you would only need to pull Cheers |
Oh I get it. I've already installed it 😅 Hope it will get merged soon |
Hi,
Today I tried getting this project to work on my Raspberry Pi 3 Model B, but unfortunately I never was able to get Bluetooth to work.. I tried with different versions of the current Raspi OS (lite, full), and same with older Raspbian releases.
Basically I always ended up with no bluetooth device showing up. When checking service bluetooth status, it always seems to respond the following:
Do you have any idea how I could resolve this? Thanks!
Edit:
On my fresh install, the output of service bluetooth status is as following:
The text was updated successfully, but these errors were encountered: