> > > Is it possible that you are canceling it before it actually gets > displayed? IOW, how short might "a few moments" be? > > I'm just brainstorming possible things that you are doing differently > than the norm. >
The notification is there for at least as long as I set the 'pause before assume speech has ended' parameter to. The endOfSpeech can't be called until after that event (where the notification is cancelled), so we can rule that one out. I'll push out the NotificationCompat.Builder update later, but even if (hopefully) it solves the issue, perhaps I should still do the honourable thing and raise it as a possible bug? Or in your experience, are depreciated method bugs pushed to the bottom of a very large pile and therefore pointless...? I appreciate your help. -- 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
