I am trying to create an Android virtual device for my application. However, options to for creating a new AVD is limited for me. I have Eclipse Juno and Android 4.0 installed. How can I get the "Create new Android Virtual Device (AVD)" window as seen on the second picture.
Related
I have a xamarin project and i want to debug it, but visual studio doesn't show any emulator or physical device.
this is the menu
I wanted to restart adb from tools > android but it's disabled. but when I open a non xamarin project (for example a web porject) this options is enabled.
I can see my device in cmd with command adb devices and in android studio, every thing is fine and I can deploy some java application to my phone.
do you have Any idea?
Update
I created new project and in this new project, every thing is fine and I can debug with my phone or emulators.
but in my existing project which I'm currently working on, there is no device in list.
It happened to me just now using vs 2019, to fix this, manually remove obj and bin folders restart vs, and that's all :)
I was having trouble using the Android emulator in Visual Studio Community 2017 and I decided to create a blank project to see if it will run. I get this error message when attempting to run it in the Live Xamarin Player:
Starting Android Emulator Android_Accelerated_x86_Nougat...
Failed to boot Android device emulator-5554...
Unable to deploy to Android_Accelerated_x86_Nougat, please ensure the Xamarin
Live Player app is open and the device is on the same network as Visual Studio.
Why would I have trouble running the emulator in a fresh blank project when I didn't even write a single line of code? Thanks for your help.
UPDATE: So I installed the latest Android SDK 8.0 along with they system image and tried to create a virtual device that uses it. But the Android Virtual Device Manager shows a, 'No system images installed' message when I selected the 8.0 framework. So I installed an earlier version of the SDK along with a system image (5) and was able to create a virtual device with it. So another question is why wouldn't the system images show up for the 8.0 framework?
The $(TargetFrameworkVersion) for Xamarin.Forms.Platform.Android.dll
(vv8.0) is greater than the $(TargetFrameworkVersion) for your project
(v7.1). You need to increase the $(TargetFrameworkVersion) for your
project
This means the Xamarin.Forms library is targeting Android 8.0 (API level 26) but your project is setup for Android 7.1 (API level 25). You can't change the Xamarin.Forms target version without downgrading, but you can change your project target version easily. You can learn more about these concepts from Xamarin. Be aware some of the details of that Xamarin blog post are already out of date!
There is another nice blog post from Xamarin which can walk you through the process of setting your system up for Android 8.0 API level 26. It's normally not this complicated, but Google changed their SDK tools internally between 25 and 26 in very major ways. They changed from GUI tools to command line tools.
You'll probably also want to get the (in preview) Xamarin Android Device Manager if you don't have a physical device to test with. This Xamarin Android Device Manager tool is the only way to create and configure API 26 and higher emulators without using the Google command line tools.
It seems as though Google has gotten rid of the GUI apps that manage the SDK and Virtual Devices in the latest version, so when you try to create a new virtual device with 8.0 it's not compatible with the GUI tools. Until Xamarin releases a GUI tool to replace them we can use the command-line to manage the SDK and virtual devices.
https://learn.microsoft.com/en-us/xamarin/android/troubleshooting/sdk-cli-tooling-changes
https://developer.android.com/studio/command-line/avdmanager.html
This is how the Xamarin SDK Manager looked when Visual Studio for Mac was first installed. Only Android 6.0 items were downloaded/installed, and only the items pictured were installed:
By default, an Android Virtual Device called “Android_Accelerated_x86” was preconfigured and available for use when I installed Visual Studio for Mac and updated Xamarin. As far as I can tell, it is an AVD created using the “Google APIs Intel x86 Atom System Image” from the above screenshot, using Android 6.0.
I am able to debug to this Android_Accelerated_86 AVD, with a Xamarin project. It works fine as expected.
I now want to create an AVD using Android 7.1. What I did was in Visual Studio for Mac, I opened the xamarin SDK Manager, and downloaded the following items (checked in the picture):
You can see I downloaded the similarly-named “Google APIs x86 Atom System Image” for Android 7.1, as was preinstalled automatically with Visual Studio for Mac for Android 6.0.
In theory, I would think this should be all I need to be able to create a new virtual device. In visual studioI go to Tools > Google Emulator Manager, and I click "Create..." to try and create a virtual device. For Device, I've tried picking Nexus 10, Nexus 9, Nexus One, 10.1" WXGA Tablet, etc. No matter what Device I pick, if I pick a Target of Android 7.0. 7.1, or 8.0, the CPU/ABI section says "no system images installed for this target". Also, if I pick a target of “Android 6.0 – API Level 23”, it says that “no system images installed for this target”, just like it did for Android 7.0 and higher.
The ONLY way I can create a new virtual device is by picking a Target of “Google APIs (Google Inc.) - API Level 23”, and then it will let me choose “Google APIs Intel Atom (x86)”, and I assume this is because I have the “Google APIs Intel x86 Atom Image” installed from the Android 6.0 section. But I have that corresponding image installed for the Android 7.1 version as well, so why can’t I at the very least pick a target of Android 7.1 and also be given a CPU/ABI choice of “Google APIs Intel x86 Atom image”? I have the same image type as is installed for Android 6.0!
I've tried this on two different machines, with the exact same results. I've also tried downloading appropriate images for Android 7.0 and 8.0, and am still having the same problem - I can't create Android AVDs past Android version 6.0. Has anyone successfully used the SDK Manager and Google Emulator Manager to configure an AVD with Android 7.0 or later? All existing discussions about this type of problem that I can find only show Android 6.0 or earlier. I also tested this with the most recent version of Visual Studio for Mac, and have fully updated all my Xamarin components via the stable auto-update channels.
Visual Studio for Mac (VS4M) uses the Android Emulator Manager within Android SDK Tools version 25. That version from Google does not support later Android Virtual Devices AVD APIs.
If you upgrade your Android tools version to the latest version (currently 27.01), you will receive this message when trying to open the Google Emulator Manager from the VS4M's Tool menu:
As it states, the latest version of the Google Android tools has removed the standalone GUI for creating AVDs.
So you can create them via the cmd-line using avdmanager which is located within your Android SDK (android-sdk-macosx/tools/bin).
❯ ./avdmanager
Usage:
avdmanager [global options] [action] [action options]
Global options:
-s --silent : Silent mode, shows errors only.
-v --verbose : Verbose mode, shows errors, warnings and all messages.
--clear-cache: Clear the SDK Manager repository manifest cache.
-h --help : Help on a specific command.
Valid actions are composed of a verb and an optional direct object:
- list : Lists existing targets or virtual devices.
- list avd : Lists existing Android Virtual Devices.
- list target : Lists existing targets.
- list device : Lists existing devices.
- create avd : Creates a new Android Virtual Device.
- move avd : Moves or renames an Android Virtual Device.
- delete avd : Deletes an Android Virtual Device.
Personally I use the one that replaced it and that is within the Android Studio (Tools / Android / AVD Manager):
To use this one does mean that you need to download the full Android Studio dmg but I already use it for writing/compiling Java libraries for Xamarin.Android binding libraries, access to Android Instant Apps tools, etc... Also its Android SDK Platform and Tools manager is "better" than Xamarin's (IMHO/Its a personal preference thing...).
I'm trying to install VS2015 Community in my PC.
When I install everything at the end the installer gives to me the following message:
I've tried to install, reinstall, update but anything changed. The only consequence that I can see is that when I create a new Xamarin solution, when I run the UWP project using Local Machine as target it starts, but then I obtain this exception message.
If I run the application from the Mobile emulator, it starts without problems.
Somewhere (sorry, I forgot the source) I've read that I should be sure to add following references for the project:
Windows Desktop Extensions for the UWP
Windows Mobile Extensions for the UWP
But I've only the first one, not the second. Maybe it's related to the installation issue?
I'm new to Xamarin and UWP, but UWP should be run to both Mobile devices and desktops, so why I have this behaviour? and what I can try to solve the installation problem that's probably related to this?
So, at the end, what I can try in order to fix the installation and allows the xamarin UWP project to run correctly in the local machine?
If I run the application from the Mobile emulator, it starts without problems.
According to your error message, it seems you are using StatusBar in your project.
While using StatusBar, please note that this is not a Universal API, this class can be only used in Mobile Device. Because status bar only exists in Mobile devices, there is no such thing in desktop, table or IoT devices. So if you use this class on Local Machine, you will get an error, but in Mobile Emulator, it can work without problems.
For more info, please see Requirements section of StatusBar.
Usually, when using StatusBar, we would use it with Runtime API check like following:
Windows.UI.ViewManagement.StatusBar statusBar = null;
if (Windows.Foundation.Metadata.ApiInformation.IsTypePresent("Windows.UI.ViewManagement.StatusBar"))
{
statusBar = Windows.UI.ViewManagement.StatusBar.GetForCurrentView();
}
if (statusBar != null)
{
//TODO
}
On Local Machine, as there is no StatusBar, ApiInformation.IsTypePresent method will return false. This will help us avoid the error. For more info, please see Write adaptive code.
But I've only the first one, not the second. Maybe it's related to the installation issue?
I'm not sure why you can't find the Windows Mobile Extensions for the UWP. But if you have used StatusBar and can build and run your project in Mobile Emulator, then you must have referenced Windows Mobile Extensions for the UWP. Without this extension, we can't use StatusBar and the build will fail.
Depending on the SDK you've installed, you can find following extensions in Reference Manager (Right click "References" in your project and then select "Add Reference" → "Universal Windows" → "Extensions").
I'd suggest you create a new Blank App (Universal Windows) project with Visual Studio to see if you have both the Desktop Extensions and Mobile Extensions. If you still have problem in new Blank App, I'd suggest you use Visual Studio Uninstaller to uninstall Visual Studio completely and also check the Control Panel to make sure you have uninstall all related stuffs like the SDKs. Then you can try to reinstall Visual Studio to see if it works.
I am unable to deploy an application via Visual Studio 2015 Update 2 to my Lumia 650. In the past it was possible but now I get the following error indicating to change the build configuration of a project or add an ARM device.
The build config is set to 'ARM', the device is connected via USB and my configuration manager looks like this.
The platform targets seem correct, so the config setting 'ARM' points to the platform target 'ARM'. I can run the app on my local computer, but I cannot deploy it to my phone. I also can't run the app in an emulator because if I choose the setting, VS does not change the caption and accept it. I don't have any more ideas.
If it helps I could provide my .sln file with all build configurations if desired. The only thing I did was checking out my source code to a new location on my hard drive. Since then I couldn't deploy anymore. Someone got any hints?
UPDATE:
I cannot deploy to my phone, run the app in an emulator or run the app in the simulator. The only thing that works is running on the local machine. Even all new apps I create cannot be deployed or run in an emulator or simulator. Visual Studio and SDK repair installation was made, no notable change.
If I load an old Windows Phone 8.1 RT or Silverlight project everything works normally, I can use the emulator and I can deploy it to the phone.
Right click your app in VS -> Properties -> Debugging
There is a combo box to select the target device. In my case there was no selection and I chose 'Device'. Now it works again.
https://dotblogs.com.tw/billchung/2016/04/03/051455