Recently upgraded from API 16 to 17. Has been retaining all AVDs that were added before and they were working fine after the upgrade too. But today I deleted all old AVDs and added few new ones, each with each device specification available. Earlier, the booting time was around 5 minutes for AVDs with recent versions (4.1.2) and around 2 minutes for AVD with 2.3.3. But now, AVDs with 4.1.2 or 4.2.2 takes 10 to 15 minutes to boot. Moreover, it fails to load launcher. When I touch on the launcher button on the Home screen, it loads the list of Apps and displays a usage tip, "To add an app to your Home screen, touch & Hold it" over it. So far expected. But touching on "OK" for this tip leads to "Unfortunately, Launcher has stopped" error. Not touching on anything leads me back to the home screen.
Tried unchecking AVD options, "Hardware keyboard present" and "Display a skin with hardware controls". Still the issue remains.
It was a memory issue. Problem fixed on incrementing the default value of VM heap by a factor of 16. (16 to 32 and 32 to 48).
I know this should be more a comment then an answer, but I'm too new to StackOverflow. Hopefully a mod transfers this answer.
Are you using an Intel image? Because those ARM images are really slow. When you want to use an Intel image you should also install HAXM (https://stackoverflow.com/a/10772162/1741111). Be sure to select it the right settings. 768 RAM is the maximum on Windows.
These are my settings:
Yes, same issue on my latest SDK for Android 4.4. I am running the "ARMeabi-v7a", from the AVD (Android Virtual Device) Manager.
Every time I started the emulator, it would crash once you selected the apps screen, and tried to launch an app. The emulated app launcher would crash with
Unfortunately, the Launcher has stopped.
Really a pain.. I am running at the API level 19, so probably due to internal program bloat...
Once I raised the VM heap memory from 16 to 48, I noted that a special help program runs, with a big outline of a hand pointing at the "Downloads" app, and explaining that you can press and hold any app to move it to the main screen.
I am running on a WIN-XP (32-bit) old dual core Centrino Toshiba Satellite Pro, so maybe on newer 64-bit machines, the error does not show up. But thanks, Rajeesh.
I just used AVD Manager to edit the parameter screen for the ARMeabi-v7a emulated target device, and now the emulator launches successfully, and I can see (and run) my first "Hello World" app, built with the Eclipse ADT stuff. - Mark_L
Related
I'm trying to launch a project in Android Studio using the Android Virtual Device Manager. At first the Android Emulator pops up with a Google icon and a loading bar, but it never actually finishes loading.
I also tried running the program without using the Device Manager and just clicking the 'Run' button. A, in which case I get this:
"Instant run requires that the platform corresponding to your target device (Android P Preview) is installed."
And if I click on "Install and continue" it says:
"All packages are not available for download!
The following packages are not available:
- Package id Platforms;android-P"
These are all the versions I have installed:
Instant run requires that the platform corresponding to your target device (Android P Preview) is installed.As you can see, the Android P Preview is actually installed. Although it says on the right it's "Partially installed" there doesn't seem to be any update option.
I have no idea why this won't work.
Please help.
This seems like a memory issue with your AVD. Newer API emulator images may require at least 1 or 2GB of RAM in the AVD's settings, and a larger VM heap size.
Setting RAM too low will cause the emulator to either fail to start, or start but never end booting. Use at least 1024 or 2048 MB for API26 images.
Setting RAM to a value higher than your system’s capacity will fail to start the emulator
Emulator’s first boot seems to require more RAM. If you create an emulator with 512 MB for the first time, it might never end booting and hang. If you create it with 2048 MB, start it up, then close it, you may be able to run it with as little as 512 MB from now on, to a certain extent. All RAM values here refer to the AVD’s assigned RAM
Taken from this blog post. Also check out there if you need HAXM or Hypervisor for hardware acceleration.
I am using Eclipse to develop android applications. Initially the AVD used to run fine but when I launched it today, it just did not load. It just kept showing the blank screen with the word ANDROID glowing. I waited for quite a couple of minutes but it did not start. I even reinstalled my sdk but still no progress.
I am using Windows 7(32 bit) with 4 GB RAM.
Check virtual devices characteristics of your device created, sometimes if you choose a big resolution it doesn´t wokrs. check this.
also, I recommend you to use Android studio because eclipse is no longer used
I recently had to reinstall Android Studio as a last ditch attempt to fix the "java_find.exe not found" bug. Unfortunately, this new build seems to have a radically different AVD interface that makes me unable to configure a lot of aspects of my virtual devices that I would have been able to with the original format and worse seems to only create emulated devices that never progress past the boot-up screen. After an extensive amount of google-ing I seem to be the only one on the planet who has this interface, so any explanation or advice would be massively appreciated.
(EDIT) Here's an image of an emulated device I just made. For the API I have no other option other than different versions of 21. In this case I chose the first option.
However, the same problem still persists where the emulator never progresses past the android screen. (It's been running for 10 minutes now when before my emulators would start in less than two.)
I've also just noticed this error hidden way in the bottom left corner of android studio.
"Could not find a matching system image for ABI x86, API 19/null: Could not find a matching system image for ABI x86, API 19/null"
Could this be related at all?
After an extensive amount of google-ing I seem to be the only one on the planet who has this interface
Fear not! I have the same screen. I installed android studio last week and I'm on the Beta version 0.8.14
Unfortunately, this new build seems to have a radically different AVD interface that makes me unable to configure a lot of aspects of my virtual devices that I would have been able to with the original format and worse seems to only create emulated devices that never progress past the boot-up screen.
I just created an AVD for the sole purpose of trying to recreate the issue. I created an AVD with a Nexus 4 and api 19 (kitkat 4.4.2), then booted it by pressing the play button in the Actions area.
It did take a couple mins (~4) but eventually it booted and now works fine.
any explanation or advice would be massively appreciated.
Explanation: sadly don't have one
Advice: reinstall and see what happens. Or show me your actual virtual devices screen so I can try and reproduce your errors.
Edit
I created a new AVD with the same specs as yours, and it booted fine.
Do you have these system images installed? (in SDK manager) or at least the one(s) you are trying to use for your AVD
Well? I've tried increasing the RAM size of the emulator to 1024 MB and there was little improvement on the speed, however, it's still unusable. It has the speed of a turtle.
Anyone got better ideas to make it faster? Is there something I'm not doing correctly?
Check out the android developer documentation regarding 3.0 emulator performance. Scroll down to About Emulator Performance.
Copied tip for convenience:
Tip: To improve the startup time for the emulator, enable snapshots for the AVD when you create it with the SDK and AVD Manager (there's a checkbox in the AVD creator to Enable snapshots). Then, start the AVD from the AVD manager and check Launch from snapshot and Save to snapshot. This way, when you close the emulator, a snapshot of the AVD state is saved and used to quickly relaunch the AVD next time. However, when you choose to save a snapshot, the emulator will be slow to close, so you might want to disable Save to snapshot after you've acquired an initial snapshot (after you close the AVD for the first time).
Seems like everything 3.0 and beyond is slow for me. Everything before that runs very fast in emulator for me. However, I have an Intel integrated graphics card in my laptop. When I turn 3D setting to "Application Settings," I get relatively decent performance from the emulator, at least when it starts up, but then when I try to start any app from the default main app menu (contacts, for example) I get launcher errors. That happens for me on 3.0, 3.1 and 3.2. The one thing I'm suspicious of is that I'm running 64-bit Java SDK. Seem to be a number of posts out there related to 64-bit, but mostly they seem to be point to using 64-bit SDK with 32-bit Eclipse or vice versa, but in my tests, I am not even running Eclipse, haven't even reinstalled the ADT yet, just the Android SDK and created a few emulator instances. Again, prior to 3.0 everything is fast. 3.0 and beyond not good, but A LOT better with graphics settings as I mentioned above. If I could get past the launcher issues, I think I might be all set. Oh, btw also, for 3.0 and beyond, I bumped the memory up to 1024. I've tried increasing the heap for apps to double the default (from 48 to 96) but that doesn't seem to have alleviated my launcher problems.
It is slow. You can try creating a new Emulator with a smaller resolution.
I remember someone at google I/O saying that the HoneyComb emulator will run really really slow due to hardware acceleration turned on.
The PC may use software rendering for OpenGL hence the bad performance. The almost everything you see on the HoneyComb screen is rendered using OpenGL ES.
감사합니다,
Reno
I am trying to test my app on android emulator. So as soon as, i am choosing run the application, a new window pops up on the screen and after taking 1-2 minutes, it goes not responding.
I also tried running the emulator separately using AVD manager. Using this, i am able to start the emulator; but after 3-4 minutes - it goes "not responding".
OS- Windows 7 32 bit [ intel pentium 3.00 GHZ + 2GB RAM]
Java - 1.6
Android SDK - i have the latest SDK with 3.0 OS
IDE - eclipse Helios Service Release 2.
Plz help, i am unable to do anything.
Update: can you guys point me towards other 3rd party emulators which i can use?
Update2: My emulator is taking too much time in launching now. Can this be a cause? If yes, then how do i decrease the boot time?
(This isn't so much of an answer, but might go some way to figuring out the source of the problem; I'd comment on the original question instead but don't have enough rep to do so)
I keep having this problem too. I have an app with a few activities, one of which contains a layout with a Canvas which runs its own thread to do drawing processing. All of the activities run fine except for this Canvas activity which seems to crash the emulator in the way the OP described (the emulator .exe itself crashes rather than the application within the emulator) if left to run for a few minutes. As far as I can tell I'm not doing anything unusual with the thread - I copied the Lunar Landar example in the SDK and worked from that so I'm doing everything "by the book". The app runs fine on real devices.
So, while I realise the OP may be long gone, could anyone else with a similar problem confirm that the affected Activity is using a Canvas, drawing Thread, or anything like that? This problem is a real pain and I can't find any other discussions/solutions for the matter.
EDIT: I recently did a complete, clean re-install of the most recent versions of Eclipse and the Android SDK with all the updates and that seemed to solve the problem. Guess there was a bug in an older version of the emulator that was fixed in a more recent release.
Have you enabled snapshots. If you enabled it then you can be trying to open a incorrectly saved snapshot. If so, while starting the emulator with launch options, uncheck launch from startup
#mudit:remember Android 3.0(Honeycomb) is dedicated entirely to only tablets and not the mobile phones..
Does the emulator prompts you "not responding" in your app or when you just start the emulator without launching an app, too?
A strong advice: you don't need to restart the emulator for every app launch, just keep him running (maybe you already do that).
Does the logcat show some errors prior to the "not responding"? Have you tried creating another AVD?