USB-C Display Support #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Displayport only works if UART is disabled
Right now, display hotplug is broken. Also, manually forcing the display leads to Mir destroying the internal display.
Ok, USB-C display out works in Ubuntu Touch with the following modifications:
ubports/libhybris@fbeb930a18-> only treat display id 0 as primary, otherwise the external display causes the internal one to get disconnectedThe Pixel defaults to 1920x1080 for external displays (hardcoded in the exynosdisplay vendor library). It can be overwritten via
(the comparison is exact, so writing 2560x1440@60 does not work if the mode is 59.95 Hz).
Usually, Android's system_server would register with IUsb, which causes the Pixel's vendor USB HAL to start its uevent worker listening for USB type-C events. Since we don't run system_server in Halium, we need to manually register with IUsb. This could be done by a new service included in the Halium container, but I decided to do it on the host instead to prevent Pixel specific code in the Halium build.
I still need to set up an automated build for this and set up a systemd service to autorun it when the container starts.
It only compares the integer part, so
2560x1440@59works for 59.95Hz.For 1440p, one also needs to set
Otherwise it defaults to a displayport link rate that only supports 1080p and the exynos module drops higher resolution modes.