2

To increase performance, I want to allocate 1024 MB RAM to a tablet emulator. Problem is that it won't start, i.e. no windows/consoles show up when I click Start in the Virtual Device Manager. If I let the device to its default 256 MB, it starts. How can I fix this?

I'm using Windows 7 Ultimate with Intel i7-2.2 GHz and 8 GB RAM DDR3. It used to work fine on 32-bit windows.

Kara
  • 6,115
  • 16
  • 50
  • 57
Gabriel
  • 2,054
  • 4
  • 26
  • 34
  • Is it an issue of changing the default (i.e., only works on the default setting) or is it only an issue when you set it to a size that's "too big"? As a quick test, will it work with 512? – Jon O Apr 17 '12 at 13:56
  • worked with 512, but not with larger RAM – Gabriel Apr 17 '12 at 14:02
  • try to make priority high to the AVD process – haythem souissi Apr 17 '12 at 14:09
  • @haythemsouissi still the same. I also got a dialog that the emulator process crashed – Gabriel Apr 17 '12 at 14:25
  • Just had a thought: if you try to run it via command line, do you get any output back? There's a how-to on running the emulator from the command line here: http://stackoverflow.com/questions/4974568/how-do-i-launch-the-android-emulator-from-the-command-line – Jon O Apr 22 '12 at 17:02

2 Answers2

4

I know this isn't an answer to the particular question you have asked, but it may help with the underlying issue: you can increase the performance of your emulated device by switching to an x86 version.

The Android emulator has always been painfully slow for me, even on a quad core rig with 8 gigs of RAM, so I started following the Android x86 project. Not long ago, I finally took the plunge into getting it set up, and it was easier than I expected--and it's really, really fast.

If you have VirtualBox installed, all you have to do is download eeepc.iso from the project's website (for whichever Android version you prefer), create a VM for it in VirtualBox with however much RAM you want it to have, and boot it up. Pick VESA mode from the menu, disable mouse integration on the VM, and skip the google account login process. You'll be good to go.

Then just set up port forwarding for ADB from guest:5555 to localhost:whatever-port-you-choose, and point ADB at localhost:whatever-port-you-choose, and it'll work even better than the ARM emulator that ships with the SDK.

Jon O
  • 6,532
  • 1
  • 46
  • 57
  • Works for 2.3 eeepc. I appreciate your answer. Although it isn't 100% on topic, it helps a lot, since it works a lot faster than the standard arm emulators. If I don't get an answer to help me fix my problem with the ARM emulators by the end of the bounty, I'll mark this as the correct answer – Gabriel Apr 22 '12 at 14:11
0

I disabled the camera support and I was able to use 1024MB of RAM.

Nikhil
  • 16,194
  • 20
  • 64
  • 81
4g0st1n0
  • 1