| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: I7efc245395bd91a656b30d420c9b080877162360
|
|
Change-Id: Ie73d665085d5ce7358c285bf332ef1dc96005d0f
|
|
Change-Id: Icfec2a830f037b21f6afaa796bf49da610567e7b
|
|
Change-Id: I2f568df92f88dfe8de18d24dd004239f52761aa6
|
|
The lock is now only held long enough to swap the queue with a new ArrayList.
Bug: 2542233
Change-Id: I8c1c3d4d0b5b53166cc239fc0069d69929b43f91
|
|
Change-Id: I86ff1b78fc309b758c6457be867509b71042d42e
|
|
A ServerThread holding a lock on mQueue in StatusBarService invoked a
callback in NotificationManagerService which required a lock on
mNotificationList. At the same time, a BinderThread holding a lock on
mNotificationList was attempting to post a message to StatusBarService
which requires lock on mQueue. The fix is to release the lock on mQueue
in handleMessage() before running the actions at the end of the method.
|
|
Change-Id: I3fc69b5a8b600e23fccc88e9d80eb3495fad16d4
|
|
|
|
Bug: 2432590
|
|
pulling down the
windowshade.
This makes it happen less often when you pick up the device or push open the keyboard.
|
|
The animation was removed to fix 2298803 because if the windowshade
was tracking when this happened, it would get stuck.
|
|
Add checks for fwdlocked and updated system apps
add more tests
remove duplicate adds
|
|
The new flag, DISABLE_NOTIFICATION_TICKER, will be used by
the car dock app (in conjunction with DISABLE_EXPAND) to
minimize distractions to the driver.
It may also be used by the secure lockscreen to avoid
leaking personal information when the screen is on but the
device is locked (e.g. when the desk dock app is running).
Change-Id: Ibc8efde7da7501767163ae0a75f7c369b824e2a2
|
|
The steps to reproduce this were kind of interesting. You needed to have
a notification with a bogus RemoteViews in the first position in the list,
and then have another notification come in with an earlier timestampe. In
that case, it would get a bad index for the new (not bogus) view that was
being added.
|
|
Add new broadcasts ACTION_MEDIA_RESOURCES_AVAILABLE and
ACTION_MEDIA_RESOURCES_UNAVAILABLE that get broadcast by
PackageManagerService when sdcard gets mounted/unmounted
by MountService so that packages on sdcard get recognized by
various system services as being installed/available or
removed/unavailable by the system.
The broadcasts are sent before the actual package cleanup which includes
mounting/unmounting the packages and we force a gc right after so
that any lingering file references to resources on sdcard get
released.
|
|
|
|
Bug: #2361749.
|
|
This provides a quick fix for http://b/2298803 (if the
in-call UI comes up while the user is holding the
windowshade, the shade sticks in place and the display
becomes unresponsive).
(NB: The shade disappears immediately when the status bar is
disabled. It might be better for the shade to animate
closed; indeed, this seems to be what the code was trying to
do, but an unfortunate interaction of the animation and
touch-handling code is what caused this bug in the first
place.)
Change-Id: I92a824fe385c8d6e51993be1657b492e580f1e7b
|
|
|
|
|
|
Fix the flags for the StatusBarExpanded window that were causing the Window Manager to
think that it needed input.
|
|
This reverts commit 6e8f47b0ed2ffdb55b695d9f154cccd3ea3c98de.
|
|
This reverts commit b96a9d9296925fef6a1c0e5ad4d847d96bf9acb5.
|
|
As per Dr. No; revert commit 6a7899a8d6444989657d1058666269263b5b50c0.
|
|
As per Dr. No; revert commit 0d7dc3b800d0489c43ad9071615b2b4ebec80443.
|
|
Follow up to bug 2195678. This was one of the reprocussions that
I was worried about with respect to that bug, so I'm counting
Dr. No on that change as the one for this one.
|
|
Bug 2195678
We had all this stuff there to keep the notification view
around so it doesn't need to be reconstructed each time,
and we weren't using it. This fixes that, and it looks
much better now.
|
|
shade jump up and down
This thing needs to be rewritten. It's grown too complicated for what it's doing,
and I don't like the physics anyway.
Also, this leaves the bug where if you press back while it's animating down, the
animation is ignored. However it no longer jumps down all the way, it just
essentially ignores the back key.
Also, this makes the collapse get executed on the back key up event, so it works
with the swipe on the soft keys at the bottom of the screen.
|
|
Dr.No from mcleron.
Change-Id: Iaca2268684f83fe8757e64db0b0e047a19755311
|
|
to scope them
|
|
|
|
|
|
unlink DeathRecipients in a whole bunch of places to avoid memory leaks
|
|
Now we have a 5-second time after home is pressed, during which
only the home app (and the status bar) can switch to another app.
After that time, any start activity requests that occurred will
be executed, to allow things like alarms to be displayed. Also
if during that time the user launches another app, the pending
starts will be executed without resuming their activities and
the one they started placed at the top and executed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
