Should the chefs start helping Android?

[sjs01]

Originally Posted by JDM_SOHC

Sounds highly unlikely to me... If writing codes were as simple as cooking ROM's, and the assumed bounty had been offered (like it already has) I think we would have had an excellent Android OS already ported for us WinMo users... But since it hasn't quite worked out like that, I doubt it's that simple...

I believe he was being totally sarcastic trying to show the OP how chefs can't just port android that simply... That's all his point was. Because apparently the OP thinks that porting android is pretty simple.

[kidwolf908]

Originally Posted by Scenemaker

Apparently cooking ROMs and writing code are one in the same... And...writing device drivers for linux is definitely something a cook who uses a visual kitchen to create a ROM can do with ease.

This is not something that I am implying at all.

The few remaining issues with Android being fully functional have to do with portions of code that WM uses. Therefore, I thought it might be beneficial if some of our more experienced and knowledgeable chefs take a look at some of the code in their ROM's (such as the WM audio driver, camera driver, BT stack, etc.)

I apologize for stirring up everyone's emotional ties to WinMo, I was simply trying to bring up a possibility that may not have occurred to anyone yet.

I am very appreciative of the chefs and all that they have done. I ABSOLUTELY AGREE that without the cooked ROMs, the TP2 would be a much more buggy and slow device. However, I feel that in the past few months, noticeable improvements in ALL WinMo ROMs have been few and far between, which is why I thought it might be a good time to call WM good and be done with it.

Who knows, maybe I am just flashing the wrong ROM's. I've been using X ROM exclusively since April... I guess I should check out some of the others like Vin's ROM.

[kidwolf908]

Originally Posted by sjs01

I believe he was being totally sarcastic trying to show the OP how chefs can't just port android that simply... That's all his point was. Because apparently the OP thinks that porting android is pretty simple.

The OP (being myself) doesn't think it is that simple. The OP (myself) simply thought that the assistance of some WM chefs might help move the ball forward a little on the few remaining issues in Android since the remaining issues have ties back to how WM does things.

[sjs01]

Originally Posted by kidwolf908

The OP (being myself) doesn't think it is that simple. The OP (myself) simply thought that the assistance of some WM chefs might help move the ball forward a little on the few remaining issues in Android since the remaining issues have ties back to how WM does things.

I'm sorry, from your posts it looked like you thought it was just simple to port android, and seemed like you thought the Chefs should just start doing everything we say. Your first posts didn't seem like all you wanted the Chefs to do is move the ball forward, it seemed like you wanted them to drop what they were doing to work on android.

[JDM_SOHC]

Originally Posted by sjs01

I'm sorry, from your posts it looked like you thought it was just simple to port android, and seemed like you thought the Chefs should just start doing everything we say. Your first posts didn't seem like all you wanted the Chefs to do is move the ball forward, it seemed like you wanted them to drop what they were doing to work on android.

x2 on that

[kidwolf908]

Originally Posted by sjs01

I'm sorry, from your posts it looked like you thought it was just simple to port android, and seemed like you thought the Chefs should just start doing everything we say. Your first posts didn't seem like all you wanted the Chefs to do is move the ball forward, it seemed like you wanted them to drop what they were doing to work on android.

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.

[quick99si]

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.

[kidwolf908]

Originally Posted by quick99si

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.

I'm not saying they will be able to do it either. I'm just saying that out of all of us, the cooks are probably the more technically inclined and coule therefore, probably, offer the most help.

[austin420]

[Scenemaker]

Originally Posted by JDM_SOHC

Sounds highly unlikely to me... If writing codes were as simple as cooking ROM's, and the assumed bounty had been offered (like it already has) I think we would have had an excellent Android OS already ported for us WinMo users... But since it hasn't quite worked out like that, I doubt it's that simple...

You failed to detect my sarcasm, sir.