Hi, yes I do have the splash screen setup like that, so there is at least
instant feedback the app is loading, but it then sits there just a bit too
long.
Good to hear it's set to improve in the next release... When might that be
pray tell?
On 26/11/11 12:18 PM, "Jonathan Pobst" wrote:
>Hell
Hello!
We've shaved about a second off of startup time for the next release
(measured on a Nexus One).
Also, you might want to try this method of splash screen, as the image
shows immediately when the user launches the app, before the monodroid
runtime is initialized.
http://docs.xamarin.com/
Thanks Chris. My issue with startup performance is from when I tap the
application to when I get my first chance to run code. Once I get my first
OnCreate() call on my SplashActivity, I do utilize background threads and
and IoC container, but it's loading the runtime that's the problem.
I know the
I'm sure that you have already looked at this, but what about a background/non
UI thread for loading what is needed?
Wally
> Date: Fri, 25 Nov 2011 06:48:10 -0800
> From: skylog...@btconnect.com
> To: monodroid@lists.ximian.com
> Subject: Re: [mono-android] Test on Real Device before paying for
You're right, I'm only loading one row of config/preferences data on startup,
so I don't think that increases the startup time by much at all; all other
SQLite activities are only carried out when needed. As you say, hopefully
the startup times can be brought down somewhat in future MfA updates.
R
Hi!
I'm receiving often a *SocketError.TimedOut* from *ReceiveAsync* in a
multi-threaded Mono App on Android 3.2.
Android 2.1 & Android 2.3 works fine.
I link armeabi-7va.
Can it be something connected to runtime multi-threading issues?
--
View this message in context:
http://mono-for-android
You could consider lazy loading data, as in only loading data when
actually needed.
Depending on how much data you need to load, it shouldn't be that time
consuming to load a few rows from an SQLite database.
But you are right the startup process on Android is a bit slow,
hopefully Xamarin will lo
Hi,
Well, my app takes 6 secs to start up on my ZTC San Francisco. However, the
main activity reads quite a few preferences from a SQLite table on startup,
so that probably slows things a bit. I haven't really looked at optimising
startup times yet, so I'm not sure whether or not it could be speed
Hello,
Re.: We're sorry you're getting crashes, this is most likely due to weird
data on the android log which the plugin wasn't parsing correctly.
Can this log be cleared in the meantime? If so, how? Ive found other
circumstances when VS2010 crashes ocasionaly, for example, after building
