What is Reddit's opinion of
Firefox Nightly for Developers (Unreleased)?
From 3.5 billion Reddit comments
Popularity Score: 27
This app was mentioned in 46 comments, with an average of 2.35 upvotes
Best Comments
After switching to Firefox on desktop a few weeks back I've finally done the same on mobile.
Firefox Nightly has greatly improved scrolling over how it used to be. It's a lot more similar to chrome scrolling (not quite there yet, but much more usable) and has support for desktop extensions. I have it set up with https everywhere, ublock origin, privacy badger and a custom theme. It has replaced Chrome beta as my primary browser. https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
Recent Reddit post about it https://redd.it/8fc2f0
Updates are lagged on Google Play because of COVID-19, but installing https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora will get you the update with the additional extension support once Google approves it.
You can already use uBlock Origin on both Nightly and Preview.
Try out Firefox Nightly -- it's faster than stable, and has a nicer UI than stable. It's a much lower risk endeavor than on desktop, and you can keep stable installed.
The stable version of Firefox does not support system autofill, but Firefox Nightly does. I use Bitwarden with it, but it isn't perfect. I know you can install Bitwarden as an extension on mobile Firefox If you don't want to install the nightly version, but it's a pain to use.
No that's not the one.
https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
This is the link that the notice on the previous nightly redirects to. And it's the same as the one listed on the official site.
Download Firefox Nightly and see if this is fixed. It was fixed recently.
There are some links which don't redirect to the Play Store app. Google redirects links you click on their pages first and then sends you to the respective apps but as I can see, most of the apps are opening in their respective apps including from the Google app and the website.
Check it and please report back. Okay?
I don't think they will rename the package name on Android (they can't afford to create this mess a second time and I don't think ordinary people look at package names). They will probably only change the branding in the Play Store and within the app.
Similar to how Mozilla hasn't changed the package name of org.mozilla.fennec_aurora to org.mozilla.fennec_nightly and then to org.mozilla.fenix_nightly, even though it transitioned from Aurora to Nightly and then to Fenix. ;)
Btw. the package name of RiotX will get deprecated in favour of the older package name. People won't have to reinstall to transition to the stable RiotX codebase once it is ready.
Hi, it's a known issue, keep an eye on this: https://github.com/mozilla-mobile/fenix/issues/8754
Edit: seems like it has been fixed. Can you test this on Nightly version, and report any issues in the GitHub issue thread?
There are some bugs related to the download manager so they might be affecting the speed check on the latest Nightly. And in the coming weeks.
And if you still have issues then you can file them on GitHub: https://github.com/mozilla-mobile/fenix/issues.
As a user would see it, no. The only difference is that<org.mozilla.fennec_aurora> contains code to migrate user profiles.
The issue I mentioned is not resolved for me. Some apps open in their respective apps but not all. If you need up-to-date fixes to see if the issue you mentioned is resolved is to test on a Nightly. Currently developers seem to be still working on it.
This the issue thread: https://github.com/mozilla-mobile/fenix/issues/10281
The fix is in th latest Nightly you can download it from the Play Store. And give feedback on it.
> I didn't like the way tabs were, i preferred something like firefox stable or chrome (but don't want to use chrome). Can this be changed? (I don't think I can get used to current setup)
You may prefer the way Firefox Nightly works: https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
>Didn't have print (I can live without this though)
Watch https://github.com/mozilla-mobile/fenix/issues/10217
>Customise home page (i can live without this though)
You mean like a web page?
>Regarding add-ons will it get the support as standard firefox..
We're not sure how many add-ons will make it over, because the Fenix UI is standard Android, not custom like Fennec (Firefox for Android) and some APIs may never be supported. Time will tell though.
>Also regarding using beta version is this going to be merged into main firefox?
Not merged, but the main Firefox will eventually become Fenix (the new codebase).
Try Firefox Nightly - it is the preview of the new Firefox that will be coming out soon. Even though it is a beta version right now, it is phenomenally smooth and bug free.
Give it a try as a secondary browser, add uBlock Origin and I bet you'll likely make it your main browser within a few days of use.
https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora&hl=en
Ok, you said
> I wanted to use Firefox but couldn't because it lags like hell (looking forward to Quantum)
But 57 is the first Quantum release. So you're experiencing it.
Also, you can test Nightly 58 right now. I believe it will use a separate profile.
This was fixed on Nightly a few nights ago. Should work in recent nightlies. Will take some time before it reaches Stable.
Update: This is also fix in the beta channel. Should be fixed in the next major version number stable release.
There are no simple ways to trigger profiles in Firefox for Android. I believe it is possible via adb but that requires the device to be connected to a computer. Use the Aurora (soon to be nightly) release if you need a 3rd profile.
It is not possible to share profiles on Android as the profile is stored in the application data area and each app is given a unique user account which prevents access to other apps data.
Here is the post from the blog, who can't read it because of invalid SSL. Imported from https://github.com/mozilla/release-blog/ repo.
Part 1/2
Dawn project or the end of Aurora
date: 2017-04-17 08:30:23
categories: firefox release
As described in the post on the Hacks blog, we are changing the release mechanism of Firefox.
What
In order to address the complexity and cycle length issues, the release management team, in coordination with Firefox product management and engineering, is going to remove the Aurora stabilization phase from the cycle.
When
On April 18th, Firefox 55 will remain on Nightly. This means Firefox 55 will remain on Nightly for two full cycles. On June 13th, Firefox 55 will migrate directly from Nightly to Beta.
Why
As originally intended, Aurora was to be the first stabilization channel having a user base 10x the size of Nightly so as to provide additional user feedback. This original intent never materialized.
The release cycle time has required that we subvert the model regularly over the years by uplifting new features to meet market requirements.
How
The stabilization cycle from Nightly to Release will be shortened by 6-8 weeks.
A staged rollout mechanism, similar to what we do today with Release, will be used for the first weeks of Beta.
Our engineering and release workflow will continue to have additional checks and balances rolled out to ensure we ship a high quality release.
We will focus on finding and fixing regressions during the Nightly cycle and alleviate time pressure to ship to reduce the 400-600 patches currently uplifted to Aurora.
A new feature will merge from Nightly to Beta only when it's deemed ready, based on pre-established criteria determined by engineering, product, and product integrity.
Tooling such as static analysis, linters, and code coverage will be integrated into the development process
FAQ
What will happen to the Aurora population on Desktop?
The Aurora population will be migrated to the Beta update channel in April 2017. We plan to keep them on a separate “pre-beta” update channel as compared to the rest of the Beta population. We will use this pre-beta audience to test and improve the stability and quality of initial Beta builds until we are ready to push to 100% of beta population. Because we presented Aurora as a stable product in the past, the beta channel is the closest in terms of stability and quality.
From the next merge (April 18th), users running 54 Aurora will remain on the Aurora channel but updates will be turned off. In case of critical security issues, we might push new updates to these aurora channel users. Aurora channel users will be migrated to Beta channel in April ‘17. For this to happen, we need to make sure that the Developer Edition features are working the same way on the Beta update channel (theme, profile, etc).
What will happen to the Aurora population on Android?
Because Google play doesn't allow the migration of a population from an application to another, the fennec population on aurora will be migrated to the nightly application. For now, we are planning to reuse the current Google play aurora application and replace it by Nightly to preserve the current population.
Why are we taking different approaches with the Desktop and Android Aurora populations?
Aurora channel on Desktop has been around for a long time and has a substantial end-user base that Beta channel will benefit from.
Fennec Aurora on Google Play is a recent addition and we believe merging this audience with Nightly makes more sense. It also simplifies implementation.
I am running Developer Edition, what will happen to me?
Developer Edition, currently based off Aurora, will be updated to get builds from the Beta branch. There is nothing Developer Edition users need to do, they will update automatically to the Beta build keeping the Developer Edition themes, tools, and preferences as well as the existing profile.
Will I still be able to test add-ons with Developer Edition?
You can continue to test unsigned add-ons on Nightly builds or load WebExtensions temporarily in Beta and Release builds.
We are also continuing to provide unbranded builds of the beta and release branches which are able to run unsigned add-ons - including bootstrapped - for development and experimentation. These versions will not be verified by QE, but will receive updates , which is an improvement to the unbranded builds we currently provide for add-on development..
How will you mitigate the quality risk from cutting 6-8 weeks of stabilization from the cycle?
Instead of pushing to 100 % of the beta population at once, we will use a staged rollout mechanism to push to a subset of the beta population. For the first phase, we will be pushing to the former aurora population. As a second phase, we will be targeting specific populations (Operating system, graphic card, etc)
In parallel, QE will also do preliminary nightly sign off to detect early new potential issues. Release management will be much more aggressive in term of feature deactivation.
Last but not least, the aurora cycle was used to finalize some features. Instead, feature stabilization will be performed during the nightly cycle.
What are we doing to improve Nightly quality?
To improve the overall quality of nightly, a few initiatives will help.
Nightly merge criteria
New end-user facing features landing in Nightly builds should meet Beta-readiness criteria before they can be pushed to Beta channel.
Static analyzers
In order to detect issues at review phase, static analyzers will be integrated as part of the workflow. They will be able to identify potential defects but also limit the technological debt.
Code coverage
Code coverage results are going to be used to analyze the quality of the testsuite and the risk introduced by the change.
Risk assessment
By correlating various data sources (VCS, Bugzilla, etc), we believe we can identify the potential risks carried by changes before they even land. The idea is to identify the functions where a modification has more chance to induce a regression.
How often will Beta builds be updated?
We will continue to push two Beta builds for Desktop and one Fennec build each week of the Beta cycle.
Will Developer Edition continue to have a separate profile?
Yes. The Developer Edition separate profile feature is a requirement for transition. If for whatever reason this feature cannot be completed by the end of the year we will need to return to creating rebuilds of Developer Edition as previously done to ensure those users are not cast away.
What will happen to the Aurora branch after Firefox 54 moves to Beta?
Updates on aurora channel will be disabled on April 18th. The desktop and aurora populations will be migrated as described above.
What criteria will be used to assess feature readiness to move to Beta?
We will be monitoring crash rates, QE's sign offs, telemetry data and new regressions to determine overall Nightly quality and feature readiness to merge to Beta.
How and who will determine whether a feature is ready to move to Beta?
End-user facing features will be reviewed for beta-readiness before they are pushed to Beta channel. Following is a list of criteria that will be used to evaluate feature readiness to merge to Beta:
- No significant stability Issues
- Missing Test Plans
- Insufficient Testing
- Feature is not Code Complete
- Too Many Open Bugs
More detailed criteria defined in this document.
Are there any changes to Release or ESR channel?
No changes are planned for Release or ESR channel users.
Does this change how frequently we push mainline builds to Release channel?
No, but changes added in Nightly can make it into a Release build about 6-8 weeks sooner than they do now.
What will happen for l10n process when we remove Aurora?
Focus for localization will move from mozilla-aurora to mozilla-central. Localization tools (Pootle and Pontoon) will read en-US strings from a special mozilla-central clone: l10n-drivers will review patches with strings landing in the official mozilla-central repository, provide feedback to devs if necessary, and land updates every 2-3 days in this special repository. Localized content will be pushed to l10n-central repositories.
There are no changes for developers working on Firefox: Nightly and mozilla-central remain open to string changes, including the extra six weeks that Firefox 55 will spend in Nightly, while Beta is still considered string frozen, and requests to uplift changes affecting strings are evaluated case by case.
Users interested in helping with localization should download Nightly in their language.
What will happen for l10n process by the end of year?
For Firefox and Firefox for Android we will shift to a model with a single repository for all channels for each locale. This change will be reflected in localization tools, allowing localizers to make a change to a string and see that update applied across all channels at once.
H990DS: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
Others: https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
custom kernel can be found here: https://forum.xda-developers.com/v20/development
RCTD remove (require root): https://www.xda-developers.com/rctd-remover-removes-lg-root-checking-tool/
firefox nightly for android (also can be download from mozilla ftp): https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora&hl=en
Try Firefox Nightly (Aurora). I find it faster than the official Firefox release and Chrome.
I'm told this feature is present on Aurora. Please test with it and let me know! :)
How does the reference browser differ from the nightly release?
Why wait? Get Nightly today... https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
You can just download Nightly now: https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
I've seen problems with Sync on friends' Android devices, but they went away when using Nightly. Worth a shot.
So is Firefox Nightly for Developers dead, or still a thing?
Because it just got updated 2 hours ago ...
So if I have this version: https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora&hl=en_US Am I safe or should I move to a different app?
Okay, have you checked if it works in Nightly version?
Tab Sync isn't in Firefox Beta yet. It is available in Firefox Nightly, though: https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
i'm using Firefox Nightly, ps. the screenshots are outdated
Firefox Nightly is still around even in the non Preview version. https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
You can in Nightly: https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
What device, although the OS is helpful too. Do you see the issue if you install Firefox Nightly? https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
Check out Firefox Nightly, Brave got as bloated as Chrome was for me and I didn't like how Focus was basicly just an always an incognito browser.
> -Firefox Quantum’s new engine uses 30% less memory than Chrome
> -Powered by a new, cutting-edge engine, Firefox has doubled its speed from last year
> - Uses the new WebExtension technology
https://www.youtube.com/watch?v=VJiwh5gRm6c
https://www.mozilla.org/en-US/firefox/quantum/
http://www.firefox.ro/what-are-webextensions-and-why-do-we-need-them.html
https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora&hl=en****
https://www.youtube.com/watch?v=VJiwh5gRm6c
Firefox Nightly has been my main Pixel and PC Browser for the last month or so. It's so good to see Firefox back to its former glory AND have uBlock Origin on mobile.
> -Firefox Quantum’s new engine uses 30% less memory than Chrome
> -Powered by a new, cutting-edge engine, Firefox has doubled its speed from last year
> - Uses the new WebExtension technology
https://www.youtube.com/watch?v=VJiwh5gRm6c
https://www.mozilla.org/en-US/firefox/quantum/
http://www.firefox.ro/what-are-webextensions-and-why-do-we-need-them.html
Dev! :D
check it out on Android too! the scrolling is much improved compared to Stable. https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora
Try Firefox nightly
https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora&hl=en_CA&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dfirefox+nightly+android+play+store Firefox Nightly for Developers – Apps on Google Play
I experienced the same thing. Updates have stopped for the old apk.
Unfortunately, to my knowledge, the only way to regain update access is to install the app again fresh from Mozilla - what happened was, and I don't understand why this would be done this way at all - coinciding with the Aurora switch, the decision was made to rename the Nightly app to org.mozilla.fennec_aurora (instead of the other way around).
This means, per how Android operates (matching apk name overrides previous version), the renamed apk can no longer be installed on top of the old app name that you have installed now.
In the meantime, it seems Nightly has just been added to the Play Store as an unreleased app (again, with the app name org.mozilla.fennec_aurora!), so you might as well install it from there and migrate your settings to it (in essence, use sync for what you can and reinstall the rest manually).
After I completely migrated my settings a few days ago (it took hours! Android Firefox has no features to support the changing of release channel or downgrading) Mozilla added a third, new way of grabbing the Nightly apk now. If the ARM or Intel specific apk matches your old one, you might be in luck with the upgrade.
If not, then you should probably go with the Play store install. I feel this process went completely backwards for us Nightly users on Android.