* The values are kanged from hammerhead and may introduce
latency as it is not selected for any of our panels
and stock does not set these values in the first place.
Change-Id: Iee854ea77d1e8216c8f01aee2f71a178ffcfaf5c
Setting ro.lmk.medium to 800 to prevent important processes from being
killed at medium vmpressure levels.
Bug: 77299493
Test: lmkd_unit_test
Merged-In: I37e1651a0a2b148a852e5bde86501024d4f87bbf
Change-Id: I37e1651a0a2b148a852e5bde86501024d4f87bbf
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
(cherry picked from commit c954ec2eb318518cfa5c6f64a688fd8c809e91c5)
* Seems like mobile data doesn't get toggled
properly after doing this...
This reverts commit f5e6804eff.
Change-Id: I833a2d79c3d1b1ff2a0cb0b94f44d0eda9efab03
* That allows us to set calling account to 'Ask every time'
without it being reset to sub 1 every boot.
Change-Id: Ifb204fd07ec232fe3c55a92b6fc286786782c28b
As seen in the vendor image dumps, equuleus ships with goodix_fod
and ursa with goodix_fod or synaptics.
Change-Id: I2ccef59698a570dcb35c331dd7994fb7f7af68f0
This is no longer a thing in CAF HALs and is currently causing breakage
since the HALs are now guarded with this flag.
Change-Id: I740e2f122a6d3a1896dc11f06d87949553ab7bb1
This is more like a hack, also observed in the stock HAL, for pre-P shipped devices
because those have fpdata store path set to /data/system/users/ by the FingerprintService.
Force treble compliant path and thus avoid using data_between_core_and_vendor_violators
attribute:
> typeattribute hal_fingerprint_default data_between_core_and_vendor_violators;
> # access to /data/system/users/[0-9]+/fpdata
> allow hal_fingerprint_default fingerprintd_data_file:dir rw_dir_perms;
> allow hal_fingerprint_default fingerprintd_data_file:file create_file_perms;
Change-Id: I388f993de7f95fc68007d945f5a9cc975afde120
Drop the reference to YouTube because that's product-specific.
Moreover, the purpose of such thermal profile should be video streaming,
so name it in that generic way.
Change-Id: Ifa8c97a2d231a24fda016a876c06b59825a068a6
There can be an edge case where the BOOT_COMPLETED intent is not
yet received and user tries to open Dirac sound settings. Avoid
letting it crash by making sure init is executed before showing the
preference screen.
Change-Id: I77e6bdd0c61994338f0dbbce4bfa532d84b8afb7
Add a frontend for Dirac sound optimization settings.
Inject into sound preferences through settings IA.
Change-Id: I37f6e64fa440c43dbe238cc65af5f9b0bbd60d83
Signed-off-by: Joey <joey@lineageos.org>
Move labels to genfscon to reduce the overhead inevitably
introduced with the extensive regex.
On the other hand, power_supply/dc/* sysfs nodes were already
labelled in device/qcom/sepolicy and changing its labels was
causing undesired denials while /vendor/bin/init.qti.chg_policy.sh
script tried to update the nodes ownership as seen bellow:
W chown : type=1400 audit(0.0:25): avc: denied { setattr } for name="current_max" dev="sysfs" ino=57421 scontext=u:r:qti_init_shell:s0 tcontext=u:object_r:sysfs_wireless_supply:s0 tclass=file permissive=0
W chown : type=1400 audit(0.0:26): avc: denied { setattr } for name="dc_adapter" dev="sysfs" ino=57426 scontext=u:r:qti_init_shell:s0 tcontext=u:object_r:sysfs_wireless_supply:s0 tclass=file permissive=0
W chown : type=1400 audit(0.0:27): avc: denied { setattr } for name="input_current_now" dev="sysfs" ino=57424 scontext=u:r:qti_init_shell:s0 tcontext=u:object_r:sysfs_wireless_supply:s0 tclass=file permissive=0
W chown : type=1400 audit(0.0:28): avc: denied { setattr } for name="input_suspend" dev="sysfs" ino=57423 scontext=u:r:qti_init_shell:s0 tcontext=u:object_r:sysfs_wireless_supply:s0 tclass=file permissive=0
Change-Id: Ia763482e9890e232ab0e2ef0afdc3699bcec4fc0
* There's no interest in allowing rild to create tombstones,
neither to unnecessarily touch qcril.db
Change-Id: I174ce6d9fc0d12a61706922048f9155f190b31a8
As a result, all ro.camera props aren't automatically labelled camera_ro_prop and some props
can be accessed by priv_app and untrusted_app.
Bug: 134899434
Test: GCA record video / audio; logcat | grep ro.camera.sound.forced
Change-Id: I79873591f312fb05786973a470427d5f4ec9bc82
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
This was basically forcing all props starting with vendor.camera. to
be labeled as camera_prop.
The side effect of doing that was the relabel of props that were
supposed to have a particular label for some reason. Take for example
vendor.camera.aux.packagelist which isn't desired to be relabeled
so to avoid having to write additional local sepolicies.
Change-Id: I1b7c952a241688f6517e1742719e77b6141e2cd2
Enable ro.lmk.use_minfree_levels flag to use minfree levels to decide
when lmkd should kill. This makes lmkd work the same way lowmemorykiller
kernel driver used to work.
Bug: 77299493
Bug: 75322373
Test: lmkd_unit_test
Change-Id: Ic29d7fd21af1cb6af3a7d2a175d210775a09987e
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
During bootup the device first enumerates in ADB only composition
and then falls back to the persist.sys.usb.config.
Prevent this enumeration in ADB only composition during bootup
by setting the sys.usb.configfs from init.qcom.usb.rc
Change-Id: I6c93a778cc0decc6b5c256c60734b0597d753a9d
0x9020 composition includes DIAG + ADB + DUN + NMEA. Add support
for the same.
Change-Id: I364d4e87b63d7e5dfb394db6e92e650764b7cc96
Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
