| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This happens when users archive or delete email from the watch. Currently the
conversation notification is cancelled in
NotificationUtils.validateNotifications()[line 775] by comparing current ids
with previous ids stored in memory. If the gmail app is restarted, previous
ids will be cleared and some conversation notifications may not be properly
cancelled.
The solution is to add the notification id to the notification action.
NotificationActionIntentService will use the id to cancel the notification if
it is a remote action.
Bug 16371569
Bug 16376756
Bug 16020553
Change-Id: If70e075e258823906fc062b89ce9b023b419680d
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Skip undo on phone when the action is perform remotely
* mark conversation as read after reply.
Created separate pending intent for Wear actions. NotifActionIntentService
skips the Undo for remote actions. ComposeActivity adds a converstion uri
to start a service to resend notification.
Bug 15332337
Bug 15332837
Bug 15532541
Change-Id: I9fb51ec6ac393075b08f770bbc3b3490aab622e3
|
| |
|
|
|
|
|
|
|
|
|
| |
Also fix a long-standing issue that caused notification intents to never
get updated during development (we weren't setting FLAG_UPDATE_CURRENT).
We can remove the version tag from the intent data URI later.
Log reply/reply-all setting.
Bug: 9861033
Change-Id: I49b2ab529de4167d1c8b42a8b053bcc2b9f65a23
|
| |
|
|
|
| |
Bug: 10161543
Change-Id: Ic0fc9e6881c951f69cce4e04edd55f7a82db017f
|
| |
|
|
|
|
|
|
|
|
|
|
| |
AlarmManager unparcels everything in the Bundle, which causes a
ClassNotFoundException.
So we'll take some code from Clock, and shove a NotificationAction
into a byte array, and parcel that. Other processes can unparcel this
without causing any problems.
Bug: 9051575
Change-Id: Ie8fbf1f8b4e8a1523f02c2d84fe50a780a4d90c7
|
| |
|
|
|
|
|
|
|
|
| |
Fixes b/7923968. Instead of resending all notifications
when the undo bar disappears, we only resend notifications
for the account-folder pair that had the undone notification.
This means that when the undo notification disappears,
no additional notifications will go out.
Change-Id: I55155e9abfbe34cc7c0fc4f0e6448a70e921413b
|
| |
|
|
|
|
|
|
|
| |
Multi-project change with:
If514cfed9538f0c2433a9427f15608ba5878ee05 (Email)
I407b8900220e7dbdda81d6572f0ee374ae3d3833 (UnifiedGmail)
Bug: 8483722
Change-Id: I86b368de45533faa3f639f631d56e16f5cbca36e
|
| |
|
|
|
|
|
|
|
|
|
| |
If no real lock is set, selecting a notification action should launch
the ComposeActivity in front of the lock screen.
Rather than going through a Service, we now launch ComposeActivity
directly, and clear the notification from there.
Bug: 7957838
Change-Id: I6344c93656106b2875bafac5bec18236d5c1d996
|
| |
|
|
|
| |
Bug: 7901223
Change-Id: Iebc2010ae0f489fd6955c88a1d32df94baa9ce68
|
| |
|
|
|
|
|
|
|
|
| |
Clear the notifications when the user selects the reply/reply-all/
forward action.
Also fixes a bug with those actions not always doing the right thing.
Bug: 7742529
Change-Id: I479eef30864fe1fcae3e9c7aafaa21481e51d05c
|
| |
|
|
|
| |
Bug: 7742911
Change-Id: Ifd1a45331280a2e9c4dc0f200818ad71d60f02a0
|
| |
|
|
| |
Change-Id: I105ec247bbf30413077136cf6868079c3e4a70ef
|
|
|
Change-Id: Ib4507c880334b2b7c3b8549d7f30a7260e09b4a1
|