Quote:
Originally Posted by kidwolf908
My bad. I have edited my initial post to reflect my intentions.
I don't think chefs should stop doing anything. Cooking is (obviously) their passion and should continue to be. However, I think with their assistance, we could make the TP2 and even greater device by adding the diversity and functionality of Android OS.
|
Not to be a **** or anything, but have you ever personally "cooked" a rom for WM? The cooks don't necessarily do it the same way you or I might, but after the various build and Manila versions taken from other similar devices (these don't come in easy-to-use packages found within the "Kitchen"), I think customization and optimization become the main focus for our chefs (regsitry entries, applications, themes/startup screens, Manila/speed/power tweaks, etc..). I don't mean to oversimplify what they do because if making quality and stable roms were easy, we'd all be running our own crap
It takes time, patience, plenty of updating, and lots of testing to make a rom worth running more than two hours.
Now consider porting an entire operating system to a specific hardware set and decompiling drivers while tracing events and fuctions through both the code and harware drivers... it's a very different animal from WM roms. The sticking point right now is the sound (read about it in the Andoir subforum). I've looked at a several functions and proposed fixes in the Android forums, and it's definitely while almost infinitely more involved than cooking roms (coming from 6+ years of C/C++). I'm not familiar with any of the cooks' programming backgrounds and for all I know they may be perfect for the job; I'm just saying that cooking roms and porting Android and don't have much in common in terms of knowledge and experience necessary for success.
It's similar to asking your surgeon to perform an engine transplant on your car.