hudiy.eu

Posted: **Sun Apr 19, 2026 6:46 am**

Hi.

Firstly, I'm just a beginner with hudiy and Android Auto so please foprgive my lack of knowledge. Is there a getting started guide somewhere? I've tried looking but can't not been able to find anything...

So, I have a raspberry PI 4B, bookworm with a touch display 2 (uses DSI not HDMI). I'm connecting with Android Auto on my phone via bluetooth and the phone is connected to hudiy's wifi hotspot, which seems to be working fine, but not sure how audio is supposed to work. Am I supposed to connect my vehicle's bluetooth to the RPI for audio or use the 3.5mm audio jack to my vehicle's aux input? At the moment I can't get either to work.

When I use the audio jack, the problem is that the jack isn't the default sink. I can exit hudiy, right click the audio icon and choose it and it'll then work, for any sound played on the RPI, but after a reboot, the setting is reset.

I've tried using 'wpctl status'. There is only 1 sink, the audio jack and it has no asterisk to show it id default. I can use 'wpctl set-default <ID>' to set it to the sink, which also gets reset after a reboot.

Trying a bluetooth approach, everything connects, but no audio comes through. I do probably need to do more experimentation on this approach tbh, but not sure if it's even supposed to work this way.

Many thanks in advance.
edit: ending of post truncated!

Posted: **Sun Apr 19, 2026 9:23 am**

Hello,

When Android Auto is connected and both speechAudio and mediaAudio are set to true (https://github.com/wiboma/hudiy/blob/ma ... ndroidauto), audio data is transmitted via either USB or Wi-Fi (depending on your Android Auto connection method) and will be played by the sound device connected to the Raspberry Pi (internal Jack, HDMI, or a sound card). When speechAudio and mediaAudio are set to false, the audio output will be selected by the phone (e.g., an A2DP device that is paired with your phone, the jack output, or the internal speaker).

The issue you are describing looks very similar to the one with the echo cancel module on Trixie. On Trixie, when there is no microphone input (e.g., from a sound card), the echo cancel module will take the sink's monitor as a microphone input and, as a result, will cut all the audio played by the sink.

The solution is to disable the echo cancel module when you do not plan to use a microphone in your setup, or to simply connect a microphone input. Disabling the echo cancel module can be done by modifying $HOME/.hudiy/share/hudiy_startup.sh (the script where all PipeWire modules are loaded).

The default sink in the system after installing Hudiy is hudiy_equalizer_sink. PipeWire and WirePlumber will automatically create routing where the hudiy_equalizer_sink outputs to the audio device. You can check and edit the routing generated by PipeWire/WirePlumber using, e.g., the qpwgraph utility.

Also, is there any specific reason for using Bookworm in your setup? We definitely recommend using Hudiy on Trixie. Trixie is currently the actively developed version of the Raspberry Pi OS. Additionally, it provides features like selecting the hotspot's channel bandwidth (increasing Wi-Fi throughput) and Bluetooth cover art. Bookworm receives only critical security updates and is marked as a legacy OS.

To disable the echo cancel module loading, please replace the contents of $HOME/.hudiy/share/hudiy_startup.sh with the following (Bookworm):

Code: Select all

#!/bin/bash

EQ_SINK="hudiy_equalizer_sink"
DUMMY_SOURCE="dummy_source"

sink_exists() { pactl list short sinks 2>/dev/null | awk '{print $2}' | grep -Fxq "$1"; }
source_exists() { pactl list short sources 2>/dev/null | awk '{print $2}' | grep -Fxq "$1"; }
until pactl info >/dev/null 2>&1; do sleep 0.1; done

# Gives PipeWire and WirePlumber additional time to detect all audio devices
sleep 1

sink_exists "$EQ_SINK" || pactl load-module module-ladspa-sink sink_name="$EQ_SINK" plugin=hudiy_equalizer label=hudiy_equalizer control=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
source_exists "$DUMMY_SOURCE" || pactl load-module module-virtual-source source_name="$DUMMY_SOURCE"

pactl set-default-sink "$EQ_SINK"
pactl set-default-source "output.${DUMMY_SOURCE}"

$HOME/.hudiy/share/hudiy &

Posted: **Sat Apr 25, 2026 7:58 am**

Hi.

Thank you so much for your help. Apologies, when I checked, I am running Trixie (I'm not quite sure how I was under the impression I was running Bookworm!).

Disabling the echo cancel line worked great, thank you, however I decided to get a sound card as you mentioned as I've not been able to get hey Google working - the command activates the facility, but it can't then hear what I say, so I figured the sound card's microphone may well sort that, which it has.

Finally I just wanted to say what an amazing product you have with hudiy. I spent so much time trying other (no longer supported/dead) solutions before I came across hudiy and by far hudiy was by far the easiest and best.

hudiy.eu

problems with audio

problems with audio

Re: problems with audio

Re: problems with audio