How to quickly update the package without restarting the simulator?

by Brett Chabot » Wed, 31 Dec 2008 04:19:00 GMT

Sponsored Links
 You could try to re-install the app instead, using
adb install -r my.apk

Although re-installing will retain the application's data, which might
not be always what you want.

Also, I wasn't clear from your message whether you are doing this or
not, but it should not be necessary to close and restart the emulator.
I just leave the emulator running while I'm doing my app development.

Hope that helps.



How to quickly update the package without restarting the simulator?

by Xiongzh » Wed, 31 Dec 2008 07:15:14 GMT

 Yes, do not need to restart the simulator. Just re-run the application
within Eclipse. The plugin is wise enough to reuse the simulator and
reinstall the package.
Here's the console log:
[2008-12-31 07:10:35 - ApiDemos] Android Launch!
[2008-12-31 07:10:35 - ApiDemos] adb is running normally.
[2008-12-31 07:10:35 - ApiDemos] Launching:
[2008-12-31 07:10:35 - ApiDemos] Automatic Target Mode: using existing
emulator: emulator-5554
[2008-12-31 07:10:35 - ApiDemos] Uploading ApiDemos.apk onto device
[2008-12-31 07:10:40 - ApiDemos] Installing ApiDemos.apk...
[2008-12-31 07:10:56 - ApiDemos] Application already exists.
Attempting to re-install instead...
[2008-12-31 07:11:17 - ApiDemos] Success!
[2008-12-31 07:11:17 - ApiDemos] Starting activity on device
[2008-12-31 07:11:20 - ApiDemos] ActivityManager: DDM dispatch reg
wait timeout
[2008-12-31 07:11:20 - ApiDemos] ActivityManager: Can't dispatch DDM
chunk 52454151: no handler defined
[2008-12-31 07:11:22 - ApiDemos] ActivityManager: Starting: Intent
{ comp={} }


Sponsored Links

How to quickly update the package without restarting the simulator?

by Xiongzh » Wed, 31 Dec 2008 07:37:21 GMT

 Hope in the next version of Android SDK, developer need not to package
and reinstall the apk while debugging ...


How to quickly update the package without restarting the simulator?

by Pete Wright » Fri, 02 Jan 2009 05:44:27 GMT

 See the other replies in this thread. You don't need to. Just leave
the emulator running, make your code changes and run the application
again. The emulator will not reboot and go through the startup process
over again, but will instead just run the newly changed app.


Other Threads

1. Android unit testing

Hi all,

I'm interested in the current solutions for Android to address the
following requirements:
- Unit testing for building blocks (activities, content providers,
- Integration of unit tests into the project build (maybe through dx --
junit if it works...)
- Integration tests

I only took a look at android-positron. It doesn't integrate with
Eclipse ADT plugin, so unit tests can not be started from Eclipse. I
managed to run one simple test (both as java application and using /
system/bin/am ) but it looks that the only way to verify the test
results is by taking a look at the logcat file. Am I missing something
Does anyone know a good practice for testing Android's building

Looking forward to the answers from test-driven development



2. Its a Zoooooommmm MDK (ZoomMDK)

Hey guys,

maybe I've got something interesting for you ;D

"Someone" sent me a ZoomMDK as a present (doesn't want to be named),
which is a generic Hardware platform, which is officially able to run
Android. TI is the big one behind. Tomorrow I'll get it from my local
customs and start reviewing it and document my experiences.

All that will be posted on First article of many:

If I got it running, my plan is to test hardware-intensive appliations
(like Tom Gibaras MoseyCode, Andnav, and maybe YOUR app) on this real
device. Then we will see how well performing the device is against the

Stay tuned :)

Regards, plusminus
#  Worlds largest Android Development Community / Tutorials

(sorry for posting in multiple forums)

3. Run two android instances on the same host and comunicate betwen them using socket

4. Looking for a fast UI platform for embedded linux

5. thunderbird client issues

6. OSCAR/XMPP/IRC chat client

7. chat client