Add support One-handed mode system properties flag to enable B3
project.
Bug: 200899897
Test: Build a new ROM build to manually test
Change-Id: Ia511f9a298f76589780f258daf657d36c666e206
Add a file "fstab.gs101-fips" alongside the existing "fstab.gs101" in
order to specify different encryption settings in FIPS mode.
"androidboot.fstab_suffix=gs101-fips" on the kernel command line will be
used to select the FIPS fstab when needed.
As the two fstabs should be otherwise identical, generate them from a
template file so that they will stay in sync.
Note that generating the fstabs requires that they be installed as build
system modules rather than via PRODUCT_COPY_FILES, which results in the
vendor_ramdisk copy of the fstabs being installed to system/etc rather
than /. This shouldn't cause any problem, now that Android has been
updated to look for the fstab in this location too.
Bug: 191417025
Change-Id: I1d115e014df8ba2fb83046ac0b9b791597364846
(stopship hack) Roll forward the SPL so that we can test
rollback cases in testing before launch.
Bug: 187105270
Change-Id: Ic0bdb7e3ece264aa42af1965421a485a8f16980b
(stopship hack) Roll forward the SPL so that we can test
rollback cases in testing before launch.
Bug: 187105270
Change-Id: Ia6e75f0b6699f7967d4b92ef973f5ca6af1b5e6a
Revert "Detect factory reset and deleteAllKeys"
Revert "Add deleteAllKeys to IKeystoreMaintenance"
Revert "Enable deleteAllKeys from vold"
Revert "Allow vold to deleteAllKeys in Keystore"
Revert submission 15521094-vold-deleteAllKeys
Reason for revert: Causes infinite loop in Trusty KeyMint
Reverted Changes:
I9c5c54714:Detect factory reset and deleteAllKeys
I2fb0e94db:Allow vold to deleteAllKeys in Keystore
Id23f25c69:Add deleteAllKeys to IKeystoreMaintenance
Ife779307d:Enable deleteAllKeys from vold
I4312b9a11:Enable deleteAllKeys from vold
Bug: 187105270
Change-Id: I0a236e0308b9b8354e669b9261fc22a88a01f743
If vold detects when setting up metadata encryption that there has been
a factory reset, call deleteAllKeys on Keystore to delete old user data.
Bug: 187105270
Test: booted Oriole twice
Change-Id: Ife779307db0fe161c8889f7aaab34e2899a6c9e6
(stopship hack) Freeze the SPL so that we can test more
rollback cases in testing before launch.
Bug: 187105270
Change-Id: Icb475d6c3331d26a6b5314cbb0cdf2cbe1428a27
So devices not supporting CDMA don't include the feature by mistake.
Bug: 194307361
Test: inspect build artifacts - telephony.cdma.xml is included
Change-Id: I0fe3a3624d2cda2b57347402d62e8a16513174e5
Merged-In: I0fe3a3624d2cda2b57347402d62e8a16513174e5
(cherry picked from commit d808d99ce089ca4c7ff4e2abe8ee76b4eeb38a64)
Avoid SF cache thrashing in some cases.
Bug: 189928400
Test: no flicking issue with the testbuld (removed displaycolor fix)
and flicking happens after set the prop to 0
Change-Id: I24aa79001ec21cff18ae5ac8ff988f70ed121061
We have seen cases SF main thread running longer occasionally which may
run in danger of missing frames. This CL lifts cpufreq for SF when touch
boost is active to compensate the sudden jump of its cpu demand.
Bug: 192099706
Test: Build
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: I49b2d589249f60a38eab907afbadfbcfdd233d1c
Launcher prop needs to be accessed in system partition only,
hence move the related prop to /system/build.prop
Bug: 192621663
Test: ro.launcher.blur.appLaunch prop is set correctly,
and Blurs are disabled on App launch.
Change-Id: I6721d59498c5d35dfd560f429b8aed7a01ac29fc
All devices use gralloc4 now, so this code is unused.
Bug: 174998182
Test: builds for the affected devices
Change-Id: Icff36a0204f7f9fd10ae7269248aef8a08c5fc1e
Setting backend thread affinity with higher uclamp value can cause
governor to clock little cores to max. Disable explicit affinity for
driver backend threads.
Fixes: 192486236
Test: build, see SF's backend threads on mid cores in gpu comp.
Change-Id: Id1b17d9783fc65f2d2541fa9c6166d771494cd42
This among other things greatly increases tethering performance.
Bug: 185092876
Test: TreeHugger, built and booted on an oriole, enabled tethering
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: Ic9f0b4bef05250bb38c91dc1e046366098d98dc0
They are use by the GOogle Play Store to filter devices
that might need low latency feature.
Bug: 189793763
Test: Build and check the files
Change-Id: Ibf71147b971bfc4fe4e769772851e604203395b8
Since all the WHI phones have 6GB+ RAM, we should be using at least a
6GB dalvik-heap config, as being done in pixel5 and older devices.
Test: build and boot
Bug: 189738006
Change-Id: I5a232d2901dec819b225812d023d2e5a43d3e0a6
The property should be based on device max refresh rate.
Move to raviole config files.
Bug: 177493042
Test: build
Change-Id: I34c42c87e92208e9f8140197e00f713aafaa63ba
When display and SF falls out of sync, there is a possibility that while
display holds on to a buffer, a composed buffer could be waiting in the
decon thread. Since maxFrameBufferAcquiredBuffers is 2, GPU will have to
wait for display to swap out the buffer it is currently presenting to be
able to compose for the next frame, which leads to SF missing its
timeline for subsequent frames.
Bug: 190842189
Test: perfetto
Signed-off-by: Devika Krishnadas <kdevika@google.com>
Change-Id: I434e8644cff2538589c1c9b2bf731afae0aa8980
