I usually develop my android tests at Windows using the Eclipse IDE. But now that I am needing to do the same at Ubuntu, for some unknown reason the emulator isn't getting loaded, but is getting frozen at the android launching screen. It doesn't show any error message, just get stopped on that screen(I am waiting for more than 2 hours), I don't know why. I am using the Ubuntu 12.04 Precise-Pangolin, and trying to launch the Android 2.2(Froyo) at emulator.
Depending on your hardware and what version of android you are using, it can take a long time. Honeycomb+ for me took over an hour on my somewhat high end laptop the first time it booted, I thought it had frozen.
Related
I am using Android Studio on a Ubuntu virtual machine.
I not yet got to the point where I am debugging my code. I am only trying to launch the emulator in Android Studio. After learned that my computer could not handle a high resolution emulators, I picked the appropriate ARM image. But when I launched the device from teh Device Manager, I could see that it seemed the emulator was trying to load but it stopped after just a few seconds with this error.
Logcat is, of coure empty. I have not even gotten to the point where I am debugging code.
I am using Windows OS and when I get this error, I open the task manager, find the qemu-system-x86_64.exe process and kill it.
You can do something like this in Ubuntu.
I am new to android studio, and I do not have an android phone, so the first thing I actually tried to do is to try out the emulator before I get any further into android studio, but I am facing alot of problems.
When I press on the RUN button, I do find a "Nexus 5X API 27 X86" by default, when I run it, well here comes the problems. Sometimes it runs and opens properly, but without being able to find my app on the device, sometimes the app opens automatically. The device is always so slow, most of the times when I try to open an app, I get a msg "APP(google most of the time) has stopped working" or "Android is starting.." out of nowhere, and that same msg sometimes pops out automatically when I first run the emulator. Sometimes I get "Application Installation Failed" error, found some solutions saying to trun off instant run, I turned it off and I still get the error sometimes.
Generally, it is just impossible to start coding with such device, I had an android phone before and it was much easier.
As far as I know, my laptop should easily support both the android studio and the emulator.
One more thing, whenever I try to set up a new device on kitkat or something, the device doesnt come alive, just a stuck black screen with a logo in the middle.
My laptop:
Intel Core i7-5500U 2.4GHz
4gb RAM + 8gb RAM
Nvidia GeForce 920m - 2gb
64bit
And yeah, HAXM is installed.
Android Studio 3.0.1
Any assistance would be appreciated.
You can try genymotion if you feel android emulator is slow. https://www.genymotion.com/
you can find the difference between the android emulator and genymotion.
android genymotion vs emulator
Emulator's now is much faster and better then genymotion,just create your own device going to avd manager and then try to run it,one more thing , did you turn on intel virtualization in bios ?
I decided to give Xamarin a try. So I followed the various articles at https://developer.xamarin.com/guides/cross-platform/getting_started/ to install Xamarin, then build an Android app. That was pretty easy, especially since I already have Visual Studio 2017 installed. The code compiled fine. I set up an Android Virtual Device and tried to debug/run the app in that AVD. Everything I've tried results in:
Build succeeded.
Unexpected install output: Error: Could not access the Package Manager. Is the system running?
Deploy failed on ...[AVD device here]
I have VS 2017 running on Windows 10.
The development experience was encouraging, since I've been using VS/C# for such a long time now, but getting past this emulator issue has, so far, been a complete roadblock. Any help would be appreciated.
Could not access the Package Manager. Is the system running?
Are you using ARM based emulator ? They are extremely slow and take lots of time to boot up. As Anubhav Ranjan said, just wait until emulator be loaded completely, once it finished it should work.
Try using an x86 based emulator, and use the Hardware Acceleration. Those run much faster, still a little on the slow side, but bearable.
My Android emulator beachballs on startup almost every time I try to use it. I'm currently using Android Studio 0.2.0 build 130.737825 on OSX 10.8.4. It seems like it will launch into Android once or twice, then if I close and reopen, it hangs on the black screen before the Android splash screen. At this very moment, it's been hung for about 15 minutes. I don't see anything useful happening in Console. And Android Studio is fine. It's just the emulator that hangs.
The android emulator is pretty much unusably slow. I recommend using genymotion instead of the emulator. Genymotion runs the android device as a virtual machine, so it's basically like having a real device running. And it's super fast.
Android's emulator is slower than Apple's simulator. you can refer to here to know why. But you can actually enhance the virtual device(x86 not ARM) performance, if you install Intel x86 Emulator Accelerator(HAXM) which can be found in Android SDK Manager.
I'm trying to run the Android emulator with the ICS (Android 4.0) OS but after a 15 minute wait on a fast quad core machine, it's still not doing anything. I understand it's emulating the arm cpu, hence it's slow - but this hasn't even gotten off the loading screen yet! Has anyone managed to get it to run? Any tips?
Try launching without the Launch from snapshot feature
Launching some of my AVD's from command line with
./emulator -avd ...
Gives
savevm: unable to load section cpu
that may or may not be related to the problem(?), but basically launching without the snapshot starts up the emulator.
This happened after I upgraded to Android SDK to 4.0
My solution is the starting Emulator manually but with Target 2.2., let's say with API level 8, then your project will be easily loaded on Emulator.
I made sure to turn off "Load from Snapshot". And mine will still not load. I am going on about an 1 hour now and still sitting
In my case, I succeeded to get ICS emulator by executing $ emulator-arm -avd your_avd_name whereas launching from eclipse (i.e. going through emulator.exe instead of emulator-arm.exe) fails consistently.