Without going into details since this is a public forum, suffice it to say that
it might not be in your best interest to delicense the app when it has been
licensed successfully in the past. This approach has helped us in dealing with
these issues, and perhaps a similar approach might help out
Based on those threads and the issues list, it seems that receiving a broadcast
is the main known way that this is triggered (aside from not having a
foreground service, but I do have one), but I have logs on all my onReceive and
it doesn't seem to be that. :(
On Mar 13, 2014, at 2:45 AM, Pent
Interesting, I wasn't aware of the strictfp modifier. It seems that
changing one of the floats to a double may have fixed it... I sent out
several more specific tests and waiting for the remote debugger to confirm.
:)
On Wed, Aug 7, 2013 at 5:12 PM, Nobu Games dev.nobu.ga...@gmail.com wrote:
If
.
On Thu, Aug 8, 2013 at 2:17 PM, Digipom Inc. digi...@gmail.com wrote:
Interesting, I wasn't aware of the strictfp modifier. It seems that
changing one of the floats to a double may have fixed it... I sent out
several more specific tests and waiting for the remote debugger to confirm.
:)
On Wed
Thanks, I've added my info to the bug. Hope that we can figure out a
solution.
On Tue, Mar 19, 2013 at 2:34 PM, Harri Smått har...@gmail.com wrote:
Hi,
There's this one rather recent issue which might be related to what you're
seeing;
https://code.google.com/p/android/issues/detail?id=52446
Hi Al,
Thanks, this seems like a good approach. This was just what I was wondering
-- how to statically configure things so as to avoid the Android bugs with
runtime enabling/disabling. I'll give this one a shot! :)
On Tue, Feb 19, 2013 at 3:08 AM, al achim.leub...@googlemail.com wrote:
You
Ok, I was just wondering, as I once turned an app project into a library
project by simply checking the checkbox, kept the old package name for the
library and created a new app project with a different package.
I was just wondering if there was something I might have overlooked or some
bad side
On Thu, Aug 16, 2012 at 7:57 AM, Mark Murphy mmur...@commonsware.comwrote:
On Thu, Aug 9, 2012 at 11:23 AM, Digipom digi...@gmail.com wrote:
I got bitten by this the hard way. The official documentation on services
doesn't have any warnings about this, so I figured onDestroy() was good
.
On Thu, Aug 16, 2012 at 10:29 AM, Mark Murphy mmur...@commonsware.comwrote:
On Thu, Aug 16, 2012 at 10:19 AM, Digipom Inc. digi...@gmail.com wrote:
Not everything is designed to be used indefinitely by a service.
It's hard to think of something more suited to a service than recording
9 matches
Mail list logo