Simon Broenner wrote: > Hmmm, I'm beginning to get that feeling too. > > Any idea what the cause could be? Obviously I'm not using any auto task > killers or anything like that... :(
Off the top of my head, no. If you're a developer, and you can get it to happen, plug it into USB and scan logcat for any interesting messages. Usually, Android logs when it is killing off processes, and it feels like your Browser process is getting killed. If you're not a developer, the only advice I can offer is for you to come up with a repeatable scenario that consistently causes the problem, preferably from a freshly-rebooted phone. (even more ideally would be a phone with no third-party apps, but I'm guessing this is your personal phone, so having you wipe it would be a bit intrusive) If you can find such a scenario, post it here or on [android-discuss], so we can see if other devices exhibit the same behavior. If we can find cases across several devices, it's probably an Android bug. If the only other cases are Milestones, it might be a Motorola bug. If we can't reproduce the problem, I'd start taking a real close look at any third-party apps you have installed. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training...At Your Office: http://commonsware.com/training -- 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
