Actually you don't need to speed it up. you could put the stuff that takes so long in a different thread ans let your UI activity stay inactive (not do anything, simply return the onCreate/onResume method. When the background task has finished you con continue. But normally you will have to switch back to UI task then so you don't break the application when performing UI stuff in the wrong context. You will also like to add some progress dialog or something like that.
Let me suggest using AsyncTask for this since it is pretty handy for this job. Stephan On 20 Jul., 02:55, Mark Murphy <[email protected]> wrote: > On Mon, Jul 19, 2010 at 4:48 PM, tar9919 <[email protected]> wrote: > > For some reason, one activity (launched in a new process) often takes longer > > than 10 seconds to start, which exceeds the LAUCH_TIMEOUT defined in > > ActivityManagerService. > > How do I make the VM tolerate longer launch time without giving up wake > > lock? > > You don't, since that is baked into firmware. Instead, you need to fix > your activity to start faster. Not starting it in a new process would > be a fine starting point. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 3.1 Available! -- 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
