1234791 - [Flame] Very irritating unnecessary touch events

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::System, defect)

Description

[shine [:shine]]

Flame has been sending very irritating unnecessary touch events occasionally. It is unpredictable. When it comes, the device is totally useless. You have to physically fight with the device to get things done.

It's not just me, some of my friends from my regional community have been facing the same issue until they switched over.


Bug 1053659 is related / similar but has been RESOLVED FIXED by sending replacement devices. That was in the center of the screen alone. I've had it in many points. I thought this was due to my use of the device (I use it extensively since it is my primary device), but I confirmed it was a bug when my friends reported that they were facing the same issues for months. I strongly believe that this is not a device issue and could be a Gaia issue because the touch events are random and affects more than one device.

The bug disappears after an OTA or a restart (for a while), but it comes back again. I've flashed different builds to see whether it was a build issue. Everything under 2.0 doesn't have this issue. Some builds of 2.2 is fine as well. Some other builds of 2.2 and up have failed me. The most disturbing part is that I can't predict when the bug happens or when it'll disappear. Sometimes this happens when I need to use my phone in an emergency. It hurts when people ask me to get a better phone and that Firefox OS sucks. :frowning:

I'm on the nightly channel (build ID : 20151023030241). The one that is supposed to pass the smoke tests and be the most stable for the flame.

I could be wrong. Or maybe I'm judging too much. I really wanted to use Firefox OS as my primary device. Even if I get a new device, I'll make sure it is compatible with Firefox OS (has a well-maintained port).

I've reached to a point that I've finally given up and decided to get an Android (though I really don't want to).

PS : let me know if you need logs or more info. I'd be happy to provide them.

Comment 1

[Mihai Barbat]

A video of the issue would help I think. Did you also try with the lastest builds? switch to nightly-latest, as 20151023030241 is very old now!

Comment 2

[Rigin Oommen]

I think you are using the version between 2.0 and 2.2.

Comment 3

[Rigin Oommen]

i faced this issue in 2.1 at that time i made a hard reset to the phone

Comment 4

[shine [:shine]]

Attachment: WP_20151223_003.m4v

Video of the bug irritating general use.

Comment 5

[shine [:shine]]

(In reply to Rigin Oommen from comment #2)
> I think you are using the version between 2.0 and 2.2.

I'm on the latest build in the nightly channel. The version is 2.5 now.

Comment 6

[Rigin Oommen]

(In reply to Shine Nelson [:shine] from comment #4)
> Created attachment 8701423 [details]
> WP_20151223_003.m4v
> 
> Video of the bug irritating general use.

It seems to be funny(ചാത്തൻ) behaviour. can you try to restore the factory settings instead of hard reset

Comment 7

[KUMARESAN_C_S [:CSK]]

This same issue has happen to my flame device and my friend device too. I do all the process told by rigin but it will not solve the issue..

Comment 8

[Marcia Knous [:marcia]]

Shine: Can you please make sure to update to the latest Base image and report back as to whether you are still seeing this bug? In one of the discourse threads I saw, you mentioned you were still using V3.

Comment 9

[shine [:shine]]

(In reply to Marcia Knous [:marcia - use ni] from comment #8)
> Shine: Can you please make sure to update to the latest Base image and
> report back as to whether you are still seeing this bug? In one of the
> discourse threads I saw, you mentioned you were still using V3.

I flashed the latest base image (v4) last night and updated to the nightly-latest build 20151229030208. The issue still persists. I guess it's a hardware issue then.

I'm happy that I was able to use the device as my primary device for a good 6-8 months.

Comment 10

[Rigin Oommen]

(In reply to Shine Nelson [:shine] from comment #9)
> (In reply to Marcia Knous [:marcia - use ni] from comment #8)
> > Shine: Can you please make sure to update to the latest Base image and
> > report back as to whether you are still seeing this bug? In one of the
> > discourse threads I saw, you mentioned you were still using V3.
> 
> I flashed the latest base image (v4) last night and updated to the
> nightly-latest build 20151229030208. The issue still persists. I guess it's
> a hardware issue then.
> 
> I'm happy that I was able to use the device as my primary device for a good
> 6-8 months.

can you flash with some lower version of Firefox OS like 1.3. i dont think its a hardware issue

Comment 11

[shine [:shine]]

(In reply to Rigin Oommen from comment #10)
> can you flash with some lower version of Firefox OS like 1.3. i dont think
> its a hardware issue

So did I. I'm now convinced that it is indeed a hardware issue. I'm going to try the latest stable (v2.0) anyhow. I don't know where I can find lower versions. Please point me to some 1.x builds if possible.

Comment 12

[shine [:shine]]

Oh nevermind the lower versions. I found it in the same MDN page. I just didn't scroll enough. ;-)

Comment 13

[shine [:shine]]

Confirmed with v2.0 and v1.3. Both versions have the same issues. My flame is dead! :'(