The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a tall order with the usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save precious RAM on this
device.
Change-Id: Ic2f9edd811879e3f18876a508273a9544d8a23e0
This change yields considerable SQLite performance gains. It
should be generally safe as this device has irremovable battery.
Some OEMs have been doing this for years.
Change-Id: I541709fc771d4b501b56b8555e5e8a04486d0293
[dereference23: Take values from curtana-user 11 RKQ1.200826.002 V12.0.4.0.RJWMIXM release-keys]
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
Change-Id: I4153efdbd5ac95a32607d8aba1b6bbbdb02765c0
On builds where A/B support is enabled the system image acts as the
rootfs. In this case we can no longer create the non-hlos image mount
points at run time as we used to. We now create them as part of the
build itself.
Change-Id: I30d98f7c50fca3ce7117b9b8d87150655bb5b440
Add AVB flags to compile recovery image
as a chained partition. This is required
for safe OTA when multislot support is
not present.
Change-Id: I1115eba4038e6fcaa61440846a25861366996ed4
Signed-off-by: Volodymyr Zhdanov <wight554@gmail.com>
* AVB's `--flags 3` argument builds a disabled VBMeta with
disabled hashtree, so no need to set both flags individually.
Change-Id: Ibe9ee322a5af58f13e76d53e18dee49451fe8838
Partitions that use vbmeta_system can be found by looking at
avb flag in fstab from boot ramdisk.
--flags 2 makes the verification function of avb always return a
positive result.
--set_hashtree_disabled_flag builds the vbmeta images with the
HASHTREE_DISABLED bit set and as a result they don't need to manually
disable dm-verity via e.g. 'adb disable-verity'.
The rest of the configuration is taken from
https://source.android.com/devices/tech/ota/dynamic_partitions/implement#avb-configuration-changes
Change-Id: I381feef8f6fefc8449ca50d85d704b67bcc8a77e
This can be checked by looking for a rild service in system.
If it's missing, then a vendor ril service is being used, in
our case, it is qcrild.
Change-Id: I5378de6eec4ff2511a49c19c0fc474658efe338f
Signed-off-by: Albert I <kras@raphielgang.org>
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
Change-Id: Icf9f877415cd6242f27b248b6821bd3464790904
Partition sizes can be found by query-ing sysfs.
For example, for super partition.
> ls -la /dev/block/by-name/super
lrwxrwxrwx 1 root root 16 1970-03-23 06:51 super -> /dev/block/sda17
> cat /proc/partitions | grep sda17
259 1 8388608 sda17
The size needs to be multiplied by the block size used by
/proc/partitions, which is 1024 bytes.
Logical partitions found inside the physical super partition
can be found by looking for entries with the logical flag in the
fstab inside boot ramdisk.
Change-Id: Ic65df8e093a601e3f603c40174b116b20072ee27
* This libinit has been made to commonize device variants props handling
[dereference23: Adapt for Xiaomi SM6250]
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
Change-Id: Iab68ff451ab1d6e861fb4cda4ef07fad3123ecde
