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
A recent kernel-side change in the display driver [1] updated the
hardware port ID, resulting in a new display ID.
[1]: 0a3ce41964
Change-Id: I83ece64dd7151cfbea90e73fa71f252fe70356ac
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
* 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
Moving the corresponding core_64_bit_only make file after removing the
entry from the common64.mk file. This is to enable the GSI components for
64 bit option available.
Change-Id: Idefd924e096371ae53fd76781257667b4f5a2fb7
* 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
