That process got me closer. I ran the commands you shared this afternoon at 800x600, and the touchscreen display worked, but the touch input only worked on the bottom half and was inverted both in the x and y directions.
Then I tried running the commands just now, with different HDMI-1 modes from xrandr. The 720x480 caused the screen to glitch out with a black screen and static-y pixels. Then I switched it to 800x600, and the screen corrected itself and displayed the image, still cut off UI. I followed it up with 1024x768 and 640x480, and the visual didn't change. I switched back to 720x480 because it would fit on the screen like you said, and the touch input works well (no inverses or dead zones). I flipped it to 800x600 and the touch input became off.
I think 720x480 might set the displays right for the next steps, how do I make these settings permanent?
As for the next steps I think I have to find a way to tweak MoOde's WebUI dimensions and responsiveness. Would you know how I could do that or is that a question for the MoOde forums and boards?
Then I tried running the commands just now, with different HDMI-1 modes from xrandr. The 720x480 caused the screen to glitch out with a black screen and static-y pixels. Then I switched it to 800x600, and the screen corrected itself and displayed the image, still cut off UI. I followed it up with 1024x768 and 640x480, and the visual didn't change. I switched back to 720x480 because it would fit on the screen like you said, and the touch input works well (no inverses or dead zones). I flipped it to 800x600 and the touch input became off.
I think 720x480 might set the displays right for the next steps, how do I make these settings permanent?
As for the next steps I think I have to find a way to tweak MoOde's WebUI dimensions and responsiveness. Would you know how I could do that or is that a question for the MoOde forums and boards?
Statistics: Posted by Spiffy24 — Wed Apr 16, 2025 6:41 am








