After doing some testing I found out that the performance is radically improved when running the app on a device outside of Visual Studio (meaning disconnecting the phone from the PC and then starting the app on the phone). It's still slow to start, but that's only when doing a cold start, so a splash screen might be just the solution I'm looking for. Thank you :)
Based on the above, I'm now interested in learning how long the app will keep running in the background (with no userinteraction) before Android decides to shut it down so the user must do a cold start of the app the next it should be used? Cheers, Nicklas From: monodroid-boun...@lists.ximian.com [mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Matthew Groves Sent: 11. august 2011 15:21 To: Discussions related to Mono for Android Subject: Re: [mono-android] Slow launch Here's a splash screen example from an older forum post from Brian Long that's worked for me (see also: http://mono-for-android.1047100.n5.nabble.com/Slow-poor-performance-td4390223.html;cid=1313068734524-953) http://blong.com/Downloads/MonoAndroidJavaSplashScreenApp.zip It's pretty simple, and all the instructions are there in comments. -Matt On Thu, Aug 11, 2011 at 9:15 AM, Jonathan Pryor <j...@xamarin.com<mailto:j...@xamarin.com>> wrote: On Aug 11, 2011, at 4:25 AM, BluePosition wrote: > Jonathan Pryor-2 wrote: >> That is, it launches in 2.3s. > > This is way to slow. If 2.3s is too slow for startup, would a splash screen work? Unfortunately we have no samples for what to do for custom splash screens, but it involves writing a Java activity (the "real" activity) which displays the splash screen (google for Java code) then launches the managed activity through the generated Android Callable Wrapper. You'll want to investigate e.g. obj/Debug/android/src to see the generated wrappers (for types & names) and obj/Debug/android/AndroidManifest.xml (which also provides the types & names you can use with Activity.startActivity). > I've been running the app on a HTC Sensation and the startup speed isn't much > better on that device. If your app is taking far longer that 2.3s to launch, then you're doing to much work in your Activity.OnCreate() method. Try doing more work on a background thread. - Jon [0] http://www.htc.com/europe/product/sensation/specification.html [1] http://www.gsmarena.com/htc_google_nexus_one-3069.php _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com<mailto:Monodroid@lists.ximian.com> UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
