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>
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
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
Maybe TARGET_PROCESS_SDK_VERSION_OVERRIDE is not required but decided to
keep it as for now because it is not harmful
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: Ie3733945ff11c50e08d2d133e63da76309ace0c6
The file is from apq8084/android_device_samsung_trlte-common, and I edit
its node paths for our tablet.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I5be7bb7aa1e00c96280da18b9208c44c0ba3abd2
