Page 1 of 2
Low Android Auto Resolution
Posted: Fri Aug 01, 2025 5:39 am
by pault
Good Afternoon,
Software looks great! Just having an issue where the Android Auto resolution is much lower than the resolution of the rest of the UI. Have you encountered that problem?
Screen:1024x600 (7in)
PI: Pi5 8gb
Phone: Pixel 7a
also getting a Couldn't find matching udev device error
Re: Low Android Auto Resolution
Posted: Fri Aug 01, 2025 6:27 am
by hudiy
Hello,
Glad to hear that, thank you!
Regarding the resolution:
By default, Android Auto uses a resolution of 480p. This can be changed in the main_configuration.json file:
https://github.com/wiboma/hudiy/blob/ma ... ndroidauto
For a screen resolution of 1024×600, you can use the following values to utilize the entire screen surface:
Code: Select all
"resolution" : "720p",
"widthMargin" : 256,
"heightMargin" : 120,
Explanation:
720p corresponds to 1280×720
Your screen resolution is 1024×600
1280 - 1024 = 256 -> widthMargin
720 - 600 = 120 -> heightMargin
---
The "Couldn't find matching udev device" error originates from the Raspberry Pi file manager (pcmanfm). By default, it attempts to mount newly connected USB devices as mass storage. You can disable this automatic mounting behavior in the pcmanfm settings.
Re: Low Android Auto Resolution
Posted: Fri Aug 01, 2025 8:20 am
by Zyox
Could you please provide an example for how this would work with screens in the middle of these settings/awkward sizes?
I'm trying to run on the following:
- 8 inch 1280 x 800
- 9.3inch 1600x600
Thanks!
Re: Low Android Auto Resolution
Posted: Fri Aug 01, 2025 9:17 am
by hudiy
Zyox wrote: Fri Aug 01, 2025 8:20 am
Could you please provide an example for how this would work with screens in the middle of these settings/awkward sizes?
I'm trying to run on the following:
- 8 inch 1280 x 800
- 9.3inch 1600x600
Thanks!
Sure,
For 1280x800:
Code: Select all
"resolution" : "1080p",
"widthMargin" : 640,
"heightMargin" : 280,
Your display resolution is 1280×800.
Since 720p (1280×720) does not fit vertically (720 < 800), 1080p (1920×1080) must be selected.
widthMargin: 1920 - 1280 = 640
heightMargin: 1080 - 800 = 280
For 1600x600:
Code: Select all
"resolution" : "1080p",
"widthMargin" : 320,
"heightMargin" : 480,
Your display resolution is 1600×600.
Since 720p (1280×720) does not fit horizontally (1280 < 1600), 1080p (1920×1080) must be selected.
widthMargin: 1920 - 1600 = 320
heightMargin: 1080 - 600 = 480
Just for the record — in Hudiy, you're free to set any size and position for the Android Auto or Apple CarPlay projection. It doesn’t have to be fullscreen.
You can use the remaining screen space, for example, to display your own custom overlay with OBD-II data or any other useful information.
Re: Low Android Auto Resolution
Posted: Fri Aug 01, 2025 9:19 am
by Zyox
Amazing thank you for the quick reply.
I'll play around with the custom overlay on the wide-screen for sure. Sweet.
Re: Low Android Auto Resolution
Posted: Fri Aug 01, 2025 9:44 am
by hudiy
Zyox wrote: Fri Aug 01, 2025 9:19 am
Amazing thank you for the quick reply.
I'll play around with the custom overlay on the wide-screen for sure. Sweet.
You are welcome! You can find examples on our GitHub
https://github.com/wiboma/hudiy/tree/ma ... les/api/js
Just for the record - widescreen display isn’t required to use overlays. They can be shown on any type of the screen, layered over any content. Hudiy comes with built-in overlays for displaying navigation meneuvers from AndroidAuto and for displaying volume controls.
You can find more details about overlays in the documentation:
https://github.com/wiboma/hudiy/blob/ma ... d#overlays. It’s a really powerful tool for customizing your system.
Re: Low Android Auto Resolution
Posted: Sat Aug 02, 2025 2:21 am
by pault
Thanks for the quick reply. I will try this later today. I'm wondering if the margin essentially shrinks the size of the Android Auto display on the screen, or if it simply instructs the program on how much to scale the software. Is automatic scaling a feature you are thinking of adding? I think having scaling options within the menu would be nice, as exiting the HUDIY app to edit files on the Pi is a bit of a pain. Just food for thought. I know this app has only been out for a couple of weeks. Thanks for all you do.
Re: Low Android Auto Resolution
Posted: Sat Aug 02, 2025 7:30 am
by pault
hudiy wrote: Fri Aug 01, 2025 6:27 am
Hello,
Glad to hear that, thank you!
Regarding the resolution:
By default, Android Auto uses a resolution of 480p. This can be changed in the main_configuration.json file:
https://github.com/wiboma/hudiy/blob/ma ... ndroidauto
For a screen resolution of 1024×600, you can use the following values to utilize the entire screen surface:
Code: Select all
"resolution" : "720p",
"widthMargin" : 256,
"heightMargin" : 120,
Explanation:
720p corresponds to 1280×720
Your screen resolution is 1024×600
1280 - 1024 = 256 -> widthMargin
720 - 600 = 120 -> heightMargin
---
The "Couldn't find matching udev device" error originates from the Raspberry Pi file manager (pcmanfm). By default, it attempts to mount newly connected USB devices as mass storage. You can disable this automatic mounting behavior in the pcmanfm settings.
I set the settings as you have them and it still looks like 480p. Should I mess with the DPI setting???
Re: Low Android Auto Resolution
Posted: Sat Aug 02, 2025 7:41 am
by hudiy
Margins work in a way that Android Auto adds black borders of the specified size, and then uses the remaining area to display the UI. Those black borders are later cropped out by Hudiy.
DPI only affects the size of elements in the Android Auto interface - it doesn't change the actual resolution.
Do you maybe have developer options enabled in Android Auto? Sometimes they force a specific resolution (like 800x480), which could override the settings.
The settings you should use depend on what you're trying to achieve.
If you notice sharp edges on Android Auto elements or see black borders on the screen (wrong aspect ratio), then you should adjust the margins and resolution to properly size the video stream. But if everything looks fine visually, then tweaking the DPI is enough to adjust the size and layout of the Android Auto interface.
We’re considering adding an autoScaling option to the AndroidAuto settings. When enabled (by default), Hudiy would automatically calculate the appropriate density and margins. Disabling autoScaling would allow users to configure these parameters manually, preserving the current behavior.
Re: Low Android Auto Resolution
Posted: Sat Aug 02, 2025 8:41 pm
by pault
hudiy wrote: Sat Aug 02, 2025 7:41 am
Margins work in a way that Android Auto adds black borders of the specified size, and then uses the remaining area to display the UI. Those black borders are later cropped out by Hudiy.
DPI only affects the size of elements in the Android Auto interface - it doesn't change the actual resolution.
Do you maybe have developer options enabled in Android Auto? Sometimes they force a specific resolution (like 800x480), which could override the settings.
The settings you should use depend on what you're trying to achieve.
If you notice sharp edges on Android Auto elements or see black borders on the screen (wrong aspect ratio), then you should adjust the margins and resolution to properly size the video stream. But if everything looks fine visually, then tweaking the DPI is enough to adjust the size and layout of the Android Auto interface.
We’re considering adding an autoScaling option to the AndroidAuto settings. When enabled (by default), Hudiy would automatically calculate the appropriate density and margins. Disabling autoScaling would allow users to configure these parameters manually, preserving the current behavior.
Hey! thanks for all the help. I included some pictures to show my issues, because nothing has worked yet. Is there something i need to run after changing the config to apply the settings? I have just been rebooting.
- PXL_20250802_203433473.MP-min.jpg (110.36 KiB) Viewed 43 times
- PXL_20250802_203450732.MP-min.jpg (196.62 KiB) Viewed 43 times
- PXL_20250802_203406905.MP (1).jpg (160.78 KiB) Viewed 39 times