Very strange. Someone pointed out to me that I really shouldn't be using com.android as a package, since it's not my domain. I just hadn't changed it from when I was mirroring LunarLander. And since I changed it, my apps has yet to take longer than 3 seconds to load.
On Jan 10, 12:20 pm, "[email protected]" <[email protected]> wrote: > Hi all, > > I'm pretty stumped here. > > I've got an app that more or less follows the layout of LunarLander, > with an Activity, a View, and a Thread. The View extends SurfaceView > and the thread is what does the drawing. It is relatively light on > resources - 16 PNGs totalling 240KB, one simple layout xml, and one > simple values xml. > > The load time for the app is all over the map. It sometimes loads in > under a second, sometimes it takes as much as 50 seconds. But as long > as I don't touch it, it *always* finishes loading eventually (if I try > to interact with it, I get the "isn't responding" window and have the > option to kill it.. though even then it will finish loading if I wait > long enough). The behavior is the same whether I'm running my code on > the emulator or an actual ADP1. > > I've done a fair amount of logging to try to figure out what's going > on, but I'm not getting anywhere. My activity's onStart() is always > done in less than 2 seconds; my view and thread are also ready to go > within 2 seconds. Even my first call to onDraw() is always done in > under 3 seconds from the time the activity starts. > > After all that is done, I'll be starting at a blank screen (with my > title bar) for a very arbitrary amount of time. Finally, the logcat > will show me: > > I/ActivityManager( 52): Displayed activity > com.android.slots/.SlotsAndroid: 11301 ms > Of course, 11301 ms is sometimes 800ms, 3000ms, 20000ms, or 50000ms > instead. Unfortunately, until that line shows up, my app is > unresponsive and does not actually fill in the black space on the > screen. > > I can't figure out what is going on in the time between when my app > seems to be saying it's completely ready and when android decides it's > ready to go. Has anyone else seen this? Does anyone else have any > ideas? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
