Please, no. There is good reason to not notify the package being killed. Two thoughts: 1) Maybe you guys need to ask yourselves why users are force stopping your apps? 2) If someone uses force stop they should already acknowledge that some information might be lost.
On Oct 2, 3:56 pm, Lucas <roll...@gmail.com> wrote: > Hello, > > I was having the same issues. And i was not able to solve it the way i > wish it. > > I think this is a great feature on android, but also i think it has it > faults. I think that the system MUST send to my package > ACTION_PACKAGE_RESTARTED before killing the process, or at least call > onDestroy on it, because now i am not able of make a correct clean-up > of the state my application is. > > In my personal case i have a worker thread that must finish cleanly in > order to make my app re-launch in a reliable state. > > I am going to add a case in Android issues regarding this, > > regards, > > Lucas > > On Oct 2, 9:22 am, "Mark Murphy" <mmur...@commonsware.com> wrote: > > > > I'm not saying that this is a bug, I just want to know if there is > > > any way to know from my application that it is being killed by the > > > application manager. > > > No. > > > -- > > Mark Murphy (a Commons Guy)http://commonsware.com > > Android App Developer Books:http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ 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-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
