Ensure that the list of attribution tags considered "producer" or "source"
includes the attribution tag of the location provider itself. This is
particularily important if the location provider does not use any
attribution tags, as this ensures the null tag is included in the list.
Bug: 186572461
Test: manual
Change-Id: I9a7b2e9b67cbeb700d5c04730541ad4bf051d0da
There are 2 reasons that led to this change.
Right now on trusted displays Dimmer is offered on windowed
magnification display area, but no one offers it on untrusted displays.
There is no guarantee that windowed manification display area always
exists either on all OEM.
In Task#getDimmer() if the task is fullscreen but is translucent it asks
for a dimmer from one of its ancestors, and WindowState#applyDims() uses
Dimmer as if it always can get one. There can also be system dialogs
(e.g. ANR dialogs) that don't belong to any TaskDisplayArea that also
needs a Dimmer.
Therefore add a dimmer to RootDisplayArea.
Bug: 186436456
Test: atest TaskTests
Change-Id: I284b60124e27496352c27f446a2742e3e4756ec9
Also adds the number of views and ExpandableNotificationRows
to the subtext. The former is likely to be in the 1000s for
a healthy SystemUI process; the latter should be roughly
equivalent to the number of notifications (otherwise there
is a leak).
Fixes: 159917121
Test: make, pull down QS, examine tile
Change-Id: I97b17fb8e991264db612b8a6689051b8d83b4222
Add traces to show what messages are currently being handled inside
ViewRootImpl's handler.
bug: 184951839
Test: presubmit
Change-Id: I00c04250b3ea00fb32473d9fa35390510e8692c5
We had two problems, the first one is that the latency instruemntation
overlapped with the jank instrumentation; the second one is that
the swipe / fling instrumentation might be ended too early and the
fling part was ignored.
Bug: 169221093
Bug: 176953201
Test: See the doc list in comment
Change-Id: I11937d02a3a05c82dd2526ae59ccd472f39309c7
Instead of the explicit version check, using the PlatformCompat
api to check whether the feature is enabled or not.
Bug: 160928779
Test: atest android.appmanifest.cts.UsesNativeLibraryTestCase
Change-Id: I316ef37804f75ea05503fb82c021de1701789133
Goal:
In order to get better translations from the expert to users
Bug: 184872714
Test: manual test
Change-Id: I776ddece7163ba3ee6643d4e19f5d45c558aad39
A frame might be missed in both app and SF so adding a separate counter
to keep track of the overall number.
Test: manual
Bug: 185897790
Change-Id: I0ed4e0dc4ef949f40ba612b68860a2da3d0e7e91
Fail with a more general error message if the provided component is not
installed, this avoids exploiting the API to identify which packages are
installed without holding QUERY_ALL_PACKAGES
Test: Manual testing
Bug: 184658476
Change-Id: I47b80acb4c847f3bc0c6550deca40b192f57d598
As part of the new "Nearby devices" permission work, the
registerStateChangeCallback() API has been relaxed to no longer
require permissions. However, we've discovered that some apps were
depending on that SecurityException being thrown, so this change
restores throwing behavior for those legacy apps.
Bug: 186176507
Test: atest BluetoothInstrumentationTests
Change-Id: Ife536dee246b300ffb3dd78aef0b059a230f3835
The IME window may show later depends on whether the task snapshot
contains the snapshot of IME surface, and whether the edit view
is still focused. If display orientation is changed, IME window may
take longer time to redraw. That requires to adjust the timing
of the removal starting window to avoid flickering.
For short term, just fallback the case to legacy behavior that
applies normal screen rotation animation.
Bug: 160451808
Test: Launch a landscape app which opens IME from portrait home.
Return to home and launch it again. The IME window isn't
flickering in 2 orientations.
Change-Id: Idfdf129adbfbee6634d8a27aa78da1f631bd213b
Fixup non-writable app-private dirs that could have been left around by
an earlier race condition in the setup of the FUSE filesystem.
Bug: 181726193
Bug: 182088154
Test: erase userdata, check Youtube dirs are fixed up correctly
Reason for revert: fixing issue in original CL
Change-Id: Ifacf807f62dec3c9e22b5e5af0f2b00c4423ede4
This reverts commit 13f793aec9.
Reason for revert: Breaks device health checks; crashes if dir is null.
Bug: 181726193
Bug: 182088154
Fixes: 186633787
Change-Id: Ia28df79c6ff4aacd6bdadf1d9c540f49dcace707
- update elevation
- update font family to GS Text instead of Google Sans
Test: manual (see screenshots in bug)
Fixes: 185632543
Change-Id: I5c87a287f3e288198fc70f30ac9abb2c47ebb1eb
Make sure it won't introduce redundant fling animation when touch on
divider bar didn't exceed tap threshold. This make sure it won't queue
extra sync transactions with SyncTransactionQueue. Also skip redundant
checks after detected double tap in staged split.
Fix: 186626153
Fix: 179004532
Test: tapping on divider bar of legacy and staged split, it won't make
split sloggish.
Change-Id: I2a326f54f25d77e86fa51bca67b68daca21dedfc
This is necessary for EthernetNetworkFactory because it uses
the static lib NetworkFactory which needs to test where it runs.
Wifi services also need this for its own factories.
Bug: 183902758
Test: ClientModeImplTest
OemWifiNetworkFactoryTest
TelephonyNetworkFactoryTest
UntrustedWifiNetworkFactoryTest
WifiNetworkFactoryTest
Change-Id: I73cc38d7857934fe50995c666915662de4c154ce
While unlock device, there will call showStartingWindow for every
visible activites, which is not necessary because there will only
need one starting window for each task.
Bug: 185318171
Test: atest ActivityRecordTests
Change-Id: I417e0b516de388373d49dc68f1ce6cf52dd1fd3e
