Add a new permission that only allows other system services to call
networking related methods. This permission is intended to prevent
other apps from calling these methods that might leave networking
services in intermediate states.
Bug: 36538042
Test: build, run wifi unit tests, boots, wifi connects
Change-Id: Icba6ad5280e9a8863bd1c706ca34b7add8de5294
(cherry picked from commit fa84050a7e51e2a6643ea242b43f16cd6e3114dd)
1) Switch AccessibilityButtonChooserActivity to non-exported
2) Update AccessibilityButtonChooserActivity's intent action to
be CTS-compliant
3) Switches to correct permission to validate a click of the
accessibility button originated from the status bar service
Bug: 36866328
Bug: 36976440
Test: Manual / Created app to validate launch protection
Change-Id: Ifcd5e8dbbe683dc99bb900a5870a9ba374fbd5d4
Added config_supportsMultiDisplay. Devices that have the config set
to false will not allow launching activities on secondary screens.
Bug: 36776777
Test: android.server.cts.ActivityManagerDisplayTests
Test: #testMultiDisplayDisabled
Change-Id: Iebb79044440866b1693897b0b53ccb987b5fd8e0
Also clear this overlay once the data changes. Some views call
notifyValueUpdated even if the value did not change. Hence remeber the
data that was autofilled and check if the data really changed.
Make the autofilledDrawable publicly accessible so that virtual views
can use the same UI.
As the activity is not aware that the views were autofilled the state
has to be explicitly persisted over activity lifecycle events as part
of the view. The lifecyle does not work yet as the AutofillIds are not
stable over activity lifecycle events.
Fixes: 34946006
Test: Autofilled and changed all supported views.
cts-tradefed run cts-dev -m CtsUiRenderingTestCases
Change-Id: I58b105bb221f1b6466dd136dfe5062d3babb5aa8
- factor out attributes to themes
- use themeing to change ambient header to larger text and icon size
Bug: 30876804
Test: receive notification on ambient screen, observe that header text is slightly larger
Change-Id: I70f79400e2ce47b862b3b501421aa71187866e61
This adds the new runtime protection level flag that if set means
the permission can only be granted to apps that target runtime
permissions (>= M).
ANSWER_PHONE_CALLS has also been made runtime-only.
Bug: 30932767
Test: cts-tradefed run commandAndExit cts-dev -m CtsPermission2TestCases
Change-Id: I42b30414c808730f2d5961ca31b6e3db740b8cf7
The file has fallen out of date since it was fundamentally
updated in commit 50e9b86. This change brings it up to date
with 2017b.
This change also switches back to using zone.tab as a source
of time zone IDs. In commit 50e9b86 the source was switched
to zone1970.tab. Although this switch wouldn't have
meaningfully affected time zone calculations it does alter
the exemplar locations for automatically detected time zones.
This information may surfaced to users in some places and
can lead to confusion because zone1970.tab uses zones that
span multiple countries, while zone.tab zones tend to be
more local. Reverting should lead to a subtly better
localization experience.
During this work a number of unexpected differences between
zone.tab and zone1970.tab were uncovered. These have been
questioned upstream via the IANA mailing list on 31st March
2017.
Notable other updates:
Addition of Asia/Famagusta for Cyprus.
Addition of Asia/Atyrau for Kazakhstan.
Addition of Europe/Saratov for Russia.
The following have been queried with IANA and differ between
zone.tab and zone1970.tab:
Removal of Indian/Reunion for French Southern Territories
Removal of Pacific/Honolulu for United States Minor Outlying Islands
Removal of Asia/Bangkok for Vietnam.
Bug: 25338903
Test: Build / CtsUtilTestCases
(cherry picked from commit 11e51123865d0fdde39407e50038371d88fee302)
Change-Id: Ia5f078af704af06b1cc9ac456c9c2edde74eecfe
bug: 30982298
Test: manual - shared images in Camera, texts in Messenger, and webpages
in Chrome.
Change-Id: If335c269ca54145839ad8fd4b3f9b93a74b550f8
(cherry picked from commit 35b9e3015565850e9de963e4bda1be227825df5d)
If the snapshot starting window has different dimensions than the
snapshots we have taken, we do the following:
- Create a child Surface that has exactly the dimensions of the
snapshot.
- We fill the parent surface with the app background color, as well
as all screen background decorations (status bar background,
navigation bar background).
- We also clip of the status bar/navigation bar background in some
cases, as it looks ugly if it's not behind the system bars.
- Furthermore, we inherit all layout flags on the window and all
layout relevant SystemUI flags on the window such that it's very
likely that the size will match, and the system bars are drawn
correctly.
- In order to make the transition from the snapshot to the real
window a bit more predictable/less messy, we enforce a minimum
duration the snapshot is visible, which is slightly more than our
app transitions.
Test: TaskSnapshotSurfaceTest
Test: Open app, go home, go landscape, open app again
Test: Go to multi-window, open app from recents with a snapshot
taken in fullscreen.
Fixes: 36703868
Change-Id: Ia2d4add6971a18ab7aa2942d2b644d6e87a402af
