* Depending on which display the device uses, the node path changes so modify the hal to verify which one actually exists and set it.
* Goodix ts uses spi0.0 and fts uses spi0.1, so suppport both of them.
Signed-off-by: BarryBlackCat <silva.tiago0910@gmail.com>
Change-Id: I2d3ff57651655d5612ff355241a5933137a7bbec
This is a squash of the following:
Author: Ethan Chen <intervigil@gmail.com>
Date: Sat Dec 1 13:53:00 2018 -0800
Declare EUICC permission
Change-Id: I1b151021ca9fc6cf35141b2ccb337bc83197089e
Author: razorloves <razorloves@gmail.com>
Date: Fri Oct 18 00:06:22 2019 -0500
Move eUICC permissions xml to /product
All eUICC items were moved to /product in Q.
Change-Id: I614f86b16f61959c47465863ab1d5d55030209ab
Change-Id: I323dce8b848b44e45ed21002950059e58719113c
* From bangkk_g-user 11 T3TC33.18-48-6 233c5 release-keys.
* Camera seems dead in latest blobs for some unknown reason.
* Let's use old ones for now.
Change-Id: Ic3e5370bc2f5bc9c6909353d7e6e7490cd3ea2c8
* E init : Control message: Could not find 'android.hardware.biometrics.fingerprint@2.1::IBiometricsFingerprint/default' for ctl.interface_start from pid: 689 (/system/system_ext/bin/hwservicemanager)
Change-Id: If70a4b227356c9a3edd98ebe32974040f086ecf4
* Keep the sensors hal config in device tree.
* Drop the rest since sensor service is being built from common tree.
Change-Id: I0b0d2dc2488af08e820ed58ff10070a041c4621d
* Remove regulatory info overlays.
* Drop dubai camera.
* All configs updated from bangkk MMI-U1TC34M.22-64-18 build.
Change-Id: I1fa8c8d6adb783dad7176a168fed6117211f4899
As of 14 QPR2 this is broken, let's remove it instead of updating it
every 3 months. breakfast is the way to go.
Change-Id: I097bd54b894d9a49c7ce8b1ab6f343349e268fd8
Unfortunately, QPR2 seems to cause this app to randomly crash when checking
for aux cameras and I don't currently see a fix, so let's drop it for now
until a solution can be found
Change-Id: Ife2b51aac6c1f77b59cce498e29cd105a5564658
These use the front camera frequently but aren't critical to
functionality, so we don't need to disrupt 5G services.
Change-Id: I0d23c3bfec936ddefcabb93e6a579a5eb11b3574
We don't need to disable 5G entirely during front camera usage, because
apparently only N78 band in SA 5G (Jio) is affected. Lower bands, such
as N28, does not break front camera so let's just disable the offending
band via RIL OEM commands when front camera is active.
Reversed the band editing mechanism from stock qcom-moto-telephony-ext.
Inspired by 70eebccf64
Change-Id: I6ccb247a5d1b1521e1828304f5570269d9e3f221
On some network(s) (confirmed on Jio), the usage of 5G kills front
camera and crashes the camera app. Logs reveal hardware or firmware
issues related to interference or bandwidth, which is out of my
expertise:
[ 63.301897] CAM_ERR: CAM-ISP: cam_ife_csid_irq: 5016 CSID:2 RX_ERROR_LANE0_FIFO_OVERFLOW: Skew/Less Data on lanes/ Slow csid clock:300000000Hz
Until this can be actually fixed (if ever), a temporary workaround.
Inspired by a860cc8189
Change-Id: Ifefb36cf113a5f25feda771ea7729418553e74ed
