Closed Bug 1072086 Opened 10 years ago Closed 10 years ago

Device responds only to multitouch (not single touches) in certain areas.

Categories

(Core :: Panning and Zooming, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1072645

People

(Reporter: khuey, Unassigned)

References

Details

I'm filing this even though I don't have STR because I expect this will come up again during stress testing.

I managed to get my phone into a state today where it would not accept single touches in the app viewport.  That is, touching once on the software home button and on the lockscreen worked, but touching once on the home screen or various apps did not work.  If I tapped or scrolled with two fingers the app viewport worked as one would expect with one finger.  It was as if there were -1 fingers touching the app viewport.

Some combination of multitouches got me out of this state too, so I don't have much state to provide.

I suspect this is a multi-layer APZC bug but it might be a system app issue too, so CCing the usual suspects.
Version: 32 Branch → Trunk
Unfortunately nothing actionable here right now, but I'll keep an eye out for something like this. Off the top of my head I'm not sure what would cause a situation like this.
I wonder if it's an issue with APZCTreeManager::mRetainedTouchIdentifier - like maybe it doesn't get cleared for some reason, and then the hardware / whoever sets touch identifiers reuses the touch identifier in a subsequent touch, and we end up ignoring a touch point we don't mean to?
This might be a different issue, but today just while browsing the web on latest master *all* touch event stopped working for me within a browser frame. They worked on system chrome, and I could hold the home button to go into task manager, but they would not work in the browser. I did not try scrolling with two fingers, and I did not see anything in logcat.
That's pretty similar to what I saw, if you didn't try multitouch.
This will likely be fixed by bug 1072645. Since this bug is not easy to repro I'm going to optimistically dupe it over, but please reopen if this still happens with that patch applied.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.