Skip to content
Branch: lineage-17.0
Commits on Nov 16, 2019
  1. core: allow specifying building ramdisk(s) with lzma

    invisiblek authored and arco committed Dec 2, 2016
    * Add a flag that specifies which ramdisk(s) to compress with lzma
    * If not specified, fall back to gzip
    * Example: LZMA_RAMDISK_TARGETS := boot,recovery
    Change-Id: I9cce4da90343fb6dfb7039863649e37d78262726
    Force bsdiff for recovery_from_boot.p if not using GZIP
    imgdiff expects a ramdisk to use GZIP, which is causing a chunk
    size issue if recovery is using LZMA
    Change-Id: I3194b4faed25a298fe23b4e24b6dea2885bafda8
    commit 30da083
    Author: Gabriele M <>
    Date:   Thu Feb 9 13:59:27 2017 +0100
        releasetools: Generate recovery-from-boot.p with bsdiff if necessary
        If TARGET_NOT_USE_GZIP_RECOVERY_RAMDISK is true, we want to use bsdiff
        to create recovery-from-boot.p, otherwise there are high chances that
        imgdiff will fail. Currently this is done only when running make, but
        not when we re-create the patch from releasetools, so do it.
        Also, since recovery-resource.dat is used as bonus data for imgdiff,
        don't build it if we are going to use bsdiff.
        Change-Id: I93a662a358ee79f56b8acd4329eedd166a176c66
        (cherry picked from commit 543d737)
    Change-Id: I9cce4da90343fb6dfb7039863649e37d78262726
  2. Merge tag 'android-10.0.0_r11' into lineage-17.0

    invisiblek authored and haggertk committed Nov 6, 2019
    Android 10.0.0 release 11
    Change-Id: If2e16dea1b7d14c3288d8e52c8533ba78e159db1
You can’t perform that action at this time.