| commit | 16a1cf9e654bcaf3618213df7b9e82db3bdb5d40 | [log] [tgz] |
|---|---|---|
| author | Jernej Virag <jernej@google.com> | Thu Jul 13 16:59:29 2023 +0200 |
| committer | Selim Cinek <cinek@google.com> | Wed Sep 13 20:09:35 2023 +0000 |
| tree | f4986bfefe1d52b513a74814c70e4be383563f16 | |
| parent | 04cc4301f24ad066468571686a42737734f67396 [diff] |
Restore trimMemory behaviour from T When we moved trimming code to ResourceTrimmer in I84637049a106a94bf9f06c5261c2941b55db4ba0, we also moved trimMemory(ComponentCallbacks2.TRIM_MEMORY_UI_HIDDEN) which happens after unlock from StatusBarKeyguardViewManager to the ResourceTrimmer behind a TRIM_FONT_CACHES_AT_UNLOCK flag. Now that we've disabled TRIM_FONT_CACHES_AT_UNLOCK, this also disabled the trimMemory call we were doing since way before Android U. To full restore pre-U trim font behaviour, this call should not be flag guarded behind the font caching flag. Bug: 275486055 Bug: 290898642 Bug: 293929945 Test: Updated unit tests (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:4bc215c4101b9504c244356ad0264ea1f4912bbd) Merged-In: I677855fff144a53d212b65575111491c78803817 Change-Id: I677855fff144a53d212b65575111491c78803817