I think the problem is some kind of Context mismatch because the resource was in the framework but
referencing an app class.
Change-Id: Ia6b37c9c8be5dddc836331859e779cd80dd32596
Line-item veto is there, but allows you to cancel some
notifications you probably shouldn't be canceling. (Should
hide the "X" in those cases.)
No preference given to "sticky" notifications, because
there's no such thing yet.
Notifications are now limited to 4 visible icons, per spec.
The implementation is a total hack for now.
Change-Id: Ibdf433ae94189117f983c510fe5e0cff0bf5c44c
When a FLAG_HIGH_PRIORITY notification is posted and the
foreground activity is immersive, this window will be shown
to the user. It disappears after a while (currently 10s,
which is far too long to be usable but is very handy for
testing) and can be dismissed by a tap.
Artwork is extremely rough; please ignore the aesthetics.
Still TODO:
- sticky alerts for ongoing priority notifications
- tap to launch PendingIntent associated with the
notification
Change-Id: Ief4a98b84cc836d33359bd7d65de9909f5186317
Then, now that StatusBarManagerService is the only thing in that package,
move it up to the regular services package. (I've been waiting for 4 years
to delete that package!)
Change-Id: If5faf44641319fd19e486d1f4e5bc1c6dfcff3ad
Artwork is FPO but serviceable enough. Many hardcoded font
colors & styles were moved to styles.xml where they belong.
AM/PM finally given the old heave-ho (but configurable in
StatusBarPolicy.java).
Notification content remains on a light-gray background for
now (so as not to screw up custom RemoteViews) but status
icons will definitely need across-the-board rework to look
better against a dark background.
(Re-integrated on top of new status bar code.)
Change-Id: Ia180b3c2ba8e23c9a2f50cf46f98f12958022b53
