[myTouch 3G, Magic Android Development] :
I'd have to look at your rom again today to be able to list all of the differences, Szusz. I believe incompatibilities in the ramdisk, boot.img-kernel, update-script (the famous "getprop" statements), and build.*.prop files can all cause the rom to hang during the first boot.

I have been thinking about our random, energetic approach with Froyo over the past 1-2 days. For sure I don't make decisions for the group, but it seems to me that the intent of this thread "[HOW-TO] Compile AOSP Froyo + [ROM] Latest AOSP Froyo for Sapphire" was and should be to help increase our knowledge on how to compile the rom only. There is already confusion between 32B and 32A, the instructions in the first post are great for those who want to compile the rom, the details related to flashing the rom and to the updates people are making are all over the place. The energy and teamwork is great, but the result is a little messy.

I think it would be better to start two or three threads; one for 32A old radio, one for 32A new radio, and one for 32B. I am not sure if the 32A old radio thread is required, but I guess that depends on user demand and on how many issues exist with the new radio. The purpose of these threads would be to provide a place where (1) everyone can contribute to cooking a solid version, (2) we can provide instructions on how to flash and set up the rom, etc. The purpose of this thread, dferreira's HOW-TO, would stay focused on improving our ability to compile and fix bugs at that level in the rom.

I also think we would be more productive if different people assumed different roles (loose roles I mean because this is after all free-for-all open source community). For example, Sanpei has already proven to be our defacto kernel dev for 32A new radio. dferreira did a great job of putting together a tutorial that made this all possible and hopefully he can continue to provide support with compiling and trouble shooting at that level. Szusz did a great job of compiling the 32A new radio version. And there are many cooks, testers, newbies, etc. in here who are into helping. People can do whatever they like obviously, but I think we would have a stronger team if we each focused on one or two areas and improved our skills.

I started a 32A new radio Froyo thread a while back. We can use that for 32A new radio or I can kill and delete it and someone else can replace it. Either way is fine by me - whatever makes people happy and works - I am not in this because of ego or personal aspirations or anything. Someone else could start a 32A old radio thread if desired and the same for 32B.

I am personally into cooking. Capy is a better cook than I am in many ways in my opinion. Alan (despite driving me crazy :) ) did a great job cooking the CM old radio rom. Other cooks are showing up in this thread who are solid. Maybe it makes sense for Szusz to focus on compiling the rom (since he stepped up already and did a nice job). [By the way, when booting the rom first time, there are errors in the logcat that imply that something related to linking was not done right when compiling the rom - so already there may be ways to fix things by getting better at compiling. Also, maybe the fix for the camera will come from or before compiling - it may not be something the cooks can do.]

I also don't think we'll benefit by having too many variations of cooked Froyo roms - not at this point at least. I think our goal should be to first get rid of as many bugs together as possible for 32A old radio, 32A new radio and 32B before we go off in our own directions.

Anyway, you get the idea. If everyone likes this approach then let's have at it. If you guys think it's lame, that's ok by me and we can continue in our usually manner :)