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
- 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
* 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
This removes the default mounting of debugfs, as
it is no longer allowed from android-S new-launch.
Change-Id: I78878e1c4177c07d66b13e5659d4360252c5f87b
-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
Change-Id: I0b92b246d773db85aa03d033b2cecee54347cbd1
Implement a USB gadget HAL based on the default implementation from
AOSP and move key features from init.mt6768.usb.rc to it. Also remove
triggers for some proprietary USB features that aren't too useful on
custom ROMs and seem to exist mostly for engineering purposes.
Change-Id: Ie920fea8b3834d3bada2609df66ca68ddbb980b1
Google added a check for this prop in R, and if it's running
it will show a notification about it that it's impacting performance.
Why it's not disabled by default I don't know, so just force disable
it here.
[bengris32] Convert to standalone init script and install to system_ext
Change-Id: Ia06ef15388e7e701ed526664e7748f133ad01ee2
* Move the persist.adb.nonblocking_ffs property into
PRODUCT_DEFAULT_PROPERTY_OVERRIDES to ensure its set
everywhere.
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I543194ffd3a87dc4ff3093cb6919c194e501ffa2
adbd
Recent changes to adbd have enabled nonblocking_ffs by default.
These have seeminly uncovered some bad memory corruption in the
kernel ffs gadget driver on every kernel I've tried so far.
Unfortunately I've not been able to diagnose what is going wrong,
so for now, lets disable the nonblocking_ffs.
We still need to root cause the issue as it's a problem even with
the mainline kernel on HiKey, so its likely a generic kernel issue.
Disable nonblocking_ffs in recovery, too.
Change-Id: I7a0797cc9e8e5f263e533beea23642f768c0f017
Signed-off-by: John Stultz <john.stultz@linaro.org>
* All AEE, Meta mode, Factory mode related scripts
have been removed.
Signed-off-by: bengris32 <bengris32@protonmail.ch>
Change-Id: I20ab2c44768ca3f83f8515c2c4455924aaa394d9
