Wishes/Bugs

[hudiy]

Hi,

I have a suggestion / request.

When opening a menu in hudiy or opening an extension like a html page, There is a nice soft transition effect that makes it smooth. The pages almost fade in, however when opening CarPlay via the resume button it has a hard snap from the hudiy interface to carplay, can you make this smoother? I don’t know if there is other areas this could be applied but it would elevate the polish on this area of the UI. kind regards

Great idea, thank you. We will add it in upcoming version.

[tomryan31]

Maybe a strange wish / request, as I fully understand the build being on top of Linux, but is there any thought put towards having Android Auto work without a tethered phone connection (offline for instance?) with Google Maps or the like?

I had initially started my project (before discovering Hudiy) with an install of KonstaKang's AOSP 16 as a tablet and was going to provide data over tethered USB or hotspot so a GPS + RTK could function without a cell phone.

I haven't played with HTML Customizations / overlays (saw the images with OpenStreetMaps), just didn't know if there was any investigation into natively supported android applications (or a build on top of AOSP). I realize this would be a huge undertaking, certainly beyond me, but wanted to inquire.

Thank you for such an amazing product!

[korni92]

Having multiple phones connected, it would be great to be able to switch between these when using android Auto. At the moment it seems that it randomly pics the one, that connects first.

[MrNick]

Perhaps this RPi DSP would integrate with Hudiy. From Warsaw, Poland, where there seems to be a lot of talent.

https://lectronz.com/products/louder-raspberry-hat

[k.s.deviate]

Would it be possible to add an input option? Specifically usb audio input, like an aux. I wish to use a usb sound card with line in to be able to run analog audio into and out of the pi.

[hudiy]

Would it be possible to add an input option? Specifically usb audio input, like an aux. I wish to use a usb sound card with line in to be able to run analog audio into and out of the pi.

This should be configurable directly in PipeWire using the loopback module. The loopback module can redirect the audio stream from a source (e.g., your input) to a sink (e.g., your audio device sink or hudiy_equalizer).

https://docs.pipewire.org/page_module_loopback.html
https://docs.pipewire.org/page_pulse_mo ... pback.html

[hudiy]

Having multiple phones connected, it would be great to be able to switch between these when using android Auto. At the moment it seems that it randomly pics the one, that connects first.

Hudiy implements logic that allows only one phone to be connected via Bluetooth at a time. The main reason for this behavior is a hardware limitation: the built-in Bluetooth module, as well as most USB dongles, can only handle A2DP and HFP connections from a single device simultaneously. With multiple concurrent A2DP and HFP connections, the Bluetooth stack may behave unpredictably (e.g., resulting in stuttering audio or a complete loss of sound). Therefore, when a new phone connects, Hudiy automatically disconnects the currently active one to ensure only one device remains connected.

The hardware (MAC) address of the last connected phone is stored in $HOME/.hudiy/cache/cache.json and Hudiy will attempt to reconnect to it automatically upon startup.

[gwynethh]

Maybe as things stabilize, some of the supporting scripts can be automatically installed as part of an update. Things like the safe shut down, screen dimming and automatic rear camera activation. This might help some of us noobs. (Thanx for your help on these in other posts).

[hudiy]

Maybe as things stabilize, some of the supporting scripts can be automatically installed as part of an update. Things like the safe shut down, screen dimming and automatic rear camera activation. This might help some of us noobs. (Thanx for your help on these in other posts).

Thanks for the suggestion. Making our GitHub examples more user-friendly is definitely a priority - especially regarding autostart and dependency installation. It’s currently in our backlog, but we're slightly behind schedule mainly due to issues with RAM availability and pricing, which impacted Raspberry Pi costs and forced us to prioritize accessibility for the Pi Zero 2, 3B, and 3B+. Managing the RAM constraints on those models took significant effort and forced a shift in our priorities. We expect to be back on track by version 1.22/2.18 and at that point, we will focus fully on suggestions from the forum.