Yeah, I noticed the missing sound as well. Seems that I failed to test it again after the previous resync back in march, and since I’ve just gotten back to work this week (new baby at home, so I was off work for a while), I didn’t actually receive a call in my car until just a couple of days ago. And because I’m getting used to a new routine this week, I haven’t even had a chance to dump the logs.
What I’m seeing in your log there that stands out, is “BTCARD: -1”.
This means that it has not picked up the alsa device corresponding to the bluetooth i2s. There are two possible places for the problem; the HAL, or the KERNEL. Both of these possibilities are tied into audio related changes in the kernel.
What I mean by that is this;
Either the code in the HAL that detects the path of the alsa devices was unable to account for the changes in the kernel, or the kernel is no longer presenting the alsa device corresponding to the i2s.
Neither possibility is particularly difficult to fix.
The code that detects the sound card;
The relevant kernel bits are here;
The way to tell if its kernel or HAL:
You’re looking for a sound device that supports BOTH capture AND playback, that is NOT the USB card.
This is the actual selection criteria I’ve used, which I’ll admit is not the strongest;
If you look at it right now, what you can do is run “ls -l /dev/snd” and “ls -l /sys/class/sound” and post theie outputs here.
Also, if you could get a log of usbaudio from higher up in the logcat “logcat | grep usbaudio”, and a dmesg, those would also be very helpful.
Note that contrary to my previous statement that I wasn’t going to work on software until I’m through with the hardware, this is a small enough bug and significant enough annoyance to me that I’ll definitely work on it asap.
And finally, you will note that I’ve changed over to gitlab. I’m not comfortable with the ownership changes at github, so I’m not going to be using them any further.