[HD2 Android NAND Development] john0902:
Ah, I do have the 1gb HD2, not the 512mb one -- I guess that explains why the A2SD+ scheme seems like it wastes ~500mb of internal space on mine, since it's designed for a model with 512mb less of internal space.

I have a 16gb SD card, but I'm not sure of the class. It tests out on SD Tools to 11.3MB/s write and 8.8MB/s read. I do know that before making an sd-ext partition, running things off SD, using FA2SD, always seemed slower. Like I remember running Galaxy on Fire 2 off SD and scene changes would take like 10 seconds, rather than like 2 seconds when moved to internal memory.

Even with the 1gb HD2, using a 150mb system partition and a 760mb data partition, I have often run out of internal memory for apps, had to juggle with moving apps to SD, limit installs, etc. Right now, I have the following /data usage:

550.0M	/sd-ext/app
259.3M	/sd-ext/dalvik-cache
236.0M	/data/data

and that's not counting another ~200MB of user apps I've actually converted to system apps to move them out of /sd-ext/app and into /system/app (in order to move them from external to internal memory.)

Given the extra 500mb in /data that I got with A2SD+ on the 1gb HD2, what I've ended up experimenting with is making the /data partition smaller and the /system partition bigger and moving user apps from /data/app/ to /system/app/. The partitioning tool was limited to a /system partition of just under 450mb, so that's what I made. This is my partition scheme and utilization:

/dev/block/mtdblock3 447.0M 290.2M 156.8M 65% /system
/dev/block/mtdblock5 464.9M 256.4M 208.4M 55% /data
/dev/block/mtdblock4 10.0M 1.2M 8.8M 12% /mnt/cache
/dev/block/mmcblk0p2 1.8G 842.0M 889.8M 49% /sd-ext
/dev/block/vold/179:1
12.9G 10.2G 2.7G 79% /mnt/sdcard
/dev/block/vold/179:1
12.9G 10.2G 2.7G 79% /mnt/secure/asec

However, this approach (assuming there is no other problem with it of which I'm ignorant) is pretty tedious, 1) because it takes time and effort to convert user apps to system space, and 2) because not all apps run properly off system (e.g. Google+ and Google Maps worked, but Google Goggles didn't.) Also, even despite all my efforts, I still have about 350mb unused internal memory. So I'm wondering if the next logical move would be to try to reinstate the dalvik-cache (~260mb) on internal memory, rather than on SD -- or, alternatively, if there is some other approach that would make the most of the 1gb HD2's storage.

I actually notice frequent slow downs on my HD2, often getting the "stopped responding: wait/force close" dialog. When installing apps, for example, it slows down considerably. When choosing a new widget, or a shortcut from the list of apps, there are big delays in getting the list. I had to go back to the old version of DroidWall, because the new version with app icons in the list just crawled. Perhaps I just have too many apps. Similarly, with about 100 contacts, I've yet to find a contact tool with smooth scrolling with contacts with pictures. Likewise, I've tried Launcher Pro, Go Launcher, ADW, ADW EX and they all seem to stutter or bog down, once loaded up with 5+ screens of widgets, if only at least when zooming in and out of the screen preview. Maybe I just have too many widgets.

My memory 'free' looks like this:

# free
total used free shared buffers
Mem: 420860 407268 13592 0 3940
-/+ buffers: 403328 17532
Swap: 0 0 0

when pretty much idle, except for whatever is running in the background.

Any advice?

Any pointers to the scripts to move dalvik-cache back to /data/? Is it as simple as removing the /data/dalvik-cache symbolic link pointing to /sd-ext/dalvik-cache? Or is there something in the ROM to rebuild it if it's missing?

Thanks for any input.