Ok got an update on this one:
First I thought it might be my virusscanner (nod32) because I saw at
the same time quite often ekrn.exe also getting relatively high in CPU
usage (20-20%). Set .img files to be excluded from scans. But it might
just have been a regular background scan (and always been there), and
I only started to notice it because I was looking for a cause of the
slow machine. I did install another antivirus (avast), which seemed
to do fix the slow emulator. But after 2 days: again slow emulator.
Then I found out the real reason: my laptop was getting too hot! After
I let it cool down (until the fan doesn't make much noise anymore and
the casing is a lot cooler), I noticed the emulator ran at the normal
speed again! By running less programs I was able to keep the
temperature low enough for longer periods. Would I start too many
programs, it would get too hot again after a while (fan made more and
more noise, casing getting hot), causing CPU usage to go up. Reason
for that is that the laptop starts to run slower when it gets too hot,
causing heavy programs quickly to take up a lot of CPU percentage
wise.
After making sure my fans were running fine via some software like
speedfan, it could only be the hardware. Turns out there was a lot of
dust blocking the side air-input of the fan (only visible after
unscrewing the fan). After removing that the laptop hasn't gotten that
hot anymore nor a slow emulator. So all is running fine again at
normal speed.
So this might have been specifically my setup, but maybe yours has the
same problem...
Hope this helps anybody.
On 2 jul, 13:11, Brad Gies <rbg...@gmail.com> wrote:
> I have the same issue... and I have even more memory than you have.. :(
>
> On 02/07/2010 9:50 AM, MarcoAndroid wrote:
>
>
>
>
>
> > Oh and when it's slow and I check memory usage (via windows task
> > manager), at most 2G is in use.
>
> > On 2 jul, 15:32, Kostya Vasilyev<kmans...@gmail.com> wrote:
>
> >> Marco,
>
> >> Do you have enough physical memory in your computer?
>
> >> -- Kostya
>
> >> 02.07.2010 17:15, MarcoAndroid пишет:
>
> >>> Small update: I even created a new 1.6 avd, but that starts up as slow
> >>> as the old one.
> >>> Then I finally did a reboot of my machine --> all ran fine again for a
> >>> few hours. So apparently something was still running/hogging the
> >>> emulator. As said, after a few hours slowness kicked in again.
>
> >>> On 1 jul, 16:15, MarcoAndroid<marco...@gmail.com> wrote:
>
> >>>> Hello,
>
> >>>> More and more the Android emulator launched via Eclipse (via Run As
> >>>> Android Application) keeps slowing down, or the device is not found,
> >>>> or the user data image is in use by another emulator.
>
> >>>> I've searched and search the internets ;) but none of the solutions
> >>>> mentioned work (these are: delete pid file, setting ANDROID_SDK_HOME,
> >>>> making sure my avds are on local disk). Below I'll post a couple of my
> >>>> experiences trying to solve it. I couldn't solve it, but maybe
> >>>> somebody sees something familiair or it might help other people
> >>>> finding the problem.
>
> >>>> Below you see an example of suddenly the device not being found
> >>>> anymore.
> >>>> First there's a normal launch (09:54:13), then there's a second one
> >>>> (started 30 secs after the previous one) that just fails. I waited
> >>>> quite a long time (no high CPU for the emulator), then 'device not
> >>>> found' after about 4mins. Notice it didn't get to starting the
> >>>> Activity (which it did for the first run). Also notice that the
> >>>> Success took 4mins to appear instead of 2 seconds for the first run.
> >>>> So it says device not found, but the emulator is running, I can see
> >>>> it, it's eating cpu.
> >>>> Why would it not find it anymore? Could something like this be caused
> >>>> by my network card being gone for a split second? Or my internet
> >>>> connection gone for a few seconds (doubt it, it's all local right?) I
> >>>> didn't notice it being away, but maybe it did under water.
>
> >>>> [2010-07-01 09:54:13 -
> >>>> MediaControllerCode]------------------------------
> >>>> [2010-07-01 09:54:13 - MediaControllerCode]Android Launch!
> >>>> [2010-07-01 09:54:13 - MediaControllerCode]adb is running normally.
> >>>> [2010-07-01 09:54:13 - MediaControllerCode]Performing
> >>>> com.test.code.MediaControllerCode activity launch
> >>>> [2010-07-01 09:54:13 - MediaControllerCode]Automatic Target Mode:
> >>>> using existing emulator 'emulator-5554' running compatible AVD
> >>>> 'HVGAsdk1.6'
> >>>> [2010-07-01 09:54:13 - MediaControllerCode]Uploading
> >>>> MediaControllerCode.apk onto device 'emulator-5554'
> >>>> [2010-07-01 09:54:13 - MediaControllerCode]Installing
> >>>> MediaControllerCode.apk...
> >>>> [2010-07-01 09:54:15 - MediaControllerCode]Success!
> >>>> [2010-07-01 09:54:15 - MediaControllerCode]Starting activity
> >>>> com.test.code.MediaControllerCode on device
> >>>> [2010-07-01 09:54:17 - MediaControllerCode]ActivityManager: Starting:
> >>>> Intent { cmp=com.test.code/.MediaControllerCode }
> >>>> [2010-07-01 09:54:44 -
> >>>> MediaControllerCode]------------------------------
> >>>> [2010-07-01 09:54:44 - MediaControllerCode]Android Launch!
> >>>> [2010-07-01 09:54:44 - MediaControllerCode]adb is running normally.
> >>>> [2010-07-01 09:54:44 - MediaControllerCode]Performing
> >>>> com.test.code.MediaControllerCode activity launch
> >>>> [2010-07-01 09:54:44 - MediaControllerCode]Automatic Target Mode:
> >>>> using existing emulator 'emulator-5554' running compatible AVD
> >>>> 'HVGAsdk1.6'
> >>>> [2010-07-01 09:54:44 - MediaControllerCode]Uploading
> >>>> MediaControllerCode.apk onto device 'emulator-5554'
> >>>> [2010-07-01 09:54:44 - MediaControllerCode]Installing
> >>>> MediaControllerCode.apk...
> >>>> [2010-07-01 09:58:32 - MediaControllerCode]Success!
> >>>> [2010-07-01 09:58:32 - MediaControllerCode]Failed to upload
> >>>> MediaControllerCode.apk on device 'emulator-5554'
> >>>> [2010-07-01 09:58:32 - MediaControllerCode]java.io.IOException: device
> >>>> (emulator-5554) request rejected: device not found
> >>>> [2010-07-01 09:58:32 - MediaControllerCode]Launch canceled!
>
> >>>> And when I try it again after the above device not found problem I
> >>>> get:
>
> >>>> [2010-07-01 10:01:26 -
> >>>> MediaControllerCode]------------------------------
> >>>> [2010-07-01 10:01:26 - MediaControllerCode]Android Launch!
> >>>> [2010-07-01 10:01:26 - MediaControllerCode]adb is running normally.
> >>>> [2010-07-01 10:01:26 - MediaControllerCode]Performing
> >>>> com.test.code.MediaControllerCode activity launch
> >>>> [2010-07-01 10:01:26 - MediaControllerCode]Automatic Target Mode:
> >>>> launching new emulator with compatible AVD 'HVGAsdk1.6'
> >>>> [2010-07-01 10:01:26 - MediaControllerCode]Launching a new emulator
> >>>> with Virtual Device 'HVGAsdk1.6'
> >>>> [2010-07-01 10:01:26 - Emulator]emulator: ERROR: the user data image
> >>>> is used by another emulator. aborting
>
> >>>> Totally weird, there's only one emulator.exe running (windows XP) and
> >>>> Eclipse, just like the first 2 runs.
>
> >>>> I know I can clear the locks, but that just restarts my emulator, so
> >>>> that's the same as exiting& starting it again.
> >>>> Starting the emulator outside Eclipse only works a few times, then it
> >>>> says again that the user data image is used by another emulator.
>
> >>>> I've tried Automatic target mode and specifying the correct avd image
> >>>> in the run configuration (for 1.6 and 2.1 avds). Didn't matter.
>
> >>>> I've also tried adding the -wipe-data flag at each start, but that
> >>>> doesn't change anything. Tip: an emulator *does* get slow when it gets
> >>>> full (run 'adb shell df' to see if your emulator is filling up). Then
> >>>> use the -wipe-data flag to clean up (note that user data gets wiped!)
>
> >>>> Is the DDMS maybe locking the emulator in some way at certain times?
> >>>> It definitely sometimes happens when I click the emulator in DDMS and
> >>>> then try to relaunch (redeploy) the same app.
>
> >>>> Also strange: when I launch another app (after exiting the emulator),
> >>>> it will start a new emulator but with the previous app already
> >>>> started!
> >>>> For some reason it is thinking that's still running? Or is Eclipse
> >>>> telling it?
>
> >>>> I did notice this: after first DDMS detecting the emulator being
> >>>> online, after a little bit it is just gone from the list of Devices!
> >>>> Something is apparently taking over the emulator or it can't be found
> >>>> anymore by DDMS it seems? Of course emulator.exe is still running.
>
> >>>> And sometimes after a couple of deploys the emulator just slows down
> >>>> terribly. CPU goes up to at least 50% (windows XP btw).
> >>>> Then stopping the current one and starting a new emulator might take a
> >>>> looong time again to start: shiny android logo showing much longer
> >>>> than usual, it shows No Service when it finally gets to the homescreen
> >>>> of the "phone", after a while it then shows Android finally. And then:
> >>>> Errors in console:
> >>>> [2010-07-01 14:49:32 - Logcat]device (emulator-5554) request rejected:
> >>>> device not found
> >>>> java.io.IOException: device (emulator-5554) request rejected: device
> >>>> not found
> >>>> at com.android.ddmlib.AdbHelper.setDevice(Unknown Source)
> >>>> at com.android.ddmlib.AdbHelper.executeRemoteCommand(Unknown
> >>>> Source)
> >>>> at com.android.ddmlib.Device.executeShellCommand(Unknown
> >>>> Source)
> >>>> at com.android.ddmuilib.logcat.LogPanel$3.run(Unknown Source)
> >>>> Logcat output is empty, emulator runs at 5%.
>
> >>>> At this point (worked for about 5hrs coding, deploying, exiting
> >>>> emulator, waiting, starting emulator etc) the emulator just won't in
> >>>> any reasonable time anymore, even after multiple exits and startups of
> >>>> Eclipse + the emulator. It takes about 10 minutes to see the main
> >>>> screen, after which I get popups in the emulator saying
> >>>> android.process.media not responding, application alarm clock not
> >>>> responding. After I clicked Wait for both, my app is still not
> >>>> showing.
> >>>> After exiting eclipse + emulator I did check if there's no more
> >>>> emulator stuff running (I only know to look for emulator.exe).
>
> >>>> And finally what I tried: turning off boot animation didn't make any
> >>>> change.
>
> >>>> Anybody?
>
> >>>> Regards,
> >>>> Marco
>
> >> --
> >> Kostya Vasilev -- WiFi Manager + pretty widget
> >> --http://kmansoft.wordpress.com
>
> --
> Sincerely,
>
> Brad Gies
> -----------------------------------------------------------------------
> Bistro Bot - Bistro
> Blurbhttp://www.bgies.comhttp://www.bistroblurb.comhttp://www.ihottonight.com
> -----------------------------------------------------------------------
>
> Never doubt that a small group of thoughtful, committed people can
> change the world. Indeed. It is the only thing that ever has - Margaret Mead
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
