[Nexus One Android Development] Docmjldds:
Long Humble Pie+ reply follows.....

There's always one in a crowd of many that.........:eek:;) I can eat crow when it's served up in a correct fashion. I knew sooner or later someone , with proper experience, that knows what they are doing, and insisted they have done it correctly all along, would eventually post here and make me have humble pie and crow ala mode. No harm no foul. I deserve it. But that said, I will stand by my opinion that fully 75% of posters here have NOT tried to do it the way it has worked for me, so all I can do is treat everyone as equal until stated by someone...like you of course.

There are issues here, out of my control too. Until only a few hours back in a PM chat with Rod, look at the EXT4 large partition and it automagically becomes EXT2 large. Now, I have no idea why it does this. I have no idea if in doing this, it makes this unstable to the point that it may work under set circumstances based on hardware differences.

The nand issue. I can state I probably wrote close to two dozen or more posts back at specific users who would basically tell me I wasn't doing it correctly, and I would fire back that I too have had years of experience in PC's (I'm a youngish 60 BTW) and cut my teeth in DOS 2.0 and QEMM memory management from the late 1980's. IOW...Until I was led to discover that I had an astounding 85Mb of bad blocks in my /data partition, along with a few more bad blocks in /system and /cache, it was driving me insane why users could follow eVil along for weeks installing Sense ROMS and I had bootloops only. (I'm assuming you know of eVil and Sense ROMS)

So, this EXT4 to 2 issue for one is annoying to find out. The fact I also had issue here with partitioning in thre phone instead of externally, and when I switched methods, everything worked, is basically why I was insistent on this issue too. All I can do is state what works for me and ask users to repeat. I guess, I have been around too long to know that know matter what any of us do here, there's always outside influences that throw us a curve ball.

When I see users asking...should I wipe my caches before I install, etc. or I really don't want to do a full wipe, can I....fill in the blank......or when I see how come when I use a2sd commands this doesn't work......I think you get my point. Also, FWIW....c2sd command will totally mess up the working setup. Don't use it. A nandroid backup does restore with no problems, BTW. I tried the terminal command tonight when out in a restaurant, taking a break from this, and my wife laughs at seeing the X for 15 minutes, before I grumble and restore.

Good post. Thanks for the effort. I appreciate users that do go the distance and put in the time correctly. That's the only way that apples and oranges can really be compared here.

Here's to Rods next tale of woe for us to try, although I have to say, I am running the ROM as stated with 2700+ Quad scores, but more importantly, showing like a few others that this can work. And before this, I did write up a decent FAQ on using similar scripting in a2sd ROMs such as stock MIUI-DEV versions that run terrific with 2200+ quad scores, stability and a ton of EXT memory as we are supposed to have here. And the script works on CM7 ROMs too.

BTW....it was the OP from Kangorama that finally showed me how to see bad blocks with a logcat of an install. Then had to battle with HTC to RMA for a replacement, after I had rooted my phone. They did replace it, BTW.