sm8450 and above have a very annoying SMS receiving bug where for some
carriers it won't work after a device restart if QTI telephony injection
isn't available, but one of the workarounds is to either use airplane
mode toggle or eject the sim card and reinsert it
Instead of doing that? Let's try and automate disabling and enabling the
sim card
EDIT: Some holi/blair devices have this problem too.
Co-authored-by: Marc Bourgoin <themard85@gmail.com>
Change-Id: I76732c2a668ff179e32050aee4abe315de3d9357
MAC_1_PATH does not exist in the N200, causing a 10-second delay in
generating MAC addresses. By that point, the WLAN driver has already
failed to get a MAC address, thus leaving Wi-Fi broken.
Change-Id: Iab2d34aa9db9e8843108b90b203e82f915c79bda
This feature relies on wireless charging capabilities, which the Nord
N200 lacks.
This reverts commit d2493c7765.
Change-Id: I44753bd51d3f1a812999607ae67bc431b561f750
OnePlus does not ship their DASH/Warp Charging feature with the N200.
Their 18W block is most likely just a rebranded QTI charger.
Change-Id: I176b3bd91877943f76b0db6e146ea845e0bf2d55
The fingerprint HAL in hardware/oneplus is mainly for devices
with FOD, which the Nord N200 does not support.
ID mismatches will make the generic HAL fail, so hack the goodix
blob to fix it.
Change-Id: I0724569ed1105d8c63075286987ad56ea0ecd078
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.
Change-Id: Iedbbcc5086c09f549e91e73ece7311563c378347
tri-state-key package has been integrated into KeyHandler app, and
KeyHandler itself no longer needs to be added to lineage-sdk overlays.
Change-Id: I13b8f05e8e0b036c9303a01ec0c7e2d99b6756f7
There seems to be a race condition somewhere that prevents
it to be properly labelled, so move to genfs.
Change-Id: Ie2d1deeb19a871eb0b9f5120a92432fda658d725
The list of folders for genfscon was generated using following script:
for f in `adb shell "find /sys/devices -name wakeup -type d"`; do
adb shell "ls -Z '$f' | grep -qv u:object_r:sysfs:s0 || echo '$f'"
done
While list for regular file_contexts was just a simple grep "wakeup[0-9]".
Change-Id: I66abd501ce53b84e7268948d01d7b6c6c42cfbd1
SELinux is more and more annoying nowadays, we all know that...
After spending hours to figure out why camera wasn't working while
on enforcing mode, the audits finally showed up after booting
into permissive mode. :S
05-31 01:19:55.133 877 877 I provider@2.4-se: type=1400 audit(0.0:456): avc: denied { read write } for name="capture" dev="sysfs" ino=116259 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
05-31 01:19:55.133 877 877 I provider@2.4-se: type=1400 audit(0.0:457): avc: denied { open } for path="/sys/kernel/tof_control/app0/capture" dev="sysfs" ino=116259 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
Change-Id: I1727b1a299a02f15b75dce9a4d5c72201f6632c3
