search

lukasjapan / bt-speaker

A simple Bluetooth Speaker Daemon for the Raspberry Pi 3
GNU General Public License v3.0
495 stars 95 forks source link

Software not playing sound after a while... #3

Open lucatk opened 7 years ago

lucatk commented 7 years ago

I don't know if it's the software or my hardware that's faulty... Whenever I connect to the Pi after it had been inactive for a while since last using it (eg reconnecting to the Pi the next day), it won't play any sound to my 3.5mm jack. It still connects and the bluetooth works just fine, but it won't play any sound unless I completely reboot it.

Also, a sound indicating when the Raspberry has successfully connected to a device (and also to verify that it does still play sound) would be very helpful. I might just as well suggest an "auto-reconnect" feature while I'm at it, so my Pi would always connect itself if it finds any known device..

Thanks in advance, I really do like this project!

lukasjapan commented 7 years ago

Hi, I haven't tried to connect for so long, so I might look into this this weekend if I find time.

About the sound indicator, I have done it for my personal project and might include the feature in this repository as well.

Auto reconnect is a bit tricky for now because I think you would need some way to tell the daemon to remove "autoconnected" clients. Otherwise there could be complications when multiple clients are involved.

lukasjapan commented 7 years ago

Connect/Disconnect sounds were added.

lucatk commented 7 years ago

Nice, how am I going to update my software?

lukasjapan commented 7 years ago

I updated the install script and it should now work over an existing installation. So you can try to run the command from the readme file again.

I made some changes to the systemd daemon definition file, you may also have to run systemctl daemon-reload. Systemd will explicitly ask for that if needed.

dbaumgarten commented 6 years ago

@lucatk can you check if the aplay-process is running when there is no sound? (sudo ps -aux | grep aplay ) Also what does your log say? (journalctl -u bt_speaker) Is it showing IOErrors?

You could be having the same problem as described in issue #30 .