You just redeploy the app from your IDE or the command line..

Use adb ..

> I tried with both home key, and also pressing the back key to get out
> of the application to see if that reloads the application. But seems
> like its not reloading the application. Any idea how can I ask the
> emulator to reload the application without restarting?
>
> On Jul 6, 7:07 pm, jahid <[email protected]> wrote:
>> Thanks guys. But once my code base changed, will the emulator take the
>> changes automatically, and all I have to do is, go back to "home" and
>> from there open the application again? Or how do I ask the emulator to
>> reload?
>>
>> And,    Fabrizio Giudici, thanks for your good suggestion. But the thing
>> is, I just started with Android, so I don't know a lot of thing (like
>> how to upload an app on my device...). So I think it will take little
>> time for me to get hold of all those things :|
>>
>> On Jul 6, 6:44 pm, Fabrizio Giudici <[email protected]>
>> wrote:
>>
>>
>>
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>>
>> > On 7/6/10 18:31 , Dominic Mitchell wrote:> On Tue, Jul 6, 2010 at
>> 10:31 AM, jahid <[email protected]
>> > > <mailto:[email protected]>> wrote:
>>
>> > >     I am trying out Android. It takes a huge amount of time to run
>> an
>> > >     Android application on AVD (through IDE, I tried both IDEA and
>> > >     Eclipse). I was wondering, if its same for you guys, or I am
>> missing
>> > >     something. If its same for you guys as well, isn't it that
>> Android
>> > >     application development will take huge amount time, and most of
>> them
>> > >     will go into this loading time?
>>
>> > > If you're running the emulator for the first time, it does take a
>> > > long while to boot up.  But if you leave it running, and just
>> > > redeploy your code into it, you should see a significant speedup.
>>
>> > +1. But I'll add two points:
>>
>> > 1. Unlike as it happened with JME, it's very fast to deploy to a real
>> > device connected by means of USB. So I often develop directly with the
>> > device.
>> > 2. I strongly suggest you to separate in different modules the code
>> > that depends on Android from the one that doesn't - and if you use TDD
>> > or a similar technique for developing the latter, you'll be *very*
>> fast.
>>
>> > - --
>> > Fabrizio Giudici - Java Architect, Project Manager
>> > Tidalwave s.a.s. - "We make Java work. Everywhere."
>> > java.net/blog/fabriziogiudici -www.tidalwave.it/people
>> > [email protected]
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
>> > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
>>
>> > iEYEARECAAYFAkwzXVcACgkQeDweFqgUGxdxwQCfW8t7LdqJ7z4HeFAMNXkjct6l
>> > yQ0An0VKVNUh2OOBVZSwlN8OCftjYL1u
>> > =cuyw
>> > -----END PGP SIGNATURE-----
>
> --
> You received this message because you are subscribed to the Google Groups
> "The Java Posse" 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/javaposse?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "The 
Java Posse" 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/javaposse?hl=en.

Reply via email to