ChatGPT解决这个技术问题 Extra ChatGPT

Android emulator doesn't take keyboard input - SDK tools rev 20

I've upgraded the SDK tools to revision 20 (from 18) and since the upgrade, the emulator doesn't seem to accept input from laptop's keyboard. But only using the emulator's own 'soft' keyboard (that appears when an input field is focused).

I've tried reinstalling the SDK tools (and the whole SDK for that matter), uninstalled and reinstalled Eclipse Android plugins, re-created emulator devices. But none of that seem to help and its driving me mad. Its hopeless to key-in using a laptop's trackpad.

Has anyone encountered this problem?

A side effect of this seems to be that the search button in the emulator doesn't seem to work either. Thankfully, the same fix for the keyboard fixes the search button as well.
I have also found that for some apps I had to go to Extended Controls -> Send keyboard shortcuts to -> s/Emulator controls (default)/Virtual device/

G
Gili

Update

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:

https://i.stack.imgur.com/2On6A.png

If you notice that the soft (screen-based) main keys Back, Home, etc. are missing from your emulator you can set hw.mainKeys=no to enable them.

https://i.stack.imgur.com/Bva7C.png

Original answer

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!

Add: hw.keyboard=yes

To: ~/.android/avd/<emulator-device-name>.avd/config.ini

Similarly, add hw.dPad=yes if you wish to use the arrow-keys to navigate the application list.

Reference: http://developer.android.com/tools/devices/managing-avds-cmdline.html#hardwareopts

On Mac OS and Linux you can edit all of your emulator configurations with one Terminal command:

for f in ~/.android/avd/*.avd/config.ini; do echo 'hw.keyboard=yes' >> "$f"; done

https://i.stack.imgur.com/LB9Q1.png

Or by manually setting the skin in config.ini:

skin.name=WXGA800
skin.path=platforms/android-16/skins/WXGA800

(example is for API 16)


As the other answers mentioned you can use the AVD Manager tool as well but I have experienced bugs that prevent it from saving config changes.
Is there any global setting that will affect all of my existing avd? I don't want to change about 20 existing avd.
Editing the config file worked for me, but oddly I don't see the UI shown in the picture, despite having version 21 of the SDK.
It happened again. I had a working emulator hardware keyboard, then upgraded from SDK 25.0.3 to 26.0.x and the hardware keypoard stopped working. The same answer fixes the problem though. But, I wish I knew why/how the emulator setting was changed.
you can open the avd manager tool via android avd at a commandline. androiddocs.com/tools/devices/managing-avds.html
M
MyNameIsAnz

Confirmed. I had the same problem after upgrading to Tools version 20. I had to Edit the AVD to add an option as follows:

From Eclipse, Go to AVD Mananger. Select the particular AVD and click on Edit Go to the Hardware section, click on New. Select the Property Name : Keyboard Support By default, it is added with a value of 'no'. Just click on the value column and change it to 'yes'. Click on Edit AVD again.

This will add a property hw.keyboard=yes in config.ini file for the AVD.

You also have to set hw.mainKeys = yes


Make sure the value column loses focus before clicking Edit AVD or the change to 'yes' will not be saved!
Hi, I followed the above instructions, but still can't insert any text using my PC key board. When I double click on the AVD listed under the AVD Manager, I find that the edit is successful as it indicates hw.keyboard:yes. Am I missing something???
I suggest the following : Delete the AVD and create a completely fresh AVD with the Keyboard support.
H
Hong

https://i.stack.imgur.com/ihoEK.png

https://i.stack.imgur.com/I0NHJ.png

https://i.stack.imgur.com/DHZ5t.png

Click Finish and start the emulator to enjoy the keyboard input.


Worked for me after enablinh keyboard input setting but wondering how did it stopped working by itself in first place.
It is so frustrating that this checkbox unchecks itself after every emulator update :(
In my case, keyboard was enabled, but did not work in the emulator. The fix is to disable keyboard, start emulator, terminate emulator, enable keyboard.
J
Joel Pelaez

Look in AVD Manager, select the AVD and click in Edit. In Hardware section: click in "New" and search for "Keyboard support" and add with OK button and set the value to "yes" and save changes with "Edit AVD"


weird thing is, when i set this value to yes, it forces the value back to no, anyway will test with a new Device again
I preferred this answer. Using the AVD manager is a more memorable solution than changing the config.ini file.
V
Vincy

Google wanted to give some more headache to the developers.

So, what you have to do now is edit your AVD and add "Keyboard Support" for it in the Hardware section and change the value to "Yes"


Didn't work for me, the avd keyboard support value of "yes" doesn't stay saved, it keeps reverting back to "no".
Actually Google wanted to improve things. Most devices now don't have hardware keyboards, so the default should be none/disabled. Yeah, it's easier to work with the emulator with one, but that's not mirroring real world conditions. The correct way is to make devs specifically enable it.
N
Nerower

Add the following line hw.keyboard=yes to your AVD config file ~/.android/avd/<avd_folder>/config.ini


s
starbeamrainbowlabs

Restarting the emulator helps sometimes when typing is unavailable - despite keyboard input being enabled for your Android Virtual Device.


P
PbxMan

Just in case somebody finds it usefull.

I had a problem with the KEYCODE_DPAD_UP it belongs to the trackBall. to solve this change your avdfolder/config.ini hw.trackBall=yes and push DEL or F6


W
Witold

Here is some workaround that actually worked for me, it is the same solution as in the most popular answer - just add hw.keyboard=yes to config.ini but since this didn't work for me I additionally

renamed config.ini (any name will do) to something like consssssfig.ini restarted emulator (obviously it didn't start) renamed config.ini back again (I am not sure if relevant) I added this new parameter (hw.keyboard=yes) at the beggining of config.ini file


w
wilddev

Sometimes computer keyboard stops working on android emulator. Today I've noticed, that after pushing this button (that I marked with red arrow), keyboard starts working again (seems to be some issues with emulator window focus)

https://i.stack.imgur.com/ghfkQ.png


E
Eric Cloninger

Look for the hidden .android folder in your user home folder. You might rename or delete this folder, recreate your AVD, and restart the emulator. It could be there is a .ini file in that folder that has that setting munged.


yes i did delete the .android and avd files too.. did not help though. thanks for the input
D
Davek804

Recreating an AVD with the Hardware Keyboard + setting the boolean to true was the only solution that worked for me; the other two main solutions (terminal or editing an existing AVD via GUI) both resulted in software/emulator crashes on my Mac. Making a new AVD resulted in the keyboard working just fine.


p
persec10000

I have used an emulator for API Level 23, which does not take keyboard input for installed apk. So I have created new emulator for API Level 29, and then it works. Following is the step to install new emulator.

Open "Android Virtual Device Manager" Create new Virtual Device. When you select a system image, please choose and download the last version(API Level29) on "Virtual Device Configuration" window