Apparently on AOSP builds, these nodes when read by the hals
with O_RDONLY attribute, need an elevated read permission, which
is apparently unneeded on mtk builds/stock rom.
This fixes video playback/OMX
Signed-off-by: Vaisakh Murali <mvaisakh@statixos.com>
Change-Id: I7f358d0037de569a4eb038e5ac2a17b7651d307d
Signed-off-by: fjrXTR <fajarslebew31@gmail.com>
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
- init services fail to setup encoders on boot and camera and
screenrecord fails to open video1 when trying to encode a video.
- While we may wanna consider looking through services that make use of
these devs and correct their groups for AOSP, this gets the job done
for now.
Change-Id: I0278efe201a9cbaa20c650fdc32bed6f9ecfd017
Signed-off-by: fjrXTR <fajarslebew31@gmail.com>
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
* We also changed zram_loopback_size with zram_backingdev_size so correct it.
Bug: 145116439
Test: confirmed there is no warning and zram backing device was configured
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: I51be34c59203813a2f493eee6ab442c9940b75d7
Signed-off-by: fjrXTR <fajarslebew31@gmail.com>
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
-Set max_comp_streams to num of cores since upstream also moves this to percpu.
Bug: 38249616
Test: boot and run zram-perf showing better performance
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
The ndk_platform backend will soon be deprecated because the ndk backend
can serve the same purpose. This is to eliminate the confusion about
having two variants (ndk and ndk_platform) for the same ndk backend.
Bug: 161456198
Test: m
Signed-off-by: xyzuniverse <dev.xyzuniverse@gmail.com>
Signed-off-by: fjrXTR <fajarslebew31@gmail.com>
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
* On non-gms builds, /system is ext4, just use the variable set in
BoardConfig.mk to configure postinstall
Signed-off-by: Woomymy <woomy@woomy.be>
Change-Id: I20407e3e6b34b143f88c5c8054e575ce2fa55684
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
Drop unused GPU node and instead use input touch boost for boosting
whenever a touch input is detected upto 50% and for a duration of
1 millisecond, improving overall scrolling and responsiveness.
Signed-off-by: Vaisakh Murali <mvaisakh@statixos.com>
Change-Id: I77c163ea7a2cf9546c321b180b2304b099fc7a34
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
* Clean-up the scenario table by removing hints which
would never be triggered under an AOSP system.
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: Ib4572fe68ed7e0e77124895b47b59daa0e3786c0
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
* This hint along with almost every MTKPOWER_HINT depends on fwk side changes
* Use INTERACTION hint to boost stuffs on interaction instead
Change-Id: I79603458fb525cdc1b6ac58cee31b84d63083f79
Signed-off-by: SamarV-121 <samarvispute121@pm.me>
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: I8de2a2935901cbd3eaa50ce2d8aa09f61080ba02
Merged-In: Ie633ea788dab3389a3407ec9a461b5837befca46
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.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 tall order with the 8 GiB of usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save RAM.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
Signed-off-by: dodyirawan85 <40514988+dodyirawan85@users.noreply.github.com>
Shirayuki39