I am trying to use android virtual device as emulator for my appium scripts but while creating AVD I am not getting any option to select under CPU drop down
I have installed android studio bundle and have installed system images for Android 7.1.1. Below are images for same:
Please help me how can I resolve this issue.
You can clearly see the message in the CPU drop down saying "No System image installed for this target".
Just install the remaining unchecked System Images(Except Android TV and Android Wear) for Android 7.1.1 and try. It should work.
Related
I built simple cordova android app, for that I'm trying to run in my physical android mobile.. but it showing
No target specified and no devices found, deploying to emulator
No emulator specified, defaulting to VisualStudio_android-23_arm_phone
Waiting for emulator to start...
Any suggestions or help would be appreciated.
I recommend not to use the built in Android emulators from Visual Studio. Instead, download the Android SDK Manager and then change your Visual Studio's ANDROID_HOME path to use it:
To download and update the Android SDK standalone refer to Download System Images and create Android emulator in that page.
Notice that if using VS2017, your Deploy to Emulator option will be gone, but there are workarounds to keep deploying to emulator manually.
I got a new laptop this week (Win10), installed Visual Studio 2015 community, followed by Xamarin. I've created a blank Android project, uncommented the SetContentView(...) line in MainActivity.cs, then build the solution. However I'm running into various problems when I try to run it:
The list of emulators (next to the green "run" button) only contains two entries: "Android_accelarated_x86 (Android 6.0 - API 23)" and "Android_ARMv7a (Android 6.0 - API 23)". Is this normal? The Xamarin doc'n seems to suggest that a number of "Xamarin xxx" emulators would be installed.
When I run the project against "Android_accelarated_x86", the emulator starts up, Visual Studio reports the deployment is successful, but Visual Studio stops debugging. In the output window I see this:
InspectorDebugSession(0): StateChange: Start -> EntryPointBreakpointRegistered
InspectorDebugSession(0): Constructed
Android application is debugging.
Couldn't connect to logcat, GetProcessId returned: 0
InspectorDebugSession(0): HandleTargetEvent: TargetExited
InspectorDebugSession(0): Disposed
If I hit run again, the app seems to start on the emulator, but then a message appears saying "Unfortunately xxx has stopped" (where xxx is my project name). The above messages appear in the VS windows again (apart from the one about 'Couldn't connect to logcat...').
I've also noticed that the "Manage Virtual Devices" item in the dropdown is greyed out, so I presumably can't try creating a different emulator?
Shooting from the hip on this one but do you have the Android SDK installed? It should install a number of other emulators and give you access to the device manager.
There are emulators you can INstal with Visual Studio. Emulators that come with the Android SDK and emulators that install with Xamarin Studio.
One additional thing to try would be to install Xamarin Studios. It does a slightly better job in my experience of setting up your environment then VS Does.
Firstly, the Manage Virtual Devices is referring to Xamarin Android Player VMs (which is now deprecated). We're working on getting this removed if Xamarin Android Player isn't present.
To create / edit / fix your Google AVD VMs you should select Android Emulator Manager. Regarding the number of devices listed, I'd probably ensure everything Xamarin is updated..
Visual Studio > Tools > Options > Xamarin > Other > Check for Updates
..and also update all your SDK components. If you have an Intel CPU you should use the x86 images for best performance. If you haven't already installed this you can get it here:
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
If you update any images it could be that your AVD needs repairing, which you can do in the Android Emulator Manager by selecting the relevant image and clicking Repair.
Also, you will only be able to deploy to devices that your project is targeting, so it's worthwhile checking the AndroidManifest.xml or by right-clicking your project and checking the 'minimum' and 'target' Android API levels to ensure you're encompassing the AVDs you have created.
I am trying to run a phonegap application for android on my OSX.
when I try to run phonegap through CLI I get this
No target specified and no devices found, deploying to emulator
Error: No emulator images (avds) found.
1. Download desired System Image by running: /Users/susanne/Documents/roger/02_Onni/09_development/application/android-sdk-macosx/tools/android sdk
2. Create an AVD by running: /Users/susanne/Documents/roger/02_Onni/09_development/application/android-sdk-macosx/tools/android avd
HINT: For a faster emulator, use an Intel System Image and install the HAXM device driver
I have done no 1. but I cannot find the 'android avd' file mentioned in number 2. Also even though I connect an android device it does not find it.
I would be very happy if anyone could help. This is probably not a phonegap specific question but rather an Android question.
This problem is because of you didn't created device. So you have to firstly create the device in android sdk.
For creation of android device you have to install the avd first.
i have some screenshot hope help you.
Prepare your Android API like this:
Then go to Tools->Manage avds :
In my case i have created 2 devices already. go to Create:
and then add specification that which kind of device you want here is dummy for your understanding :
click Ok and your device will created. then run your app again.
thanks.
I have issues with the build in qemu emulator in Android Studio. There are some other Android emulators out there. How to configure Android Studio to use a different emulator? I use leapdroid emulator http://www.leapdroid.com to run apps and games.
Leapdroid is compatible with Android adb, i.e., using the same port numbers starting with 5555, so there is really nothing special to do, pretty much same as what you do with the built-in Android emulator. If you run "adb devices", you will see a device named as "emulator-5554".
Here are the steps:
Launch Leapdroid vm, which contains android 4.4.4 image
Launch Android Studio, and click Android emulator tab, a device named as "Emulator unknown 4.4.4" will show up inside the device list, and you can select it.
You should be able to see the logcat, and debug your Android app, etc.
Make sure that you close all other emulators first, in case there are conflicts.
I've also attached two screenshots for clarifications:
There are options like:
Genymotion: https://www.genymotion.com/
config with Androi Studio here
Visual Studio Emulator for Android
https://www.visualstudio.com/en-us/features/msft-android-emulator-vs.aspx
config with Android Studio here
I hope this help you
Did you try using Genymotion? It is the fastest emulator I've come across.
-Download it from their website for your required system specifications.
-You will also need an account to download the device images.
-Once all that is done, when you simply run the emulator, the device should show up in your ADB choose device window.
-You may also want to use Genymotion plugin for android studio for easy launch of virtual devices.
I have been running Android Studio 1.5.1 doing development on a WMWare copy of Windows 2012 R2 and everything works fine. I've been able to run the device emulator with no problems and start various versions of Android running in AVD.
Android Studio 2.x Change
I recently installed Android Studio 2.0 (see image below for exact version).
Now when I attempt to run the emulator nothing happens.
Well, actually I do see a message in the status bar of Studio when I attempt to start the device, but then that message disappears and nothing happens after that.
There is a warning that I need to turn off Hyper-V (see image below), but I don't believe that is possible since this is a VM.
No Longer Possible?
Is it not possible to run the emulator on the VM any more?
More recent versions of the Android Emulator require hardware virtualization support (Intel HAXM).
Unfortunately, most virtual machines do not provide HAXM instructions to the guest (a VM within a VM), so you will be unable to use the emulator within the virtual machine.
I just installed Android Studio 2.1 on my Windows 2008 R2 VM (running VMWare) and I'm happy to report that it is possible to run ARM based AVD (Android Virtual Devices) on the VM.
Steps To Run Arm-based Virtual Device on VMWare
Go to location where you've installed the Android SDKs (in my case it is at %appdata%\Android2\SDK\
If you are in the right place you should see a directory structure and directories like the ones shown in the first image below.
Start the AVD.exe by double-clicking it.
You will see a window like the one in the image below
Take a close look and notice that this is running an ARM(armeabi-v71) image. When you download images you have to download ARM-based images. (no x86 images will work on VM).
Also, you cannot start these images from AVD that launches from Android Studio 2.x
Make sure you have an environment variable named ANDROID_SDK_HOME set to path which is similar to the one at the top of the AVD manager (in image).
Once you do all of this and start an ARM-based image on a VMWare VM it will warn you that it is faster with HAXM but at least the image will run.
Finally, you can see if you attempt to launch your Virtual Device from the AVD Manager in Android Studio then it will warn you that Hyper-V needs to be turned off. Of course you cannot turn Hyper-V off on a VM.
EDIT -- Running Android 7 ARM Image
#mcflysoft asked about running an android 7 ARM image. At first I didn't think it worked, but if you open up your SDK manager and install the exact ARM OS image shown in the following picture, it will run on a Windows VM:
ARM image Containing Google APIs
I tried installing the ARM image that contained the Google APIs and that one would not ever start. There were failures logged which I could see in c:\> adb shell logcat.
Beware : It Is Really Slow
However, running Android 7 seems extremely slow and I don't see a web browser.
Not sure how helpful it may be to you, but you can get it working.
Good luck.
The simplest solution I've found so far is to use a device farm, for example Samsung's device farm:
https://developer.samsung.com/remotetestlab/galaxy/rtlDeviceList.action#444
It's free to use and you can deploy your apps just like in an emulator (Right Click -> Test -> Remote Debug Bridge -> follow the instructions).
And since those are real devices, the speed might be even better than on an emulator on your personal PC.
I've had the same problem so I'll post an answer in the hope that someone might find this useful in the future. I can run Android Studio in my VM but when I try to start up an emulator, I can't download an image due to "Your CPU does not support required features (VT-x or SVM)"
Although I didn't get a virtual device up and running, I got round the problem by using BlueStacks. You install BlueStacks on the VM. BlueStacks (at the moment) runs Android 7.1.1, SDK 25. Inside BlueStacks, go to Settings/Preferences and Enable Android Debugger Bridge (adb) following this set of instructions. Then you should be able to run your app on BlueStacks from inside Android Studio. Logcat can see any log statements from BlueStacks.
The alternative (without enabling the debugger bridge) is to locate the .apk file for your app and then open that with BlueStacks APK installer. Logcat still sees the traces.
It's slow on a VM. You also have to set android:testOnly="false" in your XML file