summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author “Sherry <yuandizhou@google.com> 2024-08-30 08:53:59 +0000
committer “Sherry <yuandizhou@google.com> 2024-08-30 08:53:59 +0000
commit8b5e8a2673bbbe0f95a7e12cd21bd6852092a1b8 (patch)
treeb8539953a769bc33c6fe345516c42a0e39d539cb /libs/androidfw/StringPool.cpp
parent365edfba6397a805d1d161e6e7ba58ef9257fde7 (diff)
Fix large clock is wrongly scaled down in lockscreen and wrong pivot when applying scale in AOD
That large clock is scaled down in lockscreen is because we apply scale from scaleViewModel when scaleClockOnly is true (large clock is visible) in AOD, but we didn't recover it when small clock is visible, so AOD scale value is kept in large clock views when transitioning from AOD to lockscreen. So when we change from small to large clock, we use the legacy scale value, which scale large clock down in lockscreen. That wrong pivot issue is fixed by explicitly clear pivot whenever applyConstraints is called in ClockSection to avoid using legacy value when clone / applyTo is called for constraintSet. Bug: 357182038 Test: mannually test by showing large clock with notification in landscape mode of Felix, and then fold the device and clear notification, see that the log outputs the correct value for scale and pivotX. Flag: com.android.systemui.migrate_clocks_to_blueprint Change-Id: I92a2befd48f257e93bf088af60cafe9e212eac6a
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions