> > No, I was referring to the error message. While it *says* "Bad > notification for startForeground", it appears that this error might be > raised even if *nobody* called startForeground(). Hence, I am telling > you to not over-emphasize the "Bad notification for startForeground" > portion of the error, as it may be a red herring, fluke, or something > else fishy. >
I'm with you now. > > IMHO, the real question is: where is your contentIntent going? > Somehow, Android is winding up with a Notification object that has a > null contentIntent, and that appears to be unsupported, at least on > Android 1.x/2.x. In the cases where you are explicitly supplying a > contentIntent, it should no longer be null. Are you doing anything to > the Notification object after you call notify()? > > No, nothing... The notification says "I'm listening" and then is cancelled a few moments later 'on end of speech input' from the service. First time I got the error using null contentIntent, I thought, okay, I'll just add in the content to suppress the error, but my headaches started when it appears to make no difference either-way or regardless of the actual contentIntent supplied... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
