clarify ART workaround

This commit is contained in:
Daniel Micay 2024-03-21 15:17:45 -04:00
parent cab5bd8119
commit 349aba9ee8

View File

@ -744,7 +744,7 @@
<ul>
<li>backport 12 upstream fixes from the mainline MediaProvider, Wifi, NetworkStack and HealthFitness APEX modules</li>
<li>Bluetooth: revert broken upstream change and changes depending on it to fix Galaxy Watch 6 Classic and likely other devices impacted by the same issue (this was a failure of upstream testing and release engineering for AOSP and doesn't impact the stock Pixel OS because it uses a different APEX module revision branched from an older revision of AOSP but it will impact every other AOSP-based OS on Android 14 QPR2 since there isn't a Bluetooth mainline module published in the Play Store and AOSP yet)</li>
<li>Android Runtime: disable stripping symbols for libart to restore compatibility with obfuscated Chinese apps broken by Android 14 QPR2 when not using the mainline ART module</li>
<li>Android Runtime: disable stripping symbols for libart to restore compatibility with many obfuscated Chinese apps using a specific obfuscation SDK which was broken by Android 14 QPR2 when not using the mainline ART module due to the mainline module being based on an older codebase</li>
<li>Android Runtime: remove Android's hard-wired <code>speed-profile</code> compilation for launcher apps which was limiting ahead-of-time compilation for user installed launcher apps to the parts of the code included in baseline and/or cloud profiles rather than compiling the whole app via our default <code>speed</code> compilation which we use to replace JIT compilation and JIT profiles guiding background AOT compilation</li>
<li>allowlist using device controls quick tile when unlocked since it already has a toggle for controlling availability so our new default requirement of the device being unlocked needs to be overridden for it</li>
<li>revert disabling hardened_malloc for Broadcom Bluetooth HAL (does not appear to be a memory corruption bug found by GrapheneOS but rather the stock OS is using an older Bluetooth module without the issue)</li>