StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>Update</strong>: Starting with Android SDK Manager version 21, the solution is to edit <code>C:\Users\<user>\.android\avd\<avd-profile-name>.avd\config.ini</code> and change the value </p> <pre><code>hw.ramSize=1024 </code></pre> <p>to </p> <pre><code>hw.ramSize=1024MB </code></pre> <p><img src="https://i.stack.imgur.com/5PPAu.png" alt="Android 4.2 API 17"></p> <p>The emulator is really slow, <del>hope they will release the intel images soon</del> use the new API17 Intel x86 images if you want to change it .. (<a href="http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager/" rel="noreferrer">HAXM</a>, <a href="http://www.developer.com/ws/android/development-tools/haxm-speeds-up-the-android-emulator.html" rel="noreferrer">Configuration</a>)</p> <hr> <p><strong>Earlier Android SDK Manager releases:</strong></p> <p>Had the same problem with the built-in WXGA800 skin. I got it working by editing the virtual device setup to:</p> <ul> <li>Target 4.0.3 API 15 / 4.1.0 API 16</li> <li>SD-card 300MiB </li> <li>Resolution 1280 x 800 (set manually -not the built-in ones)</li> <li>Device ram size 1024MB (with MB added to the number)</li> <li>Abstracted LCD 160</li> </ul> <p>Here my tablet config for 4.1.0 API 16 <code>C:\Users\<user>\.android\avd\<avd-profile-name>.avd\config.ini</code></p> <pre><code>hw.lcd.density=160 sdcard.size=300M skin.path=1280x800 skin.name=1280x800 hw.cpu.arch=arm abi.type=armeabi-v7a hw.cpu.model=cortex-a8 vm.heapSize=48 hw.ramSize=1024MB image.sysdir.1=system-images\android-16\armeabi-v7a\ </code></pre> <p>This config shows the software keys too <img src="https://i.stack.imgur.com/uugIE.jpg" alt="Screenshot Android 4.1 emulator 1280x800@160"></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload