I'm new to android studio, so I don't know why the emulator isn't working. I don't get any errors, it even says it has a successful build but the emulator just sits there and at the bottom it says waiting for all target devices to come online. I've tried invaliding the cashes, I've deleted and re-created a new device, I've wiped the AVD data. No matter what I do it won't load the emulator. Does anyone have a clue what going on because I really need some help please.
I've tried invaliding the cashes, I've deleted and re-created a new device, I've wiped the AVD data. No matter what I do it won't load the emulator. Does anyone have a clue what going on because I really need some help please.
Related
No emulators are currently running
Wrote a program in Kotlin. Everything was fine, everything worked. I turned on my laptop a week later. Launched Android Studio/AS/. The code opens fine. Only emulators do not display the phone. Writes that there are no working emulators. No reboots of either the system or the AS, updates with a full restart of the program help. I want to delete the device, Device Manager/DM/ also does not allow it, because DM says that it is now working. I can’t find any AVD services. In the Task Manager, I can’t find anything either.
Dear gurus advise what to do.
The next step is to reinstall AS. I just can’t reinstall AS every time the emulator freezes.
Thanks in advance.
By the way, as I have no choice I reinstall the AS that helps.
Android promted me to upgrade to 3.5 today so I have. Even since I've been having issues with the AVD and running my code on the emulator.
I've posted about my previous issues here
After those solutions still didn't allow me to run the app (different errors) I've decided to just uninstal and reinstall Android studio.
Now, every time I try to run it my whole computer crashes.
It starts with this screen popping (sorry for the terrible photo, had to be quick). It says emulator warning: crash service did not start.
And then this:
What am I supposed to do? Already completely uninstalled Studio.
Ok, I don't know exactly what the problem was but it seemed to be solved. As I mentioned, when I've unistalled and reinstalled before the problem persisted. Even if I've uninstalled all the devices from the avd and created new ones.
This time I've done the same but didn't just install a new device, but did it with a different version (Oreo 2 instead of 26). I'm not sure why but it works now.
You should create a new emulator whose settings reduce the size of the ram and memory.
I've seen a couple of similar problems on SO, but none of the solutions has worked for me.
Until a couple of weeks ago, saving / starting Android Virtual Devices from snapshot worked perfectly, but not any more. I have an AVD that works the first time I start it up, but, when I close the window and start it a second time, the state is "offline" and the target platform is "unknown".
Restarting adb doesn't help, and neither does restarting Eclipse. I can wipe the user data and it will work, but then I have the same problem the next time I start it.
I could wipe the user data every time, and not use snapshots, but loading up the emulator from scratch is very slow.
After taking a long break from Android development, I started again. I've been using Android Studio for a while and I haven't had any issues like this. If you're using Eclipse and are having this issue, try switching to Android Studio and see if that helps.
The emulator won't launch my apps even on a real device! I've tried every solution online, even reinstalling android sdk,ADT plugin. The app run SOMTIMES(4x to be exact) though, like awhile ago, when i got home i tried it again, and it run on my first try then i began working on the code again then i tried to run it, won't run again. Even basic apps like hello world won't run most of the time. I've set the run configuration to let me choose my device everytime, but even the device chooser wont show up(showed up once only), i tried waiting for 30 minutes(also tried the kill-server start-server) but it just wont run! my real device, or the emulator is listed on the DDMS perspective and there's nothing on console. please help, cause I've wasted 2 days for this already.
Have you also tried, taking the USB cable then disabling debugging and then enabling debugging and putting the USB cable back.
I remember this happen to me, so I did what I mentioned and surprisingly it works. Hope it work for you too.
Maybe you should try deleting your emulator and creating a new one. Make sure that all your settings are correct and that you are targeting the right OS version.
I've had quite a few problems with the emulator and wiping them and starting from scratch worked more often than not.
As for the real device, the first real hurdle is getting the right drivers so that your PC can recognize it, after that kill-server start-server usually does it. I'm surprise that didn't work for you.
I have a problem with the Android Emulator and its SD card. I am developing an application that writes files to /sdcard. Everything works fine, until I exit the emulator by clicking its close button. After restart the files are empty (size 0), but still in the directory. Of course, they have not been empty as long as the emulator runs.
This looks like a failed sdcard unplug, like with usb stick. But I am not sure, how the emulator treats the card exactly. I am starting the emulator from Eclipse, and get an error at exit, when I close the emulator.
The problem did not exist before I updated my Android plugin. I could use all my files after restarting the emulator. Moreover, the problem does not occur on the real thing. I am using the most recent Android stuff, and Eclipse 3.5.
I already tried deleting my emulators and creating a new one. I also tried shutting the emulator down with the red telephone button, but that did never complete. Of course, my app is not a service and has no threads pending at shutdown.
Any ideas, you friendly people out there?
I am currently seeing the same problem on mine using an API 4 emulator, but putting the apk on my actual android device it works fine. It only happens if I close the emulator and restart using "Debug As" or "Run As". My current workaround is to start the emulator before running / debugging my app... not shutting down the emulator prevents this from happening, although I wish I had a real fix.
The problem went away by itself. I have no idea, what caused the healing. I did not do anything particular. I just continued working.
Thanks for your attention.