I am new to android development and installed the ADT. I have Created AVD and launched the emulator. But the problem is that I don't see the call button enabled. Can anyone please let me know what I am doing wrong here?
Some AVD device definitions disallow the AVD from displaying "hardware controls". You can change the settings for this in the Eclipse AVD manager, if that's what you're using, or you can alter the AVD class settings for the device by hacking the files that tell the IDE what (let's just say a Nexus 7) the physical device is like. A Nexus 7 has an all-glass screen, so no "virtual button" will show up on emulator, but if you emulate an older android flip phone with a physical keypad, the AVD emulator will show those as "virtual buttons".
You can go hack the device definition files by hand in a text editor to allow virtual "hardware buttons" to show up in the emulator (look for something like "hardwarekeys=true",
or you can chose another device to emulate that actually came with physical buttons, since that AVD definition will already be set to display some virtual "buttons".
Related
I am new to android development, I want to know how can we add Samsung galaxy devices/skin into my emulator?
I can able to add skins of Samsung galaxy but can't see in AVD manager.
I need help to understand this.
Steps to add new skin into your Android Emulator:
Need to download the skin of your desired device, Recommended URL https://developer.samsung.com/galaxy-emulator-skin/galaxy_note_series.html to download
Then unzip this downloaded file, Now copy and paste this to /Users/YourUserName/Library/Android/sdk/platforms/android-29/skins
Launch android studio and open AVD manager
Now we need to add a device definition for that recently added skin
In AVD manager click to this create virtual device option
Now you will see the an option for New Hardware Profile option at the bottom left of this popup.
Click to this New Hardware Profile, you will get a popup for Configure Hardware Profile. Add device and device type then scroll down and you will find an option for Default skin dropdown, Choose your newly added skin
Afterwards press this finish button at the right bottom and you are done with device definition configuration.
Now you can create your own virtual device with this newly added device definition.
I cannot get an Android Virtual Device to launch on my Surface Pro. I have had no problems on Windows XP, 7, or OS X.
I have tried launching from the AVD Manager, it opens the option dialog and when I select launch it acts like it is working, however the emulator never shows up.
When I select Run As Android Application from a project it acts like it is starting, once again nothing ever shows up.
Either way I get no error messages in the console.
I have tried disabling UAC.
Thanks for your help.
Right-click the program's icon and choose Properties.
When the Properties dialog box appears, click the Compatibility tab and then click the Run Compatibility Troubleshooter button.
Windows 8 tries to guess what version of Windows your program needs, and then it applies the changes. If the program begins working, you're through.
If the program still has trouble, though, move to Step 3.
In the Compatibility Mode section, select the Run This Program in Compatibility Mode For check box and select the program's desired Windows version from the drop-down list.
http://www.reddit.com/r/Surface/comments/1ael60/surface_pro_and_dj_software_also_android/
Please refer to my question and answer here:
< Android Emulator and AVD will not run on Surface Pro >
As it turns out you can run the Android Emulator and AVD on the Microsoft Windows 8 Surface Pro.
You will need to rollback the graphic drivers:
< http://answers.microsoft.com/en-us/windows/forum/windows_8-hardware/latest-graphics-driver-update-makes-bluestacks/1f67d99f-3626-4110-aa22-773856b226cb > Method 1: I would suggest you to roll back to the previous driver.
a) Press Windows key + X on the keyboard.
b) Click Device Manager.
c) Double-click on Display Adapters.
d) Double-click on your Graphic Card Drivers
e) Select the Driver Tab
f) Click on Roll Back Driver.
I still recommend using Bluestacks as an alternative method for Android Emulation.
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 keyboard present and display skin with buttons option in configuration.
So i just want to enable the Dpad Buttons on emulator
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.
This sounds crazy, but it worked for me:
Launch a fresh emulator from the Android Virtual Device(AVD) Manager.
Note: "DO NOT START THE DEVICE".
Find the configuration file, something like: ~/.android/avd/XXXX.avd/config.ini
Notice that this directory has only one INI file.
Edit config.ini:
change hw.dPad=no to hw.dPad=yes
The AVD Manager will still show dPad=no when you click on Details. It appears to not catch on until the virtual device is started. (Clumsy? yes)
Start the device. It should show DPAD without the complaint about it not being there.
The DETAILS button in AVD Manager should also show 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.
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
I found this solution in a different file. I am using SDK version revision 20.
Create a fresh AVD from you AVD manager.
There is no option in AVD manager to enable DPAD. I tried even by clicking Edit.
Go to C:\Users\%USERNAME%\.android\avd\YOUR_AVD_NAME folder
Open hardware-qemu.ini file. Here you will get all hw config details.
There you will find hw.dPad = no; Change it to hw.dPad = yes and save the file
Restart your AVD and Voila !!! DPAD is now enabled in Emulator.
Edit 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.
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
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:
Hi I have a Android application that I am trying to run on a tablet in eclipse. However, when I run it I can only open it in a phone view. I went to the properties and changed it to Android 3.1 but that did not fix the problem. Does anyone know the fix here? Thanks
If you mean that you need the emulator to show such kind of display, just change the kind of display you need. Go to the AVD manager and create a new virtual device:
Eclipse: Window -> AVD manager -> new
Choose appropriate Android version. Then for the display choose appropriate skin (e.g. WXGA, which is tablet). After you create this virtual device, you can run your code against it. If the device is still run in portrait mode, you can always flip it using ctl + f12 to landscape.