losing touches in arale when home button is pressed

Bug #1439285 reported by Daniel d'Andrada
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
High
Alexandros Frantzis
mir (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Might be a bug in arale's drivers, but worth checking mir first.

Image: vivid-proposed #155

Steps to reproduce:
1 - lay one finger on the screen and start moving it (do *not* lift it)
2 - while step 1 is ongoing, tap the home button with another finger a couple of times

Expected outcome:
touch events from step 1 keep coming as long as your finger is moving

Actual outcome:
Eventually you stop receiving touch events from step 1. If you lift your finger and tap on the screen you will get a touch-pressed with a new id. So you will never even get a touch-release for the finger from step 1.

Tags: patch arale

Related branches

tags: added: arale
kevin gunn (kgunn72)
Changed in mir:
importance: Undecided → Critical
Changed in mir:
assignee: nobody → Alexandros Frantzis (afrantzis)
Revision history for this message
kevin gunn (kgunn72) wrote :

alf offered to take a look tomorrow
btw, dandrader saying he's just heavily crippled by this issue, not necessarily dead in the water

Changed in mir:
status: New → In Progress
Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

This behavior seems to be caused by an optimization present in the Android input stack, which is supposed to reduce the latency of handling certain "app switching" keys like "Home".

As a quick fix, the attached patch disables the optimization, but we should investigate if/how we can make use of it with our usage scenarios (esp. if we actually enable a home button in a device).

Revision history for this message
Daniel d'Andrada (dandrader) wrote :

I confirm the patch does fix the bug. Excellent work!

Changed in mir:
milestone: none → 0.13.0
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.13.0

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
importance: Critical → High
Changed in mir:
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "Proposed fix for lost input events with home button" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mir - 0.13.1+15.10.20150520-0ubuntu1

---------------
mir (0.13.1+15.10.20150520-0ubuntu1) wily; urgency=medium

  [ Cemil Azizoglu ]
  * New upstream release 0.13.1 (https://launchpad.net/mir/+milestone/0.13.1)
    - ABI summary: No ABI break. Servers and clients do not need rebuilding.
      . Mirclient ABI unchanged at 8
      . Mircommon ABI unchanged at 4
      . Mirplatform ABI unchanged at 7
      . Mirserver ABI unchanged at 31
    - Bug fixes:
      . Can't load app purchase UI without a U1 account (LP: #1450377)
      . Crash because uncaught exception in mir::events::add_touch (LP: #1437357)

 -- CI Train Bot <email address hidden> Wed, 20 May 2015 21:20:15 +0000

Changed in mir (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.