My application has an inbuilt IME which the user has set to their default.
In certain situations within my app (I won't bore you with which), I need
to automatically switch to an alternative keyboard, but just for that one
view - as soon as the user clicks on another view (or exits the
.
On Thursday, 14 February 2013 08:44:54 UTC-5, brandall wrote:
My application has an inbuilt IME which the user has set to their
default. In certain situations within my app (I won't bore you with which),
I need to automatically switch to an alternative keyboard, but just for
that one view - as soon
This question is a long shot, as it's a peculiar problem
I have a foreground service which controls my application's text to speech
and recognition functionality. My implementation works correctly for
thousands of users, but a handful a Galaxy SIII users are reporting a
problem whereby
It seems there is no answer here or on Stackoverflow for this behaviour, so
I have to assume it's a notification from a service bug for a small number
of Android devices. Where do I report this as a bug?
On Saturday, June 30, 2012 9:19:18 PM UTC+1, brandall wrote:
The full error also
There should be an error message appearing to the right of the Bad
notification for startForeground: portion of your message, based upon
the source code that I am reading. Are you sure there is nothing
there? Posting the entire stack trace is considered a fairly
conventional step when
java.lang.IllegalArgumentException: contentIntent required:
pkg=com.brandall.nutter id=1079820303
notification=Notification(vibrate=null,sound=null,defaults=0x0,flags=0x60)
There's nothing else relevant in the output.
Is that in your null Intent case? The message makes more
Actually, I think that part of the message may be a fluke. There
appear to be two cases which call the postNotification() where that
exception is raised, and only one of those is for a startForeground()
scenario, if I am reading the source properly.
To clarify, I don't call
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
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
Well, I don't see any deprecated methods in what you are doing.
However, bugs that cannot be reproduced tend to be problematic in all
software development.
I'd assumed that the posted method had been depreciated in favour of
NotificationBuilder. I see that it hasn't though.
I'll get
10 matches
Mail list logo
