Apps Ideal Ecipse Configuration for faster Android Emulation

[dothackjhe]

We have a class at school about Android apps development so the need for a fast and bug-free Android environment emulation is essential. The problem, however, is that Eclipse (the IDE we use) is not set at that by default. Can anyone tell me an ideal setup configuration that ensures not just fast, but bugless execution of the Android emulator? That's the problem we often encounter.

This laptop I uses right now has a dual core processor (AMD E350 @ 1.6 GHz) in it with 4 Gb of RAM. A decent spec for this IDE I think.

 

[jonbonazza]

No matter how fast your rig is, the emulator is just plain slow and buggy. If you really want the best testing experience possible, then I recommend you use a physical device.

 

[jonbonazza]

Also, moved to Dev 101. =)

 

[dothackjhe]

I see. The sad part, however, is I do not yet own any Android-operating device of which testing any developed application to a physical device is out of the option.

Now that you mentioned the emulator being buggy, do you know how to fix this error: "failed to install <appname>.apk on device 'emulator-5554'? That occured when I tried to run some lines of codes in the emulator both on my laptop and my school lab's computer.

 

[jonbonazza]

Above that line it usually gives a few lines giving the reason for the failure. Can you paste those lines of code here?

 

[dothackjhe]

Here's what's written on the console tab:

[2012-07-03 08:50:27 - Activities] ------------------------------
[2012-07-03 08:50:27 - Activities] Android Launch!
[2012-07-03 08:50:27 - Activities] adb is running normally.
[2012-07-03 08:50:27 - Activities] Performing ph.edu.comteq.activities.ActivitiesActivity activity launch
[2012-07-03 08:50:27 - Activities] Automatic Target Mode: launching new emulator with compatible AVD 'AndroidVirtualDevice'
[2012-07-03 08:50:27 - Activities] Launching a new emulator with Virtual Device 'AndroidVirtualDevice'
[2012-07-03 08:50:58 - Activities] New emulator found: emulator-5554
[2012-07-03 08:50:58 - Activities] Waiting for HOME ('android.process.acore') to be launched...
[2012-07-03 08:56:29 - Activities] HOME is up on device 'emulator-5554'
[2012-07-03 08:56:29 - Activities] Uploading Activities.apk onto device 'emulator-5554'
[2012-07-03 08:56:29 - Activities] Installing Activities.apk...
[2012-07-03 08:59:31 - Activities] Failed to install Activities.apk on device 'emulator-5554!
[2012-07-03 08:59:31 - Activities] (null)
[2012-07-03 08:59:33 - Activities] Launch canceled!

Notice that the launch was canceled yet I was not trying to close the emulator.

[Update]

To my surprise, the emulator runs just fine even with such log in the console tab. This was not the case yesterday though. I'm guessing this got something to do with touching the Android earlier than it should be (resources not fully loaded).

For someone who's studying programming in an Android environment, the emulator being slow and buggy can be disheartening lol. I guess programming apps for this mobile OS really is best done in the actual physical device.