No longer needed now init listens for property changes on a
separate thread.
Bug: 186580823
Test: Cuttlefish boots successfully
Change-Id: Ief3a546d2154231d18957c2f703bd128966d7288
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
* It is started in the on init phase in /system/etc/init/hw/init.rc
Change-Id: Ie10e1d4c520329a76627a965ca139f9ad0f71875
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
As one can see in cfq_arm_slice_timer(), the CFQ I/O scheduler supports
two parameters that can make it delay I/O: group_idle and slice_idle.
Restore I/O performance by setting both the group_idle and slice_idle
parameters to zero.
Bug: 213617178
Bug: 313578691
Change-Id: I02429876790a6456ca957ff7c38f0c8bf88127f9
Signed-off-by: Bart Van Assche <bvanassche@google.com>
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
m8250-common: hbm: Add preference for time-based HBM disable
To specify a duration after which High Brightness Mode (HBM)
is automatically disabled if the lux level falls below the
defined threshold.
[EmanuelCN: Use thread sleep and recheck lux after timeToDisableHBM]
Signed-off-by: AnierinB <anierin@evolution-x.org>
sm8250-common: hbm: Deactivate the HBM tile when the screen turns off
When the screen is turned off, HBM will shut down and the HBM tile should become inactive.
sm8250-common: hbm: Refresh the QS brightness slider whenever the HBM is activated
The brightness slider should be set to 100% when the HBM is activated.
sm8250-common: hbm: Avoid writing to the backlight when turning off the HBM
Not needed.
sm8250-common: hbm: Include a 7-second delay when turning off the HBM
The HBM turning off while walking through a shadow was frustrating. Address this issue by verifying if the threshold has been reached after the 7-second delay.
sm8250-common: sepolicy: allow parts to get SettingsLib prop
ThermalSettingsFragment's use of ApplicationsState includes a
check of whether a package is an instant app or not. The function
isInstant() in AppUtils reads settingsdebug.instant.packages prop
to retrieve a list of instant packages for debugging purposes.
We do not actually use this property, but this check triggers an
SELinux denial for every package in the list and spams the logs
with permission denied errors. Get rid of these log spams by
allowing parts to read the prop.
Test: open the thermal profile settings and check logs
sm8250-common: sepolicy: Allow devicesettings write to vendor_sysfs_graphics
sm8250-common: Disable hbm thermal throttle
adapted to stone (sm6375)
Co-Authored-By: Emanuel <emanuelghub@gmail.com>
Co-Authored-By: maxwen <max.weninger@gmail.com>
Co-Authored-By: Hikari-no-Tenshi <16803494+Hikari-no-Tenshi@users.noreply.github.com>
Co-Authored-By: Anierin Bliss <anierin@evolution-x.org>
Co-Authored-By: Alec Chan <88945170+alecchangod@users.noreply.github.com>
The health AIDL HAL service provides functionalities of charger,
therefore system charger at /system/bin/charger is deprecated.
On top of that, QTI health AIDL HAL service enables suspend by
default, the equivalent of setting ro.charger.enable_suspend
for legacy charger.
* 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
