Yes Dianne. Really thanks for your help. I have found the root cause. One of our third-party lib have used the AnimatedImageView. It works fine on 2.2 but break on 2.3. That's why we cannot find any clue from our own source code, because the third-party lib is a JAR file.
The problem is solved. Thanks you very much. On Mon, Apr 18, 2011 at 10:24 AM, Dianne Hackborn <hack...@android.com>wrote: > Well I can tell you what the problem is with the linked error: > > E/StatusBarService( 1325): couldn't inflate view for notification > com.lectek.android.ecp/0x0 > E/StatusBarService( 1325): android.view.InflateException: Binary XML file > line #8: Error inflating class com.android.server.status.AnimatedImageView > E/StatusBarService( 1325): at > android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:581) > E/StatusBarService( 1325): at > android.view.LayoutInflater.rInflate(LayoutInflater.java:623) > E/StatusBarService( 1325): at > android.view.LayoutInflater.inflate(LayoutInflater.java:408) > E/StatusBarService( 1325): at > android.view.LayoutInflater.inflate(LayoutInflater.java:320) > E/StatusBarService( 1325): at > android.widget.RemoteViews.apply(RemoteViews.java:939) > E/StatusBarService( 1325): at > com.android.systemui.statusbar.StatusBarService.makeNotificationView(StatusBarService.java:554) > E/StatusBarService( 1325): at > com.android.systemui.statusbar.StatusBarService.addNotificationViews(StatusBarService.java:585) > E/StatusBarService( 1325): at > > That application is trying to use a private implementation of the platform > -- com.android.server.status.AnimatedImageView -- that does not exist in > 2.3. > > On Sun, Apr 17, 2011 at 6:39 PM, A.TNG <tang.j...@gmail.com> wrote: > >> Hi Dianne, >> >> I've tried on 2.3.3 emulator, still cannot reproduce this issue. >> Meanwhile, I search the internet and find another app have same issue and >> that guy provide more detail log about the crash. >> >> http://www.miui.com/thread-78164-1-1.html >> >> On Mon, Apr 18, 2011 at 12:11 AM, Dianne Hackborn <hack...@android.com>wrote: >> >>> Okay, thanks for the explanation. >>> >>> I believe this error only comes from calling Service.startForeground() >>> with a bad notification. Look for wherever you use that method and make >>> sure the notifications you build are always correct. >>> >>> Have you tried running on the 2.3.3 emulator? >>> >>> >>> On Sun, Apr 17, 2011 at 3:41 AM, A.TNG <tang.j...@gmail.com> wrote: >>> >>>> Thanks Dianne for your kind reply. >>>> >>>> I'm really sorry for making some misunderstanding. "com.xxx.xxx" just a >>>> sample package name. It's not exist in the real world. But thanks for your >>>> "BTW", you're a nice person. >>>> >>>> The puzzle I cannot figure out is that in my application, I never send >>>> Notifications as the crash information described. I also check all related >>>> component in framework (which my application may use). It seems they also >>>> don't send notifications. So, that make me don't know how to fix it. >>>> >>>> On Sat, Apr 16, 2011 at 4:26 PM, Dianne Hackborn >>>> <hack...@android.com>wrote: >>>> >>>>> As it says, you are trying to post a notification that is invalid. >>>>> This particular error happens when the notification you give to >>>>> Service.startForeground() is invalid. >>>>> >>>>> (Btw, I really really hope you aren't using "com.xxx.xxx" as your app >>>>> package name.) >>>>> >>>>> On Sat, Apr 16, 2011 at 12:37 AM, A.TNG <tang.j...@gmail.com> wrote: >>>>> >>>>>> Hi Guys, >>>>>> >>>>>> I developed a application and put it on Android Market. This >>>>>> application support Android API from level 7 to level 10. It works >>>>>> prefectly >>>>>> on Android 2.1 and 2.2. Recently, it seems many user start to use Android >>>>>> 2.3.3. I start to get a strange crash as following: >>>>>> >>>>>> android.app.RemoteServiceException: Bad notification posted from >>>>>> package com.xxx.xxx: Couldn't expand RemoteViews for: >>>>>> StatusBarNotification(package=com.xxx.xxx id=0 tag=null >>>>>> notification=Notification(vibrate=null,sound=null,defaults=0x0,flags=0x2)) >>>>>> at >>>>>> android.app.ActivityThread$H.handleMessage(ActivityThread.java:1044) >>>>>> at android.os.Handler.dispatchMessage(Handler.java:99) >>>>>> at android.os.Looper.loop(Looper.java:123) >>>>>> at android.app.ActivityThread.main(ActivityThread.java:3691) >>>>>> 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:841) >>>>>> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599) >>>>>> at dalvik.system.NativeStart.main(Native Method) >>>>>> >>>>>> I cannot reproduct this crash on my HTC G7 with Android 2.3.3. Also, >>>>>> I've searched all my source code. I find nothing about send notification >>>>>> with flag ON_GOING (flags=0x2). This kind of crash information is full >>>>>> of my >>>>>> backend crash report system. I really worry about it. >>>>>> >>>>>> Have anyone met this problem? If you have any clue about it, please >>>>>> share with me. Thanks a lot. >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Jiyu >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Android Developers" group. >>>>>> To post to this group, send email to >>>>>> android-developers@googlegroups.com >>>>>> To unsubscribe from this group, send email to >>>>>> android-developers+unsubscr...@googlegroups.com >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/android-developers?hl=en >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Dianne Hackborn >>>>> Android framework engineer >>>>> hack...@android.com >>>>> >>>>> Note: please don't send private questions to me, as I don't have time >>>>> to provide private support, and so won't reply to such e-mails. All such >>>>> questions should be posted on public forums, where I and others can see >>>>> and >>>>> answer them. >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> Jiyu >>>> >>> >>> >>> >>> -- >>> Dianne Hackborn >>> Android framework engineer >>> hack...@android.com >>> >>> Note: please don't send private questions to me, as I don't have time to >>> provide private support, and so won't reply to such e-mails. All such >>> questions should be posted on public forums, where I and others can see and >>> answer them. >>> >>> >> >> >> -- >> Regards, >> Jiyu >> > > > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > -- Regards, Jiyu -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
