I think a lot of apps don't use the onStop or onStart. I never found a use for them (so far...).
onCreate, onResume, onPause and onDestroy are the most important ones. The xxxxNonConfigurationInstance() methods for configuration changes. On Mar 5, 9:26 am, Zuli <paolo.zuli...@gmail.com> wrote: > I agree with Mark Murphy, it seems a problem only when the home screen > is displayed after the activity, if I open another activity on top of > that (long press on HOME) or if I receive a call the onStop is > correctly called... > seems to me quite a big issue, think about all the activities that use > the onstart and onstop methods to coordinate their work, how come so > few people have noticed that? > > Zuli > > On Mar 5, 6:00 am, Streets Of Boston <flyingdutc...@gmail.com> wrote: > > > > > mmmmmm... my app makes use of saving and restoring instance state a > > lot and it works as well on theNexusOneas on the Droid or G1. But i > > don't use the onStop callback at all. And I don't use the > > onRestoreInstanceState either. Instead, i use the > > onRetainNonConfigurationInstance() and > > getLastNonConfigurationInstance() methods. These work well for me. > > > On Mar 4, 8:25 pm, Zsolt Vasvari <zvasv...@gmail.com> wrote: > > > > I think there are some issues with the background activity life cycle > > > management on theNexusOne. > > > > In my app, I have a background and foreground activity. When I tilt > > > the phone so it switches orientation, the first time around the state > > > is properly saved and restored for the background acrivity. But if > > > when flip it back, onCreate is called with NULL for the Bundle, so I > > > lose state. (and no, onRestoreInstanceState is not called, either) > > > > I'd create a small app that demonstrates this, but frankly, it would > > > be a waste of my time as it probably wouldn't get looked at anyhow. > > > So just take my word for it.... > > > > Zsolt Vasvari > > > > On Mar 5, 4:29 am, Mark Murphy <mmur...@commonsware.com> wrote: > > > > > Mark Murphy wrote: > > > > > schwiz wrote: > > > > >> It should be called when you press back but not home, but I have > > > > >> noticed this problem using openeclair on my G1. Perhaps its a new > > > > >> feature/bug in 2.1? > > > > > > No, onStop() should be called when you press either BACK or HOME. For > > > > > some reason, it is not doing that in theNexusOne. My best guess is > > > > > that it has to do with theNexusOne'shome screen implementation, but > > > > > that's just a guess. > > > > > BTW, here's the open issue: > > > > >http://code.google.com/p/android/issues/detail?id=6094 > > > > > -- > > > > Mark Murphy (a Commons > > > > Guy)http://commonsware.com|http://twitter.com/commonsguy > > > > > _Android Programming Tutorials_ Version 2.0 Available!- Hide quoted > > > > text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - -- 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
