Databases
StackOverflow2013
Postsdbo
POAndroid - Bad notification posted only on Android 2.3
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid - Bad notification posted only on Android 2.3
    primarykey
    data
    text
    <p>I'm receiving reports about crash in Android 2.3 when displaying notification. The stacktrace I have is:</p> <pre><code>android.app.RemoteServiceException: Bad notification posted from package com.megadevs.hubi: Couldn't expand RemoteViews for: StatusBarNotification(package=com.megadevs.hubi id=1 tag=null notification=Notification(vibrate=null,sound=null,defaults=0x0,flags=0x62)) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1048) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:130) at android.app.ActivityThread.main(ActivityThread.java:3687) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:507) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600) at dalvik.system.NativeStart.main(Native Method) </code></pre> <p>I've read that Android 2.3 have some issue with AnimatedImageView, but I don't think I'm using it... The code I run for displaying the notification is:</p> <pre class="lang-java prettyprint-override"><code>NotificationCompat2.Builder builder = new NotificationCompat2.Builder(getApplicationContext()); notification = builder.setOngoing(true) .setAutoCancel(false) .setPriority(NotificationCompat2.PRIORITY_DEFAULT) .setSmallIcon(notificationSmallIcon) .setWhen(System.currentTimeMillis()) .setContentIntent(notificationIntent) .setContentTitle(downloads.elements().nextElement().getFileName()) .setProgress(100, (int) downloadable.getDownload().getProgress(), false) .build(); startForeground(DL_NOTIFICATION, notification); </code></pre> <p><strong>UPDATE:</strong><br> I've discovered that the problem appears when I try to updated that notification started with startForeground(), the code I run is:</p> <pre class="lang-java prettyprint-override"><code>notification.contentView.setProgressBar(android.R.id.progress, 100, (int) download.getProgress(), false); mNotificationManager.notify(DL_NOTIFICATION, notification); </code></pre> <p>But it works correctly on ICS and JB, so why is it giving problems on Ginger?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdmarcato
    1. USdmarcato
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid - Bad notification posted only on Android 2.3
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAndroid - Bad notification posted only on Android 2.3
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid - Bad notification posted only on Android 2.3
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODid you ever find a solution for this? I'm running into the same thing :|
      singulars
      1. POAndroid - Bad notification posted only on Android 2.3
      1. USYuvi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload