The configs are set for interactive, not EAS. So we have to edit those
configs to be based on EAS system.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
I imported sched_boost implement to my custom kernel, which is for HMP system
basically but to use the CAF power optimizations we should have that node.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
As our power HAL only can work when if perfd exists, we have to import this
binary from another device.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
blu_schedutil is basically from the Pixel 3 kernel, and I did import
this to my custom kernel. This has been developed for the better battery
performance based on schedutil.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
The msm_irqbalance configuration of lge_msm8996-common has more IRQ
numbers for excepting mdss and kgsl-3d0. This is good to improve UX stability.
Refers:
d5f348aedd
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
As we're building our power HAL ourselves, the
TARGET_POWERHAL_SET_INTERACTIVE_EXT flag doesn't working at all. So I
merged this feature to our power HAL to use the extension works, which
is disabling S-Pen panel, LCD, hardware touch key power.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
By copying files from LineageOS/android_device_lge_msm8996-common, it is
more proper for supporting EAS.
Refers:
- ca20a0d81e
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I55cfcb3b764059aac81d265529bdb979c6334f45
This also resolves my workaround for building kernel,
780bb8553c
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: Ia6baaa3f2055206f7e21fbf97d2616b03b95ff79
This is used by the new "virtual disk" feature used by vold to help
debug and test storage code on devices without physical media.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I89c9263f4d1843a751f39fb5c7d7d2150267a295
Update of the commit 24df69b
Confirmed this working with clean installation
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I21ddd66000d18fa93a77e1eb6714f1ae6fd7f0b2
Seems settings this to true breaks unlocking process sometimes on our
device
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I0e1f9bd260e62f76a06c5cca2576c5d925c9b91c
Ours somewhat contaminated for Samsung specific setups. So I removed all
the stock media configs and import them from
LineageOS/android_device_oneplus_oneplus3
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I36cbc17d0f6da25733b4d4bc9c57469ddf0fb866
It will handle Wifi Tethering more properly.
Refers:
- 6419ffb0f8
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: Ie916cb5ec8be4cf837efd4de8444cc327013b1af
It will handle Wifi more properly.
Refers:
- ee18061dca
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I22cbfaddd9c13a6ae653856a751012faf38f202f
As our tablet was updated until Android 9, I tried to use SDK API level
28 but it couldn't init the camera feature. But setting to level 27
seems working well.
Here is the details of overriding SDK API level from a LineageOS commit,
which has Change-Id: I1d95a4019c298497dce504894d0db705e541a92d
```
Replace file pinning applied in commit fee6d01 by setting the lower SDK version
that exempts mm-qcamera-daemon from the tight restrictions on mutex calls.
This allows us to update to the latest blobs without needing to manually
re-patch the offending camera lib.
```
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: Ib75d5806c1facbd8e4e5dd4ea140a2716c6c2f54
This will be detected by a system, we should not set that value
explicitly
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I78fc095de92455cb511ba7d729e842f816805b23
To use KeyDisabler for hardware touch keys.
This will disable touch keys properly.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I6c2cfb8577bab19c708300aa16e0eb18730c293d
Got values from the following repository;
https://github.com/LineageOS/android_device_lge_msm8996-common
That also uses the property values from Google
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: Ib104190b235a07c9c92933ebe6984c2f6426a11e
