[HD2 Android NAND Development] AngelDeath:
I appreciate your look at the rom, and your input, so let me point a few things out so you understand some of the things, and by no means is it a bashing, but might clear some things up in your thoughts.

First a 400mb partition clearly isnt enough, thats just barely giving you any space at all, with a 445mb partition and 8mb boot and 8mb cache, you have a bit more breathing room. The rom fully installed, takes exactly 403.26mb (Give or take a few mbs), a 400mb partition clearly gives the system partition 0mb of room to do anything. Also understand as for TMOUS users we have the space to put this rom on, where EU users have to use an SDcard, most roms being released today use just about the whole phones space to install the rom, and hence having extra info stored on the sdcard. One of the key problems for us is, using magdlr, its setup to use only 512mb for rom, because this was done based on EU phones being limited in space. (Please if I am wrong someone correct me). If colluta made a magdlr for TMOUS users to use the whole phone, I think alot of the shaving of the rom wouldnt be done, and some of the issues would stop I think.

As for the ram, your 100% right, its a hog, but every sense is, the bigger and complex sense becomes the more hungry it is. But as a suggestion, I would suggest if you didnt do it based on your reply, i would re-partition your phone to 445mb and give it the breathing room it needs (Assuming your a TMOUS since you used a 400mb cwr), and then try, the phone has been setup so apps install in the data part of the phone as to save space since you have close to 400mb of room. If you look at most of the roms Sense 3 that are out, all of them wouldnt fit at all on our phones. Mine does. Its been shaved, apps have been removed, etc. The first rom ram with the same amount of ram as mine does, I might have squeezed 20 ro 30mb more, but thats far from enough.

The idea of Android OS is it suppose to uses the ram as needed and when an app needs ram it kills background unused apps to free ram, now does that actually work flawlessly? I bet not. But I have been running this since last night with moderate use, and even I am surprised as how well its running and its responsiveness. Is there room for improvement? Absolutely, I'm a programming idiot and dont know the first thing about android, I am use to windows. And your right its going to come to a point where these roms arent going to work on older phones due to space constraints, but supply and demand.

But lastly its coming to a point with these roms, that people who cant upgrade, for whatever reason and are stuck with older phones, or who just like their phones, have a choice; Do I got for an older rom and play my games and do hundred things at once when I really dont have to, but want to, or Do I use the new roms and dont do as much as I use to except the important things? Same as desktops, do i buy Intel for stability and work, or do I buy and AMD for games. Same concept in a way with froyo sense and gingerbread sense.

And to answer about maps and such, the problem from what I gather with google maps is not the ram useage, but the reference point in the rom thats causing it. Remember there are not many people attempting 3.0 as you said, maybe cause its big, maybe cause not many chefs are left in the HD2 and moved on, but just as an example, the DesireHD and Inspire 4G have less ram then the HD2 and it runs near perfect on those, the reason? more dev's trying to make it work. So the map glitch, graphix glitch etc also have to do with the source possibly, we still dont know if that will solve anything.

But Thank you for the input, I always like comments, whether they are good, bad , ugly, or indifferent, its well appreciated.