Closed Bug 772283 Opened 12 years ago Closed 3 years ago

[ARMv6] Fennec for armv6 fails to respond to tapping links


(Firefox for Android Graveyard :: General, defect)

16 Branch
Not set


(Not tracked)



(Reporter: xwei, Unassigned)


(Whiteboard: [ARMv6])


(1 file)

Fennec for armv6 fails to respond when tapping on links most of the time. 

Steps to reproduce:
1. Go to
2. Search for anything
3. In the result page, try tapping on any result link.

Fennec should go to the link as requested.

Tapping on a link have a chance to be ignored by fennec. i.e. nothing happens after tapping on a link, even though we could see the link is getting focused.

Build used: nightly for armv6 (20120709)
Devices used: HTC Wildfire S, Samsung Galaxy Fit, Samsung Galaxy Gio.
Platform: 2.3.x
I am trying to figure out what could be causing this issue.

Do the 3 tested phones all fail with the same frequency? The Galaxy Fit has a fairly small screen, but the Wildfire and Galaxy Gio seem to have 320x480 screens and decent processor speed & memory.

Can you attach some logcats?
Try checking the logs on a debug build.
The logs are obtained from Galaxy Gio, with nightly debug build from 20120716. I've performed this a bunch times and those logs seem to be there every time there's a non-responsive tapping on links from google search.
Whiteboard: [ARMv6]
Should I get a debug build to gather more information?
Thanks for the offer to get more data. I think for right now we have enough info. We are starting to work on important armv6 bugs. Hopefully we can get this sorted out.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly]( an issue can be reported at the [Fenix GitHub project]( If you want to discuss your report please use [Mozilla's chat]( server and join the [#fenix]( channel.
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.