We are using neuralnetworks 1.2 since f7ec886eb3 but the context is still 1.1
Change-Id: Ic31eb9f145793ab05ba44e46df799df281275b36
Signed-off-by: Alex Damaratski <alexeydomoratsky1@gmail.com>
Since Android 10 blobs are being used, org.codeaurora.ims still runs
as phone UID as seen by these denials:
m.android.phone: type=1400 audit(0.0:2914): avc: denied { read } for name="u:object_r:qcom_ims_prop:s0" dev="tmpfs" ino=13660 scontext=u:r:radio:s0 tcontext=u:object_r:qcom_ims_prop:s0 tclass=file permissive=0
m.android.phone: type=1400 audit(0.0:473): avc: denied { call } for scontext=u:r:radio:s0 tcontext=u:r:hal_imsrtp:s0 tclass=binder permissive=0
Change-Id: Ic8c1b7996b9e0e7b63ba2a153441c9e8467a8a31
There's nothing really that different here when compared to the
common HAL except for the specific DT2W handling, which can simply
be supported as a power feature lib.
Change-Id: I4c9c2530c8090e05dab38ed829d59ece5e00e1fb
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
It is no longer a surprise for anyone to see Xiaomi shipping the same
device with different displays and different displays usually mean
different touchscreen drivers.
The current double tap handling in the power HAL only takes into
account one specific node, meant to be set in the device tree.
However, if the touchscreen was registered as a different input device
it would cause the feature to be broken. Address the issue by iterating
through the input devices in order to find one supported touchscreen
input to be used.
Co-authored-by: LuK1337 <priv.luk@gmail.com>
Change-Id: I2f7fb4a8b0c9cd1a16d6c2b93602d285a191f170
The charger daemon has been moved to /system/bin, so mimic that change
but keep using the nice deamon. Also the service label got changed to charger
and daemon is now labeled as charger_exec, therefore update it accordingly.
Change-Id: I93a88aef41f52837fd0be691e414a5319b689208
Moving from the default implementation to a binderized service with no
wrapping.
Now using 1.2 implementation of the IPower interface.
Change-Id: Ibefd916544f51545e6889684a051b2ecc5867fe2
