Would it be possible to have a mailing list for discovered Android bug?
I wish I knew this one sooner so I could avoid many user complaints in the
first place. And also spending hours digging into my code and trying the
reproduce user issues.
--
You received this message because you are
I am using service and onStartCommand returning
START_STICKYhttp://developer.android.com/reference/android/app/Service.html#START_STICKY.
I have also register some broadcast receiver in onStartCommand. It is
working fine in all mobiles. On Samsung mobile it stop working around after
30
To be fair, I obviously do not know for a fact that HTC devices
are intentionally ignoring the startForeground() method. Here are the bug
reports though so y'all decide...
http://code.google.com/p/android/issues/detail?id=9663
http://code.google.com/p/android/issues/detail?id=9682
As for the
I have an app that uses the notification bar in a similar way but I provided
a setting in preferences that they can use to turn off the notification.
On Wed, Mar 2, 2011 at 11:48 AM, rich friedel rich.frie...@gmail.comwrote:
To be fair, I obviously do not know for a fact that HTC devices
are
Jake,
Regarding onStartCommand isn't called after restart.
This is more like a terminology problem: when Android restarts the
service it actually recreates i.e. calls onCreate() method only.
onStartCommand() is not called because nobody requested this service
directly (e.g. no other process
My issue was that according to the documentation, onStartCommand would be
called, but with a null intent. Dianne confirmed it was an error in 2.3/3.0
and will be fixed in the next platform release.
Using onCreate did solve the problem though, as said above.
I never thought to try DDMS. The
That is similar to how I was using the onStartCommand() method.
I check for a null intent and then if it's not null check to see if there is
a specific intent extra passed. If that extra is passed then I know the
user explicitly started the service and not the system. This is an issue for
me
Yes it is not a compatible device if it is ignoring startForeground().
Which device is doing this? This would be really bad, since things like a
music app (including the standard Android music app) relies on this to be
able to play music without interruption.
The workaround I would suggest is
On Mar 1, 9:08 am, Jake Basile jakerbas...@gmail.com wrote:
It's been a month, and this regression bug still hasn't even been reviewed.
In my experience, no bug report (other than those submitted by Google
Android team members themselves) ever gets acknowledged or it's status
updated. That
My other suggestion would be to run a diff on the 2.2 and 2.3 source
trees and see where it has been broken, in your opinion. If you can
point to an exact piece of code, you may have better luck getting this
resolved.
Unfortunately, you will forever have to do this workaround (or at
least as
10 matches
Mail list logo
