am: c2ec322
* commit 'c2ec3226ea018e415c57871727c34d44abd80ca4':
Camera2: update API per API council review
Change-Id: I4ad3be32bee216a92731b07901a661c1ce0463b3
am: 1476f35
* commit '1476f3573be229ae00c3a13afb324648305a8bf8':
Allow mode of TileService to be changed
Change-Id: I8a6b58f4dd2d8bd135e4cadfdc63198720d6e7a8
Per API concil recommendation, made below API change:
* change method name from createCaptureSessionByOutputConfiguration to
createCaptureSessionByOutputConfigurations
* Change method name from
createReprocessableCaptureSessionWithConfigurations to
createReprocessableCaptureSessionByConfigurations
Bug: 27950067
Change-Id: I8346d384210556a40bc2544c3660cc4819f304a1
Currently, we can only wholesale disable effects outside of zen mode.
There are some devices that require long running suppression of features.
Effects disabling was added previously to support this. However, calling
suppression was broken recently on a device where we needed notification
suppression, but not calling suppression.
This CL remedies this problem by adding more granular disabled effects
hints. The NotificationManagerService has been updated to handle these
request types and present ZenModeHelper with a unified map of what should
be suppressed.
Bug: 27992763
Change-Id: I38b4706446dfd6e1c3eb97266dbc3332b250adda
Since the mode of a tile service was set in onTileAdded, it couldn't
be controlled by developers if they updated their tile. To handle
the mode has been moved to a boolean meta-data flag to indicate
a tile should be an active tile.
Bug: 28043969
Change-Id: I6403d34f8cb70809edc07769389d5a1f835c1ab3
Let apps invoking the system chooser specify components to filter out
such as themselves; this will prevent duplicate nonsensical UX where
it doesn't make sense for an app to share to itself.
Similarly, let apps provide their own Direct Share targets for when
they do want to let users share via their own internal services in the
same UI. These options can be used together.
Also fix a bug where a lingering binder reference from a remote
ChooserTargetService that hasn't been GC'd in the remote process could
keep an active reference to a ChooserActivity instance.
Bug 28073484
Change-Id: Ib613b1153b49dfedf79574b1af7c45379eceec24
am: ee03cdf
* commit 'ee03cdf9a71c67edd56f3dfef3c4258aa36800dc':
Hide unnecessary extra name constants in ClipDescription
Change-Id: I425e34fa44893b1e745e387a8393df52bd275136
This change adds support for the new MessagingStyle, which
supports a fully back-and-forth messaging/chat experience
within the notification display itself.
Bug:28043958
Change-Id: Ibb9c2a0784f028d8cf01bd3cee4fecc5f72d68cd
Also block all callbacks if the listener is not connected.
Also update the documentation to make lifecycle restictions
more clear.
Bug: 27582839
Change-Id: I029304e1fb87bd8d754cfb4641ba8cc095fc2b2e
am: 9f1e6de
* commit '9f1e6de054f836e3b35bb96998c1400435cd5d7a':
Adds a content-intent-launching-activity flag to WearableExtender
Change-Id: If09863a35440db6b0fc10c021226c9b61b52283f
am: 106d380
* commit '106d380ae98c80fe25130be1286479258515503e':
Deprecate methods not supported by Material-style date picker
Change-Id: I1973884a036352f02269e0ecd366cee0edc5e2b0
This adds a flag to WearableExtender (and Action.WearableExtender)
indicating that the attached ContentIntent will launch an activity
on Wear, which lets the platform know that it can (and should)
generate a sleek transition for the launching of said intent (as
opposed to the intent causing change in the background).
Bug:28019194
Change-Id: Id8b422ea52c5e941e38558aaf31ce2cf4bb7c6f3
am: ac51be5
* commit 'ac51be5b1cd048397ed9e4e0e7d6bac5b3610394':
Deprecated the contentinfo and the number
Change-Id: I6acb57542bba80a9d4e8fadfbd480c3b3102ff3b
am: cfb4721
* commit 'cfb472112dfac835950b4c53fdf921c569388114':
More work on issue #26390151: Add new JobScheduler API...
Change-Id: Idd203c9daba08a3498c8184028554d5136101085
