I had the same issue after upgrading the developer tools (v20.0.0v2012...). All of a sudden none of my android virtual devices would accept any input from my physical PC/Mac keyboard.
This is how I fixed it:
Eclipse > Window menu > AVD Manager
Select your virtual device and click Edit
Under Hardware, Click New
Select Keyboard Support then click OK
The Snapshot option speeds up the boot of the emulator by saving a snapshot of its RAM once it has booted, and restoring from that snapshot on future uses. That way, it doesn't have to run the boot process (which is slow, because it's emulated) every time you start the emulator.
The Use Host GPU option uses the host computer's OpenGL implementation (which ...
well wait-for-device, as you already realized only waits until the adb daemon properly started. This is already at init time. In order to check for a complete boot you cann ad to your script something like:
long as getprop sys.boot_completed != 1 sleep some seconds
check getprop sys.boot_completed again
shell input keyevent 82
1. Using command line: Here's how you can copy files to an SD card image.
You have to use adb push to copy files from Desktop to Emulator and adb pull for the reverse. Here's the syntax to copy files to or from an Emulator/Device Instance:
Copy from desktop to emulator:
adb push <local> <remote>
Copy from emulator to desktop:
adb pull <...
Please try the following settings. My environment (Target: Android 4.0.3 - API Level 15) successful.
AVD - Edit - Hardware: - New... - Keyboard support - yes
AVD - Edit - Hardware: - New... - Keyboard lid support - no
Try Android x86 as a virtual machine on Virtual Box. this is by far the best working android I have seen...
It has the basic, default Android UI.
It is fully functional.
It works 4 times faster than my HTC Sensation
Android X86 ISO files: http://code.google.com/p/android-x86/downloads/list
How to install it: http://dev.blogs.nuxeo.com/2011/10/speeding-up-...
I am using Android Studio 2.1.1 and Ubuntu 16.04 (x64). The following solved the problems (sh: 1: glxinfo: not found and libGL error:.) for me.
$ sudo apt-get install lib64stdc++6 (if it is not installed)
$ cd ~/Android/Sdk/tools/lib64/libstdc++
$ mv libstdc++.so.6 libstdc++.so.6.original
$ ln -s /usr/lib64/libstdc++.so.6 ~/Android/Sdk/tools/lib64/libstdc++
You can call between AVD's. Run 2 AVD, each will have diffrent number - it is placed on window title bar, example 5558. Call from one to other using this numbers. You can also text ;]
In your AVD you simply cannot use real celluar network because your PC/Mac do not have built-in GSM modem (even if, AVD is not supporting this kind of feature).
There are some hotkeys listed for ICS, which hopefully still work with Kitkat:
Rotating the screen: (to get that operate we must to have activated “Auto-rotate screen”)
Press F12 two times in less than 2 seconds = Rotate 90º to the LEFT.
Press F11 two times in less than 2 seconds = Rotate 90º to the RiGHT.
Press F10 two times in less than 2 ...
Have you given the Amazon Appstore's Test Drive feature a try? Super simple, runs in most browsers - simply find an app in the store for which Amazon has Test Drive available then click the big green Test Drive button (a list of Test Drive apps is here). Once you have a Test Drive session open click the home button on the bottom of the emulator to access the ...
There are 3rd-party "fake camera" apps that will let you to choose an image instead, such as:
Fake Camera by New Horizon Apps (free)
Fake Camera - donate version by Vaclav Balak (paid)
Note that you need to have the image inside the (emulator) device storage first for these apps to be useful.
Also, since these apps are not really a ...
You need to create a port forwarding to your Android device. This can be done with ADB.
adb forward <local> <remote> - forward socket connections
forward specs are one of:
localabstract:<unix domain socket name>
The Snapshot option allows you to use a feature that's similar to the Hibernate function in Windows. It saves the contents of the emulator's memory to disk when you close the emulator, so that when you open it, it doesn't have to boot the OS, but instead it can load the memory contents from the disk and resume from where you left off. This allows you to ...
How to root android emulator (Android 7.1.1/ Nougat)
I’m pleased to inform the community of an easier way to root android emulator (run from standalone Android SDK)
SuperSU app (chainfire) latest version 2.82
Recovery flashable.zip (contains su binary) (Here is alternative mirror link for flashable zip if the main link is not working : ...
This is an old question and borderline off-topic but here is how to do it in a single line:
adb wait-for-device shell 'while [[ -z $(getprop sys.boot_completed) ]]; do sleep 1; done; input keyevent 82'
You need to change the config.ini file in your .android directory. This file is found under the main hard drive directory. From there, open the avd file and you will see a list of virtual devices. Open the desired device and then open the config.ini in notepad. Then copy this text: "hw.keyboard = yes" (minus the quotes) and then save and close. The next time ...
This can happen for the following reasons:
The emulator presents an x86/MIPS CPU which the app does not support (probably not in your case as the app doesn't seem to require native code).
Google Play Services. The emulator does not have them, in fact no emulator can have them unless they licensed it from Google, and most apps depend on them.
Mobile data as ...
1) Go get GApps for the emulator from http://opengapps.org
2) Unzip to get
Launch the emulator from the command line, on linux you do
./emulator [name] -no-boot-anim -writable-system
on windows it's probably
emulator.exe [name] -no-boot-anim -writable-system
Make sure ...
This answer is for those who built the emulator from source (i.e. Following instructions from source.android.com). You need to modify a property in the following file:
In the following section of that file change the default value from no to yes:
# Keyboard support (qwerty/azerty)
name = hw....
The emulator is slow because it's an qemu that emulates a whole different CPU architecture as it's used by consumer PCs: ARM (vs. x86(_64) on your PC)
This means that every CPU instruction on the emulator's ARM CPU has to be emulated, which is per se slow. Also the emulator is AFAIK single-threaded. This means that speed-up can only be achieved by fast CPUs ...
The Android emulator doesn't currently support this, unfortunately. There is a configuration file in the build system that determines whether or not to enable the user accounts feature, and it is disabled in the emulator images distributed by Google. You can star this issue on the bug tracker in the meantime.
However there are two alternatives you can look ...
Digging through the logcat, immediately after the com.android.browser activity is launched, I found a "Fatal signal 11 (SIGSEGV)" in vold, the volume daemon that handles storage. Lots of other storage related issues in the log too. So I checked the virtual device settings one more time and noticed that the SD Card size was not specified. I had assumed that ...
Based on the comments from Google in this bugtracker - emulator support of screenrecorder isn't going to happen in the near future due to hardware requirements/limitations.
Make sure that you're not running any other virtual machines, then try again.
I was running a guest Windows 8 VirtualBox on El Capitan and I got the same error when I tried to run a virtual Android device in Android Studio. I shutdown the guest OS and VirtualBox then my AVD booted up.
You already have a working vCard file (.vcf), just import it using GMail's web interface. If this VCF is still bad, you can apply simple text processing (regex search & replace) to it before importing it to Google.
Here are the steps to import a vCard file into GMail using the web interface.
Here's an excerpt from Google's help:
Click Gmail at the ...