Closed Bug 1083035 Opened 10 years ago Closed 10 years ago

Input touch events are not recognized properly in Music app

Categories

(Core :: Panning and Zooming, defect)

Product:
Core
Component:
Panning and Zooming
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-b2g 2.1+

People

(Reporter: vasanth, Unassigned)

References

Details

(Whiteboard: [caf priority: p2][CR 723065]) 

[Blocking Requested - why for this release]:

This is clone of bug 1068751
That bug was actually resolved for some days and we see the same issue again
in later builds of v2.1
gaia f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1
gecko db7fce920e7d782d9f601384dc95924abcdaeeb8

STR
---
While music playback is going on randomly touch play/pause, next, previous icons.
Sometimes input events are not recognized 100%.
In those cases, playback doesn't change and icons keep highlighting or just touch is not recognized

Able to reproduce with some effort. Repeatedly press the music app icons with 0.5-1 second delay. Once reproduced, next time it comes very easily.
See attached video.

I checked |adb shell getevent| shows proper events in failure cases, hence the issue could be in gecko.

Note:
Able to reproduce sometimes in camera app as well
Kartikaya Gupta, 
Could you please check this?
Flags: needinfo?(bugmail.mozilla)
I've seen this too and it's super annoying.
Flags: needinfo?(bugmail.mozilla)
Whiteboard: [CR 723065] → [caf priority: p2][CR 723065]
(In reply to vasanth from comment #0)
> [Blocking Requested - why for this release]:
> 
> This is clone of bug 1068751

Actually bug 1068571.

Do you see this on 2.2 as well? I'm not able to reproduce this on my device running master after a few minutes of trying. I'll throw on a 2.1 build and check that. If you have any other more reliable STR that would help as well.
See Also: → https://bugzilla.mozilla.org/show_bug.cgi?id=1068571
I'm not able to reproduce on 2.1 either using gecko revision db7fce920e7d782d9f601384dc95924abcdaeeb8 as mentioned in comment 0.
I reproduced using same exact steps mentioned in STR.
Did you also try with the same gaia version mentioned in comment 0?
No, I used the latest 2.1 gaia version since I assumed it wouldn't matter. I'll try with that version too just to make sure. Could you attach a video of you reproducing the bug? There may be subtleties in the behaviour that are not captured in the STR.
I tried with the gaia version you posted and was unable to repro with that either.
I see this on my Nexus 5 in a debug build all the time, but I've generally attributed it to being a debug build.
2.1 FC blocker = 2.1+ (even if it ends up already FIXED or WONTFIX ...)
blocking-b2g: 2.1? → 2.1+
Tested with Full Flash on 319mb using Engineering builds

This bug does NOT repro on Flame KK builds: Flame 2.2 KK, Flame 2.1 KK

Actual Results: All buttons in Music player while music is playing is responding to each and every tap the user applies. Rapid taps also show no odd behavior. Checked share, rate, repeat and shuffle buttons as well with still no bad behavior.

Repro Rate: 0/20

Environmental Variables:
Device: Flame Master KK
BuildID: 20141015113215
Gaia: 841d0d7d1b879f0ff4b5a8727f5dd23c7b0000a9
Gecko: a280a03c9f3c
Version: 36.0a1 (Master) 
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141015143144
Gaia: 477a9e61c3edf12f32a62a19d329cd277202cc6b
Gecko: 67573e422a0f
Version: 34.0 (2.1) 
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
 the steps seem solid - This might not be occurring on Flame anymore -
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Keywords: steps-wanted
No longer blocks: CAF-v2.1-FC-metabug
Blocks: CAF-v2.1-CC-metabug
Vasanth and/or Kyle, if you guys can reproduce this can you enable the logging at the top of AsyncPanZoomController.cpp (ENABLE_APZC_LOG), GestureEventListener.cpp (GEL_LOG), and InputBlockState.cpp (TBS_LOG), repro the problem, and attach the logcat? Otherwise there's not really much I can do. A video of the problem would also help, although the log would probably let me diagnose the problem faster.
Alright, I've enabled that.  If I see it again I'll post logs.
Also NI vasanth to see if he can help with logs requested in comment #12 to move further here.
Flags: needinfo?(vasanth)
(In reply to bhavana bajaj [:bajaj] from comment #14)
> Also NI vasanth to see if he can help with logs requested in comment #12 to
> move further here.

Hi Kartikaya,
We don't see this issue in our latest builds. Not sure why it was seen intermittent.
Will surely share the debug logs & video recording if it comes again.
Flags: needinfo?(vasanth)
Ok thanks. I'll close this for now but reopen it if you run into it again and have logs.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.