Develop Reference

Cannot launch AVD in emulator: hax_slot_insert

I know others have similar questions, but my problem is a little different.
When I try launching my AVD I almost immediately receive a popup saying that "qemu-system-i386.exe has stopped working". When I exit the popup, I receive a message which says:
"Cannot launch AVD in emulator.
Output:
Hax is enabled
Hax ram_size 0x100000000
HAX is working and emulator runs in fast virt mode.
hax_slot_insert: Failed to set memory mapping (err=-14)
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
I don't know what to do.
If it helps, I am emulating a Nexus 6P running Lollipop 5.1 x86 (with Google APIs). I set the machine to 4GB RAM, 786MB VM heap, and 4GB Internal Storage.

Useful Note :
If you are specifying 1024 MB RAM then you have to specify the
device screen size is hdpi only and if it is 512 MB RAM then it
should be mdpi or other.
Conclusion :
From the above note we have clearly say that RAM Size should be specify according to the screen size. if you are specified the 1024 MB RAM size while keeping the device screen size is mdpi. then it results should be above mention error.

Large Heap Size Difference Between Emulator and Real Device

I am working on and Android app, and have noticed quite a large disparity between the heap size when I use an emulator, and the heap size when I use a real device.
I am using a Nexus 6, and a Nexus 6 emulator to test the app. When I use the real device, my heap size is around 40mb, and allocated is around 23mb.
However, when I use the emulator, my heap doesn't go above 8mb.
Why is there such a large difference?

How large your heap is depends on your device, how much ram it has total and the device manufacturer. You probably set up your emulator with little ram, resulting in that a large heap on the emulator may be smaller than a normal heap on a real device.
Consider this stack overflow post:
Detect application heap size in Android

How to reduce the memory used by the android emulator?

Is there a way to reduce memory used by android emulator? When I turn on Resource Monitor, It commits over 800MB(I guess this is the reason for all my computer's lags)!
My info:
OS:
Window 7, 2GB RAM, CPU core i3.
Emulator:
Device RAM size: 512MB, data partition size: 384MB, Skin: HVGA 480x320, SD Card: 4GiB.

Try this:
Open the Android Virtual device manager:
Click on a device and select edit:
and then on Hardware click new:
After that select the option Device ram size:
Then just put the value that you want and click on Edit AVD:
Hope that helps. Also as you may notice you can change other properties that might be useful.

One solution is to reduce the Device RAM to maybe 384 MB or 256 MB, as long as you keep the VM RAM size the same it should not affect how your app run in the emulator (except maybe making the emulator run even slower)
But if you want to do software development, 4GB RAM should be the minimum, RAMs are very cheap right now and you really should sharper your tools anyway.

Android devices with small heap

is there a list of android devices and their heap size?
I know how to check programmatically in the app, but I am curious to know.
I have devices with android heaps 32M and greater, and they have at least 512MB RAM. Could I simply assume that all devices with 512MB Ram have 32M of heap? And that devices with less ram have less heap? (16mb? 24mb? ???)
thanks

is there a list of android devices and their heap size?
Not that I am aware of.
Could I simply assume that all devices with 512MB Ram have 32M of heap?
Heap size recommendations are driven more by Android OS release and screen size. Android OS release and screen size also have an impact on minimum effective RAM on the device. So the concepts are loosely correlated, but that's it.
I'd like a list so I could determine mainly if Android 2.2+ devices with 16mb heap exist
AFAIK, you cannot rule out that combination. After all, please remember that Android is open source, so modded ROMs are welcome to configure heap sizes however they want. IIRC, at least one allows the user to choose the heap size. And there are no rules regarding device RAM or heap size in the Compatibility Definition Document, so device manufacturers are welcome to try odd combinations.

Well, you can't assume absolutely anything. There may be a trend like heaps of size 32mb+ on devices with 512mb+ memory. But that's just a trend, not a rule.

There are sofar 4 different types(based on heap size) of android devices.
Those are:
G1----16MB
Droid-24MB
Nexus one-36MB
XOOM-48MB.
XOOM is the device which has highest heap memory.

A source that could help guessing is also if you create emulators. If you create an emulator for Android 1.5, it doesn't automatically adds the "Max VM application heap size" attribut under hardware. But starting with Android 1.6 it sets it automatically to 24 MB. If you choose Android 4.0.3 then it sets it automatically to 48 MB. Maybe that's some kind of typical minimal heap sizes for these Android versions.
EDIT: Just found this: https://stackoverflow.com/a/2634738/1037994. So combining the emulator attribut with this statement, I would guess 24 MB as minimum for Android 2.2+ devices.

How to give max size vm heap and ram size and partition in emulator in honeycomb

How to give max size vm heap and ram size and partition in emulator in honeycomb?.I have run the large application with apk size 89.6mb but
I am getting Installation error: INSTALL_FAILED_INSUFFICIENT_STORAGE
I had given
vm.heapsize 48
disk.cache.partition.size 1024mb
hw.ramSize 512
sdcard size 1 gb
still i am getting error can anybody help to solve this problem
Thanks

Open up your Android Virtual Device Manager (assuming you're using that), and select your emulator.
Click Edit, and simply change the values you need.
My assumption is that your heapSize is too low (I usually set it to at least 25% of my set ram size just to be sure), considering your SD card space is 1 GB.