AndroidAuto 1080p touchscreen issue

[SeriousVlad]

Hi! I'm running Gudiy on Raspberry Pi5. When I launch AndroidAuto in 1080p mode, the touchscreen is really unresponsive when trying to do any slides with my finger, as in moving the map around or scrolling the song on Spotify. Regular touches work perfectly.
I tried launching it in 480p or 720p and I could use the map perfectly fine - dragging worked well. What could be the issue? It doesn't seem to be the performance problem, because when I Alt+Tab on the desktop a touch works fine.

Would appreciate any help, AA config below.

Code: Select all

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

[SeriousVlad]

Forgotten to attach video of the issue, here you go.
https://drive.google.com/file/d/1_UjWV0 ... sp=sharing

[hudiy]

Hello,
What touchscreen are you using in your setup?

By default, labwc has mouse emulation enabled. This might be interfering with your touchscreen in some way. You can try disabling this feature and see how the touchscreen behaves: viewtopic.php?p=878#p878

[SeriousVlad]

What touchscreen are you using in your setup?

It's a Waveshare 8.8 inch DSI (https://www.waveshare.com/8.8inch-dsi-lcd.htm).

By default, labwc has mouse emulation enabled. This might be interfering with your touchscreen in some way. You can try disabling this feature and see how the touchscreen behaves: viewtopic.php?p=878#p878

Trying it now.

[SeriousVlad]

Disabling mouse emulation changed nothing, but I have noticed an interesting behavior.
Touch works properly only in the topmost part of the screen (the third of it). I enabled the cursor display and tried using the mouse and encountered the same behavior - I can scroll the map only in the top third of the screen, while in the bottom third only clicks/taps work. (https://drive.google.com/file/d/1hTKPma ... drive_link)

Could it be related to scaling/margins because of the odd resolution and aspect ratio?

[hudiy]

With the provided details we were able to reproduce the issue on our end. Thank you. We will introduce a fix in the upcoming version, which will be available later this month.

[SeriousVlad]

With the provided details we were able to reproduce the issue on our end. Thank you. We will introduce a fix in the upcoming version, which will be available later this month.

Awesome, thanks! After the fix is done, would you mind sharing the reason for it? As a Software QA of 10 years, I have a professional curiosity about the bugs I find unintentionally

[hudiy]

The root cause is that both Android Auto and Hudiy crop the 'dragging' area of the rendering surface based on the margins set. As a result, the dragging area gets way smaller than the rendering surface and that's why dragging works only on a part of the surface. This cropping is not applied to tap gestures so that's why it is not affected. The bigger the margins, the more visible the issue becomes. It looks like this behavior was changed somewhere between Android Auto versions. We already have a fix prepared and tested. The release is planned for around April 16th.