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

Apps Slow, buggy emulator?

DaveInNYC

Member
Nov 7, 2009
52
3
When I try to run apps in the emulator via Eclipse, the emulator always takes a LONG time to load, and when it finally does, I get messages indicating various core services are not responding. Does anyone else experience this? I find it MUCH faster to just keep re-installing my app on my Droid and running it from there.
 
When I try to run apps in the emulator via Eclipse, the emulator always takes a LONG time to load, and when it finally does, I get messages indicating various core services are not responding. Does anyone else experience this? I find it MUCH faster to just keep re-installing my app on my Droid and running it from there.


Need a little more info to help you out man... What version of eclipse, what version of SDK... How did you set your emulator? what version is your emulator running? did you add the other core stuff in like sd etc? need to know how your set up to help... If you'd prefer you can pm me....
 
Upvote 0
Hey

Might be a stupid question, so no offence :)
You don't restart it everytime you run your project right? So you let it running, right?

Just because your explanation sounds like you're closing the emulator window after each launch.


Cheers

Not a stupid question, I'm just a stupid developer :eek:

I am indeed closing the emulator after each run; I am a long time desktop app developer (last time I tinkered with mobile development was with the Palm Pilot) and am just used to that way of doing things (close your app when you are done, though in this case I am treating the emulator as the "app"). I'll RTFM and see how to do it the right way.

That being said, the emulator seems to run slow, even after startup is complete.
 
Upvote 0
Need a little more info to help you out man... What version of eclipse, what version of SDK... How did you set your emulator? what version is your emulator running? did you add the other core stuff in like sd etc? need to know how your set up to help... If you'd prefer you can pm me....

Eclipse 3.5.1
Android SDK 2.0

Haven't added any other core stuff. Created the emulator AVD per the Hello World sample at Hello, World | Android Developers. Looking back on this, it creates a 1.5 emulator; I am guessing the version mismatch could be causing some issues.

As I said in my other post, I obviously need to RTFM instead of just following the Hello World instructions. Specifically, Developing In Eclipse, with ADT | Android Developers. If there is anything else I missed, please let me know.

Thanks!
 
Upvote 0
I am just playing around right now, learning the environment. What I am going to try to develop as my first app is something to make the Droid sleep/wake when going into/out of a Blackberry holster, instead of going into alarm clock mode. I really miss that from my BB.

My UI skills are wretched (no matter how well I know the platform), so I'm going to stick with little utility apps.
 
Upvote 0
Eclipse 3.5.1
Android SDK 2.0

Haven't added any other core stuff. Created the emulator AVD per the Hello World sample at Hello, World | Android Developers. Looking back on this, it creates a 1.5 emulator; I am guessing the version mismatch could be causing some issues.

As I said in my other post, I obviously need to RTFM instead of just following the Hello World instructions. Specifically, Developing In Eclipse, with ADT | Android Developers. If there is anything else I missed, please let me know.

Thanks!

Do you mind if I ask what you did to fix this? I am having the same issue you are having, and have tried creating multiple AVDs but always have the same issue.
 
Upvote 0
since i keep stumbling across this thread when googling about emulator issues... in case others do as well:

youwave cannot yet be used directly from eclipse.
last word i've found from the youwave-developer is that getting that to work is "not a high priority" for him.

so you would have to compile the apk and load it up in youwave manually each time you want to test the app you are working on. that seems more of a pain than simply connecting your phone to the computer...
 
Upvote 0
here's btw a great tutorial for using android-x86 for debugging... it really is awesome!!

http://androiddevnotes.com/2011/03/08/1299521520000.html

one thing i should note - i don't know whether it was just coincidence but i couldn't get the custom resolutions to work. i decided to give it up and just create the data/sdcard partitions instead. after that, i gave the resolutions one more shot and... tadaa! there they were. in case somebody else has troubles getting custom resolutions to work as well.
 
Upvote 0
I am new to Eclipse and Android development, and I too am finding Eclipse buggy. It does not always rebuild my project even though I have gone back to the previous version that had no errors (manually be retracing my steps). Typically, Eclipse says it can't find a resource that is there or that my app is already running when I closed the emulator before doing the rebuild. I have tried many workarounds to get Eclipse to rebuild my project with inconsistent results. For example, one time merely closing and reopening Eclipse got it to rebuild my project. I did not resave or make any changes to the code beforehand. Yet Eclipse was able to rebuild my project just because I had closed and then reopened it.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones