* Allows perf to work properly on boot to restore selected power profile
This fixes log spam -
QTI PowerHAL: Failed to acquire lock.
Signed-off-by: Ahmad Rulim <personal@rulim34.dev>
* Perf-hal tries to access the nodes but requires permissions as reflected in the logs
* 11-10 19:25:50.044 1055 1080 E ANDR-PERF-OPTSHANDLER: Cannot open/create foreground cgroup file
Signed-off-by: CHRISL7 <70589286+CHRISL7@users.noreply.github.com>
Change-Id: I730f8b8bc7cc2b17595cac6130deacbc346d008f
[1] - Add override
* Logs spam with error '-13' which basically translates to access
denied/invalid permission.
* Fix this by giving system read and write access.
Before in log:
Diag_Lib: Diag_LSM_Init: Failed to open handle to diag driver, error
= 13
Change-Id: Ic06b0de0a729052593fb3c703362c5c199f9fd0b
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
Signed-off-by: CHRISL7 <70589286+CHRISL7@users.noreply.github.com>
[1] - this fixing the goodix issue when long press the powerbutton due
annoying kernel events
Change-Id: I8d3e867de2f0c30a46c371a36b691cb9011bd519
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
Starting with Android R launched devices, debugfs cannot be mounted in
production builds. In order to avoid accidental debugfs dependencies
from creeping in during development with userdebug/eng builds, the
build flag PRODUCT_SET_DEBUGFS_RESTRICTIONS can be set by vendors to
enforce additional debugfs restrictions for userdebug/eng builds. The
same flag will be used to enable sepolicy neveallow statements to
prevent new permissions added for debugfs access.
Test: build, boot
Bug: 184381659
Change-Id: I45e6f20c886d467a215c9466f3a09965ff897d7e
Default to false if the property is not set.
Device init scripts will need to be adapted to restart
loc_launcher service when property change is detected.
Change-Id: Icbda789cd2a9a3391f437af2c07fc5127f2f09ab
Analysis of disassembled code in IDA revealed that the stock
libsdmcore is just writing the brightness to a custom sysfs node
in mi_display. Bind mount the real brightness node to that so it
gets written to the real node instead.
Change-Id: I3aa840e50b7a067667b949b0ba1f36d187602547
* Used by GCAM for DSP-accelerated HDR processing
* Arguably we should label /vendor/dsp/cdsp/fastrpc_shell_3 to
same_process_hal_file like Pixels, but the partition is prebuilt thus
we're unable to relabel it.
* Copy the file to writable tmpfs, setup attributes and bind mount back
to workaround the limitation.
[ghostrider-reborn]:
Allow adsp/cdsprpcd and neuralnetworks HAL to access fastrpc_shell_3
[kras edit:
1. rename some contexts as per qva/kona
2. extend to allow camera HAL and VPP service to access it as well]
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Change-Id: Ide90e5c7307d413db5ece736e859559f06679545
The idea is to allow us to not depend on stock QTI Bluetooth HAL, as MAC
addresses fetched from NVRAM by nv_mac script will be saved as hex-encoded
files. We can decode back saved files to then the Bluetooth one be set using
persist property so it can be read by Bluetooth HAL.
This is loosely based on similar techniques used on Mi 9 and ZenFone Max Pro M2.
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I74d07c3c3125a04962c37fe8bfcc8385d1fd3398
