Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix 1667521 - system process crash after bad notification

Browse Source 
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.
This commit is contained in:
Joe Onorato
2010-02-03 20:21:41 -08:00
parent 378a1488bb
commit 68065e0a19
4 changed files with 65 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
services/java/com/android/server/status/NotificationData.java
View File

@@ -19,7 +19,7 @@ public class NotificationData {
public PendingIntent deleteIntent;
public String toString() {
return "NotificationData(package=" + pkg + " tickerText=" + tickerText
return "NotificationData(package=" + pkg + " id=" + id + " tickerText=" + tickerText
+ " ongoingEvent=" + ongoingEvent + " contentIntent=" + contentIntent
+ " deleteIntent=" + deleteIntent
+ " clearable=" + clearable