=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === JanC_ is now known as JanC === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [22:55] TheKit: you should be able to do that via a udev property [22:56] is it using libinput? [22:56] TheKit: set LIBINPUT_CALIBRATION_MATRIX to .. hmm let me check [22:56] I found LIBINPUT_CALIBRATION_MATRIX example in libinput docs, but it didn't seem to work [22:56] yes for some time now [22:57] ENV{LIBINPUT_CALIBRATION_MATRIX}="0 -1 1 1 0 0" # 90 degree clockwise [23:04] ah .. you said the scrolling is only affected? [23:05] not the touch coordinates itself are wrong? [23:05] touch coordinates are also wrong [23:05] ok [23:06] is there any package for libinput-debug-events? [23:10] it should be provided by libinput-tools... [23:14] hmm there is no env var to change the log priority in libinput and we dont chanage it from the default [23:15] you could check udevadm info .. but I think that might not be there by default to see that the property is really there [23:24] http://pastebin.com/y3AXG5tZ - the property is there, but it doesn't affect input (tried different rotations) [23:25] I'm using vivid rootfs, can something older be used there? [23:25] hm most of ubuntu-touch is pulled out of the stable phone overlay ppa [23:27] by the way, if I use use evtest to check events, top-left is 0, 0 and bottom-right is about 1079,1919, so no rotation should be needed in theory [23:29] TheKit: then that should be what we pass on to unity8 [23:29] TheKit: I mean we dont apply any rotation within the mirserver instance inside unity-system-compositor [23:30] similarly nothing happens inside the mirserver instance of unity8 which receives the input events.. [23:30] on some devices unity8 rotates the screen - and thus also rotates the coordinates.. [23:31] because mir does not yet provide an animated orientation transition... unity8 does that internally [23:32] so there is a chance that the graphics output and input handling in u8 make conflicing decisions [23:35] Possibly. If put device landscape, screen gets rotated, but touch screen is rotated with it as it should be, and so is still wrong [23:35] *if I put