01-21-2021, 08:34 PM
(This post was last modified: 01-21-2021, 08:41 PM by TheOldPresbyope.)
(01-21-2021, 08:00 PM)Alaini93 Wrote: Do you think if I use a DSi screen like this one i will not get that problem?
I think DSI doesn't need Local UI ON, correct?
1) It should work. I have an "official" RPi 7" touch display on one system. it's a DSI display and I've never had an incident with it like you first reported with an HDMI display.
2) Not so. The Local UI has to be enabled to see the moOde WebUI with either local display technology. The screen buffers get redirected to the DSI interface by the modules and driver loaded for it. With Local UI disabled, what you'll see displayed is the console terminal output.
I've now hooked up a 3.5" HDMI LCD display to my test system. I don't use the touchscreen feature on it so the driver for that isn't loaded. Having a physical display attached didn't affect the tests I did a while back but I can repeat my test now to see if I get any funniness with this new version of the chromium-browser package.
Regards,
Kent
