I'm a little bit freshman in Android development so the some reasons may be sound incorrect.
I have been faced with a problem that the virtual keyboard is not displayed when I run the emulator for any created AVD with the varied parameters but it appears one of the following messages just without the expected keypad:
"Hardware keyboard not enabled in AVD. Use on screen keyboard" (With deselected checkbox "Hardware keyboard present").
"Hardware Keyboard. Use your physical keyboard to provide input" (With selected checkbox "Hardware keyboard present").
Also I played around the config.ini with the flags hw.keyboard, hw.keyboard.lid, hw.touchScreen but nothing couldn't help me.
The point of my question is how to get the most common view in the right side of emulator window like this.
So, currently I have resolved my issue. All previous answers did not follow my question perhaps due to unclear explanation from my side.
So, to clarify this question, before I give an answer, the main point was: I meant that there was absent not hardware or software keyboard but the emulator own skin keyboard and couple of another buttons. I guess, my AVD Manager makes incorrect construction of AVD. It's the talk of the special config.ini file that contains two abnormal parameters:
skin.name=320x480
skin.path=320x480
After I changed it, for example, to
skin.name=HVGA
skin.path=platforms\android-XX\skins\HVGA
where XX means any version within described path to skin in Android SDK folder,
all skins are applied properly and emulator look better.
Unfortunately, I still have an issue with understanding. Why after the proper installation and configuration of dev. environment the AVD Manager formats config.ini file incorrectly with parameters hw.dPad=no, hw.trackBall=no by default and skin.name and skin.path set to the wrong values.
Related
I am using Linux Mint 18.2 and Android Studio 3.0. I started my avd nexus 5 oreo, it's running but not working computers keyboard. I couldn't write anything. Only when i can write something about hundred times try with mouse right and left click. It's silly. I check avd config.ini. Thats true and see hw.keyboard=yes.
I think it can not focus on the emulator window and so its not writing.
Like i sad the problem is emulator window is not focused.
I found two solution.
Right and left keys of the mouse to be written in the text area click quickly 3 or 4 times. (So the window focuses, if you look at the window title it will be understood. Note: You have to do this every time)
Go to your Window Manager, find Focus tab, Change Focus Model -> "Focus follow mouse". (Permanent solution which Paul Freez's answer -> https://stackoverflow.com/a/42720450/4300071)
In the lastest version of Android Studio (0.8.14) it has a great new wizard for creating/configuring an AVD. However, two key things have been removed:
Hardware Keyboard Present
and the ability to choose some pre-existing/default skins
Does anyone know if this is a bug or what to do instead? I'd like to be able to type using my keyboard into the emulator.
Selecting New Hardware Profile when creating or editing your AVD will bring up a dialog box which has a check box titled Has Hardware Keyboard.
With regard to skins if you go to the Default Skin directory search and go to {Your Android SDK Location}\tools\lib\emulator\skins then you should be able to see a dynamic skin option.
Presumably this is the folder where you should be able to add new device skins, although I'm not sure exactly where the greater range of default skins are.
I was trying to fix my problem "hardware buttons not enabled in AVD" after an hour research
all I found was people who lead people to go to "hardware section and fix blabla"
but interestingly my AVD doesn't have this section.I actually found some of options under Device Definitions but still couldnt fix my problem nor found this menu.All screenshots I saw had Hardware section...
My specs are; MacOS , Android 4.2.2 (Api17) , Eclipse
P.S:everything else works perfectly .I am just missing this section.
The instructions you were looking at were probably from R20 or earlier versions of the Android Developer Tools. R21 is different and appears to be what you are running. You change the behavior of the hardware buttons on the Device Definitions tab for whatever device is associated with your AVD:
Change the Buttons drop-down to Software or Hardware depending on what you want the behavior to be.
After lengthy trial and error, I banished the "hardware buttons not enabled in AVD" problem by discovering that there are at least three distinct 'gotchas' that must be set properly. I am using Eclipse Java EE Juno with ADT version 22.3.0 (latest as of 2013 Nov 3).
In summary, it's a bit awkward to figure out the first time, but simple thereafter. The virtual device definition must include 1) hardware buttons, 2) the device definition must also be chosen in the AVD selector drop down field, and 3) the box must be ticked for displaying a skin with hardware controls. All three are critical. Step by step:
Window → Android Virtual Device Manager (See screen capture below) (NOTE: If not visible in menu, choose Window → Customize Perspective and tick Android SDK and AVD manager - but assume this has already been done if you have gotten far enough to get the above error message)
Click the first tab, which is Android Virtual Device, click Edit, and note the name of the Device listed in the second combo box field from the top. This is going to be either a built in default Android virtual device definition, or a custom one you have created (or will create) from scratch. Make note of this Device name and close Edit Android Virtual Device edit window by clicking "OK"
Click the second tab in Android Virtual Device Manager which is Device Definitions and select the device you remember from step #2 above from the list (Note to emulator developers - this setup step is slightly more awkward than necessary - perhaps tabs one and two could be tied together more closely to allow double clicking a device and editing it directly instead of having to close a tab then opening another). After selecting the virtual device definition, choose Edit (or Clone if the device you want to edit is a built-in definition because if it is a built-in device, it must be saved as a cloned copy once edited. Name the cloned device something memorable in the top left field of the Clone Device window, e.g. add "_hardwareButtons" to the end of the default name).
IMPORTANT: Edit the cloned device: Ensure that Buttons → Hardware is chosen on the right hand side, fourth field down, of the Edit Device (or Clone Device) window (from step #3 above under Device Definitions tab). This is critically important or the Hardware buttons will not be active. This is the most likely root cause of the above error message. It's OK to leave Input as No Nav unless you want to use the virtual DPad. Click Edit Device (or Clone Device) at the bottom right of the window to save your changes.
IMPORTANT: Inside Android Virtual Device manager, click first tab again, which is Android virtual device. Select Edit and ensure that the newly edited, created, or cloned device is selected by name in the Device field drop down combo box (second from top) of the AVD. (see top two screen captures above). It is critically important that the proper device is chosen here, because creating a newly cloned device does not automatically update, or associate it with, your AVD (see my comments to emulator developers above).
IMPORTANT: Also inside the same Android Virtual Device edit box, Make sure Skin → Display a skin with hardware controls is ticked. This is also critically important or you will not see any hardware buttons at all. Click "OK" to close Edit window.
For good measure (possibly unnecessary) I clicked Refresh in the first tab (Android Virtual Device) of AVD manager and looked to be sure that a green checkmark was in front of the AVD I just edited. If not, it's probably because the newly edited device is not yet connected with your AVD. Click Edit and again choose the proper newly edited device name. Click "OK" to close.
In addition and optional for the truly paranoid, you can click Details under AVD first tab and expand the window to look at your device definition specifics. Make sure that skin.dynamic is yes, hw.keyboard: is no (unless want keyboard) and hw.mainKeys: is yes and hw.dPad: is no (unless want dPad) and, as always, ensure that you have the proper device name chosen.
Now you should have a perfectly viable AVD defined that you can use in the RUN → RUN CONFIGURATION Eclipse menu and it will not display the dreaded "hardware buttons not enabled in AVD" error message.
In Eclipse, RUN → RUN CONFIGURATION, choose your app name from the left hand side (and make sure it also appears under Android tab) and that the newly defined AVD is ticked under the Target tab and click RUN. (or CTRL+F11 after the first run of any new configuration).
Here are some screen captures from a tablet emulator as an example:
I am running Eclipse on a Windows 7 machine. Since the last update of the Android-related files (Android SDK and AVD) to version 4.1, I have a weird looking keyboard:
(this is the first part of the tutorial on the Android Developer website...)
I had a real qwerty-keyboard before, but now it is not only (partly) Japanese, but I can't seem to find how to change it to a qwerty-keyboard.
I have tried checking for updates, restarting the program and the whole PC, changing AVD keyboard settings and different virtual devices with different Android versions on them (the pic shows 2.3.3).
Thanks a lot for your help!
If you click and hold (your mouse button) in the input text box, a menu should come up with Input Method Click that and a Select input method menu should appear. Select Android keyboard and you'll be back to a standard qwerty keyboard.
Try deleting the AVD instance and create a new one. It certainly looks strange but it won't take long to create a new virtual device and boot it ... certainly more constructive than pulling your hair out
I'm using a virtual device whose target is 2.3.1. If I run any of my android applications, the keyboard will show the right side on the emulator (see the image below). But I want to show my emulator without a keyboard. How can I do this?
The two other answers work, but they are not strictly correct. The reason they work is that the resolution suggested use a skin with no keyboard.
If you want to test your application for other screen resolutions you must do the following:
Add the hardware option "Keyboard support" and set it to "no".
Either edit the skin selected, or add a startup option "-noskin" for your emulator.
Personally I prefer the "-noskin" flag, because with no keyboard, the skin does not give me anything extra.
In Edit Android Virtual Device => Skins frame you can change skin from "default" (WVGA800, for example) to "Resolution" and manually write resolution of targeted device (480 x 800, for example).
Emulator will be shown without keyboard.
You should change the resolution of Emulator when you create a new AVD. 480 X 800 can used hide the keyboard of emulator.
Today I needed to hide the keyboard when starting the emulator and this worked for me.
When emulator is started, in the android keyboard options you can disable the keyboard to hide it.