I am having problems getting android SDK Manager to open from Visual Studio, it opens fine launching from Android Studio, but in Visual Studio Community Edition 2015 its not working, something flashes up but then instantly closes.
Has anyone got a solution to this? I have seen a lot of information about how to correct and SDK Manager that does not open at all, but that's not my issue, so posting this issue as its more focused on the issue from Visual Studio.
After a few hours I managed to get this working, I changed the Java version from a 32 bit to a 64 bit version, this solved it the problem.
Related
I just upgraded my android studio to 4.1 version:
And tried to run some project on this emulator:
And for some reason, this specific emulator is crashing my android studio, I have noticed that I am getting an error:
After reading about the subject, I uninstalled "Riot Vanguard" but it did not solve my problem.
More info (and partially solving the problem ) can be found in "Update" at the bottom of the question.
In addition, moments after my android studio will get closed I will get a windows blue screen (happens every time).
I didn't have this problem earlier with android studio below 4.1 version, why is this happening?
Update (problem solved for others emulators)
I have run into the same problem on other emulators as well, but I could open those emulators so I could fix the problem:
Solution 1
According to most threads that I have run into, You will need to disable or uninstall "Riot Vanguard":
Open task manager, go to the startup tab, right click on Riot Vanguard, and press disable
Solution 2
If step 1 didn't fix the problem you may want to enable developer mode on your emulator.
For some reason with android studio 4.1 android studio could not find the emulator (It will tell you that there are "No connected devices") without enabling the developer mode
Before Android studio 4.1 version I didn't need to enable the developer mode to run projects on emulators and this is what solved the problem for other emulators for me.
BUT
Although I don't have any problems with other emulators at all I still can`t even open Pixel_3a_API_30c68 emulator without it crashing
How can I fix this problem on the specific emulator?
Update 2
The problem still occurs even After updating android studio to 4.1.1
Without having "Riot Vanguard" I also could not run any emulator in Android Studio since I upgraded to version 4.1. After some hours I finally found out what caused the problem (in my case):
"Android SDK Tools" have been replaced by other SDK tools (which ?) and is obsolete now. As soon as I UNINSTALLED "Android SDK Tools" the emulator worked again.
I would be interested to know if the java version makes a different. I moved from Windows to Linux because of problems running the emulator.
Linux worked great until I moved to Android Studio 4.1. So check java and it was version 11. Changed to java8 and it worked straight first time.
Seem to remember there was a setting in Android Studio to set the SDK which I think was version 8. But can no longer find this in settings in Studio 4.1.
Updating to the latest system image of the SDK helped me.
I'm trying to use profiler but it's stuck like this.
Strangly I'we used it on same device yesterday and it worked just fine.
Android Studio version I'm using is 3.4.1.
Also tried repluging device but nothing changes.
Problem was solved by restarting Android Studio.
Updating SDK platforms and SDK built tools solved my problem.
So, I wanted to see if successfully created the database for my application in Android Studio through ADM. It has been 5 minutes and no new window opened. There are no errors it is just not launching, I guess. Even my cursor won't give me a hint if there is it's loading or not. Should I just wait for it to appear or there are things that I should do for ADM to open? My Android Studio Version is 3.0.1 and running it in Windows 10.
"most components of the Android Device Monitor are deprecated in favor of updated tools available in Android Studio 3.0 and higher."
I faced similar problem, I updated the android studio and while searching I found the below link.
After your update, Follow this link
https://developer.android.com/studio/profile/monitor.html
hope this helps :)
So I have Visual Studio 2015 installed along with Xamarin and the Android SDK, etc... After being frustrated by the slowness of the default AVD(Android Virtual Device) I took some advice to get the Xamarin Android Player.
I went through the installation process and can run a virtual device instance by itself but I cannot get this to open from Visual Studio such that when I compile my Android app's code it opens in the Xamarin Android Player instead of the slow default AVD opening.
See image below:
I had the same issue. What I did was to open up my xamarin android player and then downloaded some of the devices and then restarted VS 2015. This came up.
I know this is a year old now, but thought it was worth pointing out for others that come across this question like I did. It looks like we may be better off using an emulator that isn't the Xamarin Android Player as it has been depreciated.
https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/debug-on-emulator/
Now i am going on with the Installing Xamarin for Visual Studio 2015 Preview by following the below link:
http://www.infragistics.com/community/blogs/blagunas/archive/2014/11/14/installing-xamarin-for-visual-studio-2015-preview-side-by-side-with-visual-studio-2013.aspx
After downloading the xamarin for windows and restarted my visual studio 2015 but i can't able to see the Mobile Apps template.
I do not know where it's goes wrong and also tried with by Go to Add/Remove programs and search for Xamarin
and change for visula studio 2015.
If any one have idea about this can please help to sove this issue.
Do you have Visual Studio 2013 already installed?
Is so go to Control Panel, select Xamarin and press Change. In Xamarin Setup make sure that Xamarin for Visual Studio 2015 is selected.
Don't install the recommended edition. And be aware what options you select in the auto installer. Sometimes if you uninstall it and again install, the app templates appear back, though weird. Try it.