references during the Content Capture Sharing.
Motivation: if the remote app is killed, we don't want a possibility of
system server holding a stroing reference (through a reference chain)
to large objects in that app. Therefore what's send in the binder has to
be a weak reference. And we will store a hard reference to those objects
in the client app's static context.
Storing hard references to objects in system_servier is less critical, because that is not going to be killed.
Bug: 148265162
Test: covered by CTS tests
Change-Id: Ie561aab6019d191cf8659fb350e045089e7781ed
This allows to configure the recipient of the ADD_CONTROL intent.
Test: manual
Test: atest ControlProviderServiceTest
Fixes: 152549957
Change-Id: I29b549271da53d844d564df819cf9c1c9bc81968
Add support passphrase and ack dialogs. Passphrase should use the
exact same text and dialog as the PIN dialog, only defaulting to text
input.
Bug: 152517004
Test: Controls Mock App supports launching all dialog types
Change-Id: I3ebd51d656818f8edad9b70ccc8f0b89d6d8acc6
Bug: 150395371
Test: make && flashall
Bitmap is replacing methods that use a hidden GraphicBuffer with ones
that use the public HardwareBuffer. ScreenshotGraphicBuffer is just a
holder for GraphicBuffer and some metadata; switch it to hold a
HardwareBuffer (and rename to match).
Remove GraphicBuffer#createFromExisting, which was only called by
ScreenshotGraphicBuffer#createFromNative. Also remove JNI references to
that method, which were no longer in use.
Switch uses of GraphicBuffer that retrieve it from a
ScreenshotGraphicBuffer to HardwareBuffer.
Changes are almost entirely mechanical:
- (Screenshot)GraphicBuffer -> (Screenshot)HardwareBuffer
- GraphicBuffer#destroy -> HardwareBuffer#close
- getGraphicBuffer -> getHardwareBuffer
When creating a Snapshot in SurfaceFreezer, use the ColorSpace of the
ScreenshotHardwareBuffer.
Remove GraphicBuffer#createFromExisting. This is no longer necessary,
and although it was marked UnsupportedAppUsage, go/nonsdk-dash shows no
usage.
Change-Id: I41cb03fb65432d208820a428783de82a9f152035
Throwing an exception is not enough in this case. When the HAL
behaves unexpectedly, the system service and the HAL must be
reset and the client must be notified. Without a full reset in
this catastrophic case, the state of the HAL and the system service
cannot be guaranteed to the client.
Bug: 150569186
Test: Intentionally load an incompatible voice model and confirm the
device can recover.
Change-Id: Ia7c3f25e48f04bf32a96c64ec998fdfa52459685
Based on feedback from developers (GBoard) there are cases
where they want the app UI to cover the suggestions during
animations (keypress popup should cover the suggestion area).
This change adds a dedicated InlineContentView that is
returned when a suggestion is inflated. This view has APIs
to dynamically move its surface above/below the host window.
Also the new InlineContentView has no public constructors
as these are always created by the system via other APIs.
Finally, the InlineContentView only exposes the surface
control of the inlined UI which is useful for reparenting
to achieve clipping of multiple such views in a given area
on the screen.
When the content surface is below the app window it is not
be interactive and all touches go to the hosting app. In this
state the app can draw on top of the suggestions. When the
content surface is above the app window it is interactive
and the hosting app cannot render on top of it.
While at this this also fixes the case where a surface can
cover the suggestion surface even if it was on top of the
app window. Now if the embedded content surface is covered,
even partially, by another one the embedded UI is not
interactive.
bug:15140337
Test: atest AutofillTestCases
Change-Id: If1db185506ae6916b9d655ab647dd59b626cf61e
In R, all file path access is proxied through the Media Provider database.
This change ensures that the filesystem is indexed in the database
before broadcasting volume state mounted. This is essential as we do
not want apps to access the volume before the data is ready.
Similarly, the Storage Service processes other volume state changes before
broadcasting to other apps.
Since we want to block volume state changed broadcasts until the volume
is processed/scanned by the Storage Service, which may take time, so we
handle volume state changed in a separate thread (so as to not block its
callers like vold).
Bug: 145194312
Test: builds
Test: atest AdoptableHostTest
Test: atest com.android.tests.fused.host.FuseDaemonHostTest
Change-Id: I1677fdd5672cea531e98cda76d967af13e5fac9e
By default we hide all insets while the DreamActivity is active.
The client app has access to the main window of the activity, so it
could override this.
Bug: 151749301
Test: m && flash && start the screensaver and verify that nav bar is
gone
Change-Id: Iecdc5f67c976de5477523e9745a9e8733703c11f
* Use the original authentication instead
* Also support sending intent from augmented autofill, with the
limitation of not supporting sending back the FillResponse or
Dataset from the activity result
Test: manual
Test: atest android.autofillservice.cts.inline
Test: atest android.autofillservice.cts.FillResponseTest
Test: atest android.autofillservice.cts.augmented
Test: atest android.autofillservice.cts.LoginActivityTest
Bug: 150499490
Change-Id: I81031ff456adb4c07f530188dda80e97cc84b707
