* Generated using the command
"adb shell thermal-engine -o > thermal-engine.conf"
* We don't use thermal daemon from OOS which has these
changes inline, instead, make CAF thermal-engine happy
with the config.
Change-Id: I02e45dfbf9880c8e8418c4d8d9b4d827b4d7066d
thirteen
Somehow, the old patched PowerOffAlarm.apk got lost, so we have to
re-patch this apk again to not require oplus-specific permissions.
Update the sha1sum hash to match the new patched apk.
Change-Id: Id419245e7943de99d2316060205404b5c706f292
In libpwirissoft.so's `pxlw` class, `qcomSetDisplayMode()` ends up
calling `irisSetConfigEx()` with `brightness_level_` as one of the
parameters. `irisSetConfigEx()` ends up passing that `brightness_level_`
param to `processDisplayBrightness()`, which seems to do some sort of
additional dimming of the display output depending on what the current
brightness level is.
On AOSP, it looks like `brightness_level_` doesn't get set properly.
After hwcomposer is initialized for the first time (or terminated and
restarted), if we turn the panel off and back on at least once, and then
try changing display modes, hwcomposer seems to apply a constant dimming
of the display output regardless of the backlight level.
Let's work around that by nop-ing out the `irisSetConfigEx()` call in
`qcomSetDisplayMode()`. That way, `processDisplayBrightness()` won't get
called, and we will not get that dimming.
Change-Id: Ied87b229d596bcc597b9ccb0a47368cbcb97f54b
Even though we now have gc5035 unlocked by default, this patch seems
to still be required to achieve the following:
* enables 48MP RAW10 Capture on third party camera apps
* enables long exposure capture support on all package names
* removes the 1/30s shutter speed cap from the viewfinder on third party
camera apps
* enables support for the MFNR viewfinder on auxiliary lenses
Change-Id: If321a31aeffe22b471a08a58432096c9653c2f64
* Let's just use the OnePlus 8 Pro EU NFC configurations
for everyone, they match the OnePlus 8/8T EU configurations
so it should be fine.
Test: Verified NFC turns on, can read tags, and went
to a Dunkin Donuts and used Google Pay.
Change-Id: I1478c92dba58209098f4d4ea37fcc2bceb3f4473
This basically NOPs update_camera_metadata_entry() call that sets
ANDROID_REQUEST_AVAILABLE_CAPABILITIES_SYSTEM_CAMERA to 1 for aux cams.
Change-Id: Ie869b3eb0ea85af99904e2e23e86c4cd0acc3596
* Doesn't work, can't switch between default and oplus
GPU driver. Looking at oplus' APK, there is nothing
really inside just a shell. There were no updates for
the app in the Play Store either.
Change-Id: I0ec61c3b9abfa86368e6c23481d7edf5d8f6a036
* OnePlus reads MAC address from QMI DMS now.
* Since that was the only custom change, move back
to proprietary files.
This commit is a partial revert of 83d053860901aaa5b6fdb54c6160aac817c6806b.
Change-Id: I9e89def5258f9085e7169a1a6753cbdabd1d548c
The modified library NOPs out the instruction to change binder
threadpool, allowing the library to load and camera to work on S.
Command used:
$ SigScan -p "1F 0A 00 94" -P "1F 20 03 D5" -f vendor.qti.hardware.camera.postproc@1.0-service-impl.so
Change-Id: I1ef0ed29e4a2eb820826e5d7df1fa53c9e3df584
No longer necessary since now we can just pass `OVERRIDES` to extract
utils and it'll handle it automatically for us :^)
Change-Id: I19c97f5daa72d809dae2442fcb2b8b81a702aaf2
There are several VMTs inside that library that are prone to change
on CAF merges.
So far, last LA.QSSI.11.0.r1-12300-qssi.0 merge already modified
ConfigInterface VMT in a way that's not backwards compatible thus
it'd be better if we provided a prebuilt library instead.
Change-Id: I25fe58e6721b8d0e67882f576cfaf288c9992fc9
Fixes:
E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: com.android.hotwordenrollment.xgoogle, PID: 4331
E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/android/hotwordenrollment/common/EnrollmentUtil;
E AndroidRuntime: at com.android.hotwordenrollment.common.EnrollmentService.onCreate(EnrollmentService.java:59)
E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
E AndroidRuntime: at android.app.ActivityThread.access$1500(ActivityThread.java:237)
E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7660)
E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: com.android.hotwordenrollment.common.EnrollmentUtil
E AndroidRuntime: ... 10 more
Change-Id: I5e9605a3ecb9ec080aed554c1541ded9f25c188b
* For some users L1 isn't disabled on BL unlock.
While this occurence is a true mystery that
I wasn't able to reproduce on my hardware,
it's totally fine to include these blobs in
the vendor image so that these users can enjoy L1.
Change-Id: Ib5fdb7a41fec84a9df03296ad48473e70ce8f208
