Speeding the Android edit-debug cycle

tags:

android

views:

answers:

Speeding the Android edit-debug cycle

Developing applications for Android in Eclipse, press F11 to run the program in the emulator.

However, this means waiting for the emulator to bootup (and then unlocking the emulator's screen) each time you want to test changes to your program. Is there any way around this delay?

+3 A:

OJW

Are you closing the emulator after you test the app?

If you leave it running and then start your application from Eclipse again it will re-deploy and start (and avoid the overhead of starting the emulator).

You can also stop the application from the emulator perspective in eclipse before re-starting it.

-- Frank

Frank C. 2010-07-25 11:17:11

+2 A:

If you have a physical device, you can use it instead of the emulator, it's much faster.

JRL 2010-07-25 11:21:13

OK, let's examine this option. I have a physical device. I've just changed a line of code and I'd like to test it. Android tools - export signed application package. Enter 2 passwords in 4 dialogs. Get an ipk. Upload it to my website. Download it in phone's browser. Go to notification area, select the recent download, open package manager and install it. Open it. Run it. Now running my new software. It only took 17 steps.

OJW 2010-09-15 22:03:19

@OJW: if you have your device plugged in via USB and have the USB driver installed, pressing F11 from Eclipse will launch it on your device, not the emulator. You can even have both the emulator and your device on, and on launch Eclipse will ask you which to use.

JRL 2010-09-15 22:11:44

ansaurus

tags:

views:

answers:

Speeding the Android edit-debug cycle

related questions