Fail to use google home mini as bluetooth speaker about bluez-alsa

[arkq]

OK, I'll look deeper into that issue...
Restarting bluealsa.service should have fixed the "stuck" issue. However, it's quite possible that bluealsa service is not restarted. Simply kill it with -9: pkill -9 -x bluealsa

[arkq]

Please try the current master branch. If the issue is not fixed, please reopen it.

[arkq]

It's quite possible that you've hit the bug introduced some time ago. Unfortunately, I've got no time right now to fix it properly. Try to replace these lines:

bluez-alsa/src/ba-transport.c

Lines 1625 to 1626 in 541523a

	if ((fd = t->acquire(t)) != -1)
	acquired = true;

with:

	if ((fd = t->acquire(t)) != -1) {
		ba_transport_thread_state_set_idle(&t->thread_enc);
		ba_transport_thread_state_set_idle(&t->thread_dec);
		acquired = true;
	}

EDIT:
If this will fix your problem, please let me know, and do not close this issue.

[neslinesli93]

Thank you for the quick reply. I tried your fix and the result was virtually the same as before: aplay worked two times and then it got stuck. Here are the logs: logs_aplay2.txt

Disconnecting and reconnecting to the speaker does not change anything, I always have to reboot. Not even restarting bluealsa.service fixes it :(

[neslinesli93]

You were right, killing the daemon fixed the issue! It still got stuck after a couple aplay runs, but at least it didn't require a reboot. It was kind of strange as the bluetoothctl connect command took almost 30 seconds to run, and it even logged an error before connecting. I'll add the logs again, as I don't know if they are useful or not... logs_pkill_connect.txt