On Jul 9, 7:16 pm, Mark Murphy wrote:
> Well, they should be able to use it if they keep your activity in the
> foreground, right? What they can't do is multitask or launch your
> player from an app widget.
You're right, and we'll be notifying them of that (lots of fun
compacting that message int
On Fri, Jul 9, 2010 at 7:54 PM, Peter Jeffe wrote:
> As a result, our
> thousands of users on the Incredible won't be able to use our
> equalizer function.
Well, they should be able to use it if they keep your activity in the
foreground, right? What they can't do is multitask or launch your
playe
http://code.google.com/p/android/issues/detail?id=9663 that is.
--
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-d
Submitted as http://code.google.com/p/android/issues/detail?id=9663:
On the Incredible (and possibly other devices) the process is always
put in the background scheduling group when it doesn't have a visible
activity, even though the app's service has called startForeground().
This causes it to ge
On May 27, 3:05 pm, Nathan wrote:
> I could see that there could be a family of bugs in services on the
> Incredible. I'm hoping to meet with someone local who has one.
Yes, any service that expects to have foreground priority because it's
called startForeground() will be sorely disappointed on t
I don't know anything about this, but I do have beta testers reporting
a phone reset on the Incredible if my downloadservice runs for much
longer than ten minutes. I had thought that maybe startforeGround was
too intense and tying up the CPU, but based on this information the
opposite may be true.
6 matches
Mail list logo
