Closed Bug 859362 Opened 11 years ago Closed 11 years ago

Bad touchscreen sensibility for Ikura

Categories

(Firefox OS Graveyard :: Hardware, defect, P1)

Product:
Firefox OS Graveyard
Component:
Hardware
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID
Milestone:
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)
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)
(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)
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+
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)
Whiteboard: IOT, Spain, Ikura
Hi, Juan, could we assign this case to one ZTE engineer to make sure it's on-going? Thanks!
Flags: needinfo?(juan.perezbedmar)
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)
Thanks, Juan!!
Assignee: nobody → lv.ang
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!
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
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.
Lv, could we have your comment here to make sure this case is on-going? Thanks!
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.
(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.
We also test in 20130411 build, but use Ikura. Please use Ikura to test. Thank you!
Flags: needinfo?(lv.ang)
Whiteboard: IOT, Spain, Ikura → IOT, Spain, Ikura, [POVB]
I'm not sure who the comment 14 was aimed at, so let's add qawanted, just in case.
Keywords: qawanted
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
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)
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)
Assignee: lv.ang → nobody
Beatriz, is this reproducible with builds newer than 2013-04-11?  If not, please close as WORKSFORME.
Flags: needinfo?(brg)
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!
can anyone supply this information form the phone has the problem?
you can get the information by this :cat /proc/touchscreen/ts_information
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.
We think sensibility has been improved, could you please check this again?

resolved/fixed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
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 → ---
Target Milestone: --- → 1.0.1 Cert2 (28may)
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
David, who can verify this is fixed?  It would be nice to have an assignee here.
Flags: needinfo?(brg) → needinfo?(dpv)
is this bug related to bug 865304 by any chance? We're seeing really bad touch responsiveness on the 4/23 builds.
(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)
(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
(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.
Depends on: 865009
Depends on: 865304
No longer depends on: 865304
No longer depends on: 865009
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
(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.
(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.
Blocks: 865304
Blocks: 868335
No longer blocks: 868335
No longer blocks: 865304
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
Moved tracking over to bug 868759.
You need to log in before you can comment on or make changes to this bug.