Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>Update</strong></p> <p>As of SDK rev 21 the Android Virtual Device Manager has an improved UI which resolves this issue. I have highlighted some of the more important configuration settings below:</p> <p><img src="https://i.stack.imgur.com/2On6A.png" alt="enter image description here"></p> <p>If you notice that the soft (screen-based) main keys <code>Back</code>, <code>Home</code>, etc. are missing from your emulator you can set <code>hw.mainKeys=no</code> to enable them.</p> <p><img src="https://i.stack.imgur.com/Bva7C.png" alt="enter image description here"></p> <p><strong>Original answer</strong></p> <p>Even though the developer documentation says keyboard support is enabled by default it doesn't seem to be that way in SDK rev 20. I explicitly enabled keyboard support in my emulator's config.ini file and that worked!</p> <p>Add: <code>hw.keyboard=yes</code></p> <p>To: <code>~/.android/avd/&lt;emulator-device-name&gt;.avd/config.ini</code></p> <p>Similarly, add <code>hw.dPad=yes</code> if you wish to use the arrow-keys to navigate the application list.</p> <p>Reference: <a href="http://developer.android.com/tools/devices/managing-avds-cmdline.html#hardwareopts">http://developer.android.com/tools/devices/managing-avds-cmdline.html#hardwareopts</a></p> <p>On Mac OS and Linux you can edit all of your emulator configurations with one Terminal command:</p> <p><code>for f in ~/.android/avd/*.avd/config.ini; do echo 'hw.keyboard=yes' &gt;&gt; "$f"; done</code></p> <hr> <p>On a related note, if your tablet emulator is missing the BACK/HOME buttons, try selecting <strong>WXGA800</strong> as the Built-in skin in the AVD editor: <img src="https://i.stack.imgur.com/LB9Q1.png" alt="enter image description here"></p> <p>Or by manually setting the skin in config.ini:</p> <pre><code>skin.name=WXGA800 skin.path=platforms/android-16/skins/WXGA800 </code></pre> <p>(example is for API 16)</p>
 

Querying!

 
Guidance

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