Closed
Bug 859362
Opened 11 years ago
Closed 11 years ago
Bad touchscreen sensibility for Ikura
Categories
(Firefox OS Graveyard :: Hardware, defect, P1)
Tracking
(Not tracked)
RESOLVED
INVALID
1.0.1 Cert2 (21may)
People
(Reporter: dpalomino, Unassigned)
References
Details
(Whiteboard: IOT, Spain, Ikura, [POVB])
Hi, I think this is a specific hardware issue, probably a calibration issue. We are observing that touchscreen sesnsiblity is not good (and it's been reported during certification as a blocking issue also). For instance, if you try to select a text-box from a web site (for instance, google.com), it's difficult to select and some not experienced users should try several times to finally select it. Bug marked as a need info for the vendor. Blocking bug: P1 and nominated for tef?
Flags: needinfo?(mr.foxsmith)
Comment 1•11 years ago
|
||
Hi David, I'm not fully sure if this is a HW issue. My feeling is that it is purely related to bug 856083. Anyway, we will check it. David, Could you please make this bug dependent from bug 855322 (it seems I don't have permission for doing it) BR
Flags: needinfo?(mr.foxsmith) → needinfo?(dpv)
Comment 2•11 years ago
|
||
(In reply to Juan Perez-Bedmar [:jpbf] from comment #1) > Hi David, I'm not fully sure if this is a HW issue. My feeling is that it is > purely related to bug 856083. > > Anyway, we will check it. Please check it in detail because from our experience with other devices, this is a HW related issue and it is not the same as bug 856083. > > David, Could you please make this bug dependent from bug 855322 (it seems I > don't have permission for doing it) > Done
Flags: needinfo?(dpv)
Comment 3•11 years ago
|
||
Bug 856083 in the latest build for Open, so I'd suggest you test again, I am pretty sure as Beatriz says that the problem still persists.
blocking-b2g: tef? → tef+
Comment 4•11 years ago
|
||
Adding some colleagues in CC Please Lv Ang, Shen yang, and rest of the team, as it may be related to HW sensitivity check carefully this issue
Flags: needinfo?(lv.ang)
Updated•11 years ago
|
Whiteboard: IOT, Spain, Ikura
Comment 5•11 years ago
|
||
Hi, Juan, could we assign this case to one ZTE engineer to make sure it's on-going? Thanks!
Flags: needinfo?(juan.perezbedmar)
Comment 6•11 years ago
|
||
Sure, Kevin, Please assign it to Lv Ang. I will ping her so that she works on it or reassign it to another colleague
Flags: needinfo?(juan.perezbedmar)
Comment 8•11 years ago
|
||
I still believe it is a bug related to bug 856083, since it only happens in the browser (other text boxes don't show this problem) but anyway, I have just tried with a new build based on: gaia commit: f80afc3 Merge pull request #9055 from yurenju/bug-846197-v1.0.1 gecko commit: 8ed9c99 Bug 859552: Fix inari boot image. r=nthomas a=akeybl and this is solved. Please Lv Ang, confirm this so that we can close this issue Thanks!
Comment 9•11 years ago
|
||
We agree that the browser links are now working with this build but the sensibility of the touch display is very poor at least in my Inari sample. From the experience with other HW devices, I suggest your team to investigate it and check if you can improve the sensibility to increase the usability of the product.
Summary: Bad touchscreen sensibility for Open → Bad touchscreen sensibility for Ikura
Comment 10•11 years ago
|
||
I also recommend evaluating the sensitivity of the screen to swipe-gestures, especially opening the notification tray. That was a major issue on Unagi, where it took multiple swipes—even slow ones—to get any response from the system.
Comment 11•11 years ago
|
||
Lv, could we have your comment here to make sure this case is on-going? Thanks!
Comment 12•11 years ago
|
||
we test the latest version of Mozilla,this bug not exist. So it can be closed and if it happened again, we will reopen it.
Comment 13•11 years ago
|
||
(In reply to Firefox_Mozilla from comment #12) > we test the latest version of Mozilla,this bug not exist. So it can be > closed and if it happened again, we will reopen it. Could you please provide more detail explanation about which version it is and when we will receive it? I am testing in Inari with 20130411 and the issue is 100% reproducible.
Comment 14•11 years ago
|
||
We also test in 20130411 build, but use Ikura. Please use Ikura to test. Thank you!
Flags: needinfo?(lv.ang)
Updated•11 years ago
|
Whiteboard: IOT, Spain, Ikura → IOT, Spain, Ikura, [POVB]
Comment 15•11 years ago
|
||
I'm not sure who the comment 14 was aimed at, so let's add qawanted, just in case.
Keywords: qawanted
Comment 16•11 years ago
|
||
Using Ikura with Commercial RIL: Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/6d338a0f8c95 Gaia 2d048a9bdae54e4ec7d48326c2130591c8b869b6 BuildID 20130417230204 Version 18.0 I am not able to reproduce this issue. I tested the following scenarios using the browser: 1. Searching in google, bing and yahoo text fields (selecting the field and typing text) 2. Searching in bugzilla text field (selecting the field and typing text) There are two issues mentioned in the commments - one is selecting a text box to search (which is what we tested), and then there are browser links mentioned in comment 9. Removing qawanted for now - if further testing is needed with browser links please let us know.
Keywords: qawanted
Comment 17•11 years ago
|
||
Marcia, are you using the latest Ikura build that we received today? If so, sounds like we may be able to close this bug.
Updated•11 years ago
|
Flags: needinfo?(mozillamarcia.knous)
Comment 18•11 years ago
|
||
I am using the builds generated from our Mozilla directory, so I might not have the same build you are referring to. (In reply to Chris Lee [:clee] from comment #17) > Marcia, are you using the latest Ikura build that we received today? If so, > sounds like we may be able to close this bug.
Flags: needinfo?(mozillamarcia.knous)
Comment 19•11 years ago
|
||
Beatriz, is this reproducible with builds newer than 2013-04-11? If not, please close as WORKSFORME.
Flags: needinfo?(brg)
Comment 20•11 years ago
|
||
Hi Beatriz, you can test this again in latest version as 2013-04-23 or 2013-04-22, because these version is more closely with our 2st round test version, Thanks!
Comment 21•11 years ago
|
||
can anyone supply this information form the phone has the problem? you can get the information by this :cat /proc/touchscreen/ts_information
Comment 22•11 years ago
|
||
Reviewed on April 23th: This need to be resolved before the 3rd round of certification. The carrier will work with the OEM on this issue.
Reporter | ||
Comment 23•11 years ago
|
||
We think sensibility has been improved, could you please check this again? resolved/fixed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 24•11 years ago
|
||
Sorry, last comment was not complete. We think in latest builds provided by the vendor this issue has improved, but it will be necessary to recheck this before next testing version for the carrier Reopen the bug, as it was closed by mistake.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•11 years ago
|
Target Milestone: --- → 1.0.1 Cert2 (28may)
Comment 26•11 years ago
|
||
Unable to reproduce on the Inari device. Build ID: 20130426070207 Environmental Variables: Kernel Date: Feb 21 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/54285d67454b Gaia: c47ef39de04e634d847cc86b6acc616fabce69eb
Comment 27•11 years ago
|
||
David, who can verify this is fixed? It would be nice to have an assignee here.
Flags: needinfo?(brg) → needinfo?(dpv)
Comment 28•11 years ago
|
||
is this bug related to bug 865304 by any chance? We're seeing really bad touch responsiveness on the 4/23 builds.
Reporter | ||
Comment 29•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #28) > is this bug related to bug 865304 by any chance? We're seeing really bad > touch responsiveness on the 4/23 builds. Hi Jason, I think it's a different issue. In wikipedia case it's not possible to click on any icon no matter the attempts you do... Thks! David
Flags: needinfo?(dpv)
Reporter | ||
Comment 30•11 years ago
|
||
(In reply to Andrew Overholt [:overholt] from comment #27) > David, who can verify this is fixed? It would be nice to have an assignee > here. Hi Andrew, Sensibility has been improved, but it's still not very good. I'd maintain this issue open just for following it. Thanks! David
Comment 31•11 years ago
|
||
(In reply to David Palomino [:dpv] from comment #29) > (In reply to Jason Smith [:jsmith] from comment #28) > > is this bug related to bug 865304 by any chance? We're seeing really bad > > touch responsiveness on the 4/23 builds. > > Hi Jason, > > I think it's a different issue. In wikipedia case it's not possible to click > on any icon no matter the attempts you do... > > Thks! > David Actually, that's what the bug is. And it doesn't reproduce on unagi or any other device other than Ikura.
Updated•11 years ago
|
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Comment 36•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #31) > (In reply to David Palomino [:dpv] from comment #29) > > (In reply to Jason Smith [:jsmith] from comment #28) > > > is this bug related to bug 865304 by any chance? We're seeing really bad > > > touch responsiveness on the 4/23 builds. > > > > Hi Jason, > > > > I think it's a different issue. In wikipedia case it's not possible to click > > on any icon no matter the attempts you do... > > > > Thks! > > David > > Actually, that's what the bug is. And it doesn't reproduce on unagi or any > other device other than Ikura. That's not true. The wikipedia issues can be reproduced on unagi and any other devices. I already reopened that bug.
Comment 38•11 years ago
|
||
(In reply to Al Tsai [:atsai] from comment #36) > (In reply to Jason Smith [:jsmith] from comment #31) > > (In reply to David Palomino [:dpv] from comment #29) > > > (In reply to Jason Smith [:jsmith] from comment #28) > > > > is this bug related to bug 865304 by any chance? We're seeing really bad > > > > touch responsiveness on the 4/23 builds. > > > > > > Hi Jason, > > > > > > I think it's a different issue. In wikipedia case it's not possible to click > > > on any icon no matter the attempts you do... > > > > > > Thks! > > > David > > > > Actually, that's what the bug is. And it doesn't reproduce on unagi or any > > other device other than Ikura. > > That's not true. The wikipedia issues can be reproduced on unagi and any > other devices. I already reopened that bug. Well, I disagree then with your analysis. It works perfectly fine on my unagi device across two distinct builds - including today's 5/2 build.
Comment 39•11 years ago
|
||
Per talking over email, I'm going to close this bug and open a new bug specifically for bad touch sensitivity in Buri and a different one for Ikura.
Status: REOPENED → RESOLVED
blocking-b2g: tef+ → ---
Closed: 11 years ago → 11 years ago
Resolution: --- → INVALID
Comment 40•11 years ago
|
||
Moved tracking over to bug 868759.
You need to log in
before you can comment on or make changes to this bug.
Description
•