Page 1 of 1

Dangerous issue occurred while driving

Posted: Sun Aug 09, 2026 5:11 pm
by alex124.rh
Hi there while driving The radio woke up and when audio played it was static and at a deafening volume.

I’m wondering if something went wrong with audio config. it’s gone back to normal after a reboot so may rule out my amp dying.

It was so so loud and yet it said it was at 35%. it was occurring only when active audio playing and didn’t matter if it was autobox or Bluetooth. I am looking for some help so i can avoid it happening again can you help me look at logs or similar to see why.

please see example video https://share.icloud.com/photos/05ayAyf ... 4IW-htvavg

kind regards and thanks in advance

Re: Dangerous issue occurred while driving

Posted: Sun Aug 09, 2026 6:39 pm
by hudiy
Hello,
Please provide more details about your setup. What sound card, Raspberry Pi and power supply are you using? Are there any additional peripherals connected to Raspberry Pi? Are you running any other applications on your system? Typically, these types of problems are power-related. The Raspberry Pi is very sensitive to voltage drops, which can cause it to disconnect various USB devices, such as sound cards.

Re: Dangerous issue occurred while driving

Posted: Mon Aug 10, 2026 7:42 am
by alex124.rh
I’m using a

RPI 5
Cm6206 or similar sound card like yours
Carpihat pro
just got the sound card and autobox dongle connected to a powered usb hub

i just run hudiy and my own brightness tool

Re: Dangerous issue occurred while driving

Posted: Mon Aug 10, 2026 9:26 am
by hudiy
How is your USB hub powered? Is it a 12V or a 5V hub? Was there a voltage drop while the Raspberry Pi was booting up (e.g., from starting the engine - quite likely since the Raspberry Pi booted up while engine was running)?

Audio streams (e. g. from Hudiy) in PipeWire won't play louder than the master volume level. If the volume was set to 35% yet the CM6206 still outputted at full power and played static/noise instead of audio, it's very likely that the CM6206 suffered an internal firmware crash or desync, possibly caused by a momentary voltage drop.