No description
Find a file
Rashed Abdel-Tawab 60fe93525a lineage: Rework DTBO image generation
Currently we handle the DTBO images from start to finish, including
AVB footers, and just drop them in $(PRODUCT_OUT)/dtbo.img when done.
While this works for the most part, we are limited in what we can do
with the DTBO images. For example non-A/B device recovery images must
have a copy of the DTBO image appended to recovery (see AOSP docs:
https://source.android.com/devices/bootloader/recovery-image ). This
means that we need to pass the pre-AVB dtbo image into
BOARD_PREBUILT_DTBOIMAGE in order to let the AOSP build system handle it.

This commit reworks the way the DTBO images are built, placing them at
$(PRODUCT_OUT)/dtbo-pre.img instead and setting BOARD_PREBUILT_DTBOIMAGE
to that path so the AOSP build system can pick the images up and sign
them and append to recovery (for applicable devices).

Change-Id: I8819d7cd92ba298de67dbc7f6b321917ba8524f1
2019-06-06 07:17:27 +02:00
addonsu addonsu: Don't mount SAR system to /system 2019-02-12 10:06:12 -06:00
bash_completion Add a bash completion "--force-sync" for repo sync 2015-07-30 15:13:11 +08:00
bootanimation lineage: Don't error out when screen size isn't set 2018-03-01 06:52:37 +00:00
build lineage: Rework DTBO image generation 2019-06-06 07:17:27 +02:00
charger charger: add 400dpi symlink 2019-05-23 02:50:50 +02:00
config lineage: Rework DTBO image generation 2019-06-06 07:17:27 +02:00
libbfqio libbfqio: Remove vendor variant 2019-03-01 11:38:25 +08:00
overlay overlay: Hide the option to show battery percentage 2019-06-03 03:14:07 +02:00
prebuilt/common apns: Update Singapore's APNs 2019-06-01 16:28:09 +02:00
tools lineage: Dynamically add custom APNs 2018-12-13 07:25:18 +01:00
verity_tool verity_tool: Implement status getter 2018-10-25 09:45:24 +02:00
.gitignore http_prebuilt: Implement archive of artifacts 2017-01-09 13:42:29 +00:00
LICENSE vendor: we are now LineageOS 2016-12-28 19:44:28 +00:00
README.mkdn Lineage 16.0 2018-08-10 19:37:27 +01:00
vendorsetup.sh Lineage 16.0 2018-08-10 19:37:27 +01:00

LineageOS
===========

Getting started
---------------

To get started with Android/LineageOS, you'll need to get
familiar with [Repo](https://source.android.com/source/using-repo.html) and [Version Control with Git](https://source.android.com/source/version-control.html).

To initialize your local repository using the LineageOS trees, use a command like this:
```
repo init -u git://github.com/LineageOS/android.git -b lineage-16.0
```
Then to sync up:
```
repo sync
```
Please see the [LineageOS Wiki](https://wiki.lineageos.org/) for building instructions, by device.


Submitting patches
------------------
Patches are always welcome! Please submit your patches via LineageOS Gerrit!

Simply follow our guide on [how to submit patches](https://wiki.lineageos.org/submitting-patch-howto.html).

To view the status of your and others' patches, visit [LineageOS Gerrit Code Review](https://review.lineageos.org/).


Buildbot
--------

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

You can view the current build statuses at [LineageOS Jenkins](https://jenkins.lineageos.org/).

Builds produced weekly by the buildbot can be downloaded from [LineageOS downloads](https://download.lineageos.org/).