Go Back   Android Forums > Android Development > Application Development
Application Development Dev lounge for our application developers.

test: Reply
 
LinkBack Thread Tools
Old February 3rd, 2013, 06:44 PM   #1 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jan 2013
Posts: 10
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default How to reduce execution time in Android

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

Advertisements
marinajogy is offline  
Reply With Quote
sponsored links
Old February 3rd, 2013, 08:01 PM   #2 (permalink)
~Play Nice~
 
Unforgiven's Avatar
 
Join Date: Jun 2010
Location: Douglas, MA
Gender: Male
Posts: 24,940
 
Device(s): Moto X Developer Edition, Nexus 7 (2012 & 2013), Note II, S3
Carrier: Not Provided

Thanks: 15,578
Thanked 16,918 Times in 9,307 Posts
Default

Welcome to Android Forums marinajogy.

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

Join the fun and make some friends, register for free here.
If someone helped, hit Thanks, if you see rude or abusive posts, spam, or threads that need staff attention, hit Report.
Site Rules / Android Forums FAQ
*** Do you want to talk guns? ***

Unforgiven is online now  
Reply With Quote
Old February 4th, 2013, 03:20 PM   #3 (permalink)
Junior Member
 
Join Date: Feb 2013
Posts: 21
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default

@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 is offline  
Reply With Quote
Old February 5th, 2013, 08:09 PM   #4 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jan 2013
Posts: 10
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by cryofy View Post
@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?
ya, emulator is closed after one run
(new emulator, test, close emulator). yes

what is the best mehod
marinajogy is offline  
Reply With Quote
Old February 6th, 2013, 07:31 AM   #5 (permalink)
Junior Member
 
Join Date: Feb 2013
Posts: 21
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default

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
cryofy is offline  
Last edited by cryofy; February 6th, 2013 at 07:47 AM.
Reply With Quote
Old February 7th, 2013, 06:34 PM   #6 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jan 2013
Posts: 10
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

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
marinajogy is offline  
Reply With Quote
Old February 8th, 2013, 08:59 AM   #7 (permalink)
Junior Member
 
Join Date: Feb 2013
Posts: 21
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default

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.
cryofy is offline  
Reply With Quote
Old February 16th, 2013, 07:28 AM   #8 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jan 2013
Posts: 10
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I typed adb kill-server coman in command prompt
but got tyhe msg bad command or file name
marinajogy is offline  
Reply With Quote
Old February 18th, 2013, 05:22 AM   #9 (permalink)
Junior Member
 
Join Date: Feb 2013
Posts: 21
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default

The 'android-sdk\platform-tools' direcotory, which contains the adb executable needs to be set in the PATH variable of your os, see How do I set or change the PATH system variable?, if you want to access is from every direcotry on your command line. Otherwise it's only 'accessible' from within the above directory.
cryofy is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Development > Application Development
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 07:28 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.