Skip to content

AICP-Revived/platform_manifest

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Download the Source

Please read the AOSP building instructions before proceeding.

Initializing Repository

Repo initialization:

$ repo init -u https://github.com/AICP-Revived/platform_manifest.git -b r11.1

sync repo :

$ repo sync

Some info on how to customize your sync:

-f, --force-broken continue sync even if a project fails to sync

--force-sync overwrite an existing git directory if it needs to point to a different object directory. WARNING: this may cause loss of data

-l, --local-only only update working tree, don't fetch

-n, --network-only fetch only, don't update working tree

-c, --current-branch fetch only current branch from server

-j JOBS, --jobs=JOBS projects to fetch simultaneously (default 4)

--no-clone-bundle disable use of /clone.bundle on HTTP/HTTPS

--no-tags don't fetch tags

Smallest/fastest sync:

$ repo sync --no-tags --no-clone-bundle

Note: we already define -c in our default.xml, so no need to add it

Building

After the sync is finished, please read the instructions from the Android site on how to build.

. build/envsetup.sh
brunch

You can also build (and see how long it took) for specific devices like this:

. build/envsetup.sh
time brunch angler

Remember to make clobber every now and then!

Optional After Successful Build

After you get a working build, and if you would like to share your build on XDA (Regular Unofficial Builds), then please use the following template to create an XDA thread. Note that the template is a guideline of sort. You may make your own changes to it (especially please change the download link), but try to stick as close as possible to the template. This is to avoid cluttering and make stuff organized.

Link : https://raw.githubusercontent.com/AICP/vendor_aicp/r11.1/docs/xda_template/xda_thread-template.txt

Contributing

Unlike the original AICP I only rely on pull requests, so if you have anything to improve just fork the repo and test your changes before contributing.

Maintaining Authorship

Always make sure if you submit a patch/fix that you maintain authorship. This is very important to not only us but to the entire open source community. It's what keeps it going and encourages more developers to contribute their work.

If you manually cherry pick a patch/fix add the original author prior to pushing to your fork. This task is very easy and is usually done after you commit a patch/fix locally.

i.e - Once you type in "git commit -a" the commit message and you have saved it, type in the following:

git commit --amend --author "Author <[email protected]>"

So it should look like this once you get all author's information:

git commit --amend --author "John Doe <[email protected]>"

Picking changes from our gerrit

(From root android directory) . build/envsetup.sh

to pick every change from a topic:

repopick -t topic

to pick a specific change

repopick commit-number

example, to pick this commit: https://gerrit.aicp-rom.com/#/c/36939/

repopick 36939

Additonal build info

https://github.com/AICP/vendor_aicp/blob/r11.1/docs/aicpInfo.md

Packages

No packages published