Your main thrust is about battery drain. Is your assumption that an application that is not shut down will drain the battery really valid?
On Thu, Jan 21, 2010 at 2:27 PM, Kevin Duffey <andjar...@gmail.com> wrote: > I don't know if I like this model. :D I'll give you one reason that I don't > know if it comes up or exists often, but I think it's one of the most > confusing issues for non-techie (and even techie peeps that don't know about > programming and threads and such) users for android devices. The problem to > me is.. I am a developer that will without a doubt make mistakes. As such, > if I am writing an app that otherwise seems to run fine on devices, but I've > forgotten to stop threads when my app is paused (either by user hitting > home/back, phone call, etc).. to the users, my app may be finished. The > notion of not closing down an app and users getting used to that idea means > that they need to trust every app they ever get that it wont leave some > battery draining possibility running behind. Now, Mark I know will correct > me if I am wrong here, I've read his first book mostly and other books on > Android. It is up to us in every Activity to handle the pause/resume, > create(bundle) to resume properly if the app was actually shut down and > bundle info saved, etc. But I still can't help to think that there are thos > eapps that have "bugs" in them that have either a thread left behind > (assuming android doesn't completely shut it down) that may end up draining > the battery. I don't know for sure, but a few times now, I've come back to > my phone a couple hours later to find it dead, from a completely charged > state prior. And I don't know why. My only guess is that I left something > running, like google maps with wifi that I thought was stopped/shut down > cause I hit the home/back button. Being a developer I know it's probably in > a paused state, but this battery drain thing has happened a few times. > > Thus, my thought is.. to avoid my app possibly draining the battery, I'd > rather have a quit option to exit the app completely.. it's done, unloaded, > no threads, etc. Now on iPhone, it's well known that presently pressing the > one button kills the apps. The apps have the option to save state info > before shutting down, and some apps make good use of this to make it look > like it never shut down.. restoring the user to where they were previously > at. Most iPhone apps dont do this tho. So the thing is, this not shutting > apps down completely is a different mind set that I honestly am surprised we > would want to program to as developers concerned about battery drainage. I > would think since one of the most important things when writting android > apps is to consider battery life, would be to do everything we can to shut > our app down if the user hits the exit button. Sure, if they hit back/home, > or a call comes in or they go to status bar and select something, the > pause/resume notion kicks in. But I am having a hard time understand why you > would not want to put in an exit/quit option and cleanly shut down > everything if they choose this? I do see some games on Android doing this. > > So Mark et all, I understand the basics of what you are saying and for some > apps this makes perfect sense. But some, like games or those that may spawn > threads or do other cpu intensive things that could drain battery especially > if done in threads, it seems to me to be safe and keep our ratings of our > apps form going down to 1 star, we'd want to program defensively and make > sure our app shuts down completely. > > Just my .02 on the matter. > > On Thu, Jan 21, 2010 at 8:52 AM, Vladimir <vladimir.funti...@gmail.com>wrote: > >> "But my question is "Why does user has to wait till android closes >> particular application, Instead why doesn't user do this"?" >> >> Because this is how it is done in Android. If you change it, users >> will get confused and eventually annoyed. >> >> On Jan 21, 3:58 pm, pink 444 <pnk...@gmail.com> wrote: >> > Thanks for your replay. >> > >> > And i went through the link , which you specified. >> > >> > As i understood process will be killed by android only. >> > >> > But my question is "Why does user has to wait till android closes >> > particular application, Instead why doesn't user do this"? >> > >> > Instead of waiting till android system cleans all the resources used >> > by the application , It is more efficient if user able to clean all >> > the resources used by the application. Especially it is useful in >> > embedded environment like mobiles. >> > >> > If you take any game and user does not have any option to close the >> > game . Then the application has to wait for android system to clean >> > resources , which are owned by the application. But these type of >> > applications are not used by the user regularly(Generally Once in a >> > day or week). >> > >> > On Jan 21, 3:06 pm, "Mark Murphy" <mmur...@commonsware.com> wrote: >> > >> > >> > >> > > > In my application i have to close the application. >> > >> > > No, you don't. >> > >> > > > Hence i am using System.exit(1). >> > >> > > Please do not do this. >> > >> > > > But some times it is trying to restart entire application. >> > >> > > > What is the problem? >> > >> > > You are trying to close the application. Please do not do this. >> > >> > > If you want to simply close up an activity, the activity can call >> finish(). >> > >> > > > How can i close an application safely? >> > >> > > You do not need to: >> > >> > >http://stackoverflow.com/questions/2033914/quitting-an-application-is. >> .. >> > >> > > -- >> > > 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<android-developers%2bunsubscr...@googlegroups.com> >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en >> > > -- > 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<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
