Android-Generic Project : Getting started

On this page:

1. Prerequisites

You will need to have synced AOSP or a ROM source for Android 10,11,12 prior to adding this to your build environment.

For PC builds - Android 10, 11 & 12 (so far):

- BlissROM (q,r,s)
- AOSP (10,11,12)
- Lineage OS (10,11,12)
- Tesla OS (10)
- Carbon ROM (10)
- Dirty Unicorns (10)
- Project Sakura (11)

For Waydroid builds (Android 10 only):

- BlissROM
- Lineage OS
- /e/
- Project Sakura (10)

Please make sure you're well versed in building AOSP: AOSP building instructions before proceeding.

What you need to build with

System Requirements

Latest Ubuntu LTS Releases https://www.ubuntu.com/download/server
Decent CPU (Dual Core or better for a faster performance)
8GB RAM (16GB for Virtual Machine)
250GB Hard Drive (about 170GB for the Repo and then building space needed)

Installing Java 8

sudo apt-get update && upgrade
sudo apt-get install openjdk-8-jdk-headless
update-alternatives --config java (make sure Java 8 is selected)
update-alternatives --config javac (make sure Java 8 is selected)

Grabbing Dependencies

sudo apt-get install git-core gnupg flex bison maven gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386  lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip squashfs-tools python-mako libssl-dev ninja-build lunzip syslinux syslinux-utils gettext genisoimage gettext bc xorriso libncurses5 xmlstarlet build-essential git imagemagick lib32readline-dev lib32z1-dev liblz4-tool libncurses5-dev libsdl1.2-dev libxml2 lzop pngcrush rsync schedtool python-enum34 python3-mako libelf-dev

If you plan on building the kernel with the NO_KERNEL_CROSS_COMPILE flag, you will need to also have gcc-10+ installed:

sudo apt-get install gcc-10 g++-10

2. How to include Android-Generic Project into your Project:

(PLEASE NOTE: The source for AG v2023 has been pushed but the documentation for it has not. This documentation is only applicable to the archived version of the project.)

Including AGP into your AOSP based project is as simple as cloning it into a vendor folder.

git clone https://github.com/android-generic/vendor_ag-archive vendor/ag

3. Setting Up

Once the project is cloned, all you have to do is a couple small commands to get things going.

PC Instructions:

. build/envsetup.sh
 ag-menu pc

For the legacy menu (SSH/TTY only)

. build/envsetup.sh
 ag-menu-l pc

That's it! It will initially generate the menu items with what is available for modules on initial launch

Waydroid Instructions:

. build/envsetup.sh
 ag-menu waydroid

For the legacy menu (SSH/TTY only)

. build/envsetup.sh
 ag-menu-l waydroid

That's it! It will initially generate the menu items with what is available for modules on initial launch

4. Operation

Now we can go step-by-step through the next few steps and learn how to operate AGP

  1. Generate Manifest ( v2.x GUI/Legacy)

    This step will generate the initial manifest files for Android-x86 or Waydroid based builds. In some cases, this step may fail and state that things did not generate properly. Please read the feedback as it is usually a missing dependency. \

    **After the above steps are all complete, we are ready to sync the new manifest files that are found in your projects .repo/local_manifests folder. To do that, we added **

  2. Sync Project\

    This option is the equivalent of running "repo sync -q --force-sync --optimized-fetch --no-tags --no-clone-bundle --prune -j8" and will run in the terminal window.

    At this point, you may see "fatal: remove-project element specifies non-existent project: ........." This means that your project has removed an item from manifest a different way than we were expecting from the scripts. Solution: cd into .repo/local_manifests/01-remove.xml and comment out the line the sync script was complaining about If any other errors show up with sync, try to manually run:

    repo sync --force-sync -j4

    Once the project has completed successfully, we can continue onto the next step\

  3. Apply Base Patches

    If your project is close to AOSP, then this step should be 100% automatic and no "Conflicts" will show up. Otherwise, there is a chance things will start to require some actual work here. If you do happen to get any patches that show as "Conflicts" here, follow these instructions:\

  4. Apply Kernel Patches

    This will launch the Kernel Patching menu where you will need to select what target kernel you synced in order to apply the proper patches to it. This only applies to Upstream Linux/Google kernel branches that don't have our patches pre-applied.

  5. Build Options

    ****

    This will launch the main build menu, which contains all the options related to the build commands.

Build Options

This menu will show the various build options for compiling your project through AG.

  • Select Product Type Selecting this will ask you what device type you plan on targeting (PC: android_x86 / android_x86_64)

  • Select Variant Type

    Selecting this will ask you what build variant type you plan on targeting (user, userdebug, eng)

  • Select Apps Type

    ****

    Selecting this will present the options for included Apps type

    FOSS - Free & Open Source apps from Aurora Droid & Aurora Store (and microG client) (x86/x86_64/arm64) GMS - not implemented by default EMU-Gapps - Proprietary gapps extracted from Google's Emulator images. (x86_64 only) Vanilla - No added apps or services\

  • Select Native-Bridge Type

    ****

    Selecting this will present the options for Native-Bridge.

    None - No changes to Native Bridge aside from what Android-x86 includes by default Intel's Houdini - Will pull the latest supported ChromeOS recovery image, and extract the Houdini & Widevine files from that and include in your build. Google's libndk-translation - Will need manual setup of vendor/google/emu-x86 before using. Follow readme from that project (we were unable to reproduce results of extracting super.img automatically)\

  • Select Make Type

    ****

    Selecting this option will allow you to choose what kind of final image you would like.

    Standard .iso Image - generic .iso for MBR/EFI EFI .img file - Builds .iso for using in EFI devices RPM Linux Installer - Compiles as an .rpm installer for linux based systems and will install in a folder on the linux drive. \

  • Select Extra Options

    ****

    This will contain only options that can be interchangeable (affected with only an export or build environment variable)

    Make Clean Before Build - Will add "make clean" to your build command and have it run every time you start the build. No Kernel Cross-Compile - Will add the override for NO_KERNEL_CROSS_COMPILE and allow you to build the kernel using GCC 10/11 from your installed system instead of using AOSP or your ROM's GCC\

  • Run Make Clean

    Selecting this will immediately run the "make clean" command on your project. Clearing the PRODUCT_OUT folder\

  • Enable Rusty-Magisk

    Based on what Product you selected prior to selecting this option, the script will compile the resources needed to include Rusty-Magisk into your build\

  • Start The Build

    This command is dependent on all previous options and will also save/reload your last used build command (all the options selected in this section above), then run the build command in the terminal. From this point forward, any errors will need to be resolved manually.

Debugging

  • Resolving Patch Conflicts

    First off, we include two redundant methods for applying patches beyond the base patches script. Apply Base Patches with Resolutions: This will search through each set in vendor/ag/utils/android_r/google_diff/x86-resolutions/set# and attempt to apply any resolutions found after one of the base patches has a conflict. Apply Base Patches Verbose: This will run through the base set of patches, and offer a more verbose patching method. This script will leave a lot to manual work. Manual Patch Resolution: You will want to then make a copy of all the results of the patch scripts (Copy and paste the contents of the terminal output into a Notepad or text document). Each of the patches applied either resulted in "Applying", "Already applied", or "Conflicts". The only ones we want to pay attention to here are the "Conflicts", but only half of them.

    Some of the patches have duplicates for different vendor setups. So you will sometimes get results that look like this:

    Conflicts          system/core/0015-Bliss-init-don-t-bail-out-even-no-SELinux-domain-defined.patch
Applying          system/core/0015-Tesla-init-don-t-bail-out-even-no-SELinux-domain-defined.patch 0

    Notice how the one starting with "0015-Bliss-" failed, but the patch starting with "0015-Tesla-" applied correctly? If that happend on your vendor setup, you can ignore that patch. But if you only see one patch that had a "Conflicts", that will need to be applied and fixed.

    First, you apply the patch manually:

    git am "__patchLocationHere__"

    You can expect that to fail, but it's crutial to the next step. Next you patch the file again, but using the "patch" command

    patch -p1 < "__patchLocationHere__"

    This will generate the .orig & .rej files to help narrow down what you need to fix. Once the conflicting parts (what's in the .rej files) are resolved, delete the .rej & .orig files, then stage the files:

    git add -A

    Then we can continue the staged git am commit from the first step:

    git am --continue

    After applying the patch(s) to your local project folder, remember to generate the patch needed to resolve that conflict:

    git format-patch -1

    Then copy the patch to the appropriate vendor folder for the conflict. Any patches that are needed to be done to the ROM before applying the generic set of patches will go to the prepatch folder (pc_vendor_prepatches/treble_vendor_prepatches), while any conflicts that happened from the generic patches themselves should go to the vendor_patches folder (pv_vendor_patches/treble_vendor_patches) Example:

    cp system/core/0001-init-don-t-bail-out-even-no-SELinux-domain-defined.patch vendor/android-generic/patches/google_diff/x86/pc_vendor_patches/__YourVendorName__/patches/system/core/0015-init-don-t-bail-out-even-no-SELinux-domain-defined.patch

  • (Bliss/Lineage/Others) Apply Extras Patches

    Selecting this will apply any patches that have been added to vendor/ag/utils/android_r/google_diff/x86-extras/ These have a number of patches for Bliss and LineageOS based projects.\

  • (Bliss/Others) Apply Prepatches

    This will apply any of the pre-patches added to vendor/ag/utils/android_r/google_diff/x86-prepatch/ (Mostly only needed for Bliss so far)

Tools

There are various tools we added to help add/maintain/troubleshoot. Those are all listed below

  • Add AG Prebuilt Apps This will clone the AGP Prebuilts repo into your project and link to your build. This includes: Set Orientation - A manual screen rotation control for Android Taskbar - The featured "Desktop Mode" for Bliss OS created by @farmerbb https://github.com/farmerbb/Taskbar Taskbar Support Library - A secondary app for Taskbar that contains permissions and defaults for how Taskbar runs on Bliss OS https://github.com/farmerbb/Taskbar-Support-Library Smart Dock - The featured "Desktop Mode" for Bliss OS created by @axel358 https://github.com/axel358/smartdock Google Webview - A version we have confirmed working on our PC builds (Many ROM's include a version of Webview that does not play nice with PC builds) (FOSS ONLY) - AuroraServices - a secondary app for Aurora Store/Droid that allows a more seamless install experience. Wallpaper Overlays - Will also include any wallpapers added to the drawable folders in vendor/prebuilts/agp-apps/overlay/frameworks/base/core/res/res/\

  • Add Boringdroid This will clone in all the repos required to add Boringdroid System UI to your build, and automatically patch frameworks/base with the required additions\

  • Add Gearlock This will clone in Gearlock and will automatically launch it's scripts when you start your build command \

  • Generate Permissions This tool is meant to help figure out the various permissions that .apk's ask for, and will generate a private permissions .xml for any single (or batch folder of) apk files. will ask you to select a folder of prebuilt .apk files, and then select a permissions folder/filename to contain the resulting permissions.xml \

  • Grab Modules When updating/adding on new scripts to use with AGP, this will reload the modules list and relaunch the menu (mostly redundant now as the menu reloads the list automatically)\

  • Manifest Backup This will take all the repos currently included in your project and generate a manifest.xml with revisions included in order to easily share your project with others.

Private Tools/Scripts

This project supports an array of proprietary and enterprise functions that will be included in vendor/ag/private-scripts/ which is only accessible through licensed access to our private AGP repos. In the Public repo for AGP, you will see a placeholder script that does nothing:

  • license-to-access-enterprise-tools

If you do have access to the AGP private repos, all the scripts included in your license will show up at the bottom of the main menu. For example, in the screen below, we have three scripts:

  • Add Proprietary Files - Will let you include proprietary vendor files or prebuilts to be included in your build

  • Add Proprietary Native-Bridge - Will allow you to include a vendor licensed native-bridge, like Intel's Houdini

  • Add Proprietary Recovery - Will add your customized recovery image (Recovery development contract required)

  • And more...

PreviousProject InfoNextAndroid-Generic Project : Using With Bliss OS Source:

Last updated

Was this helpful?