schwabe93 / official_builds

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

AospExtended OS

Official builds application

Before opening a pull request to add your build into our official website, you should know a few simple things:

1. Hosting

Our files are hosted on SourceForge

2. Changelog

For each new version, you need to upload the changelog to this repository in the device specific folder.

The changelog file name must match the .zip file name and should end with .txt Eg: .zip is AospExtended-v6.2-osprey-20180906-0543-OFFICIAL.zip, changelog file name should be AospExtended-v6.2-osprey-20180906-0543-OFFICIAL.txt

3. Addons

You can add links to device specific addons(firmwares patches, tweaks, hotfixes etc) in addons.json , it will appear inside OTA app. Make sure to follow the syntax and avoid adding duplicate addons that already exists in default array, those are universal addons that can be used on all the devices.

4. Over-the-air (OTA) updates

Our system is automatic, you should not worry about updating some script, just upload the new build to the SourceForge and send a pull request with the changelog and also edit your device JSON file (builds/your_device_codename.json) in this repository.

Eg: Moto G 2015 is called osprey, so the device JSON file is builds/osprey.json

Note: New builds can take up to 30 minutes to appear on the site and in the OTA application.

5. JSON parameters

Param Description Required
oreo/pie Version name, will be shown on download portal Yes
file_name Latest build name Yes

Example: Click here

Please format your JSON code properly, here.

6. Build type

You need to add 'export EXTENDED_BUILD_TYPE=OFFICIAL' in your build environment so that the OTA app will be included in your build.

7. Device tree

Maintainers should upload their device trees on https://github.com/AospExtended-Devices

Important Links:

About