| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
If they were null, then the Parcelable would fail to work.
Bug: 126726802
Test: manual
Change-Id: I7929ffa2f20e5de1c8e68e8263cca99496e9d014
Exempt-From-Owner-Approval: Trivial API annotations
|
| |\
| |
| |
| |
| |
| | |
am: b2ad787a44
Change-Id: I6064f1fdeb3e55ccca760de6c3bb42c1a4621298
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Several @link javadoc directives were malformed, resulting in the
Javadoc code being output to the HTML.
Staged to:
http://go/dac-stage/reference/android/app/Activity
http://go/dac-stage/reference/android/app/RemoteInput
http://go/dac-stage/android/os/UserManager
Bug: 120743732
Test: make ds-docs
Change-Id: I2c00c7e1e3adcff696e6d000206aeeaea61e7ecd
Exempt-From-Owner-Approval: Doc-only change
|
| |/
|
|
|
|
|
|
|
|
| |
Allow apps to specify whether users should be able to edit smart replies
before sending them.
Bug: 111438374
Test: atest RemoteInputTest
Test: mp /vendor/google_experimental/users/cinek/Notify, post a notification with "Edit choices before send"
Change-Id: I9a37216916f05152d8ab7061ffa121948de0976a
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The behavior that #setChoices didn't render on mobile devices from apps
that target SDK < P went undocumented. Because this is changing in P and
above, this documentation needs to point out this behavior.
Also updated formatting and style of docs to improve interop with
kotlin.
Test: none
Bug: 79244189
Change-Id: Iabfe3b2ddcc369e5ec15f9773481468cbc48dabb
|
| |
|
|
|
|
|
|
|
|
| |
This patch addresses a request from the API Council (http://b/74409378).
It defines a new RemoteInput.Source annotation for RemoteInput source
constants.
Bug: 74409378
Test: atest RemoteInputTest
Change-Id: I78a006b6a600ea0c0603b2591d1a29596074a44e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL adds the following methods to RemoteInput:
* setResultsSource(Intent intent, int source)
* getResultsSource(Intent intent)
where source can be one of:
* RemoteInput.SOURCE_FREE_FORM_INPUT
* RemoteInput.SOURCE_CHOICE
Rationale: This will allow apps to distinguish direct and smart replies
for logging purposes.
Bug: 67765414
Test: atest RemoteInputTest (http://ag/3469835)
Change-Id: Ie30416640df4b2cd0424f9c75b235fc124be87a3
|
| |
|
|
|
|
|
| |
Test: make ds-docs
Bug: 64613641
Change-Id: Ie3e451a15ad1fcde63c0301aaa328793af114780
|
| |
|
|
|
|
|
|
| |
Bug: 37706825
Test: Documentation-only change
Change-Id: I5987868916010f1143e2d8227ea3ea7952c87bc7
(cherry picked from commit 4bff5a1f5a20afcfb5e8add044c050dcb1d74435)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add extras keys and methos to Notification and RemoteInput for notifications
whose contents have an audio representation and whose RemoteInputs
can accept data results (useful for, e.g., voice messaging
applications, photo results, etc).
This motivator for this change is it enables an end-to-end flow for
audio messaging including
* System receives the audio message
* Replying to the message with the user's voice
* App receives the audio reply data
Note that this CL just adds the capabilities, but does not
add any UI or implementation to perform the above flow.
Test: As agreed, this will be tested both with a set of unit tests,
and with an "end-to-end" test that simulates two apps, one
creating an audio message with audio reply action, and a
second app that executes that action, providing an audio
result.
Change-Id: I55779ac4b781d8273c13c69fded0b56ee639cf01
|
| |
|
|
|
|
|
|
|
|
|
|
| |
1. Move Extender outside of Builder
2. Rename apply/applyTo to extend
3. Move Wearable extenders into Notification.java
4. Collapse Builder model into single classes
5. Use Bundle for storage: no new parcelable types.
Minor fix to RemoteInput to use flags int for boolean options.
Change-Id: I40012fd0458ec103eabf75ed4c91f636e02f4c8f
|
| |
|
|
| |
Change-Id: I6a6f3df06d924fe72f67466d67d9feced8d8719f
|
|
|
RemoteInputs annotate actions and content intents to request
input from the user as part of an intent being sent. Results
are sent along using ClipData to avoid unparcel of developer
provided bundle values. A helper method is expexted to be used
to extract results.
Grouping allows notifications to be bundled together, with an optional
summary notification for display on older platforms. SortKey is an
important part of grouping since child notifications will likely have
a prescribed ordering. It is also useful in top level notifications
for apps that want to provide an ordering all other fields being equal.
Also provide a fluid way to to extend Actions and Notifications
using Extenders, e.g.:
Notification n = new NotificationCompat.Builder(context)
.setOption1()
.apply(new SomeExtender()
.setOption2())
.build();
This helps extension libraries provide a nice API experience for devs.
Change-Id: Ib3438ef854772c2c34d21bf1eb4ed7c9e032106f
|