You can see this bug from various perspectives. For common mice mouse, movement of the cursor on a high dpi screen is just slow. But since you still need accuracy you cannot just scale the movement. To allow exact cursor placement, movement dependent cceleration is the proper solution for this problem.
The fact that the android input stack did not offer acceleration was not a decision we made for versions prior to 0.18, but rather a bug in the velocity tracker for some reason it queried and tracked a non existent touch id. Fixing that required refactoring our tests to not rely on that bug. Which happened in the course of this year. In the end we just switched to libinuput. -- 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/1517133 Title: [regression] Mouse speed in Unity8 is much lower than elsewhere (to the point of useless) Status in Mir: Fix Committed Status in QtMir: Confirmed Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Running unity8 as a session on the desktop. The mouse is so "slow" (i.e a movement in reality moves it very few pixels on screen) that i can't really use it since i need to lift it and restart the movement a few times if i want to go to the other side of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1517133/+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
