* Our device directly measures in mA and not uA.
* This fixes "Charging Rapidly" info on lockscreen.
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
since our device doesnt have a fastcharge path (due to broken kernel source), we just adapt and stop and start batteryservice. rewritten to do exactly that
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.