* Remove regulatory info overlays.
* Drop dubai camera.
* All configs updated from bangkk MMI-U1TC34M.22-64-18 build.
Change-Id: I1fa8c8d6adb783dad7176a168fed6117211f4899
Added a device specific overlay that changes the default name
from "AndroidAp" to customized name
Test: Builds, manually verified name change
Bug: 36368950
Change-Id: I38a5f6fb950d6a45342080bae186a8ed276d94bf
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
This reverts commit 4a3a76f061.
Ghostrider_reborn fixed the brightness LUT via the kernel, so we can go back
to the stock ROM overlay values for brightness too
Change-Id: Ic41e70c7730ead1882263a89e31ca3d2438784fc
The values extracted from Stock ROM are quite dim on average and the minimum brightness is low,
So let's remove the three minimum light sensor values on config_autoBrightnessLevels and the
bottom four values and then add another value near max on config_autoBrightnessDisplayValuesNits
to help increase the minimum brightness and also bump up the values for the other automatic
brightness values.
While we're at it, we shall also raise the values for DarkeningLightDebounce and
BrighteningDebounce overlays so that it takes a lot longer before our device decides to actually
lower the brightness to prevent super jarring brightness changes.
Change-Id: Iacafa69d1e27b5201d98a832305c9afc5f228dd3
In the berlin/dubai trees we have overriding values that use the same as
the default values, so let's just revert to that.
Change-Id: I5e4ee2d89fb6c9e058db4395e50d7891c69f85d3
The partition reserved sizes were taking from stock ROM
IE, blockdev --getsize64 /dev/block/mapper/system_a
Change-Id: I7e9ba2b8f732c6ad16d45d78f577f1ac4644713d
* 12L introduced new API to fetch status bar height based on cutout, to
handle multi-display devices. However, some apps directly read the
height from overlay so the layout is broken for them.
* Since our device is not a multi-display one, set the expected height
in overlay directly as the old way to make these apps look good.
* Reduce status bar height to exactly match the cutout height.
Change-Id: I38fae2cdd20b947998766b35920d28bebcf547cf
* Enable COLOR_MODE_SATURATED (native) and drop unsupported render
intents. Set from pstar rro to avoid touching QC defaults.
* Don't enforce Display P3 for all modes, let the system decide which
to take (sRGB in most cases).
* Set default mode to "Adaptive" (in fact "srgb-enhance") which is not
too yellowish or vivid.
Change-Id: I17169a3a5a27a44c1991460c18f79668c9669713
even though we have set physical_power_button_center_screen_location_y
and config_is_powerbutton_fps, the system doesnt use the power button
location for the fingerprint sensor
There's no point to keep using custom pref to set minimum refresh rate
when AOSP smooth display feature behaves in the exact same way in
our case.
Set default peak refresh rate to 60, as this is the same value when the user
turns on and off the smooth display setting.
If its turned on, it will go to 144 Hz.
Change-Id: I497918a9c9687443a9438fb6291769f6e51d9379