Go to file
Matt Mower 5f92da62c6 overlay: remove Verizon specific eri.xml
Restore order to the universe by removing that which is evil.

For some strange reason, Verizon devices do not agree on the eri.xml to
use, even on the same spn. Since it is not universal, it does not belong
in vendor/cm (at least while there is no automatic method to check which
eri.xml should be used). Remove these so that we don't end up with
strange double-overlay issues for devices.

Change-Id: If5a28ed03c8cc6b145c151c7ebf95fabdf81f434
2014-03-07 17:31:02 -06:00
bash_completion repo bash completion: _find_repo: improve check 2013-05-05 21:37:17 -07:00
config version: Remove dash from TARGET_VENDOR_RELEASE_BUILD_ID 2014-02-16 17:15:07 +00:00
overlay overlay: remove Verizon specific eri.xml 2014-03-07 17:31:02 -06:00
prebuilt/common Add apns/eri for Boost Mobile 2014-02-25 10:30:32 +00:00
sepolicy sepolicy: allow vold to mount fuse-based sdcard 2013-12-10 17:10:50 +07:00
.gitignore gitignore 2010-06-27 20:11:11 -07:00
CHANGELOG.mkdn Update changelog and contributors list 2013-12-08 09:06:12 +00:00
CONTRIBUTORS.mkdn Update Motorola contributors 2014-02-19 09:42:46 +01:00
get-prebuilts get-prebuilts: update Term.apk download URL 2012-12-24 14:11:18 +05:30
LICENSE LICENSE: update year 2012-09-19 16:29:50 +05:30
README.mkdn Update README for CM 10.1 2013-01-26 22:01:41 -08:00
vendorsetup.sh vendorsetup: Grab from cm-11.0 build targets 2013-11-27 00:03:42 +00:00

CyanogenMod

Submitting Patches

Patches are always welcome! Please submit your patches via CyanogenMod Gerrit! You can do this by using these commands:

(From root android directory)
. build/envsetup.sh
(Go to repo you are patching, make your changes and commit)
cmgerrit <for(new)/changes(patch set)> <branch/change-id> 

repo start cm-10.1 .
(Make your changes and commit)
repo upload .

Note: "." meaning current directory For more help on using this tool, use this command: repo help upload

Make your changes and commit with a detailed message, starting with what you are working with (i.e. vision: Update Kernel) Commit your patches in a single commit. Squash multiple commit using this command: git rebase -i HEAD~<# of commits>

To view the status of your and others' patches, visit CyanogenMod Code Review

Getting Started

To get started with Android/CyanogenMod, you'll need to get familiar with Repo and Version Control with Git.

To initialize your local repository using the CyanogenMod trees, use a command like this:

repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

Then to sync up:

repo sync

Please see the CyanogenMod Wiki for building instructions, by device.

For more information on this Github Organization and how it is structured, please read the wiki article

Buildbot

All supported devices are built nightly and periodically as changes are committed to ensure the source trees remain buildable.

You can view the current build statuses in the Jenkins tool.