New/different Touchscreen won't start using old settings

[emeeder]

I originally had a 8" Touchscreen that launched perfectly.

Unfortunately I had to switch to a 8.9" Magedok Touchscreen and it just keeps blinking out and never seems to launch correctly. By the way when I did not allow your software to launch the new touch screen put it up perfect, so I know it's got to be something with the settings with your app.

Here is the settings for androidAuto in the config file...

"androidAuto" : {
"speechAudio" : true,
"mediaAudio" : true,
"resolution" : "720p",
"bluetoothAddress" : "",
"autostart" : true,
"fps" : "30",
"dpi" : 160,
"widthMargin" : 0,
"heightMargin" : 0,
"width" : 0,
"height" : 0,
"x" : 0,
"y" : 0,
"gpsDataSource" : "GPSD",
"useRpiDrm" : false,
"dayNightMode" : "COMMON"
},

What should I tweak/change to get this new unit launching properly? (Quick responses please because I am on a time crunch this week to get this installed Monday.)

The androidAuto section was the only thing I changed from the default. I don't remember what the default was, and I'm not sure what I did here that might not be happy to the new monitor.

[hudiy]

Hello,
Could you please give more details about the exact problem? How it is related to Android Auto? What exactly do you mean by it "keeps blinking out and never seems to launch correctly"? Also, how are the screen and Raspberry Pi powered?

[emeeder]

Right now they are both being powered by full power from AC source (they aren't installed in the car yet).

What I mean is that I keep seeing the touchscreen "try" to show the main HUDiy screen and I think what's happening is that it then tries to immediately launch Android Auto and due to something in those settings it blinks back out.

I don't think that it's the monitor, although I suppose I don't know that for sure. I could power down anything else running on my Pi 5 and just plug in the monitor and (without having HUDiy's user systemctl launch) just see if the monitor works... but I'm going to "assume" that that is going to work fine.

[hudiy]

Do you run Hudiy in console mode or in desktop mode? What is the detected resolution of the screen?

[emeeder]

I always run it only on the console in console mode... I never even play with the other.

(The only real tweaks I made other than those androidAuto settings was that I took "user systemctl" away and started just having it launch when the "console" (the touchscreen) get plugged in and the Pi sees that it's powered,but this setup also worked fine with the last 8" touchscreen.)

Here's the details from the monitor... 8.9" display, 1920x1200 FHD, 16:10 aspect ratio, IPS LCD, 170° viewing angle

I updated the androidAuto to this to try... doesn't seem any better.

"androidAuto" : {
"speechAudio" : true,
"mediaAudio" : true,
"resolution" : "1080p",
"bluetoothAddress" : "",
"autostart" : true,
"fps" : "60",
"dpi" : 240,
"widthMargin" : 0,
"heightMargin" : 0,
"width" : 0,
"height" : 0,
"x" : 0,
"y" : 0,
"gpsDataSource" : "GPSD",
"useRpiDrm" : false,
"dayNightMode" : "COMMON"
},

[emeeder]

Okay... nevermind. It seems to be something with the way my python script "sees" the new touchscreen monitor, cause once I shut the script down HUDiy started right up.

Thanks, though... I'll figure it out...