I'm on Manjaro, completely remove and then installed back Android Studio, but nothing seems to work.
I have Windows and Manjaro both on the same machine, on Windows it works as expected. I have no clue why it's not working.
Any suggestions would be appreciated.
Issue has been fixed as of Android Emulator version 32.1.1, just upgrade through Android Studio.
This is where the issue was report to google devs:
https://issuetracker.google.com/issues/228201899
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 am using android studio 2.3. After I updated my android sdk to the latest version, I noticed that my emulator stopped working. When I try to start the emulator it says "Waiting for target device to come online". But it goes nowhere and the emulator never shows up. After reading some posts, I installed some extra libraries Intel and ARM apis for each version of Android like 5.0, 6.0 but still that did not work. Restarted my machine, IDE, invalidated caches but that did not help.
Try rebuilding your emulator. I had a similar issue when I updated to an earlier version (2.2.2), and removing and rebuilding my emulators did the trick after installing the appropriate apis and packages. Hope this helps.
I am using a MACbook. For one specific emulator its always showing offline. The emulator has a nexus 5 skin and is a api 24 build. When i try another emulator its fine and works. i tried re-creating the emulator. when i run adb devices it says the "unauthorized".
I tried the following:
I went into the developer settings of the emulator and allowed usb debugging if to see if that would help but it did not. this happened after i updated android studio to 2.3. i also tried to wipe user data from emulator. What is going on here ?
UPDATE: THIS IS OCCURRing for my other emualtors above api 22 also . i had to switch to genymotion for now which seems to work fine and shows as online. it has something to do with updating android studio. after i re-installed studio and did not take the 2.3 update, the problem was resolved.
Don't know the exact issue but it appears there are some bugs/issues with the latest updates.
Personally I am seeing my tests fail when run by ./gradlew commands, but not when run via Android Studio IDE.
I experienced your offline issue as well, I found I could at least rectify this by running:
adb kill-server
adb devices
More info on this in another post:
https://stackoverflow.com/a/21330228/5096103
-- UPDATE --
After investigating this one a little more, I found there to be compatibility issues between Qt version 5.7.0 which the new emulator uses, and Ubuntu 14.04 and it's version of Qt. Whatever system you will be using, you will have some version of Qt installed.
I'm guessing this may be the cause/related to the issues you are experiencing.
I was successfully able to fix my system by downgrading the SDK tools from version 25.3.1 to 25.2.3. I don't get the speed improvements of the new emulator, but at least I can run my tests reliably.
Going to try resolve the issues between Qt versions, and will update this if I can get the new emulator to work correctly again.
I had the same problem. I solved it by turning on USB debugging after unlocking developer options of the emulator by clicking 7x on the build number.
I've setup the latest Xamarin Android Player (XAP) on my AMD64 server running Windows Server 2012
Hyper V has been uninstalled.
Before doing so I uninstalled Virtual Box and let XAP install its version.
When I start XAP with device Nexus 7 Lollipop it boots to the Android logo and goes no further.
What is wrong?
You need to post errors and logs.
VirtualBox should be installed I believe for the Android Xamarin emulator to work.
However, you could try reinstalling the Android player. Make sure virtualization is enabled in bios.
If worse comes to worse, you can install the Android AVD manager and use the normal Android emulator which also works on Xamarin.
The Xamarin Android Player is still in preview, any issues with can be addressed with bug report at https://bugzilla.xamarin.com/newbug
Please include the logs when you file a bug, you can generate logs by Right-click bottom bar > Generate Bug Report
In the meantime, I would recommend you to use Visual Studio Android emulators
In addition to what Prashant suggests, you can also try a different simulator image. Some of the XAP device images seem to be unable to boot properly on some machines. I've not seen any issues under OSX version of XAP, but the Windows version seems to be affected on some systems.
When I deploy my app to any Android device I get an old version of the app. I have factory reset the android phone on Kitkat 4.4.4 and have also tried installing on a newer android 5.0 device. I am always getting the same old version cached. When I debug with the ripple emulator I always get the newest changes with no issue.
I have tried adding 'preference name="useBrowserHistory" value="false"' to the config.xml in the solution with no luck. One notable change that has happened is I have moved to a new computer and I did not have this issue on the old one.
Any help would be greatly appreciated.
Have you tried to delete the bin and bld folders in your project before you deploy? It might be that for some reason your Android project is not being rebuilt. This should force it.
Try to use the option "Revoke USB debugging authorization" above "USB debugging" to update the authorization Keys in Developer Options in your Android Phone or Emulator.
I use Visual Studio 2015 with Xamarin and works for me.