For whatever it's worth, this continues to happen. It seems to happen faster and more frequently if I'm running in the debugger, but it happens fairly often under all circumstances. I've had to move all my onPause code to onStop, which is not optimal but it's the only thing that works.
I'm running on Cupcake, and my impression is that Cupcake is simply not done - there are lots of things that just flat out don't work (e.g. this problem, RelativeLayout, "route add", Thread.isInterrupted, etc). In many cases we've debugged into the system code and found the bugs that cause the problems. Can anyone comment on how true this is of more current builds? Thanks, Aaron On Apr 22, 11:08 am, asher <as...@vanteon.com> wrote: > Thanks for responding. OK, this is weird. When I posted the issue > originally, I believe I was running in a 1.6 emulator, and the > behavior was 100% consistent. I've tested it a few times since then on > my hardware (which is a custom device running 1.5), and it's been > consistent. Today, I tried it in a 1.5 emulator, and it didn't happen > at all, either in the actual application that originally exhibited the > problem or in a test app. I tried it on my hardware, and it did > happen, but then I got distracted for a few minutes, and when I tried > it again it didn't. At this moment, I can't reproduce it at all under > any circumstances. I'm confused. > > I've since moved all my cleanup code to onClose, which isn't ideal but > it probably won't hurt anything on this specialized device. I'll keep > an eye on this, and if it happens again I'll post an update. > > Thanks, > Aaron > > On Apr 16, 7:16 pm, Michael Thomas <enervat...@gmail.com> wrote: > > > > > Mark Murphy wrote: > > > asher wrote: > > > >> OK, I should have done this earlier. I created a new Android app in > > >> Eclipse, added an onPause override in the activity containing nothing > > >> but a single log message (and the super call), and ran it, and got > > >> exactly the same behavior. This seems to be either a bug in Android > > >> (I'm running 1.5), or I'm seriously misunderstanding something about > > >> the activity lifecycle. Can anyone help? If anyone's actually reading > > >> this, would you at least respond so I know I'm not shouting in the > > >> dark here? > > > > I cannot reproduce your problem on Android 1.5, Android 1.6, Android > > > 2.0.1, or Android 2.1 (emulator) or on the DROID (2.1). > > > Is it possible that the app is starting with the screen off? This can > > happen when you > > load an app from adb/eclipse. If you loaded the app in that situation, > > I'd sort of expect > > that you'd see the resume followed by pause behavior, but it's only a guess. > > > Mike > > > -- > > 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 > > athttp://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 > athttp://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
