Re: AGL 10.0.0 with Raspberry Pi4 1020x600 display issue

["Stefan Gudmundsson" <exologic@xxxxxxxxx>]

Thanks!

I'll see if I can find some time to go deeper into this area, right now, I'm
focusing on the Telematics features and protocols, that in many cases are
common between the IVI/Telematics profiles, unless you have a split system
with both units.

/Stefan

-----Original Message-----
From: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
[mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Marius
Vlad
Sent: Thursday, November 5, 2020 2:05 PM
To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  AGL 10.0.0 with Raspberry Pi4 1020x600
display issue

On Thu, Nov 05, 2020 at 12:05:00PM -0800, Stefan Gudmundsson wrote:
> Thanks for the quick feedback.
> 
> There is indeed a "wayland.ini" file, but perhaps it's ignored by the 
> system. It's in the QT recipes as well.
Wayland is a protocol, if there's a ini file for it won't be read by
anything.
> 
> It seems to me that not using more common touchscreens (that fits the 
> PI) is a mistake. Small/embedded 1080p touchscreens are unobtainium. 
> Supporting a more common panel would encourage more PoCs and tests, 
> that's my take anyway.
I don't know what the common touchscreens are for RPI but I for one welcome
and encourage contributions. I also believe we should be able to support of
variety of devices no matter the size.

AFAIK, we *never* had dynamic scaling for the demo applications, I believe
this is good opportunity to contribute just that. The demo apps load-up the
QMLs dynamically, and you can read out the current resolution of the output
before loading that. You obviously need assets and QMLs that correctly
align/map to that output resolution, for all demo apps to display/show
visually correct in tandem.

> 
> Most real implementations would use their own UX anyway, but as a PoC
Exactly, the complexity of adding global scaling was deemed unnecessary as
people are building their own UIs, the clients can take care of doing that,
and 1080p is ubiquitous since 2010. And for the demo app, people do have
displays with that resolution. 

With that in mind, we resorted to remove any additional layers of complexity
that brought that in. Global scaling w/ the help of the toolkit was added to
support systems that didn't have sufficient memory to handle a 1080
resolution (for instance, RPI3 w/ 1GiB RAM). Maybe it was just a happy
coincidence that (global) scaling was helpful for other types of panels.
> vehicle using PI's and common Touch panels would be of value, my 2c....
Sure, and I like I've said, patches are welcome to address the issue.
> 
> /Stefan
> 
> 
> -----Original Message-----
> From: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> [mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Marius Vlad
> Sent: Thursday, November 5, 2020 9:56 AM
> To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  AGL 10.0.0 with Raspberry Pi4 
> 1020x600 display issue
> 
> On Thu, Nov 05, 2020 at 09:36:20AM -0800, Stefan Gudmundsson wrote:
> > Hello,
> Hi,
> > 
> >
> > 
> > AGL 9.0.0 works well with a Raspberry Pi4 HDMI touchscreen with 
> > resolution of 1024x600.
> > 
> > But in 10.0.0, the display appears up scaled many times, you only 
> > see upper quadrants of images and HMI is at least 4x too large, 
> > including text etc. A regular HDMI monitor works, as does a HD TV.
> > 
> >
> > 
> > I have tried setting mode in wayland.ini, but that does nothing. 
> There's no wayland.ini configuration file.
> > 
> >
> > 
> > Considering it worked in 9, something changed/broke to 10.
> > 
> >
> > 
> > Any ideas? Where can I find adjustments to screen resolution? 
> Long story short is that you need a 1080 resolution for your display 
> to work with the demos.
> > 
> > Will it only honor "standard" resolutions?
> It will honor whatever resolution you use in your weston.ini file, but 
> the applications are expecting a 1920x1080 resolution. With the 
> lastest release
> (10) a 1080 (HD) display will be needed to work out-of-the box. 
> Any other resolutions will need modification to the demos.
> 
> Previously this was possible by letting the toolkit handle that, so 
> there's nothing in the way of doing the same thing, as a work-around 
> (and you can find examples from previous versions on how to do that).
> Either way, by using adjusting the applications to handle multiple 
> resolutions, or by using the toolkit to perform the upscale/downscale 
> for you, you'll need to operate modifications for every application.
> > 
> >
> > 
> > Stefan
> > 
> >
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8819): https://lists.automotivelinux.org/g/agl-dev-community/message/8819
Mute This Topic: https://lists.automotivelinux.org/mt/78056612/2167316
Group Owner: agl-dev-community+owner@xxxxxxxxxxxxxxxxxxxxxxxxx
Unsubscribe: https://lists.automotivelinux.org/g/agl-dev-community/leave/4543822/883735764/xyzzy [list-automotive-discussions82@xxxxxxxxxxx]
-=-=-=-=-=-=-=-=-=-=-=-