I am trying to test a simple status bar notification program on Android 3.0 emulator.
When I try to run my application from eclipse, sometimes either I see a message that apk can't be installed when I check the DDMS log, I see java outOfMemory error. Though my application is fairly simple just one java file.
Sometimes when I launches my emulator it shut down my windows completely. I tested this on Windows XP and Ubuntu as well. In Ubuntu too when emulator was about to launch completely and showing home page my OS crashes.
Any other version of Android works well on my PC like 2.2, 2.3. I see this issue only with 3.0 (honecomb) version. Any resolution to this?
Thanks
Manish
Well when making an AVD from the AVD Manager , assign it maybe 200 -500 mb and this issue will be resolved.
I have noticed the resource usage while running 3.0 is much more than 2.3 and below. The error you are getting refers to the emulator/eclipse needing more memory not your application. How much memory and CPU do you have?
Related
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've been using Android Studio for a few months without any hiccups but now it keeps using too much computer resources resulting to system crash and sometimes blue screen of death. The usage of CPU and RAM goes up to 100% when gradle is running and crashes every time I try to use emulator. When I type the code the program works fine. My Android Studio version is 2.2 right now. Any solution?
I have a problem with my Android Studio Emulator. when I run my app, emulator started but doesn't start.
my app always shows this screen:
The console doesn't show any error:
Android emulator has a lot of weakness such as slow respond, bugs and others. Usually, when there is problem with emulator, I delete it and recreate new one. Try to change the specification of emulator such as CPU/ABI.
As alternative there is a recommendation of android emulator, try genymotion
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.
When I try to launch Android emulator, it crashes on Mac OS X. It was working some time ago, but now it isn't and I don't have an idea why.
Crash log: http://pastebin.com/04MjCqaS
Terminal log in verbose mode: http://pastebin.com/L6y6rUr0
Same issue here, I'm running a mac mini with 8GB of RAM and MacOS Lion. It used to work with the old AVD with some random crashes every now and then but since the last update to APi 17 it's a pain in the neck.
The ADT bundle doesn't work at all. After tweaking the memory limits on eclipse.ini file it throws random memory errors. Also it's not been able to download and install the m2e (maven to eclipse) plugin.
I moved to IntelliJ and I'm able to launch AVD manager but none of the "old" created devices work. If I create a new one and I launch it it works until I close it, then I have to restart the Mac and create a new device. Also it randomly shows errors when I want to delete those old created virtual devices.
Also the DDMS fails to start. I launch it, shows its icon on the Dock but it doesn't respond until I force close.
What a Nightmare.
** EDIT **
I found at android dev bug tracker this issue when you're running 2 screens: here
This is happening to me with the android emulator. I solved it like this:
cd ~/.android/avd
ls *.avd
Now choose the emulator that is crashing and
cd name_of_the_emulator.avd
touch emulator-user.ini
vi emulator-user.ini
And now reset window.x, that's window.x=0
exit and run the emulator.
If you move and close the emulator to the secondary screen it will crash the next time you want to run it.
Kill your Docker process
One problem I have seen multiple time is with Docker. Android Emulator crashes when Docker is running on Mac.
I was following the PhoneGap "Getting Started" guide for Android, and when I got to "Deploy to Emulator," after I created a new AVD, my Mac would crash and reboot. I stumbled on this thread, but thought it worth mentioning that what actually solved the problem for me was an Intel patch for the Hardware Accelerated Execution Manager located here: http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager
This is because Android SDK use some deprecated libraries of Mac OS X. I have the same problem (sometimes even kernel panic) before I start use android device. Maybe in future versions of Android SDK this problem will be fixed.
I just updated the Android SDK manager to the latest Android 4.2 (API 17) level updates, and now all my old AVD's crash. The newly created one using API 17 works, however.
I have the same issue. You can try to create a new AVD with the appropriate API level. I am able to run these the first time(s) after creating. That seems to be a memory error.
My AVDs are able to run the first time after reboot. After this they keeps crashing.
I had the same issue using mac 10.6 and 2 monitors one through a usb adapter to HDMI.
I have tried all of this suggestions and nothing did work.
I ended up creating a new user into my mac and with the same android sdk and same eclipse with a new workspace did work.
I'm not sure whether just creating a new workspace would do the tweak, I didn't try it.
for those who come across to this annoy issue worth to try it before switch to a new account.
You can delete your emulators from ~/.android/avd
Then create new emulators.