A video pause workaround was made due to a signaling limitation in the QC
modem.
Test: Manual
Bug: 62436425
Change-Id: Ic90ded9621929c0821894776c1191f20ddce9afa
* This is only available on Nexus/Pixel devices, and we have our own
implementation in livedisplay.
Change-Id: I8343e4986d7dd8413bd8d36dfad0309a4c08026e
* Restart HIDL camera provider to cover some edge cases where camera isn't
working on FDE devices with boot pin enabled.
Change-Id: Ia757e9d07de26008f426fca582439d68b6d6fecb
Signed-off-by: Albert I <krascgq@outlook.co.id>
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
* For some reason, booting with headphones plugged in results
in a broken speaker output if FDE secure boot is enabled.
* Restarting audio HAL after decryption seems to resolve the issue.
Change-Id: Ie14b89841bf811f0fb09edb0a04fd28aafecde87
Signed-off-by: PIPIPIG233666 <2212848813@qq.com>
Increasing the tcp_rmem is not sufficient to achieve higher rates
for TCP downlink as all sockets in the system are still bounded
by the core socket rmem_max.
CRs-Fixed: 2351198
Change-Id: I198457745a9e48f0098457e86e7d9523c6249cbd
- all vendor init services should be prefixed
with vendor
- radio.atfwd.start -> vendor.radio.atfwd.start
persist.radio.atfwd.start -> persist.vendor.radio.atfwd.start
This property is now qualified as a platform property and is not
whitelisted. Therefore it must be renamed to continue to be
used as a trigger.
Change-Id: Iebb0eed75f7ac6f71085ac12cf2a3e7414defb09
CRs-Fixed: 2223094
As per sepolicy, add vendor prefix to specific properties.
i.e, persist.vendor.sys.ssr.enable_debug,
persist.vendor.sys.mba_boot_timeout,
persist.vendor.sys.modem_auth_timeout,
persist.vendor.sys.pil_proxy_timeout.
Change-Id: Ibeb87194e2ca9b831fc5e721a87764920c21276d
To support end-to-end DRM content playback with SG List feature,
android.hardware.drm@1.0-service needs to have access permission
to /dev/qce to map & unmap ION buffer virtual address with HW Crypto
Engine. So, set /dev/qce device permission 0660 and let it be
accessible by user "system" and group "drmrpc".
Change-Id: If9c0ed70acc2bb063344692374f51441fe84eff6
Creating new directory as persist Bluetooth addr
location is changed from /persist/bluetooth to
mnt/vendor/persist/bluetooth.
Change-Id: Idb30dcd9d0af5f9271955e4c7eeff0bd9afe80ad
CRs-Fixed: 2324749
On android P, vendor persist folder is in /mnt/vendor/persist/.
Change time persist foler to /mnt/vendor/persist/time.
Change-Id: I325dfa2ed336d9ae0a2b5850ec3683db205a513c
* starting rtpd on bootup without waiting for DATA_DAEMON
prop and restarting when property is set
Change-Id: If121089334ef2c0b335320bb561a553163042ba3
Starting imsrcsd on bootup without waiting for DATAD property
which will load libimsrcsbaseimpl and register HAL services
Change-Id: I17c1891583ea99baa31efec0e8ba316e4fbf25f3
hvdcp_opti daemon stores some parameters in
/mnt/vendor/persist/hvdcp_opti directory. Create the directory.
Change-Id: I0cf17467792cc294e6ce1a7f35a356cc0e960e86
Start loc_launcher as gps user and set uid/gid of loc_launcher
to gps and enable SETUID and SETGID caps for loc_launcher, so
that we can start loc_launcher as gps user instead of root and
still have capabilities for SETUID and SETGID. Also remove not
required permissions groups for loc_launcher.
Change-Id: Ie9f1506874b3c3148f9170c8d5db9afd1e70025c
CRs-Fixed: 2192881
To support ODL to read data from QDSS, create a custom group
and set permission of byte-cntr device. And also set
permission to coresight-tmc-etr/block_size to enable
byte-cntr feature.
Change-Id: Ic80156667dd7511392d5970ddcbd0fdc43ffffca
Signed-off-by: Saranya Chidura <schidura@codeaurora.org>
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
* To prevent property name collisions between properties of system and
vendor, 'vendor.' prefix must be added to a vendor HAL service name.
You can see the details in go/treble-sysprop-compatibility documents.
Test: succeeded building and tested on a sailfish device.
Bug: 36796459
Change-Id: I48e6ee0ae3fe401e39efb273256d991fac676357
Treble compliance.
Bug: 70228425
Bug: 70393317
Test: complete wifi test in b/70393317
Test: Test wifi on Taimen and Sailfish
Test: verify sockets exist in /data/vendor/wifi/wpa/sockets
Change-Id: I0bfc3a351419f0a03498e79664949f353369bf1b
-dpmQmiMgr permissions are updated with radio group
to communicate with QMUXD socket.
CRs-Fixed: 2183993
Change-Id: I37195ffc6602d009ac4cace6c742484e70a768ec
Issue: cameraserver or camera-provider service is not able to
write pid's to cpuset/camera-daemon.
Solution:
1) Increased the cpu to 0-7
2) Moved camera-daemon folder creation from on-boot to on-init.
CRs-fixed:2200628
Change-Id: Ifc80c09ae09b353b3c8a0603f14e5ff4206d6796
