summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Caitlin Shkuratov <caitlinshk@google.com> 2024-08-05 20:43:30 +0000
committer Caitlin Shkuratov <caitlinshk@google.com> 2024-08-05 20:49:01 +0000
commitb64d6c6040528012cee5ef09ece5cdcbb78564f9 (patch)
treed0c29f399bc01b5333aa5a642e9ca5eebf572fd3 /libs/androidfw/StringPool.cpp
parent5fa182d8e1e8850b94d3fef88d007be5749cd4bc (diff)
[SB][Screen chips] Don't change recording start time once it's started.
If the user is screen recording a single app, `ScreenRecordChipInteractor` emits two models very close together (~7ms apart): 1) Recording(taskPackage=null) 2) Recording(taskPackage="some.package") This is because the recording state comes from ScreenRecordRepository, but the taskPackage comes from MediaProjectionRepository, so the taskPackage comes in slightly later. Previously, ScreenRecordChipViewModel would change the start time when the second `Recording` event came in. Changing the start time on the Chronometer makes it skip a second, due to some of the internal workings of the Chronometer class. This CL updates the ScreenRecordChipViewModel to not change the start time once the recording has started. Fixes: 349620526 Bug: 332662551 Flag: com.android.systemui.status_bar_screen_sharing_chips Test: Screen record a single app -> verify chip timer doesn't skip from 00: 00 to 00:02 Test: atest ScreenRecordChipViewModelTest Change-Id: Ia6fb78ee050bad835403b781862b53028eacbb51
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions