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
Test: manual testing - ensure that the brightness value in
Settings>Display>Brightness Level can go the full range from 0% to 100%.
[wight554: adapted for our value]
Signed-off-by: Volodymyr Zhdanov <wight554@gmail.com>
Change-Id: Ife1f2796bb3b8ec5f508903afd30a31556b49cbe
The stock configuration oddly sets this reside on /data/nfc which is not
writable by modern policy. Instead, all vendor runtime data should go
into /data/vendor.
Signed-off-by: Marijn Suijten <marijns95@gmail.com>
Change-Id: I60a94a39239268046016fcf8be4a613ef4ae6541
Earlier implementation uses DEFAULT_OFFHOST_ROUTE to update Tech A,B
route location and also as route location for payment apps not having
route location (secureElementName attribute).
Tech F is handled separately using DEFAULT_NFCF_ROUTE.
New change introduces DEFAULT_TECH_ABF_ROUTE config which will be
used to update Tech A,B,F and DEFAULT_NFCF_ROUTE will not be used anymore.
DEFAULT_OFFHOST_ROUTE will be used only to update route location for
payment apps not having route location (secureElementName attribute).
Change-Id: If9ee25038d5b05a1a5bbf04f3a51c9ac1324ae74
[dereference23: Rely on libinit instead of device codename]
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
Change-Id: Ic135add84d3e1d88a852b798b312b2ea025866a4
