DAC Sound/ USB MIC

[hudiy]

The audio routing and pw-dump look fine. Both in Android Auto and outside of it, voice calls are handled through Ofono and PipeWire. The issue might lie on the Ofono side, possibly with MTU negotiation.

Could you please send the output of the lsusb and hciconfig commands?

Please also post output of hciconfig captured during the phone call - it will show number of received/sent SCO packets.

Also you can check using sudo btmon command if there is a TX/RX SCO traffic during the phone call.

[Giggig]

Here are all the logs you requested!

[Giggig]

I've had an interesting development, I started trying out multiple sound cards I had laying around the house and out of 5 sound cards the only one that worked with calling was a sound blaster G3 I had connected to my main PC. The problem seems to be a conflict, maybe caused by ofono that doesn't make it work with all but one sound card of mine. Very strange!
Another thing I noticed is that trying to route manually through qpwgraph the audio from the hudiy sink to the Pi's 3.5mm jack output instead of the sound card output, while maintaining the mic input through the sound card. To my amazement it actually worked! I still haven't figured out how to connect the hudiy sink to the Pi's internal sound card permanently but that shouldn't be too hard to figure out

[hudiy]

Thanks for keeping us updated on this. We checked the btmon traces and pw-dump. It looks like SCO traffic is working fine in both TX and RX. The MTU also seems correct. PipeWire appears to select the CVSD codec (8 kHz) for this dongle — probably due to the small MTU (48). That shouldn’t be an issue anyway.

Have you managed to resolve the problem? We can try to find such a dongle (it’s quite a common Cambridge Silicon Radio clone) and test it on our side.

You could also consider creating an issue on the PipeWire GitLab: https://gitlab.freedesktop.org/pipewire ... e/-/issues as the issue is strictly related to PipeWire.

[Giggig]

I tried using yet another audio dongle but with no avail, as of now the only one that has worked has been the soundblaster g3. What I'm thinking of is to follow the same setup that I used on opendash: audio coming out the Pi's internal jack and mic input coming in through the USB audio dongle. I'm still not sure if to make the audio go through the Pi's internal audio I have to specify it through hudiy's configuration file or through wireplumber.

By the way, what kind of DACs have you tested that are confirmed working?

[hudiy]

The Raspberry Pi’s headphone jack has very poor quality. It’s better to use even the cheapest USB sound card instead of that output. In our test setups, we usually use these sound cards:

https://www.unitek-products.com/product ... -converter
https://www.ugreen.pl/en/products/other ... 205-143396

As for Bluetooth dongles, we mainly use the built-in Bluetooth module on the Raspberry Pi and these USB dongles:

https://www.ugreen.pl/en/products/adapt ... query_id=1

All audio handling (such as routing, HFP, A2DP, equalizer, detection and management of sound cards and Bluetooth dongles) is done by PipeWire and WirePlumber. In Hudiy, you can configure which audio sink you want to control the volume of and which audio sink should receive the music. In practice, Hudiy simply uses the PipeWire API to say “increase/decrease volume on this sink” or “play this audio buffer on this sink.” All the underlying logic happens inside PipeWire.

What’s interesting in your pw-dump is that the dongle is using the CVSD codec for HFP. In our tests, we usually saw the mSBC codec being used, which is effectively the standard today. The use of CVSD may be related to the low MTU (48), whereas, for example, the built-in Bluetooth module in the Raspberry Pi operates with MTU 60.

In the meantime, we’ll order one of these Cambridge Silicon Radio 4.0 clones and test it with PipeWire on our side.

[Giggig]

I tried ditching the Cambridge Silicon Radio clone, replacing it with the Pi's onboard Bluetooth module and it finally worked! Even on the original audio dongle. Can't believe it was the Bluetooth module all along. I was always told that the Pi's onboard Bluetooth wasn't good enough for this use case but apparently this works fine. If I find any issue I'll just buy the ugreen Bluetooth dongle since it's also available in my country.

Thank you for helping me and thank you for making this software, now I can finally wrap things up and put everything back in my car. Thanks again!

[gregausina]

it would be good for a hardware section offering the basic or best plug and play options to get Hudiy implemented into a car and then users have the choice to add and improve. For example I have got the CarpiHat Pro with DAC means everything is clean and in one place and the other end of the DAC 3.5mm can go to whatever my car stereo setup is etc...

I'll include my notes on what I did for the DAC/USB Mic and include it here to help others.

Very good suggestion. I also have a Carpihat Pro and I struggle to configure audio. I've put my project on hold and I hope the new OS Trixie will help solve the sound management. I'm happy to see that I'm not alone with that hardware choice. I've been a little bit ambitious regarding my knowledge of the raspberry pi environment and I hope to find some help here because I can't find very usefull info on the carpihat pro anywhere.
Thanks for Hudiy ! It is very promising.