With the QPR2 merge, the AOSP implementation doesn't allow
toggling linked & unlinked volumes as a setting; it has to
be set by config or overlay.
Since we like customization, enable separated volumes
Also needed crdroidandroid/android_frameworks_base@922f964
Signed-off-by: AmolAmrit <amol.amrit03@outlook.com>
* Our device directly measures in mA and not uA.
* This fixes "Charging Rapidly" info on lockscreen.
* Adjusted values according to avicii
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: AmolAmrit <amol.amrit03@outlook.com>
Some banking apps read the file /proc/net/unix to
find out whether things like Magisk are installed/running.
To prevent that, chmod it 440.
This file isn't needed by any other process when boot is finished.
I've tested this and banking apps that did not work before
and recognized Magisk being installed now don't recognize
that and work just fine.
Signed-off-by: aswin7469 <aswinas@pixysos.com>
Signed-off-by: firebird11 <hbgassel@gmail.com>
Change-Id: I8f4c3ce55fe206786018ffba5e3301c52158a844
Signed-off-by: strwbrry143 <alexfinhart@gmail.com>
This fixes an issue with displaying fast charging on the lock screen
when connecting/disconnecting the charger.
Change-Id: I6c72ef056ee247ca6f1ddb12b3542becd7636a90
Signed-off-by: AmolAmrit <amol.amrit03@outlook.com>
The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a somewhat tall order with the ~5.3 GiB of usable RAM that
we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Disable pinning of the camera app to save precious RAM on this device.
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
* PowerProfile: screen.on is deprecated! Use screen.on.display0 instead.
* PowerProfile: screen.full is deprecated! Use screen.full.display0 instead.
Signed-off-by: AmolAmrit <amol.amrit03@outlook.com>
* Make auto brightness more stable, prevent the brightness from
jittering repeatedly in dim environment.
Signed-off-by: AmolAmrit <amol.amrit03@outlook.com>
* The stock ROM enables this because our vibrator supports
subtle "tick" vibration effects. Enable it in our device tree as well to make
pulling down the notification shade/QS panel feel slightly more interactive.
Signed-off-by: AmolAmrit <amol.amrit03@outlook.com>
* VENDOR from LA.UM.9.12.r1-14400-SMxx50.QSSI13.0
* QSSI from LA.QSSI.13.0.r1-09000-qssi.0
* Split CAF proprietary files
* Update Keymaster to 4.1
* Use FBE v2
* Use Non 20801/20804 (Nord) libs/firmwares
* Do not use odm/vendor dir for WCNSS_qcom_cfg.ini
This change yields considerable SQLite performance gains. It
should be generally safe as this device has irremovable battery.
Some OEMs have been doing this for years.
Change-Id: I541709fc771d4b501b56b8555e5e8a04486d0293
