It is no longer a surprise for anyone to see Xiaomi shipping the same
device with different displays and different displays usually mean
different touchscreen drivers.
The current double tap handling in the power HAL only takes into
account one specific node, meant to be set in the device tree.
However, if the touchscreen was registered as a different input device
it would cause the feature to be broken. Address the issue by iterating
through the input devices in order to find one supported touchscreen
input to be used.
Co-authored-by: LuK1337 <priv.luk@gmail.com>
Change-Id: I2f7fb4a8b0c9cd1a16d6c2b93602d285a191f170
Common config.fs/$TARGET_FS_CONFIG_GEN AID/fs configuration
file for all chipset inheriting from base.mk.
Since legacy device-specific android_filesystem_config.h and
config.fs do not co-exist, temporarily include config.fs only
if legacy file is absent. Once all legacy, device-specific
files have been deleted, config.fs can be made unconditional.
Change-Id: Ie100d0cd9db808b82d99be7139f0709390c7f3a2
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
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
