Update the documentation for settings-related and affiliation-related
methods:
* The methods for setting a global and secure settings are documented
to be mostly deprecated, because there are methods for the settings
that are honoured and some other settings no longer apply.
* The methods for setting affiliation or binding to a service on another
user can no longer work between a device owner and profile owner
since this combination is no longer a valid one.
Bug: 147795815
Test: manual, m update-docs
Change-Id: I316148cb1d90fbe94999f9d1c242f08554869e97
This is a fix in response to developers' feedback on DP1.
Add Environment API that enables apps to check whether they have All
Files Access special app access. The API encapsulates the actual
mechanics of the check, which are as follows:
* First check MANAGE_EXTERNAL_STORAGE app-op,
if it's allowed, return true. If it's denied (ignored or errored),
return false.
* If the mode is default, then check for MANAGE_EXTERNAL_STORAGE
permission, if it's GRANTED (not just declared), then return true,
else return false.
Also add test.
Test: atest EnvironmentTest # not CTS
Fix: 150115615
Merged-In: I0574827c22960bf8f074313d983f289be7142149
Change-Id: I0574827c22960bf8f074313d983f289be7142149
* Before this change, we were putting the action intent in the Slice,
but we realize that's not the best place as slice is only meant for
data representation, and intent does not fall into that
* This patch includes the code to actually fire the pending intent when
action suggestion is clicked. However, it'll only work if the fill
service have the SYSTEM_ALERT_WINDOW permission for the intent to
be fired when it is in the background. We will move it to be fired
from the client foreground app in a separate patch
Test: manual verification
Test: atest android.autofillservice.cts.inline
Bug: 150499490
Change-Id: I411a7ee05e783f7de94a54064c44a6126afe0b12
Otherwise we shift entire SF schedule for nothing...
Test: Open IME, inspect systrace
Bug: 118118435
Change-Id: I1352860a8f04271cd5dc72366ffc317175db5e3a
Add intent that signifies the desire to access the auto revoke UI inside
the Permission Controller.
Bug: 146513245
Test: none needed
Change-Id: I58d32d2c02941f65c52e054ad712541126086586
* This is to incorporate the API council feedback at b/148107416
* This is made possible by the new DataClass codegen version 15
Test: build
Bug: 148107416
Change-Id: I8adaf45a64bc08e73988d61fba56430f2b49f747
We handle changes to the leashes from the UI thread, but use
the same SurfaceControl wrapper object from the RenderThread with
SyncRtSurfaceTransactionApplier. This means that at the time
we release a SurfaceControl from the UI thread we might have already
scheduled a SyncRtSurfaceTransactionApplier to use it, and actually
that could be in the process of running, leading to racy access and
crashes. To fix this we release the SurfaceControl from the RenderThread
so that it happens behind all existing operations.
Bug: 151086678
Test: Existing tests pass.
Change-Id: I2308d1c64f3f368c32587f99ddfb9e05955f821f
In cases where we are replacing the client surface transparently (e.g.
preserved surfaces), we call reparentChildren to move client added
Surfaces of the preserved Surface to the new Layer. However we are calling
this on the WSA layer, and so we end up reparenting the BLAST Surface
to the new layer. But since we always construct a new BLAST surface on the
WM side, we end up with 2! Rather than try and juggle about when we need
to or need not to construct a BLAST surface and reparenting them across
preservedSurfaces, it seemed either to just use the BLAST surface as the
root of the reparentChildren operation.
Bug: 150013915
Test: Enable BLAST, use split-screen
Change-Id: I1357200b41d183c2331b684ff636dd40a3b98168
With Hierarchical animation, the animation layer will no longer
be a fixed fullscreen layer but animate on the parent container's surface.
In order to run a remote animation, the animation controller needs to
know bounds of the target relative to both its parent and the screen.
The CL includes:
1) RemoteAnimationTarget changes:
- Add localBounds field for indicating the target bounds which
the coodiates relatives to its parent.
- Add screenScreenBounds field to replace souceContainerBounds
to reflect the target bounds relatives to the screen.
- Mark position & sourceContainerBounds as deprecated.
2) Modified related places to set correct localBounds information.
Test: build / run, make sure installing the old version of launcher on
the this new platform change still compatible without crash.
Test: manual as follow steps:
- Launching app from launcher to split-screen secondary stack
- Swipe up to overview screen and drag TaskView to see if the TaskView
surface is shfted, expected is not.
Bug: 148780840
Change-Id: Id9dbf6de193ab73fe94bc24ef6a27edc93380a14
ICU's TimeZone.toString() prints out too much information. Only the ID
is useful.
Bug: 149014708
Test: build only
Change-Id: I7d633f7946f82696e13dbc39749b6f9f44f83fa3
Merged-In: I7d633f7946f82696e13dbc39749b6f9f44f83fa3
(cherry picked from commit 06795ef740)
The method requires NETWORK_STACK or MAINLINE_NETWORK_STACK permissions,
but the annotation was missing.
Test: m
Fixes: 150877670
Merged-In: I2af74cbcfa642f05f5e7bf85b2a8e8c38595f6ca
(cherry picked from commit e45d3ff849)
Change-Id: Ia215b74df99ae60be2e380917be68a272d658ef4
Remove disable Bluetooth action from AdapterService and move to
BluetoothManagerService.
Add factory reset reason into Bluetooth enable/disable reason list.
Bug: 110181479
Test: manual
Change-Id: I4bff3c3bb75fbb0d1e13c459c0d9d3fd3b8b3195
This class is useless at this point and introduces overhead.
Bug: 113554781
Test: FrameworksNetTests
Change-Id: Ib5f540070222865260c16c7182cc13c710a243c2
Merged-In: Ib5f540070222865260c16c7182cc13c710a243c2
(cherry picked from commit c3489ad3a6)
This cl also fixes the way to simulate the touch events in EditorCursorDragTest, with correct raw X/Y.
Bug: 150534899
Test: manual & automated tests
atest FrameworksCoreTests:EditorCursorDragTest
atest FrameworksCoreTests:TextViewActivityTest
Change-Id: I0e9ef73082534ab98ddeddee0218374ed6d556a2