History log of /frameworks/base/core/java/android/service/notification/StatusBarNotification.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
a381d375f37fa8fb4c606a5ba9b3e105f6e1ef1c 26-Jul-2013 John Spurlock <jspurlock@google.com> StatusBarNotification cleanup.

Remove obsolete ctor and obsolete accessor comment.

Change-Id: Ib72abc8fbd2a5f9a1b82da986094667f39e0bf62
/frameworks/base/core/java/android/service/notification/StatusBarNotification.java
26510320646339fc59e01d392f96efeeac6d91dd 23-May-2013 Scott Main <smain@google.com> fix javadoc links.
turns out, without parameters, javadoc will link to the best matching
method signature, even if it's from the superclass. So these were pointing
to Object.nofify()

Change-Id: I13688f2b65e898d1f000a34c88d0aaed928884b5
/frameworks/base/core/java/android/service/notification/StatusBarNotification.java
4f91efdf421e354ee2033ed640e4150cf0cef21b 25-Apr-2013 Daniel Sandler <dsandler@android.com> API: getPkg() -> getPackageName()

Bug: 8656860
Change-Id: If3062b9fc00270e5f0ecfe67e593b9a28c6bccdd
/frameworks/base/core/java/android/service/notification/StatusBarNotification.java
e6f7f2e3a01b8deb00e03ccfa93751c315f14ef0 25-Apr-2013 Daniel Sandler <dsandler@android.com> API cleanup: NotificationListener

- Wrap all public member variables in getters and make
slots private
- Rename clear* methods to cancel* to be more consistent
with existing public Notification API

Bug: 8656860
Change-Id: I84f7e71fbb627f859352a93089c6a531b44dac95
/frameworks/base/core/java/android/service/notification/StatusBarNotification.java
1a497d3a2b1496c12949e47e55f8e46d8f585be5 18-Apr-2013 Daniel Sandler <dsandler@android.com> Fix concurrency issues when parceling StatusBarNotifications.

Protip: Don't mess with Bundles after you've sent them off
for parceling in an RPC.

Note that this change reduces the payload size of
StatusBarNotification objects received in
onNotificationRemoved() callbacks; it scrubs out the
RemoteViews and Bitmaps just as the NoMan's internal archive
does. [You don't really need that information anyway when
hearing about a removed notification; most likely all you
need are the other slots on StatusBarNotification, but
nulling the whole Notification object breaks a lot of
clients.]

Bug: 8616295
Change-Id: Ic899045f2352b96dcf064d3e9e51dad52629aea3
/frameworks/base/core/java/android/service/notification/StatusBarNotification.java
5feceebb892d4cb5777cea3c6174b206705d456b 23-Mar-2013 Daniel Sandler <dsandler@android.com> New NotificationListenerService.

This is the best and only way for apps to listen for
notifications: create a NotificationListenerService, wait
for the NoMan to bind to you (as a result of the user
checking a box somewhere in Settings and agreeing to a
scary dialog box), and you'll start receiving notification
posted and dismissed callbacks. Your service, while enabled,
will also be able to clear one or all notifications.

Use this power wisely.

This change moves StatusBarNotification out of
com.android.internal into android.service.notification.
[Internal customers, including System UI and early users of
the system-only listener binder API, will need to be
updated.]

Bug: 8199624
Change-Id: I1be46f823d4b3ddc901109ec1e085cd6deb740c2
/frameworks/base/core/java/android/service/notification/StatusBarNotification.java