Develop Reference

marshmallow & lollipop genymotion emulator not at all starting but all other emulator below api 21 are working in genymotion same system

i have gone through different questions in stackoverflow regarding this topic and this is not any spam question
i am able to open all the emulators which are perfectly working but lollipop and marshmallow are not even starting in the same system at same time i have tried in different instances but no use
can any one explain me the reason why it is not working should i have to make any more changes so that both these versions work for me in genymotion
and i forgot to mention i have update virtual box and genymotion to the latest version also no use

Android Studio Emulator seems incomplete?

I have installed the latest Version of Android Studio. Now I like to set up an Emulator. I had used the SDK Manager to load the Intel Atom Image, and set up an AVD.
I think I have done this like in all other Examples but if I start the Emulator, all what I can se is an empty home screen without any other icons or setting. I thought the emulator would be like an real device, or quite close to it.
Maybe I think wrong?
But I had seen videos where the emulator is like an real phone.
What can i do to get my emulator to an pretty phone? :)
Thanks all.

Check if in your emulator parameters the "hardware buttons" are checked. However, sometimes android studio emulators are giving some errors. You can try download Genymotion emulators for android, if you don't lack ram it will work out pretty well for you.

Android SDK Emulator won't load

So i'm having awful trouble trying to get the Emulators in the Android SDK to start up. I can create the AVDs just fine, and then when hitting the 'start' button from the SDK Manager, bring up the small loading console window, indicating that the emulator is launching. However, after that, nothing happens!!
I have read many threads and posts with people having the same problem, maybe to do with the settings requiring too much memory, with some people waiting 30 minutes for the emulator to load!!
When trying to run the AVD emulator through terminal, I simply get a 'Bus Error' with no further indication of what could be going wrong...could it be a memory issue?
What I did to get where I am now:
Download the Android SDK package for Mac. I'm extracting the sdk only, not eclipse. I'm on Mac 10.6.8.
Install the SDK, and download the latest version of Android in the SDK Manager, along with default tools.
create a AVD and hit start.
window pops up to boot the emulator, that process is complete and window closes.
Nothing happens.
My knowledge of the sdk tools are very limited, all I want is to be able to do some testing...
Any help greatly appreciated!
Thanks

Actually, the simplest way to get emulators running right now is probably GenyMotion. They provide an interface, and pre-configured emulator images to make it pretty simple to get running.
This is not an endorsement (I use the standard ADT myself) but a lot of people find their tools useful.

Here is my suggestion: instead of using AVD, start using espresso and virtual remote android hardware emulator from Google servers - also known as android-test-kit. You will have the possibility to run and test you App on several different devices, without the need to spend money on actually all different devices for developing and testing purposes before releasing your Apps. You find further details here:
android-test-kit
Why Espresso
The 2 videos are somewhat long, but worth watching.
Taking this approach will solve your problem, save you money, and improve your productivity.

I run into the same issue on my mac 10.6 and it only works if i do
emulator64-x86 -avd my_android
Besides, my virtual device has to configured using x86 but not ARM
maybe this link can help you.

Android AVD Problem

I just created a android AVD which runs on the 3.1 version. After it starts running, it takes a lot of time to move from one activity to another. Is there any way I could speed up this process.

Emulators will always run much slower than the devices. Anyhow, the android emulators now are much faster than before, so make sure you keep your sdk updated (and you obviously have, since you're running 3.1).
Also, I consistently noticed that emulators running in ubuntu 11 are faster than the same emulators in Win 7 (same hardware), so you might want to give ubuntu a try.

Android emulator takes a lot of memory while it's starting up. It's normal. The thing you can do here is using a feature called snapshot. Snapshot will save your time (and probably resources) from the start booting up.
Read this article for more details:
Optimizing Apps for Android 3.0
under the "About Emulator Performance" section.
Hope it helps.

Why is my Android Emulator crashing?

I'm developing a application that works on linux. I want to port this to the Android SDK Emulator. But everytime I start the application the emulator crashed with a segmentation fault.
Somebody has any clue why a selfmade program that's running on the Android Emulator could crash the entire emulator?

Can you post up some code examples / logs of what is happening? You don't provide enough information for us to suggest why it would fail.
Best thing I can advise is to create a new emulator (only takes a few clicks) and try deploying your app on that, possibly try a different version.
If you can post up some logs/code examples of what might cause this, we can provide better answers

Another debugging point to try would be launching a demo application/Hello Android on the emulator, to see if it is your application specifically.

Apparently there was a bug in the version of the emulator that I used. When I updated the emulator to the latest version, it was solved.