Add diag hal interface for system client communication with vendor diag
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* Nullified remaining QTI Bluetooth remnants
* Remove some props
* Using usb audio hal from source
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
Quoting commit afc09932f6fa07c5f6beffbcdc2bb4691e527321 in
system/sepolicy [1]:
"Devices launching with R or eariler can this by setting following
under BoardConfig.mk"
It is impractical to replace every prop definition from qcom to
vendor_property_type for old platforms like SDM660, so relax the
enforcement to avoid triggering millions of neverallows.
ref:
[1] afc09932f6
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
Targeting S+ (version 31 and above) requires that an explicit value
for android:exported be defined when intent filters are present
Change-Id: I12d27c23624eb5259da582b86ac1bd7572754f0c
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* While it fixed the Dual SIM dropping but it introduced UI bug
like when the data is off, it still showed as turned on in UI
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
We are going to enforce that each property has an explicit owner, such
as system, vendor, or product. This attaches vendor_property_type to
properties defined under vendor sepolicy directories.
Bug: 159097992
Test: m selinux_policy && boot device
Change-Id: Ibed833cd9e5d786e82985ded6bc62abdf8cd9ded
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* It is forced to use bpf in Android S. Also we have it backported in k4.4, so this overlay is totally useless now
Signed-off-by: Ratoriku <a1063021545@gmail.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* Re-apply old HIDL Light HAL changes
* Bring back set lcd backlight support, our devices doesn't support to set lcd backlight via hwcomposer
Co-authored-by: dianlujitao <dianlujitao@lineageos.org>
Signed-off-by: Ratoriku <a1063021545@gmail.com>
Change-Id: I1561545a2bc54c6e1b49af6d09b56db506afba5c
Signed-off-by: pix106 <sbordenave@gmail.com>
* Changes authored by dianlujitao in commits 7174356 ("Improve lights HAL") and
f8e30fd ("Fix battery light not lit after notification light off") are
adapted as following:
Type(HIDL) -> id(AIDL) in functions and maps
Note: Keep backlight in the map as per b9e44e5007, allowing SF to set backlight.
Co-authored-by: dianlujitao <dianlujitao@lineageos.org>
Change-Id: I8960a1fe0b44097e703f3f067d4e432a12d26fc3
Signed-off-by: pix106 <sbordenave@gmail.com>
Add Lights in list only if its corresponding function pointer is available.
Update map to store light id & function pointer.
For Invalid Id , return operation not supported.
Change-Id: Id89345fec8b1dfb89bcfbd71c56063707ba6bb2d
CRs-Fixed: 2709805
Signed-off-by: pix106 <sbordenave@gmail.com>
lights smart pointer was used without null pointer check.
This change adds null check.
Change-Id: Ifdd82290cfe4d7ca781adbed8c8a65961c70e244
Signed-off-by: pix106 <sbordenave@gmail.com>
This change add support for Light HAL Implementation using AIDL
Change-Id: I444994ff1a1ca22134e7ef6db13043fd2c06e8a8
Signed-off-by: pix106 <sbordenave@gmail.com>
* Special thanks to @Pulkit077 and @Anush02198
* It fixes dual sim disconnecting in A12 by removing the apk
Co-authored-by: Anush02198 <Anush.4376@gmail.com>
[clarencelol: Instead of removing the apk, replace it with a working one from stock]
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* Unable to start activity ComponentInfo{org.lineageos.settings/org.lineageos.settings.doze.DozeSettingsActivity}: java.lang.IllegalStateException: Fragment org.lineageos.settings.doze.DozeSettingsFragment.HelpDialogFragment must be a public static class to be properly recreated from instance state.
Signed-off-by: ShubhamB <shubhamprince111@gmail.com>
Change-Id: Id48c903f4b6745baf26bc88b95c8425554b36f06
Signed-off-by: pix106 <sbordenave@gmail.com>
To remove bad context names, two contexts are added.
- telephony_config_prop
- telephony_status_prop
exported_radio_prop, exported2_radio_prop are removed. Cleaning up
exported3_radio_prop will be a follow-up task.
Bug: 152471138
Bug: 155844385
Test: boot and see no denials
Change-Id: Ica687a750af61f2d3386691ce6df220b180fb993
Signed-off-by: pix106 <sbordenave@gmail.com>
starting with Android 12 most HAL libraries are not included in VNDK anymore
they need to be explicitly pulled in to `/vendor` for odm blobs
to be allowed to access them:
QCamera : <MCI><ERROR> mm_camera_load_shim_lib: 3306: dlopen failed
with error dlopen failed: library
"android.frameworks.sensorservice@1.0.so" not found: needed by
/odm/lib/libmmcamera2_stats_modules.so in namespace (default)
android.frameworks.sensorservice@1.0 is used by at least mm-camera framework.
Signed-off-by: pix106 <sbordenave@gmail.com>
Thanks Google for silently changing the prop for starting iorapd
service [1].
ref:
[1] 44176c75f7
Test: boot, check if iorapd service is started, and
IorapForwardingService is not complaining
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
* Fixes error
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/qcrild": library "android.hardware.radio@1.5.so" not found: needed by /vendor/lib64/libril-qc-hal-qmi.so in namespace (default)
Signed-off-by: pix106 <sbordenave@gmail.com>
* Might as well remove it from the manifest, since it's not required
* Fixes error:
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/qcrild": library "android.hardware.secure_element@1.2.so" not found: needed by /vendor/lib64/libril-qc-hal-qmi.so in namespace (default)
Signed-off-by: pix106 <sbordenave@gmail.com>
