Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.
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.