Firefox mobile shouldn't only be available on the android market (please keep the link to the latest Android build up-to-date)



8 years ago
5 years ago


(Reporter: etenil, Unassigned)


Firefox Tracking Flags

(Not tracked)




8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100716 Ubuntu/9.10 (karmic) Firefox/3.6.7
Build Identifier: 4.0b3

Some of us refuse to install the google apps on our android devices for these are non-free software. Firefox being free software, it doesn't make sense to have to pass through a non-free software in order to install it.

There are some other markets out there, for example fdroid, and the .apk could also be directly downloadable from firefox mobile's website.

Reproducible: Always

Steps to Reproduce:
1. Go to firefox mobile website
2. Notice the links don't work as they require the market to work.
Actual Results:  
Can't install firefox without market

Expected Results:  
Having an apk file downloaded to the device.


8 years ago
OS: Other → Android
Hardware: Other → ARM
You can download the .apk directly from Mozilla's website :
Last Resolved: 8 years ago
Resolution: --- → INVALID

Comment 2

8 years ago
Will non-market builds receive updates?  I thought there was talk of turning off the updater for official builds.

Comment 3

8 years ago
Hi, thanks for the link,

I understand your reluctance to consider this a valid bug, and I can see you do have apks available. However, a link to other download options on the mobile website[1] would be a lot more convenient than searching through a search engine, especially from a mobile device.


Comment 4

7 years ago
Firefox just got added to the F-Droid repository:
We did not upload that file. However the md5sums are correct

Comment 6

7 years ago
yes, I signaled that Firefox was missing in their repository and they added it. Apparently they host apks on their own mirror, not sure how they usually get updates when new versions are released.

Comment 7

6 years ago
(In reply to Fabrice Desré [:fabrice] from comment #1)
> You can download the .apk directly from Mozilla's website :

I accept Mozilla Foundation decision not to provide packages for f-droid (although I don't like it), but please at least keep this link up-to-date. For example, just now

points to although FF16 is already out.
Ever confirmed: true
Resolution: INVALID → ---


6 years ago
Assignee: nobody → server-ops
Component: General → FTP: Staging
Product: Fennec →
QA Contact: mrz
Summary: Firefox mobile shouldn't only be available on the android market → Firefox mobile shouldn't only be available on the android market (please keep the link to the latest Android build up-to-date)
Version: Trunk → other

Comment 8

6 years ago
It is possible to create an F-droid compatible repo,  which functions like an Ubuntu PPA. Users can add this to the F-droid client and receive notifications of new versions. A current limitation is that each build must have a distinct version name and code, though I understand this will be rectified soon. If such a repo were to be made available it could be included by the default in F-droid, so that would no longer need to offer the apk on, meaning that users would always be notified of upgrades so long as the app is installed.

 If does choose to offer source builds at some point, then users would still always have the option to revert to a Mozilla-signed apk. Indeed, it should be possible to offer the repo as top priority so that users will be offered that before an build.

Comment 9

6 years ago
(In reply to david8black from comment #8)
> It is possible to create an F-droid compatible repo,  which functions like

That would be absolutely awesome ... even better if we could get whole range of Mozilla streams (nightly, aurora, beta, released).

And just to emphasize ... the link to the latest/android is still wrong.
I've updated the latest link to to 16.0.1. Bug 795774 covers keeping it up to date.

Comment 11

6 years ago
If the armv6 build was given a version name (or package ID) distinct from the arm-v7a build then it too would be allowed in the repo.


6 years ago
Assignee: server-ops → server-ops-webops
Component: FTP: Staging → Server Operations: Web Operations
QA Contact: mrz → nmaul

Comment 12

6 years ago
I'm not sure where this bug belongs now (maybe resolved, given comment 10?), but it's not something WebOps can handle.

Moving to Releng just for confirmation before closing.
Assignee: server-ops-webops → server-ops-releng
Component: Server Operations: Web Operations → Server Operations: RelEng
QA Contact: nmaul → arich
actually moving this to releng, not relops.
Assignee: server-ops-releng → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: arich
I would say that eastern timezone mornings would work best for me.
Ignore comment 14, wrong bug.
We maintain and automatically now. I'm pretty sure this bug is fixed now?
Last Resolved: 8 years ago5 years ago
Resolution: --- → FIXED


5 years ago
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.