Check device variant by using ro.boot.hwc and
ro.boot.proudct.hardware.sku and set the correct model based on
value of ro.product.marketname on stock ROM
Change-Id: Iae15a7d3558f3c4608546e42ed655a76a0fe8868
Bring back old usage of status_bar_height, status_bar_height_portrait,
and status_bar_height_landscape by set the size containing cutout size.
Bug: 216782082
Test: make
Change-Id: I0bf97352bc07e45d7694f9512266f08e7139c103
* xiaomi for some reason uses mainBuiltInDisplayCutoutRectApproximation
as mainBuiltInDisplayCutout.lets create a new mainBuiltInDisplayCutout
and make it a bit bigger than stock camera cutout and fill it to
avoid aliasing in the cutout area
Change-Id: I4936096e162131cf1463df8f9114e1a6bdba72d8
sweet supports switching between 60 and 120 Hz refresh rates, so let's
expose it in Settings -> Display -> Smooth Display for users to save
battery if necessary.
Test: visual confirmation after toggling several times
Change-Id: Ie698ec4d4e738afd2a9055dba2369233103a4f13
Add a new priority PRIORITY_DEVICE_PEAK_REFRESH_RATE, and a new config
setting config_defaultRefreshRate which maps to that priority. This
allows an OEM to easily specify a default frame rate different from the
peak frame rate.
Bug: 148978450
Bug: 154648391
Test: - Added new unit tests to verify DisplayModeDirector handles min,
peak, and default refresh rate settings correctly.
- Modified haydn to set config_defaultRefreshRate to 60Hz, confirmed
we default to 60, but that an app calling setFrameRate(120) switches us
to 120.
- Confirmed that the "smooth display" and "force 120Hz" options on haydn
work correctly.
- Confirmed Redfin works as it did before - still constrained to 60Hz.
Change-Id: Ibfc35abed2b67093b8114822d233bf1ca31eebb0
Enables default setting to 120hz mode, this can be disabled through
Settings app
Bug: 130249886
Test: wipe user settings and check default peak refresh rate enabled
Change-Id: I205d793dea3f7b971972fa850b0255dcf18db923
Since msm_drm driver is created as a module by default for
all the build configurations, it has to explicitly moved to
first stage (vendor) ramdisk as the recovery menu needs the
driver to display the UI. Hence, package this as a part of
vendor ramdisk for QGKI configurations only as GKI doesn't
have this requirement.
Change-Id: Ic3d5f5a4a1d3b32de7ec4dfe9ef03bf9b8204068
