de0u
In any system there is some limiting factor. A GPU that can drive large monitors with a high refresh rate costs more chip space and more money and more heat than a GPU that can drive smaller monitors. A GPU pulling more and larger pixels per second out of the phone's DRAM will leave less DRAM bandwidth for running apps.
It should not simply be assumed that recent Pixel Android devices can't do more than 1920x1080 @ 60 Hz over the USB-C DisplayPort.
Because Samsung and Motorola Android devices for example can do 3840x2160 @ 60 Hz (and more) over their USB-C DisplayPort, for multiple years. Some random example videos:
And they do not show any pixelation.
And:
de0u
This isn't a security issue (at least, it doesn't appear to be a security issue).
That's irrelevant. @GrapheneOS itself states that regular desktop operating systems (incl. Linux distributions) would be less secure than GOS.
So it's reasonable to assume that proper image quality on the USB-C DisplayPort output is in @GrapheneOS 's best interest, to enable the use of GOS devices as desktop alternatives.
And:
de0u
And, since Google has steadily been making changes to their external-display support, it seems likely they will be making more changes.
Hopefully so. But that still is not a reason to not bring it up on this forum.
Because @GrapheneOS is reporting to contribute to upstream. So it's not necessarily unreasonable to report these issues to @GrapheneOS (via this forum for example).
de0u
Typically the GrapheneOS project does not spend developer time trying to fix non-security "it would be nice" issues in areas of code that Google is changing rapidly. If the project doesn't plan to do anything about this, I can imagine that marking the thread as "Solved" makes sense from a tracking perspective.
As indicated above, it's not a "it would be nice" feature. It's an essential feature.
And instead of assuming what @GrapheneOS would or wouldn't think, maybe it would be better to simply let @GrapheneOS reply.