← Back to team overview

touch-packages team mailing list archive

[Bug 1488417] Re: nexus4 window mode mouse motion bounded incorrectly

 

unduping for the moment, after some discussion with anpok, while this is
similar we're not totally convinced it's the same

@duflu also, your are welcome please try this - specifically notice that if you move the mouse completely horizontal, the mouse will stick in a position that is inconsistent (e.g. sometimes sticks at a position further left or shorter left from the right edge than the previous time)
also, when the mouse "sticks" to a position while moving completely horizontal to the right, keep moving horizontal to the right, then move completely horizontal back to the left....the distance you travel back to the left is ~ the same before the mouse is "picked up" and "unstuck" giving it a feeling the position is changing for the mouse, however not rendering correctly.

note this is silo 0 where unity8 is doing the render - using the mir relative mouse events
to install
flash nexus4 with --channel=ubuntu-touch/rc-proposed/ubuntu
then install silo 0, unfortunately the silo is dirty holding back unity8 (atm i think) - so even if you install using ctrain tools you'll need to dist-upgrade
so....citrain device-upgrade 0 <device pin/password> , then apt-get update, apt-get dist-upgrade

-- 
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/1488417

Title:
  nexus4 window mode mouse motion bounded incorrectly

Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Opinion
Status in unity8 package in Ubuntu:
  New

Bug description:
  when connecting a monitor to the Nexus4 during windowed mode, the
  device is put into landscape mode. the mouse motion appears to not
  have followed the orientation and is bounded by roughly portrait width
  instead of landscape width

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488417/+subscriptions


References