* On Custom ROM's on Pixels, the downloading of
this app by SetupWizard often hangs up,
and needs to be restarted. Ship this to avoid
that.
* Added to LOWMEM checkas it isn't necessary.
* Currently, on both devices enforcing veirty, and devices not
enforcing verity, we are unable to flash files to the system
partition after a payload (a/b) style flash. Revert this
logic until is/when we figure this out.
* A/B users will need to flash the ROM, reboot, and install
from thee recovery in the other slot.
* On some devices, /system is already mounted, and when we try to
mount it ourselves, it fails, causing installation to abort
* To prevent this, umount /system before we try to mount it
* We'll first check the currently loaded slot. We can
assume the user just flashed a rom and that the target
slot for this rom is the other slot, so mount that
system image. TODO: autodetect this somehow
* Mount this system partition at /system_root (rw) and then
mount the /system/system folder at /system. We do it
this way for a couple reasons. Because it makes the
script easier to work with and because we're using
toybox from the system partition for operations, which
is expecting /system/bin/linker64 to exist.
Change-Id: Ia6f96f0864d725b0123665bbbce0e31523bb834f
* For some bizarre reason, the unzip util included with
lineage recovery doesn't work with the system/*
wildcard for unzip, so just extract the entire zip
and remove the META-INF folder from /tmp manually
Change-Id: Id11e18d7fef0c78b10f7060a10274ea0e958ea84
Signed-off-by: Paul Keith <javelinanddart@bestas.gr>
* This is done based on the total memory as reported by /proc/meminfo
* If the memory in the MemTotal field is less than 1572864 kB (1.5 GB),
then Google's SuW is removed as a precaution, as it is known to crash
on devices that don't have much memory available to use
* Thanks to cdesai for the solution idea
Change-Id: If0d5b9dff7f9536f78d4069df8665b19209fea52
Signed-off-by: Paul Keith <javelinanddart@bestas.gr>
* This workaround for recovery.fstab was only necessary for
CM recovery, however the recovery will be fixed properly
soon, so there is no need for this workaround
Change-Id: Ib7db0997d1059e9829d9ca4b4a8c208d43bc46b6
Signed-off-by: Paul Keith <javelinanddart@bestas.gr>
* Previously, files that were pinned and weren't
presigned wouldn't have the sha1sum stripped
from the name of the blob
* n.b. This only affected libjni_latinimegoogle.so
Signed-off-by: Paul Keith <javelinanddart@bestas.gr>
* This fixes issues with dpi
* Also, reshuffle PrebuiltGmsCore in blob lists,
since it has to be pinned now
* Standardize blob list naming to proprietary-files-$arch(/common).txt
* This is slightly older than the newest PrebuiltGmsCore,
but it almost never has to be updated, and Android will
silently update to a proper version with the correct dpi
Signed-off-by: Paul Keith <javelinanddart@bestas.gr>
- Fix Play services battery drain on arm
- Fixed remove-faceunlock from updater script
- Show some love for who doesn't have realpath
- Export md5 as a file too
- Simplify create checks (@stucki 6a05464df7ae80784fc8fe8ff2de65152d7bb67b)
- Move target zip out of arch directory (@stucki bf57998702c634f560535b586706931f56a3ed31)
- Clean Up after the build (@stucki f6660501afa1eaefc4d3cf1a043e5c73bdab398d)
- CleanUp final output
