On Tue, Mar 22, 2011 at 6:32 PM, Jake Colman <[email protected]> wrote:
> Do I have to assume that my application might get killed? > Yes. Not "might". "Will" ... eventually. > If my appwidget is sitting on the homescreen and displaying it's data might > it still be killed even though it's active? > Unlikely but possible. Who knows. > I recognize that my service is killed the moment it is done with its work > but does the same gold true for the appwidget's broadcast receiver? > > If the answer is yes, then is the apwidget display simply a statically > drawn thing that is displayed on the screen even if the receiver is dead? > No idea, have not worked on a widget yet. > I am assuming that your answer to all of the above is: yes, my application > might get killed. If so, how do I know when that is happening so that I can > save my location information somewhere? > You don't. It can happen at any time without warning. Save your information when it makes sense to do so (like when it changes, if it's not that frequent). How do I know when to restore it? > When you start up check your data store (wherever your saving your data to). > Also, I never see this problem on my own phone and only one user (out > of appx 180 active widget installations) is complaining. He is not using > a task killer so he is not forcing things to be killed. What might explain > only one user having an issue. > A really shitty phone? Also "not complaining" != "not happening". ------------------------------------------------------------------------------------------------- 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
