Mozilla firefox android github

Mozilla firefox android github

Firefox Focus for Android

Browse like no one’s watching. The new Firefox Focus automatically blocks a wide range of online trackers — from the moment you launch it to the second you leave it. Easily erase your history, passwords and cookies, so you won’t get followed by things like unwanted ads.

Firefox Focus provides automatic ad blocking and tracking protection on an easy-to-use private browser.

We encourage you to participate in this open source project. We love Pull Requests, Bug Reports, ideas, (security) code reviews or any other kind of positive contribution.

Before you attempt to make a contribution please read the Community Participation Guidelines.

Guide to Contributing (New contributors start here!)

Opt-in to our Mailing List firefox-focus-public@ to keep up to date.

Beginners! — Watch out for Issues with the «Good First Issue» label. These are easy bugs that have been left for first timers to have a go, get involved and make a positive contribution to the project!

1. Clone or Download the repository:

1. Import the project into Android Studio or build on the command line:

1. Make sure to select the correct build variant in Android Studio: focusArmDebug for ARM focusX86Debug for X86 focusAarch64Debug for ARM64

You can speed up or enhance local development by setting a few helper flags available in local.properties which will be made easily available as gradle properties.

Automatically sign release builds

To sign your release builds with your debug key automatically, add the following to

With this line, release build variants will automatically be signed with your debug key (like debug builds), allowing them to be built and installed directly through Android Studio or the command line.

This is helpful when you’re building release variants frequently, for example to test feature flags and or do performance analyses.

Building debuggable release variants

Nightly, Beta and Release variants are getting published to Google Play and therefore are not debuggable. To locally create debuggable builds of those variants, add the following to

Auto-publication workflow for android-components and application-services

If you’re making changes to these projects and want to test them in Focus, auto-publication workflow is the fastest, most reliable way to do that.

In local.properties , specify a relative path to your local android-components and/or application-services checkouts. E.g.:

Once these flags are set, your Focus builds will include any local modifications present in these projects.

To reduce review turn-around time, we’d like all pushes to run tests locally. We’d recommend you use our provided pre-push hook in quality/pre-push-recommended.sh . Using this hook will guarantee your hook gets updated as the repository changes. This hook tries to run as much as possible without taking too much time.

To add it, run this command from the project root:

To push without running the pre-push hook (e.g. doc updates):

Test Channel on Google PlayStore

To get Focus Nightly on your device, follow these steps:

Make sure you use the same Google Account for both steps.

Источник

Mozilla firefox android github

AndroidStudioBenchmark (Firefox Focus for Android)

AndroidStudioBenchmark contains a large codebase to measure the compilation time in Android Studio .

You are probably familiar with the following question:

«Should I buy an i5, i7, or even i9 processor for Android development? How much RAM would be enough? How SSD/M.2/NVMe influence build time?».

AndroidStudioBenchmark is initially created for my personal youtube channel https://www.youtube.com/c/serhiyradkivskyi/about to compare the performance of top laptops to choose the best system for Android development , because I hate to wait lot of time waiting project to be built. And if we are buying laptop for 1000+ USD we want to be sure that it will perform 100% faster than our current machine. But online shops in there most — don’t give ability to make real world testing on your project to compare results. And most of tech reviewers describe laptops from designers/youtubers point of view, not that much information from real software developers.

I believe the results will help developers to make the right cost/performance trade-off decision when choosing their next Mac/PC. If you are interested — just continue reading and if you’ll find this test useful — it would be very cool if you can share your result and subscribe for my channel — it would be cool to have like minded audiance to share some more test on and get feedback on any professional stuff.

Results of Android Studio Performance testing:

Videos with test results are in this youtube playlist:

Browse like no one’s watching. The new Firefox Focus automatically blocks a wide range of online trackers — from the moment you launch it to the second you leave it. Easily erase your history, passwords and cookies, so you won’t get followed by things like unwanted ads.

1. Install Android Studio:

I was running test on Android Studio 4.1.1 .

I was using default settings while installation almost for all my tests.

Intel HAXM also must be installed if you run on Intel chip (it is installed by default with Android Studio).

I have set 4Gb RAM for my android virtual machine.

And please remember your Android SDK location.

2. Download API Level 28 SDK for this do next:

Go to: Tools -> SDK Manager

Choose Tab: SDK Platforms

Select: Android 9.0 (Pie) API Level 28 and download it.

Close Android Studio after this.

3. Install JDK 8:

I have installed: Java SE Development Kit 8u271

4. Set «JAVA_HOME» path in your Environment variables (System variables):

For me it was: JAVA_HOME: C:\Program Files\Java\jdk1.8.0_271

5. Download AndroidStudioBenchmark repository:

This is a fork of opensource Firefox browser for Android (https://github.com/mozilla-mobile/focus-android).

This is quite a big project (after all gradle modules downloaded it weights 6+Gb).

You can download it as zip file to you fast SSD location.

6. Restart you system.

Then make sure that no other programs/antivirus/browsers/big massive custom processes running.

Make sure that system is quite idle.

7. Open Android Studio.

Go to File -> Open : select Firefox Focus for Android project from your location and open it.

Wait while all gradle files will be synced , it can take up to 5-10 minutes.

8. Run next command to test speed of your machine doing next work:

Go to: View -> Tools Windows -> Terminal

Type command and press enter:

Wait for assembling to complete. Run it 3 times in a row.

First time it will be your fresh build and it will take a little longer. Two next builds will be normal one.

After each build completes make a screenshot and save time result.

While system assembling watch for you Task Manager how CPU is processing, how much RAM is used, it would be cool if you can watch CPU temperature with some tool like AIDA : https://www.aida64.com/downloads

9. Share results

If you want to share result of your test with the community, please send it to my email: serhiyradkivskiy@gmail.com and I will add it here:

Letter theme: AndroidStudioPerformanceTest

Notebook model : HP 250 G5 15.6″

Android Studio version : 4.1.1

CPU model : Intel Core i5-7200U 2.5GHz

Hard disk : SSD M.2 256Gb KINGSTON SUV400S37240G (or HDD disk model)

Test results : 8:28min, 5:43, 5:37. And screenshots for them.

Additional comments : you can write here whenever you want: The CPU was running all time 100%, laptop was extremely hot near the screen, ram was used for 80% etc, fans where running very hard etc..

Contributor : If you want to leave here a link to your youtube channel/linkedin/other contact info/alias etc — you are welcome, if not — it will be empty.

10. YouTubers and bloggers

You are free to use these results in your videos and articles as well as to run AndroidStudioBenchmark to compare Macs/PCs.

If you decide to record video with this test — it would be very cool if you could upload it to youtube!

Please make sure to add the link to this repository: https://github.com/yozhik/AndroidStudioBenchmark

Please name it: Android Studio Perfomance Test on .

So everyone could find it and watch and your audiance could repeat steps after you and compare their machine results.

The results show relative performance of Android Studio, compared to other machines running under similar conditions.

About

Firefox Focus: The privacy browser — Browse like no one’s watching.

Источник

Mozilla firefox android github

Firefox for Android

Fenix (internal codename) is the all-new Firefox for Android browser, based on GeckoView and Mozilla Android Components.

Please read the Community Participation Guidelines and the Bugzilla Etiquette guidelines before filing an issue. This is our professional working environment as much as it is our bug tracker, and we want to keep our workspace clean and healthy.

Guide to Contributing (New contributors start here!)

Matrix: #fenix:mozilla.org channel (We’re available Monday-Friday, GMT and PST working hours). Related channels:

Check out the project wiki for more information.

Localization happens on Pontoon. Please get in touch with delphine (at) mozilla (dot) com directly for more information.

Beginners! — Watch out for Issues with the «Good First Issue» label. These are easy bugs that have been left for first timers to have a go, get involved and make a positive contribution to the project!

I want to open a Pull Request!

We encourage you to participate in this open source project. We love Pull Requests, Bug Reports, ideas, (security) code reviews or any other kind of positive contribution.

Since we are a small team, however, we do not have the bandwidth to review unsolicited PRs. Please follow our Pull Request guidelines, or we may close the PR.

To make it easier to review, we have these PR requirements:

• Every PR must have exactly one issue associated with it.
• Write a clear explanation of what the code is doing when opening the pull request, and optionally add comments to the PR.
• Make sure there are tests — or ask for help on how the code should be tested in the Issue!
• Keep PRs small and to the point. For extra code-health changes, either file a separate issue, or make it a separate PR that can be easily reviewed.
• Use micro-commits. This makes it easier and faster to review.
• Add a screenshot for UX changes (this is part of the PR checklist)

As a small team, we have to prioritize our work, and reviewing PRs takes time. We receive lots of PRs every day, so if you can keep your PRs small, it helps our small team review and merge code faster, minimizing stale code.

Keep in mind that the team is very overloaded, so PRs sometimes wait for a very long time. However this is not for lack of interest, but because we find ourselves in a constant need to prioritize certain issues/PRs over others. If you think your issue/PR is very important, try to popularize it by getting other users to comment and share their point of view.

I want to file an issue!

Great! We encourage you to participate in this open source project. We love Pull Requests, Bug Reports, ideas, (security) code reviews or any other kind of positive contribution.

To make it easier to triage, we have these issue requirements:

• Please do your best to search for duplicate issues before filing a new issue so we can keep our issue board clean.
• Every issue should have exactly one bug/feature request described in it. Please do not file meta feedback list tickets as it is difficult to parse them and address their individual points.
• Feature Requests are better when they’re open-ended instead of demanding a specific solution -ie “I want an easier way to do X” instead of “add Y”
• Issues are not the place to go off topic or debate. If you have questions, please join the #fenix:mozilla.org channel.
• Please always remember our Community Participation Guidelines
• Please do not tag specific team members to try to get your issue looked at faster. We have a triage process that will tag and label issues correctly in due time. If you think an issue is very severe, you can ask about it in Matrix.

Please keep in mind that even though a feature you have in mind may seem like a small ask, as a small team, we have to prioritize our planned work and every new feature adds complexity and maintenance and may take up design, research, marketing, product, and engineering time. We appreciate everyone’s passion but we will not be able to incorporate every feature request or even fix every bug. That being said, just because we haven’t replied, doesn’t mean we don’t care about the issue, please be patient with our response times as we’re very busy.

• Android SDK
• To run command line tools, you’ll need to configure Java: see our how-to guide.

1. Clone or Download the repository:

1. Import the project into Android Studio or build on the command line:

If this errors out, make sure that you have an ANDROID_SDK_ROOT environment variable pointing to the right path.

Make sure to select the correct build variant in Android Studio. See the next section.

Make sure to select «Default APK» under Installation Options inside Run/Debug configuration: see this bug.

For general development, we recommend the debug build variant. Here’s an explanation of each variant:

• debug: the default for developers, similar to most other Android apps. It is debuggable, uses a Nightly GeckoView with debug symbols, adds tools like LeakCanary for troublingshooting, and does not strip unused code.
• nightly: what we ship to the Firefox Nightly channel, using GeckoView Nightly.
• beta: what we ship to the Firefox Beta channel, using GeckoView Beta. It is more stable than nightly.
• release: what we ship as Firefox for Android, using GeckoView Release. It is the most stable.

nightly, beta, and release are unsigned and debuggable=false by default. If you want these variants to be:

Performance Build Variants

For accurate performance measurements, read this section!

To analyze performance during local development build a production variant locally (this could either be the Nightly, beta or release). Otherwise, you could also grab a pre-existing APK if you don’t need to test some local changes. Then, use the Firefox profiler to profile what you need!

For more information on how to use the profiler or how to use the build, refer to this how to measure performance with the build

If you want to run performance tests/benchmarks in automation or locally use a production build since it is much closer in behavior compared to what users see in the wild.

Before you can install any release builds, You will need to sign production build variants: see Automatically signing release builds for details.

Known disabled-by-default features

Some features are disabled by default when Fenix is built locally. This can be problematic at times for checking performance since you might want to know how your code behaves with those features. The known features that are disabled by default are:

• Sentry
• Adjust
• Mozilla Location Services (also known as MLS)
• Firebase Push Services
• Telemetry (only disabled by default in debug builds)
• Nimbus

To reduce review turn-around time, we’d like all pushes to run tests locally. We’d recommend you use our provided pre-push hook in config/pre-push-recommended.sh . Using this hook will guarantee your hook gets updated as the repository changes. This hook tries to run as much as possible without taking too much time.

Before you can run the hook, you’ll need to configure Java properly because it relies on command line tools: see our how-to guide.

To add it on Mac/Linux, run this command from the project root:

or for Windows run this command using the Command Prompt with administrative privileges:

or using PowerShell:

To push without running the pre-push hook (e.g. doc updates):

Note: If while pushing you encounter this error «Could not initialize class org.codehaus.groovy.runtime.InvokerHelper» and are currently on Java14 then downgrading your Java version to Java13 or lower can resolve the issue

Steps to downgrade Java Version on Mac with Brew:

1. Install Homebrew (https://brew.sh/)
2. run brew update
3. To uninstall your current java version, run sudo rm -fr /Library/Java/JavaVirtualMachines/
4. run brew tap homebrew/cask-versions
5. run brew search java
6. If you see java11, then run brew install java11
7. Verify java-version by running java -version

You can speed up local development by setting a few helper flags available in local.properties . Some flags will make it easy to work across multiple layers of the dependency stack — specifically, with android-components, geckoview or application-services.

Automatically sign release builds

To sign your release builds with your debug key automatically, add the following to

With this line, release build variants will automatically be signed with your debug key (like debug builds), allowing them to be built and installed directly through Android Studio or the command line.

This is helpful when you’re building release variants frequently, for example to test feature flags and or do performance analyses.

Building debuggable release variants

Nightly, Beta and Release variants are getting published to Google Play and therefore are not debuggable. To locally create debuggable builds of those variants, add the following to

Setting raptor manifest flag

To set the raptor manifest flag in Nightly, Beta and Release variants, add the following to

Auto-publication workflow for android-components and application-services

If you’re making changes to these projects and want to test them in Fenix, auto-publication workflow is the fastest, most reliable way to do that.

In local.properties , specify a relative path to your local android-components and/or application-services checkouts. E.g.:

Once these flags are set, your Fenix builds will include any local modifications present in these projects.

In order to build successfully, you need to check out a commit in the dependency repository that has no breaking changes. The two best ways to do this are:

Using Nimbus servers during local development

If you’re working with the Nimbus experiments platform, by default for local development Fenix configures Nimbus to not use a server.

If you wish to use a Nimbus server during local development, you can add a https:// or file:// endpoint to the local.properties file.

Testing experimental branches should be possible without a server.

Specify a relative path to your local mozilla-central checkout via dependencySubstitutions.geckoviewTopsrcdir , and optional a path to m-c object directory via dependencySubstitutions.geckoviewTopobjdir .

If these are configured, local builds of GeckoView will be used instead of what’s configured in Dependencies.kt. For more details, see https://firefox-source-docs.mozilla.org/mobile/android/geckoview/contributor/geckoview-quick-start.html#include-geckoview-as-a-dependency

See notes on building successfully in the android-components auto-publication section.

Источник