Hi, Have a look at this - http://jyro.blogspot.com/2009/09/crash-report-for-android-app.html
Regards On Jul 27, 6:18 am, Indicator Veritatis <[email protected]> wrote: > Your advice is certainly sound, but I can sympathize with the OP's > "Service envy", thinking that his Service should also be able to > persist for days like certain others. > > Then again, since he is talking about taking up as much as 10MB, he > should not be surprised that his gets killed more often than the > others. Any service that is going to persist for so long has to be > MUCH more lightweight than that, unless it is a system service. > > BTW: there has got to be a better way to do this than wait forever for > incoming TCP PDUS: somebody in this group once mentioned WebTCP, > though it was never clear to me how that solves the problem. > > On Jul 26, 8:39 am, TreKing <[email protected]> wrote: > > > > > > > > > On Fri, Jul 22, 2011 at 10:03 PM, scmailon <[email protected]> wrote: > > > Any idea suggestion is very wellcome :) > > > Don't attempt to keep you service alive indefinitely - it can and will be > > killed when necessary. Instead, code it to take this reality into account. > > > --------------------------------------------------------------------------- > > ---------------------- > > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > > transit tracking app for Android-powered devices -- 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
