| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Bug: 205725937
Test: manual
Change-Id: Iaa4fab4d59b1d08ba1d776f8122e296de3c446c4
|
| |
|
|
|
|
| |
Bug: 205725937
Test: manual
Change-Id: I045a8b4b21cae0f4a6e61502384e2b1a607bc1c6
|
| |
|
|
|
|
| |
Bug: 178189250
Test: manual (using POC in bug)
Change-Id: I787915c0493d18500e7531bd0ca7191532441f93
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We've been working hard to require PendingIntents explicitly declare
if they allow their contents to be mutated or not, and to finish
landing that work this change applies the new FLAG_MUTABLE_UNAUDITED
flag to all remaining code locations until they can be manually
inspected.
Bug: 160794467
Test: manual
Change-Id: I8d7ec64ac89755c14b5959bb6ef0bce203c92bf0
|
| |
|
|
|
|
|
| |
ScreenshotNotificationsController is largely unused now and
only exists to notify of errors. Removing unused code.
Change-Id: I638eb7c3e70cd9155661bf89434af7aabdf66a10
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pull apart into View vs Controller model, to separate views/
animations from state handling.
This is a large change, but not as large as it looks since
most sections are copied from GlobalScreenshot into either
ScreenshotView or ScreenshotController.
Roughly speaking, ScreenshotController handles the overall
screenshot initiation, flow, and callbacks, while
ScreenshotView handles the subviews and constructs the
animations.
Test: manual
Change-Id: Ic3238571ac2d7aa749eff078c2297f2b6ed06b78
|
| |
|
|
|
|
| |
Bug: 156020795
Test: manual, atest
Change-Id: I72206c7a52b067b77d6542d170a6483713dfeee7
|
| |\
| |
| |
| |
| |
| |
| |
| | |
rvc-dev am: 3a9ce8d11a am: 6025e31c64 am: 29f33b805b am: 9519294d6b
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/11851515
Change-Id: Id4076aad4fe8dc357c6eb39a4eccf223e17a66d4
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit c0841cf1020bd03ea5fd97daf4a3092e6d90f028.
Reason for revert: We no longer want to post a notification, due
to concerns about UI consistency.
Bug: 158854375
Fix: 158854375
Test: manual
Change-Id: Icb01a9afe7118580082c31f993265e243c9a5db7
|
| |\|
| |
| |
| |
| |
| |
| |
| | |
1e9db44dc9 am: 288382cc2a am: eed5594ed2 am: 6288e6e297
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/11826322
Change-Id: I88b5248263e80704b1a6939fad4aff4248de0c56
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 158673382
Fix: 158673382
Test: manual -- this has no visible changes since the old code was
flag-guarded behind "false", but built and ran through the screenshots
flow.
Change-Id: If09c16e8de1333137600f2192929af934ca5fd23
|
| |\|
| |
| |
| |
| |
| |
| |
| | |
am: 18bb8d11a6 am: 46cf5499f1 am: e0a089c8a1 am: be34cde3d1
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/11809243
Change-Id: I1274983a9fb05514823917d15c282018294c0a00
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replicates the old behavior of being able to use the notifications
shade as a "to-do" area for screenshots. If the screenshot is
dismissed explicitly or by timeout (i.e., not by tapping the share
or edit buttons), we post a silent notification.
Bug: 156343422
Fix: 156343422
Test: manual
Change-Id: Ie2c1db4212e7332c5fba2e93c3d1d4d5e0c99a25
|
| |\|
| |
| |
| |
| |
| | |
e0efd49ef3" into rvc-d1-dev-plus-aosp am: a1adfd1dfc am: ac6e16bcc9
Change-Id: Ie4d8f1e8a6e808f7f23aac38c0c1e29b20c572ea
|
| | |
| |
| |
| |
| |
| | |
Bug: 150710005
Test: manual
Change-Id: I54a37eb0a62234c6c53fc0f3c80e18e9ee269f12
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug: 150395371
Test: I442cd0c7a849e4c6a2fe7ba21b25a6e44417bbf5
The system needs to move off of @hidden Bitmap APIs so Bitmap can move
to a mainline module. It is valuable to provide a public way for clients
to create a Bitmap backed by ashmem, and the method's usage level is
HIGH. As I understand it, ashmem is being deprecated, so make the new
name more general: #asShared(). This method calls createAshmemBitmap(),
which must continue to exist for now due to the greylist. Add a
maxTargetSdk and publicAlternatives to move clients to the new method.
Mark asShared as @NonNull. It should only fail due to a failure to
allocate the shared memory. Throw a RunTimeException in this (rare)
case.
Add a (private) native method to check whether the Bitmap is already
backed by ashmem so it can skip the copy as necessary.
Remove outdated comments in both createAshmemBitmap methods regarding
SRGB. The new Bitmap will have the same ColorSpace as the original.
Remove the Config param from DisplayContent#screenshotLocked. It is only
ever called with ARGB_8888, which matches the ScreenshotGraphicBuffer
it is copied from. This means Bitmap#createAshmemBitmap(Config) does not
need a public version. It may need to continue to exist due to
@UnsupportedAppUsage.
Change-Id: I359187a5c70b5e241c7f5879d50fde2a7449c818
|
| |
|
|
|
|
|
|
| |
Bug: 147423001
Test: tested behavior both in old and new flows (no change to
notifications flow; visual changes to new flow)
Change-Id: If3a170c73609edb4f74db81b9109d83cc160b206
|
|
|
Pulls screenshot notification management into its own class rather
than having notifications handled in SaveImageInBackgroundTask.
(Most of) the notifications code is no longer relevant for the new
corner flow.
Bug: 137153302
Test: manual -- no user-visible changes; tested that flow remains
the same in both old and new versions
Change-Id: I9cdf900f867776d97a339ea65f21e893efc4645e
|