After trying around a bit more... If we intend to use the emulator in the future we might want to tweak which input devices are exposed the guest system. RIght now there is a single odd abs-relative-touchscreen- mouse hybrid. For odd reasons it was treated as touch screen in the past (we didnt really differ with the android stack: everything not a key event is a motion event). With libinput it will be seen as a mouse that either emits absolute or relative coodinates. So we will lack the capability to simulate touch input.
Additionally the relative mouse mode works very badly. It seems to skip a lot of mouse movement or they are scaled down? For either of the problems we might have to change the emulator window code. Which I believe we take from here: https://android.googlesource.com/platform/external/qemu/+/master/android/skin/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1517597 Title: Ubuntu-emulator is broken on rc image 3 Status in Canonical System Image: Incomplete Status in mir package in Ubuntu: New Status in phablet-tools package in Ubuntu: New Bug description: STEPS: 1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test 2. Wait for it to build 3. Run with ubuntu-emulator run rc-test 4. Starts up but the mouse never moves meaning you can't leave the first page of the welcome wizard EXPECTED: I expect the emulator cursor to follow the mouse cursor and be able to click on things ACTUAL: Emulator cursors stay in the top left preventing movement. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
