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 a sweet 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 Razer
Phone 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
* This function causes the refresh rate to change randomly, and
produces flickering on the display
* Override the original function by renaming the symbol so linker
uses the symbol from the shim instead of the original library's
symbol
Signed-off-by: daniml3 <daniel@danielml.dev>
Change-Id: I2fa6b3f834df79c32d22f5a057da2108cc9cacab
* Setup sweet sku when device is global.
* Move the nfc manifest entry to sweet hardware sku
variant.
Change-Id: I76ac75cd80f85efa6dfa68753602d934a11000a3
Signed-off-by: Arian <arian.kulmer@web.de>
Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.
Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8
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
* For avoiding halo effect on low light conditions
* Achieve this by creating a custom ImageView that its shown when the
camera is in use
Signed-off-by: daniml3 <danimoral1001@gmail.com>
Change-Id: Iedca0f0d4b304b020daf0ebec74e245581824c98
* We aren't using QCOM's perfd but our blobs still check for this.
* To avoid unnecessary errors, let's just add it back.
Change-Id: Icc44b330f21a658cfa8ded691a6628d8f62c3649
* proprietary perfd blobs can finally be nuked without breaking goodix
* we could even map the functions to use libperfmgr powerhints in the future
Change-Id: I124652f3041761966a3e3bd97c757fecc39cc5fb
* 5s is just too much long plus battery drainer
Signed-off-by: DennySPB <dennyspb@gmail.com>
Change-Id: I7e037c45cd2296a8bbd67d6bd63c212c0ef2a805
Signed-off-by: Henrique Pereira <hlcpereira@pixelexperience.org>
* ro.build. properties are set at runtime if not set
already (after libinit runs) in android 10 hence
ro.build.fingerprint wasn't set since the prop did
not contain a value while libinit ran.
Change-Id: I213c4c2c730c294c42a5d4db70359e7b49d7947e
