• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Apps How to reduce execution time in Android

M

marinajogy

Newbie
I am using Eclipse for Android development
and Latest version of Android SDK (Running XP, 2Gb Ram)

1. when run clicked, previously executed emulator appears first
then emulator default screen appears, only last current actual output appears

2. when clicked to close takes too much time (2 mns) for the emulator to disapper

3. in short execution time exceeds development/coding time in the testing process

is anyway to reduce such execution time


thnks in advance
 
Welcome to Android Forums marinajogy.:)

I moved this to the Application Development forum to get some better eyes on it.
 
@marinajogy

Do you run a new emulator every time you test a piece of code and once your testing is complete you close the emulator? In the next testing iteration you do the same again (new emulator, test, close emulator).

Is that how you currently do it?
 
cryofy said:
@marinajogy

Do you run a new emulator every time you test a piece of code and once your testing is complete you close the emulator? In the next testing iteration you do the same again (new emulator, test, close emulator).

Is that how you currently do it?
Click to expand...
ya, emulator is closed after one run
(new emulator, test, close emulator). yes

what is the best mehod
 
You don't need to close the emulator, every time you test some piece of code. Just start one emulator instance then check if it's properly listed under the Eclispe device list. If it's not, go to the command line and write "adb kill-server" and then "adb start-server".
Now if you want to test some code, hit the run button in Eclipse, test your code and don't close the emulator afterwards, just let this one emulator instance open. Next time you test some code, there's no need to start a new instance, Eclipse will automatically use the existing one and it will take only little time to upload and rund your apk.

If you have a cpu capable of x86 virtualization, for newer intel i-5 & i-7 cpus this is called vt-d, you can use Intel HAXM to greatly speed up your emulator.

Cheers
 
If it's not, go to the command line and write "adb kill-server" and then "adb start-server".

pl let me know, what this commands doing
 
Adb is the Android Debug Bridge, see Android Debug Bridge | Android Developers. It's a command line tool that lets you communicate with an emulator instance or connected Android-powered device, it's bundled with the android sdk and you find it in your android-sdk\platform-tools directory.

You can check listed devices via the 'adb devices' command. If you start a new emulator, and it is not listed here, 'adb kill-server' & 'adb start-server' should help.
 
You must log in or register to reply here.
Back
Top Bottom