* VENDOR from LA.UM.9.12.r1-14400-SMxx50.QSSI13.0
* QSSI from LA.QSSI.13.0.r1-09000-qssi.0
* Split CAF proprietary files
* Update Keymaster to 4.1
* Use FBE v2
* Use Non 20801/20804 (Nord) libs/firmwares
* Do not use odm/vendor dir for WCNSS_qcom_cfg.ini
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
* We aren't shipping wlchgmonitor for all devices, thus `disabled` is
not necessary.
* Because we are properly labeling wlchgmonitor, we don't need
`seclabel` either.
Change-Id: Ic0a28f6cef3a8dfeda560f6f04dc23feed0a601a
* 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
This change lets us use gc5035 camera, which was blocked by OnePlus long
time ago after people discovered its *magic* capabilities. By default
only `com.oem.autotest` can use it, however if we replace the first
character with a NULL byte, then strncmp returns 0, and thus we pass the
check and allow everyone to use it.
You can see the logs below that led me to discover that behavior.
[DEBUG ] JIANJIA.cpp:89 PretendOpenCamera() logicalCameraId 4, m_ClientPackageName 0
[DEBUG ] STELLA.cpp:1445 informKernel() force: -1 value: 6 buf: 5
[DEBUG ] chxextensionmodule.cpp:1005 ExtendOpen() You shall not pass 0
[DEBUG ] chxextensioninterface.cpp:298 chi_extend_open() [OP_EXT] OPEN_CAMERA X
[ERROR][HAL ] camxhal3module.cpp:772 ProcessCameraOpen() Camera Open failed with error status = CamxResultEInvalidArg
Change-Id: I9b3e4e55f07cef40886e09941f7ed0523cdf8cfa
* This introduces fixup scripts and kang mode and fixes
passing of arguments longer than one word,
such as --section "Hello world".
Change-Id: I42dde659e9bea4f7e1c9a7a3fa8da3243774ca4e
