Install the blocklist in the GKI module directory read by modprobe so
ptp_kvm is skipped on the physical device.
Assisted-by: LLM
Change-Id: I43cb04b1bf2a4782a4c4999ced344e6ae8a05f4d
Reuse the 6.6 common build while retaining WAIPIO kernel selection,
Ferrari partition sizes, shipping API and the existing hardware blobs.
Keep legacy radio declarations in the leaf manifest and replace the old
audio/PAL/AGM declarations with the common AIDL stack.
Use the common handset primary module configuration and AIDL effects
without Quasar, whose proprietary library is not supplied on Ferrari.
Load system_dlkm before the existing vendor loader. Retain the reviewed
WAIPIO module lists rather than inheriting Sun peripheral modules.
Assisted-by: LLM
Change-Id: I1fcf3cbf77e5496682f8242c931b72fd9e349050
Select the Ferrari driver profile and combined overlay with WAIPIO
v1/v2 bases. Fetch the relocated kernel, modules and devicetrees trees.
Assisted-by: LLM
Change-Id: Idb1ab8c23d2c41a29449cf91709292ee857f8e52
Ideally, this is supposed to be generated at runtime on the first
boot through calls from composer but we still haven't reversed it.
So, let's pull them from /data/vendor/display.
Apparently, this doesn't need any library fixups since it can
also load from /odm/etc/.
Change-Id: I16823871fb8a8179dcd7adab4af736bf236be9e3
The display panel that is used by ferrari/wly (Samsung S6E3HC3)
supports pixelworks soft-iris feature and its evident with the
presence of /odm/etcirissoft_samsung_S6E3HC3_dsc_cmd_mode_panel.xml.
This fixes color modes with stock render intents.
Change-Id: Iea2cf85eeb2aee9463d08759df04e5a6ec823df2
* Updated minimum brightness calculation from 4/2047 to 4/4095
to align with display DTSI's max level (qcom,mdss-brightness-min-level = 1,
qcom,mdss-brightness-max-level = 4095).
* Synced screenBrightnessRamp with Oplus SM8650.
* screenBrightnessMap is preferred as it supports only floating-point values.
* Calculated High Brightness Mode (HBM) transition point as 2047/(4095-4).
The transition lux is also obtained from OplusSmartBrightnessController.
* Removed some overlays so as to prefer the defaults.
* Update auto brightness overlays from stock display dumpsys under
OplusSmartBrightnessController.
Change-Id: I0b2513be866728f3ddf93f7fbe296d78d862c813
* Stock oplus camera does not expose 480p videos on any cameras and they are not needed.
* Rear Main camera: 60fps video is supported on oplus camera but unexposed, so lets expose it.
* Front cam: Only HD and FHD qualities are exposed and only upto 30fps in oplus camera. The same modes are exposed properly.
* UW: Supports upto HD FHD 30|60 fps but with shitty quality even in oplus camera. Oplus camera switches to main lens if 4k quality is selected. 60fps remains unexposed, so lets expose it
* Microscope supports HD 30|60 FPS modes. But unsupported FHD quality is exposed too.
sensorlocationX is calculated as width/2
sensorlocationY is calculated as (height - persist.vendor.fingerprint.optical.iconlocation) ie (3216 - 753 = 2463)
sensorRadius is calculated as persist.vendor.fingerprint.optical.iconsize/2 ie (228/2 = 114)
config_udfpsEnrollProgressBar is calculated as sensorRadius+5
Change-Id: If6556437abc7c760a45bd3f73f34e38f5d9bb3f2
lemonade/p are outliers since they use the oplus_chg driver
whereas rest of the devices uses the oplus driver.
Change-Id: I8ab004a2fa4e9cbfb246f5c9eabd701fab03cf5e
The initial densityMapping configuration had references from AOSP
DisplayDeviceConfig.java template which actually has this inverted.
Let's correct it to account for the native portrait orientation in phones.
Change-Id: I07c9567c1d0c72b7ed77c1fe8fdf399bae30dd85
pjgowtham