This allows these same writes to happen in both Android and offline
charging mode, thus enabling VOOC during offline charging.
Change-Id: Iacf85966b5fa37eedb42887d666369fb63e13c33
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
Zoom seems to try using camera ID 2 for the back camera instead of
camera ID 0. Block access to aux camera for Zoom to force it to use
camera ID 0 for the back camera.
Change-Id: I99d79259a2a3adefb72a5ffed5fbbb37bd8b756d
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
* These were moved to sysprops in Android 13 [1] and while
frameworks reads the values directly from power_profile.xml
Bluetooth app reads from the properties.
[1] 976d33062b%5E%21/#F0
Change-Id: I5bff67a15c537e8a47a19f30776fca6bf2c9fbe5
System properties set with the "=" operator cannot be overriden. This
device is used elsewhere in the system and some of the properties need
to be overridden. The "?=" operator will use the assigned value if no
other values are assigned elsewhere, allowing for overrides.
Bug: 230638462
Test: adb shell getprop | grep bluetooth
Merged-In: Ie29700e8b87f6f3fc2da741411dfbe94fa56ca36
Change-Id: Ie29700e8b87f6f3fc2da741411dfbe94fa56ca36
The class of device is a string with a list of uint8t values:
90,2,12
The meaning is as follows:
{Service Field, Major class, Minor class}
Service Field: 0x5A -> 90
Bit 17: Networking
Bit 19: Capturing
Bit 20: Object Transfer
Bit 22: Telephony
MAJOR_CLASS: 0x02 -> 2 (Phone)
MINOR_CLASS: 0x0C -> 12 (Smart Phone)
Bug: 217452259
Test: make -j; -- check that bluetooth.device.class_of_device is
correct
Merged-In: I75a6fb83a6149f58372b7aa46ccc190fd4451ab0
Change-Id: I75a6fb83a6149f58372b7aa46ccc190fd4451ab0
Those keys will be embedded into VtsSecurityAvb on host side
instead, to verify the GSI image used on the device.
Bug: 149806769
Test: build and checks those keys are removed from
$OUT/recovery/root/first_stage_ramdisk/avb/
Change-Id: I8a002ba6f1421fb460056ccae6572050bdb0ce3c
On stock, `config_powerDecoupleAutoSuspendModeFromDisplay` is set to
false. However, by leaving it set to false here, the device is unable to
enter deep sleep mode while Always-on Display is enabled. We will
deviate from stock by setting it to true here.
Change-Id: I47a0f78a43045718b3730387ea7b91c00b9c3794
* `fastchg_fw_update` seems to be needed to initialize VOOC / Warp
charging.
* `ui_soc_decimal` isn't exactly needed, as it seems to be more for
enabling the ability to calculate decimal percentages for remaining
battery capacity on the lockscreen for Oxygen OS. Nevertheless, it
doesn't seem to cause harm to enable this anyway.
Change-Id: I03dd1abe9c2c7be0b7b7576721b6f6338f1afd46
* 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
