Nmix wrote: > I did some additional testing on the 2.0 AVD, including numerous > project cleans, compiling with 1.5, 1.6 and 2.0, and cutting out large > swaths of code. The problem persists. Yet other apps I have work fine > on 2.0. > > I peppered logs in each of the major life cycle methods I implement, > and this is what I get: > 10-29 20:33:23.561: DEBUG/tag(502): onCreate > 10-29 20:33:24.271: DEBUG/tag(502): onResume > 10-29 20:33:26.101: DEBUG/tag(502): onSaveInstanceState > 10-29 20:33:26.214: DEBUG/tag(502): onPause > 10-29 20:33:26.311: DEBUG/tag(502): onCreate > 10-29 20:33:26.561: DEBUG/tag(502): onRestoreInstanceState > 10-29 20:33:26.571: DEBUG/tag(502): onResume > 10-29 20:33:27.081: DEBUG/tag(502): onSaveInstanceState > 10-29 20:33:27.130: DEBUG/tag(502): onPause > 10-29 20:33:27.211: DEBUG/tag(502): onCreate > 10-29 20:33:27.601: DEBUG/tag(502): onRestoreInstanceState > 10-29 20:33:27.611: DEBUG/tag(502): onResume > 10-29 20:33:28.162: DEBUG/tag(502): onSaveInstanceState > 10-29 20:33:28.201: DEBUG/tag(502): onPause > 10-29 20:33:28.541: DEBUG/tag(502): onCreate > 10-29 20:33:28.951: DEBUG/tag(502): onRestoreInstanceState > 10-29 20:33:28.960: DEBUG/tag(502): onResume > 10-29 20:33:29.631: DEBUG/FatCalc(502): onPause > > I finally kill it with the back key, though it sometimes takes a few > tries because the timing is critical. > > Elsewhere in the log, I found something in the logs put out by the > system process that from their timestamp may be correlated with the > uninstall/install process initiated by ADB: > > 10-29 20:33:14.391: WARN/ResourceType(55): Resources don't contain > package for resource number 0x7f060000 > 10-29 20:33:14.461: WARN/ResourceType(55): Resources don't contain > package for resource number 0x7f060001 > > These correspond to string resources in the app, both of which appear > to display normally when the app runs, in the momentary glimpses of > the app's UI display before it gets destroyed. > > This really has me puzzled. Any help appreciated.
Something in your onResume() would appear to be triggering behavior reminiscent of a screen rotation or other configuration change. I'd start by commenting out everything in onResume() and seeing if the problem persists. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android 1.6 Programming Books: http://commonsware.com/books --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
