GithubHelp home page GithubHelp logo

android_vendor_pac's Introduction

android_vendor_pac

We will not be accepting pull requests on pac github so please do not send hoping that you will be the exception. You will be contacted and told to use gerrit.

Instructions for sending to Gerrit

sudo apt-get install git-review
git clone https://github.com/PAC-man/android_vendor_pac
cd android_vendor_pac
<make edits>
git add -A
git commit -m "Message"
git-review

Register at PAC-man Gerrit and use the username that you registered under with git-review. Make sure to add your ssh keys to your Gerrit profile.

The git-review package will only have to be installed once.

If you are going to make extra additions, just repeat steps, but instead of using git commit -m use git commit --amend. Gerrit will recognize it as a new patch-set.

To view the status of your and others patches, visit PAC-man Code Review.

Files to Edit

  1. Dependencies

    • We use cm dependencies when ever possible. If you must use other remotes please be prepared to answer why and try to limit them as much as possible.
    • We use PIC (https://github.com/Pinky-Inky-and-Clyde) for proprietary repos. This is done to allow for all vendor files to be pulled from the same place. If your vendor files are not on PIC, please submit your vendor files via pull request to the appropriate repository. Please keep commit history by using remotes and merges.
    • Keep the file free of white spaces and formated to look like the rest of the devices dependencies files. Yes we are all OCD.
  2. Product MK files

    • Found in the Products directory.
    • Easiest if you copy most from other .mk files just fill in the device specific areas correctly. Make sure you using the correct resolutions.
    • If you are using your own device overlays don't forget to create the files. If you add them in the .mk then you must create them or they will not be functional.
  3. VendorProp

    • Self explanatory.
    • Keep alphabetical.
  4. Contributors

    • Keep alphabetical.
    • Don't forget to change the total devices at the bottom.
  5. Nightly/Weekly.xml

    • Nightly - If your device qualifies (no add/remove files/cherries needed) add your device here.
    • Weekly - If your device uses the add/removes/cherries (mostly legacy devices) add your device here.
    • Keep alphabetical.
  6. XDAThreads

    • Add your thread links here.
    • Keep it alphabetical.
    • Follow the format.
  7. XDA Forum Thread Template

    • Just c/p to your thread.
    • Fill in the needed specific device areas.
    • Rom DL link should direct to PAC Forum Thread.
  8. PAC Forum Thread Template

  9. devices-breakdown.xml

    • Used for our dynamic change-log.
    • Keep alphabetical.
  10. add/removes

  • Found in the manifest directory.
  • Used for legacy devices.
  • Please try to keep this as clean as possible and only use if you have to.
  • We host a ton of repos so use cherrys.sh option if possible. If we don't host it then you can use a add/remove.
  • Disqualifies your device for nightlies.
  1. cherries.sh
  • Found in tools/.
  • this injects cherry picks and patches for gerrit and other commits.
  • if pac hosts the repos then please use this method by adding your patches to our repos and sending a commit to gerrit with the patch and a DO NOT MERGE message. We will abandon the commit and you can use the cherries.sh file to cherry-pick during build.
  • very easy to use and understand (read the cherries.sh file for detailed instructions)
  • Disqualifies your device for nightlies.
  1. Overlays
  • Found in the overlay directory.
  • Used to either find your correct overlays already created or create your own.
  • If you have added your device to an overlay in the .mk file then you must create your own.
  • We have ones pre-made for xxhdpi, xhdpi, hdpi, mdpi, ldpi feel free to use these.
  1. Contact either Chad ([email protected]) or Lokesh ([email protected]) to be added to the maintainers group hangout.

PAC-Script Instructions

Usage: build-pac.sh [options] device

Options:
 -c# Cleaning options before build:
    1 - make clean
    2 - make dirty
    3 - make magicbrownies
 -d  Use dex optimizations
 -f  Fetch cherry-picks
 -i  Static Initlogo
 -j# Set jobs
 -s  Sync before build
 -p  Build using pipe
 -o# Select GCC O Level
     Valid O Levels are
     1 (Os) or 3 (O3)
 -v  Verbose build output

Example: ./build-pac.sh -c1 hammerhead

android_vendor_pac's People

Contributors

nick0703 avatar papa-smurf151 avatar bkjolly avatar singhdd93 avatar blindndumb avatar szlkiev avatar tianruig avatar markp-mckinney avatar langes72 avatar goldflame09 avatar madc0wusp avatar apascual89 avatar bluefa1con avatar cmartinbaughman avatar tdm avatar metaiiica avatar josegalre avatar grarak avatar zyonee avatar wechy77 avatar gs2usr avatar atrus5 avatar owain94 avatar c457 avatar vertigo2012 avatar garwedgess avatar mallardduck avatar jaydub82 avatar jamieg71 avatar pvyparts avatar

Watchers

Nitin Shukla avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.