On 4 kvě, 01:06, Eric F <[email protected]> wrote: > The solution here is a change in attitude. I don't use a task killer > on my phone, never have. And my phone sports good performance for > weeks on end.
Agree. I have task killer but use it really rarely. > Obviously the solution isn't to eliminate task killers. One possible > solution is to contact the authors of the most prominent task killers > and get them to try to change their UI to highlight "top resource > consuming tasks" as opposed to emphasizing the "kill all" button. When I look at Android Market I have a feeling that everybody wants to write it's own task killer while learning android programming ;-) (http://www.appbrain.com/search?q=killer). This I race I can't win. > Another part of the puzzle is educating the iditions, and another part > of the puzzle is to, as developers, use the APIs correctly. They can't > kill your service if it's not running and is triggered by > AlarmManager. I think that this is not true. I'm USING Alarm Service but my gadget still can be killed by task killers. -- 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
