From 0c1370b5f1b3e8abc934ea913a4377f05f32e4a9 Mon Sep 17 00:00:00 2001 From: Yuval Adam <_@yuv.al> Date: Mon, 7 Aug 2017 22:05:24 +0300 Subject: Initial static build --- docs/wiki/Screen-Calibration/index.html | 60 +++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 docs/wiki/Screen-Calibration/index.html (limited to 'docs/wiki/Screen-Calibration') diff --git a/docs/wiki/Screen-Calibration/index.html b/docs/wiki/Screen-Calibration/index.html new file mode 100644 index 0000000..4a201dc --- /dev/null +++ b/docs/wiki/Screen-Calibration/index.html @@ -0,0 +1,60 @@ + + +
+ + +
+ postmarketOS
+ On most Android devices, a somewhat working framebuffer is required to get Weston and other Wayland compositors running. The alternative to framebuffer would be [[DRI|Glossary#dri]].
+If your framebuffer does not work out of the box, try the following:
+ Run this to set the framebuffer resolution: cat /sys/class/graphics/fb0/modes > /sys/class/graphics/fb0/mode
+ Boot TWRP/Android and read out the correct framebuffer configurations from the /sys... paths and try to set them in pmOS
+* If you made it work, create an initfs hook, that instantly sets the framebuffer right. Example
/tmp/weston.log (via SSH) for the touch device name. For lg-mako, the name is touch_dev, but it may be different for your device.device-lg-mako to your device's aport. Replace touch_dev with your touch device name. Adjust the APKBUILD, so it gets installed properly (Example)hammerhead). If it does, you are done here. Otherwise continue for the calibration.sudo su - (Because right now, Weston runs as root)weston-calibrator as rootweston-calibrator