All populations were being set to 0, causing all colors to be wrong.
Test: manual
Bug: 191391779
Bug: 191374703
Change-Id: Id5bef180ca3e6f30e30631781a74b2efb4402ac5
This will allow us to inspect whether or not compilation times
degrade over time.
Test: ArtStatsLogUtilsTest
Bug: 170149255
Change-Id: I3a0946b4e2bba32db3c972a871bbd2519d1d70c3
Reading the history files can we expensive; don't do it
when we know we don't have to make any changes
Test: atest
Fixes: 191793576
Change-Id: I37026b14e0006420475c7f97f786ff9b139ea008
Test: manually revoke access for a DND app that has rules
created before and after b/189332346
Fixes: 191773100
Bug: 189332346
Change-Id: I7e4fc3cad00d59c6f9f64bbb0f776c3fad751d19
Change-Id: I069fcc124af24227fa50b61d4fc55d6dadc7a20b
- Use pixel height instead of tile count to determine ideal long screenshot height.
- After adding each tile, go back and see if there are gaps in the tile
set, if so then try to fill in the gap before continuing walking up or
down.
- Set max tiles to a constant as it's for system safety and not a
completion criteria in the common cases.
- Remove ImageTileSet's unused OnBoundsChangedListener (definition got
more complicated now that we're dealing with gaps).
Test: atest ScrollCaptureControllerTest
Test: atest FakeSessionTest
Bug: 189475409
Change-Id: I0cfc9519e7fa444d662ac41e0bef4fced785a98e
As part of widget restore, we need to notify participants (hosts &
providers) of the mapping between ancestral and new widget ids.
Prior to this change, this was done at the end of system restore
and after each restore-at-install of unbundled apps.
There were two issues with this:
1) We would try to notify not-yet-installed participants at the end of
system restore and then *not* try again when they were installed.
2) We relied on PACKAGE_ADDED broadcasts to know which participants were
installed, but these are delivered asynchronously and not guaranteed
to be processed before the restoreFinished call.
After this change, we:
1) Only notify participants that are actually installed
2) Use receipt of the PACKAGE_ADDED / CHANGED broadcast to trigger
notification of any restore participants that are added or changed
*after* system restore completes.
2 is safe because by the time PackageManager sends the package
added / changed broadcasts, the app data restore has been completed,
and the app has been killed if needed.
Bug: 162057170
Test: Manual restore of Keep widget via cloud and d2d
Change-Id: I51dec33d09b62faba6d7c7daacd718a3c0682f7d
Also fixes an issue which could possibly lead to no animation
when a view updated with heads up just exactly when the user dismissed
it.
Bug: 187291379
Test: dismiss notification, observe new logs
Change-Id: I6cb93c945a53031ca1a872e28be72883c1b0028d
Because stopped clipping all views, the top views that were
scrolled could flicker on the screen during notification
launches
Fixes: 191470773
Test: add scrolled notification, launch, observe no flickering
Change-Id: Ia30abfdc6a46e8680bc336c3682ff5e35b0fb606
Now Freezer "enable" flag belongs to _boot namespace but "timeout" is in
immediate one. This inconsistency confuses device_config. Solve it
by grouping them together.
Bug: 183713629
Test: device_config get activity_manager[_native_boot] freeze_debounce_timeout
Change-Id: I388215d5236b1f4450516acbe46fcb95457bf017
Legacy VPN is deprecated starting from Android S. So this API
shouldn't be called if the initial SDK version of device is
Android S+. Otherwise, UnsupportedOperationException will be
thrown.
Bug: 189808606
Test: 1. make gts && gts-tradefed
2. run gts --module GtsNetworkStackHostTestCases
Change-Id: I00f49555bbbc8ccf270056f0e4d1bfdd927ef26d
Currently, the user id is cached at the time the operation is
scheduled and the operation is skipped if the target id matches.
This is error prone because the user may have switched due to
another operation before execution.
Fix: 188742113
Test: manual
Change-Id: I01cd423343a49a0fb2f447f7a0f4a25cc2e8200f
