68065e0a19
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.
29 lines
828 B
Java
29 lines
828 B
Java
package com.android.server.status;
|
|
|
|
import android.app.PendingIntent;
|
|
import android.widget.RemoteViews;
|
|
|
|
public class NotificationData {
|
|
public String pkg;
|
|
public String tag;
|
|
public int id;
|
|
public CharSequence tickerText;
|
|
|
|
public long when;
|
|
public boolean ongoingEvent;
|
|
public boolean clearable;
|
|
|
|
public RemoteViews contentView;
|
|
public PendingIntent contentIntent;
|
|
|
|
public PendingIntent deleteIntent;
|
|
|
|
public String toString() {
|
|
return "NotificationData(package=" + pkg + " id=" + id + " tickerText=" + tickerText
|
|
+ " ongoingEvent=" + ongoingEvent + " contentIntent=" + contentIntent
|
|
+ " deleteIntent=" + deleteIntent
|
|
+ " clearable=" + clearable
|
|
+ " contentView=" + contentView + " when=" + when + ")";
|
|
}
|
|
}
|