| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
* And I was wondering why I couldn't find it anywhere... ಠ_ಠ
|
|
|
|
|
|
|
|
|
|
| |
address denials such as:
avc: denied { module_request } for pid=1 comm="init" kmod="crypto-cts(cbc(aes-ce))-all" scontext=u:r:init:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0
which caused by b/35930111
Bug: 36056446
Test: no denials
Change-Id: I2a1fd14a0225a79526f77228bddd299434f075f3
|
|
|
|
| |
* The rules came from marlin's sepolicy.
|
| |
|
| |
|
| |
|
|
|
|
| |
Change-Id: I8fd3e9ef5c97f87b2688b607d983b4b540481b46
|
|
|
|
| |
* ims apk is now in /system.
|
|
|
|
| |
Change-Id: I2fd8a24c29089a92b842aeb2cea564fcca137134
|
|
|
|
|
|
|
|
|
|
| |
* ./out/host/linux-x86/bin/assemble_vintf -m -i system/libhidl/manifest.xml \
-o device/zuk/msm8996-common/compatibility_matrix.xml
* Manual edit:
- Remove comments
- Remove vndk entries
- Set optional="false"
|
|
|
|
|
|
| |
vendor/framework/qti-telephony-common.jar"
This reverts commit 68bfbbc68600f14d7339dfe1ceeb7aa836c70107.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* We renamed 'factory' as 'vendor' on our partition table:
z2_row: sgdisk_static --change-name=9:vendor /dev/block/sda
z2_plus: sgdisk_static --change-name=46:vendor /dev/block/mmcblk0
Note that partition number for z2_plus may not be the same if you came from Indian's stock
or from Chinese's stock.
Check first the output of 'ls -l /dev/block/bootdevice/by-name/factory'
* Thanks to @cryscript for the idea and his work for z2_plus.
|
|
|
|
|
|
| |
libmmcamera2_sensor_modules.so.
* The blob changed after the upgrade to ZUI 3.5.344.
|
|
|
|
| |
* Better to go step by step avoiding breaking things... ;-)
|
|
|
|
|
|
|
| |
* The flag is no longer needed, since the new native binderized
lights HAL is being built in place of the legacy one.
Change-Id: I7dd516d0ac73152082983766b29289479be62af0
|
|
|
|
|
|
| |
* Nothing in the OSS bits takes it into account.
Change-Id: I6f949a12c643810cb1fba764bf13abb30e5dd88c
|
|
|
|
| |
vendor/framework/qti-telephony-common.jar
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add required permissions for netmgrd to use the new netutils wrappers
Bug: 36463595
Test: boot sailfish, test LTE, wifi, wifi calling and phone calls work
Change-Id: I5894ee2659f97fce4f4f2b16c54c10f42484b454
Signed-off-by: Sandeep Patil <sspatil@google.com>
|
|
|
|
|
|
| |
and peripheral manager blobs.
* from marlin OPM2.171019.029 release.
|
|
|
|
| |
Change-Id: Idff05f2626138c96dccd3ab4c26c4df1be40a606
|
|
|
|
|
|
|
| |
- imsrcsd starts alarm timers hence needs
WAKE_ALARM capability.
Change-Id: I0e72998bab6b17ca6222e5a931d26275fa784e97
|
| |
|
|
|
|
| |
Change-Id: I23adbffbe22ff622d0a6fb82290380d86c29d0e4
|
| |
|
|
|
|
|
|
|
|
| |
Remove this redundant mechanism of copying DB.
QCRIL Daemon already takes care of the copying
at runtime
Change-Id: I2213c2a8a1c9717c92f3cf5e7873c0ee9e65da35
|
|
|
|
|
| |
* Imported from ZUI 3.5.315 removing everything that is not
useful for our msm8996.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Required because the lights need to be turned off late in boot
(e.x. during fsck for disk health), and before, blank_screen
accessing light encountered a race condition where if it didn't
get scheduled before all of the processes which were getting
shutdown were getting killed, the screen wouldn't blank.
Bug: 74976325
Test: adjusting brightness continues to work
Test: screen blanks during shutdown at the correct time
including when an artificial 5s delay is inserted when
the phone normally fscks (which can also be quick)
Change-Id: I57ebc11d7ecf57ee327c681455712f4b53de6fd3
Merged-In: I57ebc11d7ecf57ee327c681455712f4b53de6fd3
|
|
|
|
|
| |
* Believe it or not, we have a more recent build than op3
for these blobs.
|
| |
|
|
|
|
|
| |
Change-Id: Ieaa9c9308a4004eeb92027b71999359ea47e5fd8
Signed-off-by: Wei Wang <wvw@google.com>
|
|
|
|
| |
Change-Id: I6dfc2f82393f23e3f11bc813057c9446985d1968
|
| |
|
|
|
|
| |
* And fix the path of android.hardware.audio.pro.xml.
|
| |
|
|
|
|
|
|
| |
libmmcamera2_sensor_modules.so.
* The blob changed after the upgrade to ZUI 3.5.315.
|
| |
|
|
|
|
|
|
|
| |
* avc: denied { read } for pid=2288 comm=m.android.phone name=libimsmedia_jni.so dev=sda9 ino=1103 scontext=u:r:radio:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
* avc: denied { open } for pid=2288 comm=m.android.phone path=/vendor/lib64/libimsmedia_jni.so dev=sda9 ino=1103 scontext=u:r:radio:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
* avc: denied { getattr } for pid=2288 comm=m.android.phone path=/vendor/lib64/libimsmedia_jni.so dev=sda9 ino=1103 scontext=u:r:radio:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
* avc: denied { execute } for pid=2288 comm=m.android.phone path=/vendor/lib64/libimsmedia_jni.so dev=sda9 ino=1103 scontext=u:r:radio:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
|
|
|
|
|
|
| |
* And edit the xml permission files to use /vendor/framework instead of
/system/framework.
* As I said on the previous commit, we have to pin the linked blobs.
|
|
|
|
| |
Change-Id: Ieb35a130a36d2edc3e6b91b29622b478ffd4848c
|
|
|
|
|
|
|
|
|
|
|
| |
Set the timestamp in display metadata so that clients aware of
private_handle such as VT can use this un-modified timestamps.
Camera framework is unaware of this timestamp and cannot
modify this
CRs-Fixed: 1050092
Change-Id: I78668d9981e354b6986caa75dca5721c1901e9b6
|
|
|
|
| |
* I don't know what happened here... xD
|
|
|
|
|
|
|
| |
* It fixes audio call in/out on GSI.
* Pin the files as there isn't support for move linked
apps & frameworks.
* We had to edit the permissions xml files to replace /system with /vendor
|
|
|
|
| |
* avc: denied { read } for pid=609 comm="generic" path="/storage/emulated/0/DCIM/Camera/VID_20180331_163634.mp4" dev="fuse" ino=24 scontext=u:r:mediaextractor:s0 tcontext=u:object_r:fuse:s0 tclass=file permissive=0
|
|
|
|
| |
* We could probably optimize them more, but for now it's enough.
|
|
|
|
| |
* And simplify hal_fingerprint_default.te
|
| |
|
|
|
|
| |
Change-Id: I5ef0c9a6919a0823e0573f623b17c3661457c353
|