Would anyone know why my application on my emulator is not updating with my code? Along with that, when I have the emulator running and I try to rerun the program it does not recognize there is already an emulator running. I figure these two issues are related.
Fixes I have attempted to of no avail:
Reset ADB
Uninstall the app on the emulator and rerun program but as I said above the emulator is not recognized. Now I just don't have the app on my emulator anymore.
I have also tried to use the Device Monitor - for an emulator but again, the emulator is not recognized even though it is running.
Reinstalled android studio
Any advice will be helpful.
Related
I am using windows in Mac Pro. In Windows Parallel Desktop I am keep on getting error message in Android Emulator like:
Google has stooped working
Settings has stopped working.
Pixel Launcher has stopped working.
Getting error message in freshly installed Xamarin tools in Visual Studio.
Googling suggested to clear the cache or force stop it, but nothing is working
For now I installed Android Studio on Mac and running project on Windows. By Following below link I ran few commands and Windows able to communicate with MAC
https://learn.microsoft.com/en-us/xamarin/android/troubleshooting/questions/connect-android-emulator-mac-windows
Not sure if this is right way. But running virtual device inside virtual machine is giving some problem.
Above thing is working fine. Let me know if there is any other best solution for this.
I have a macbook pro (Retina, 15 inch, late 2013) that is running High Sierra GM (17A365) and a fresh install and blank project in Android Studio always results in a crash (emulator64-crash-service quit unexpectedly.) when trying to run any android emulator. I have tried every suggestion I can find on the internet, NONE of them work. Here is what I have tried so far:
Since I have an external monitor connected to my mac, I tried both creating emulator-user.ini file with window.x values (Android VM crashes on Launch Mac) AND just tried disconnecting second monitor and running just on the macbook. Still crashes
Tried completely (including all prefs and hidden folders) uninstalling Android Studio, rebooting and reinstalling and setting up brand new default environment. Still crashes
Verified that HAXM is installed correctly and running loaded (kextstat | grep intel returns expected info), but have also tried without HAXM. Still crashes
Tried launching emulator from Terminal. Still crashes
Tried creating new avd from avd manager. All of them crash.
Tried changing settings in avd configs to use (or not use) Hardware/Software graphics, as well as fiddling with more or less memory than defaults. Still crashes.
Does anyone have anything left to try? I am pulling my hair out here. I would like to try my cordova app in Android, but it seems impossible from my mac.
I still don't know what caused it, but as a workaround creating a fresh account on my Mac and launching studio and emulator inside of that allows it to run. So it is something in my original account settings that is causing this crash, and I still don't have a clue what (although there are no active startup items, launch daemons, caches, saved app state, etc that I can find, I have cleared them all).
Today I downloaded Android Studio for my Debian Testing system. I wanted to run a HelloWorld application but weren't able to run it. With adb I can install it without having any problems.
However, if I try to do it with Android Studio, it gets stuck on 'Installing APKs'. The same happens when I try to start it in an emulator (gets stuck on 'Waiting for target device to come online').
My device is a Samsung Galaxy S3 with LineageOS (Android 7.1.2) and root permissions. Android Studio recognizes my phone properly.
What I've already done:
installed openjdk
set android_home
installed all the SDK-platforms since Android 4.3 and Android Emulator from SDK tools
enabled USB-debugging
tried with MTP and PTP
tried another emulated phone
installed lib32stdc++6
restarted my computer
and probably much more
I tried to do it the whole evening and couldn't find a solution. Is there something Debian-specific because I can only find instructions for Ubuntu? I have never experienced anything close to this on other systems.
Thank you in advance.
EDIT: I am now able to use my phone to run the android application by using USB 2.0 instead of USB 3.0! Is that a normal behavior since it works with native adb? I mean, if I buy a new PC after some years which has got only USB 3.0 ports, will I not be able to use phone debugging with Android Studio or is this just an issue? It is still known since 2014 (https://stackoverflow.com/a/9548311/8292104).
However, I still cannot get the app running on an AVD. I changed graphics to software, now it shows the phone but the screen remains black and the phone won't start. What can I do to fix it?
Try to completely delete and install Android Studio again, I think that it will solve the problem
Another possible solution that worked for me is to, in the application, go to
app - build - intermediates - split-apk - debug - slices
and then delete all of the contents within this folder. Then again, this only worked for me, so I would duplicate the document in case of corruption.
this is more of a benign bug in android studio. Whenever I wake my computer from sleep or hibernate the connection between the emulator and android studio is not proper and I have to restart the emulator and try again, so as a result of that (I think) all the dead emulators are always shown in the listing when trying to run the app.
And FYI I don't usually restart/shutdown my computer (once in 10 days or so). I was just wondering if there was a way to fix this bug without having to restart the computer.
Screenshot of problem
Thanks in advance!
I am having the same issue using Windows 10 hibernate.
Try terminating the adb.exe process in the task manager. Sometimes you will find two or more adb.exe processes, kill them all. Then close all running emulators (if any) and disconnect all physical devices.
You don't have to restart android studio or eclipse.
After dong this, all unknown/null emulators should be gone (at least in my case).
Did you open multiple android studio and use the terminal in android studio?
you can close all android studio, and restart them. the unknown emulator will be gone
It was working fine till I updated the Android SDK tools from the SDK Manager to version 24.1.2. However a virtual device was running at the time of the update and it asked me to close 3 processes in order for the update to continue. I thought the virtual device was interfering so I closed it and tried to proceed with the update,it gave me the same error. Therefore I cancelled the update and closed the studio. After restarting the studio,it gave an error saying the SDK could not be found and would not let me do anything else. I uninstalled the studio after deleting the SDK folder and reinstalled it. I downloaded the system images needed for the virtual devices and some other packages and created a new virtual device. When I tried to run the application,it gave me the dialogue box to chose the virtual device,I chose the newly created one and it gave the command to start the device. Yet no emulator window for the device appeared.
D:\sdk\tools\emulator.exe -netdelay none -netspeed full -avd MTK
emulator: device fd:5500
HAX is working and emulator runs in fast virt mode
HAXM is installed and it worked fine before. On checking the task manager upon launching the application,an emulator-x86.exe process appears briefly before disappearing. Nothing happens after that. Launching the program again gives the same result. If I try to launch the device from the AVD manager,I get the same result. I have tried using the arm images,varying the ram size,snapshot enabled/disabled,use HOST GPU enabled/disabled,system restarted,removal of /.android content,setting up the SDK in a different drive and deleting the ANDROID_SDK_HOME system variable and resetting it.
I have also tried with Genymotion. The virtual device window briefly appears and I can the see the android logo at startup but then it says "player.exe has encountered a problem and needs to close. We are sorry for the inconvenience." I have tried it using both the Genymotion Android SDK tools and the custom Android SDK tools to no avail. If I try to delete the device it says please stop the virtual device before deleting it even though it is not running.
I spent most of my day trying to solve exactly the same problem until one of my colleagues remembered he had exactly the same issue and that was related to Docker.
Docker uses Hypervisor Framework which is incompatible with the HAXM used by the Android emulator. Therefore if you try to run the Android emulator while Docker is running it will just quit without a warning. Quitting Docker will allow to use the simulator - Docker for Mac conflict with Android emulator
Sometimes it is because you are low on memory, or it might be an AVD specific glitch. I had many (20) devices saved in my AVD and was lower than normal on memory on my laptop. The native emulator folder would disappear right away but genymotion worked fine.
I removed the old devices and create a new one from scratch in AVD and the problem disappeared.