- Make sure you have a swap partition on your SD card. I didn't, so I unplugged my SD card after switching off the phone and used Partition Magic in Windows to: cut the existing fat32 partition by 1GB. Move the existing sd-ext partition to be the 2nd and use the remaining place there (1GB) to create the new swap partition.
- Switch on your phone and connect through to ADB. Confirm connected by e.g. "adb devices"
- Now run ' adb shell "swapon /dev/block/mmcblk0p3" '. If you have no sd-ext (i.e. your swap is 2nd partition), then you should use mmcblk0p2 instead.
- Now run ' adb shell "free" '. This should confirm you have swap enabled (the rows in swap should not show all 0, but whatever the size of the swap partition is instead).
- Once done with the install, run ' adb shell "swapoff /dev/block/mmcblk0p3" ' to disable swap again
The other alternative is of course cleaner and I believe done automatically by the installer if you install a clean ROM and have an existing swap partition. It would add the swap to fstab to be automounted upon boot and add some extra init stuff for android to enable swap on startup. If you want swap all the time and don't want to clean reinstal the ROM, then I guess you would have to do the above, more info e.g. here: http://forum.xda-developers.com/showthread.php?t=1659231. They used some swapper app for that. Or of course you can do it manually yourself by creating/editing the files needed. I am sure someone else already created some tools/scripts to auto mount swap for you
I only used the above since I am not 100% sure of potential side effects of using swap all the time. I have UHS-1 SD-CARD which was said to be unstable (even though it runs fine for me), so don't want to risk to have swap there. I will use the above again should I need swap ad hoc. You can of course do the same in some terminal emulator to avoid the need to use adb (and thus a PC/laptop to connect to it).
@rubsi: I use ART on both Nexus 10 tablet and HD2 phone. Both running Kitkat 4.4.2, CM11. It is hard for me to sensibly judge whether I have noticed any dramatical speed increase. I would say it is comparable. Even though in time I believe ART will have to be faster since it indeed avoids running any virtual machine at all and only running precompiled code, thus less processing time when running the apps. For sure the installation takes longer. Given this is very early version of ART (alpha I suppose, given that google hides it inside developer options) it is not bad at all. I think what might be better even now (even though I have no paper evidence to prove it) is the memory consumption which I believe is better in ART (at runtime of course, not at install time as seen above











