* Display charging level in percent and update
graphics for it
* Use lineage teal as the main color and red
for low charging level
* Update battery fail to match new style
* Define battery fail file to actually use
our custom image
Change-Id: I6907da5116f6bbd1788902b177ed999c1568815c
Signed-off-by: Chippa-a <bagirovvusal99@gmail.com>
This fixes the following warnings:
13:04:54 Disallowed PATH tool "pahole" used: []string{"pahole", "--version"}
13:04:54 See https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools for more information.
"pahole" is not allowed to be used. See https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools for more information.
/home/bgcngm/android/lineage/kernel/oneplus/sm8550/scripts/pahole-flags.sh: 12: [: Illegal number:
/home/bgcngm/android/lineage/kernel/oneplus/sm8550/scripts/pahole-flags.sh: 16: [: Illegal number:
/home/bgcngm/android/lineage/kernel/oneplus/sm8550/scripts/pahole-flags.sh: 20: [: Illegal number:
Change-Id: Ice2a3753301a7b7782037fd35544e2831b258650
On some devices too many .dtb files are generated. Instead of taking
all of them, allow to only take selected .dtb files for the final
DTB image.
Example: Motorola Edge 40 Pro (rtwo, sm8550) generates the following:
obj/DTB_OBJ/out/kaka-rumi.dtb
obj/DTB_OBJ/out/kalama-rtwo-base-kalama-rtwo-evb1-overlay.dtb
obj/DTB_OBJ/out/kalama-rtwo-base-kalama-rtwo-evt1-overlay.dtb
obj/DTB_OBJ/out/kalama-rtwo-base-kalama-rtwo-na-vzw-evt2-overlay.dtb
obj/DTB_OBJ/out/kalama-rtwo-base-kalama-rtwo-prc-dvt1b-overlay.dtb
obj/DTB_OBJ/out/kalama-rtwo-base-kalama-rtwo-prc-pvt-overlay.dtb
obj/DTB_OBJ/out/kalama-rtwo-base-kalama-rtwo-row-dvt1b-overlay.dtb
obj/DTB_OBJ/out/kalama-rtwo-base.dtb
obj/DTB_OBJ/out/kalama-v2-rtwo-base-kalama-rtwo-evb1-overlay.dtb
obj/DTB_OBJ/out/kalama-v2-rtwo-base-kalama-rtwo-evt1-overlay.dtb
obj/DTB_OBJ/out/kalama-v2-rtwo-base-kalama-rtwo-na-vzw-evt2-overlay.dtb
obj/DTB_OBJ/out/kalama-v2-rtwo-base-kalama-rtwo-prc-dvt1b-overlay.dtb
obj/DTB_OBJ/out/kalama-v2-rtwo-base-kalama-rtwo-prc-pvt-overlay.dtb
obj/DTB_OBJ/out/kalama-v2-rtwo-base-kalama-rtwo-row-dvt1b-overlay.dtb
obj/DTB_OBJ/out/kalama-v2-rtwo-base.dtb
with only kalama-rtwo-base.dtb and kalama-v2-rtwo-base.dtb needed.
Disabling compilation of the other kalama.dtb isn't possible, as this
would also disable the compilation of the needed .dtbo files.
Because they are earlier in alphabetical order, and the matching
board ids, the bootloader ends up selecting those, instead of the
correct ones. This results in USB (and possible other things) to
not work.
Change-Id: I486b6ec538a3e4906b5b8aa5ecb355b480b60de7
It can be the case where OEM/ODM decided to put the main DTBOs
outside vendor/qcom (e.g. vendor/oplus). Support such usecase
by generically allowing all .dtbo files found in all first-level
subdirs to be moved to base DTB folder.
Change-Id: I154d401b560535d1fa8cd7ed4965dd34a4cf75f2
All devices lauching with Android 13 (and above) must include
a system_dlkm partition, where GKI modules should reside.
Android 13 build system only supports providing prebuilt modules,
by pointing BOARD_SYSTEM_DLKM_SRC to the modules source folder.
Google will introduce BOARD_SYSTEM_KERNEL_MODULES for Android 14,
so take a step forward and use that macro to exclude the listed
modules from the usual vendor DLKM partition and place them into
the GKI module partition.
Note that the GKI modules are placed into lib/modules/androidX-Y.Z,
as defined by Google and observed in system_dlkm_modprobe script.
Change-Id: I2b1644479788cb5c9568cac738202b1d55fc28d7
The gralloc struct has been conditionally adjusted not to
break blobs that use the old struct.
So far only GRALLOC_HANDLE_HAS_RESERVED_SIZE was hooked up
for Google Pixels, but it's now time to hook up the remaining flag.
Change-Id: I175bd328bd9733b9487e349f7a8486f15ef0a450
* Mtk ImsService checks for location data to register ims,
which constantly triggers the location indicator.
Change-Id: I1b78ffd788129902a23eba844044f3afbdfe46ff
Signed-off-by: techyminati <sinha.aryan03@gmail.com>
Move some apps from common_mobile to common_full,
so that devices inheriting from common_mini don't
ship with all the apps.
Example usecase: "tablet-like" device that inherits from
common_mini_tablet_wifionly and has no camera support.
Change-Id: I723e413b0e5b43fee9011c6b55dcbc303e811c44
This appends `--version_code=$(date -u +%Y%m%d)` to aapt flags, which is
useful for flushing some caches upon system updates.
Change-Id: I6575b878f09c1c3138e12abc34d39405f51245e7
Fixes:
ERROR: HIDL interface vendor.lineage.livedisplay@2.0::IAntiFlicker is
referenced in /system/etc/vintf/compatibility_matrix.device.xml,
but there is no corresponding .hal definition associated with a
hidl_interface module in this build. Typo?
Change-Id: If7708540351db6f465504ed433638653e2c52503
All Pixels modem.img: fbpack version 1
QCOM Pixels bootloader.img: fbpack version 1
Tensor Pixels bootloader.img: fbpack version 2
Test:
export WORK_DIR=/some/dir/with/factory/images
source vendor/lineage/vars/pixels
for d in ${devices[@]}; do lineage/scripts/pixel/firmware.sh $d; done
for d in ${devices[@]}; do git -C vendor/google/$d status; done
Co-authored-by: Chirayu Desai <chirayudesai1@gmail.com>
Change-Id: Ic1990f75a6be515e5d91d65e3ddf88b8e0c90001
To specify the charging control allowed modes:
TARGET_HEALTH_CHARGING_CONTROL_SUPPORTS_{BYPASS,DEADLINE,TOGGLE},
To specify the charging control paths:
TARGET_HEALTH_CHARGING_CONTROL_{CHARGING_PATH,DEADLINE_PATH},
To specify data written to TARGET_HEALTH_CHARGING_CONTROL_CHARGING_PATH:
TARGET_HEALTH_CHARGING_CONTROL_CHARGING_{ENABLE,DISABLE}
Change-Id: I88831c84966f82648c8ca60de5abb34416140f6c
* This way the user can choose to turn it off, and it'll
never have been enabled
* If they just keep it as the default (toggle will be on in SuW),
then it'll be enabled, which is the default we want
Change-Id: I878200a0351d0b0018a975e432602de2badc4eef
