Unable to determine UFFD GC flag for kernel version "5.4.268-qgki".
You can fix this by explicitly setting PRODUCT_ENABLE_UFFD_GC to "true" or
"false" based on the kernel version.
1. Set PRODUCT_ENABLE_UFFD_GC to "true" if the kernel supports userfaultfd(2)
and MREMAP_DONTUNMAP.
2. Set PRODUCT_ENABLE_UFFD_GC to "false" otherwise.
Change-Id: Ie77d9a86a7fe94e4cade1868ffea27194f724e03
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
this commit contains following commits to introduce the fastcharge toggle for stone device that use this tree
they were renamed from sm8250-common to stone
sm8250-common: add fastcharge implementation
* Disabling fast charge may be useful for reducing the heat produced by
the device while charging, or for extending the lifespan of the battery
* This commit introduces the fastcharge HIDL, which writes in the node
/sys/class/qcom-battery/restrict_chg
0 or 1 depeding on user selection.
0 means that fastcharge is enabled, while 1 means that fastcharge is
disabled
Change-Id: I369ba9c437b3a83a88c2ce74d603b7d7ddd9cfbb
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
Signed-off-by: althafvly <althafvly@gmail.com>
6510782439
sm8250-common: fastcharge: Make user setting persistent
Change-Id: I4ff051d6f9685e94022eab32035bfe86a65264b8
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
e050f0dab0
sm8250-common: fastcharge: Use pragma once
Change-Id: I9a9e193a6f66f045f41394d059af8b71778e8d72
ff8e5f6173
sm8250-common: fastcharge: Migrate to blueprint
Change-Id: I200fd6c685183c98f0815b207adae5aa75a37238
4e0d22f486
sm8250-common: Build fastcharge implementation
Change-Id: I3e6994d2c2f419dc8ce98a060204fda3dd16df81
136d369c4e
sm8250-common: Sepolicy: Label FastCharge more general
7a619945ca
sm8250-common: Sepolicy: Fastcharge: Provide needed permissions
https: //github.com/kamikaonashi/device_xiaomi_sm8250-common/commit/298ff28a2ab9c04f953780958de6a8971a947c51
batterysecret hack
51ebc8de81
Co-Authored-By: Ivan Martynov <johnivan19999@gmail.com>
Co-Authored-By: Bruno Martins <1696148+bgcngm@users.noreply.github.com>
Co-Authored-By: Francescodario Cuzzocrea <bosconovic@gmail.com>
Co-Authored-By: Davide Garberi <dade.garberi@gmail.com>
Co-Authored-By: Mohammed Althaf Thayyil <me@althafvly.com>
Co-Authored-By: blazerpaul15 <107421375+blazerpaul15@users.noreply.github.com>
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
Crash:
- E android.hardware.thermal@2.0-service.qti: ThermalHAL not initialized properly.
- E ThermalHalWrapper: Couldn't get temperatures because of HAL error: ThermalHAL not initialized properly.
It is inherited by base_system.mk as of QPR2
Change-Id: I020a05b233f61ea28d03199cbc76051e6e97e1dc
Signed-off-by: mukesh22584 <mks22584@gmail.com>
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
The health AIDL HAL service provides functionalities of charger,
therefore system charger at /system/bin/charger is deprecated.
On top of that, QTI health AIDL HAL service enables suspend by
default, the equivalent of setting ro.charger.enable_suspend
for legacy charger.
set new flag TARGET_DEBLOAT for optional remove_packages
this may be useful to debloat updater for unofficial roms. you can expand the list for any package, just write them in the Android.mk of remove_packages folder
Co-Authored-By: Michael Bestas <mikeNG@users.noreply.github.com>
* CANNOT LINK EXECUTABLE /vendor/bin/mlipayd@1.1: library vendor.xiaomi.hardware.mlipay@1.0.so not found: needed by main executable
Signed-off-by: rdx420 <padraramesh420@gmail.com>
This is a squash of the following commits:
1. Optimise dex flags for a faster boot
* Used multiple threads and speed profile to hasten the first boot
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Change-Id: I2cce5ddf7d50308511e81436fcac613b2c6537bf
2. Rework dex flags again
When I went through https://source.android.com/devices/tech/dalvik/configure my previous configs felt wrong, this one should be perfect (I hope).
Even though there is a slight trade-off for boot time by using the speed profile, we do make up for it by using 8 threads.
PRODUCT_DEX_PREOPT_DEFAULT_COMPILER_FILTER attempts to compile all prebuilts fully optimised to speed level, thus the phone doesnt need to deal with it.
I also do know that this might be a trade-off on size, but I do see the first boot time is more worthy to trade-off.
The speed level mentioned here runs dex verification and compiles all AOT methods.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
Change-Id: Ic0156ff8956a7c5f53820be6db438f6f6399d3c0
3. Switch certain dexopt profiles to verify
Prebuilt apps like Gmail/Google App, will be updated by google play, and there is no need spend time and space optimising what is going to be replaced.
Switch to Google's recommendation of using verify for an OTA package.
Applications still stay on speed.
Instead, replace the install profile with speed-profile making apps perform better.
13.0
