Repository to upload config file for NikGapps ecosystem to create a custom build for you

• Working knowledge of NikGapps configuration file
• That's it. No server, No core Gapps knowledge, No other cost!

• Yes, if you want to skip reading and jump to video tutorial. Here is the video tutorial that you should follow to create a custom build.

1. Fork this repository: Click on the fork icon at the top right corner of the repository page.

   

2. Wait for the forking to finish.

   

3. Download the latest version of the nikgapps.config.

4. Copy the downloaded file to the specific target Android version folder (e.g., place the config file in the '10' folder if you want to create a build targeting Android 10).

   Note: Do not reuse, modify, or delete any existing '.config' files from any of the folders to avoid issues during building and troubleshooting.

5. Rename the config file: Set the name you want for your custom NikGapps build. For example, renaming to xyz.config will create NikGapps-xyz-arm64-androidversion-date-signed.zip.

6. Configure your config file: Set AppSet=1 or >>Package=1 to include it in your package, or set it to 0 to exclude it.

   • You can also set packages to 2 to include them in your package and prevent the AOSP package from being removed when your package is installed.
   • Example: YouTube=1, PixelLauncher=1, >>PixelTips=1 will include these packages in your custom Gapps build, while Drive=0 will skip the package. Any other values will be ignored.

7. Commit the config file to your forked repository. Ensure the name is unique and ends with '.config'.

8. Send a pull request to merge your config file into this repository.

9. Wait for the pull request to be merged: This should take less than 30 minutes.

10. Once merged, the NikGapps ecosystem will build your custom Gapps.

11. After the build, your config file will be moved to the archive with '_date' appended to it.

12. Find your build: Look for the date folder in Config-Releases, where you will find your build.

• Follow above steps again as once the custom build is created, config file will be moved to archive

For More information on this repository, refer nikgapps blog