I am using android sdk 4.0.3 ,I have created an Emulator of it. Now I have a problem that the emulator is showing the Disabled DPAD Buttons .I have set up the Hardware keyb
Every emulated device is based on a more or less real device, which you chose as '4.0" WVGA (480x800:hdpi)' this doesnt only concern the resolution of your emulated device bur also its hardware features. In the main screen of the avd-manager enter the tab that says device definitions. there you can edit your chosen device and you will find the dpad under input.
You have to uncheck the hardware keyboard present option. It would then be enabled. So the option would be
Display a skin with hardware controls - true
Hardware keyboard present - false
This sounds crazy, but it worked for me:
~/.android/avd/XXXX.avd/config.ini
INI
file.config.ini
:hw.dPad=no
to hw.dPad=yes
dPad=no
when you click on Details. It appears to not catch on until the virtual device is started. (Clumsy? yes)hw.dPad=yes
I ran into this while trying to bring up the "Snake" demo. It failed to run, asking to press the UP key -- and the pad didn't respond! After getting DPAD set, the demo can be controlled through the pad.
This appears to be a bug in the AVD Manager. If you get dPad set to 'yes', it can be set to 'no' through the AVD Manager. But changing 'no' to 'yes' requires the above workaround.
I found this solution in a different file. I am using SDK version revision 20.
Edit
.C:\Users\%USERNAME%\.android\avd\YOUR_AVD_NAME
folderEdit config.ini
as
hw.dPad=no --> hw.dPad=yes
. Clone Device Definitions with enable keyboard
Enable Input -> Keyboard.
For your previous AVD, So you wouldn't face this problem anymore in the future.
The virtual device folder has a config file , just like my Mac OS X and a VM(A17) :
~/.android/avd/A17.avd/config.ini
change
hw.dPad=no
to
hw.dPad=yes