Quote:
Originally Posted by Malatesta
lol, no doubt this place can get confusing...
Trying out different ROMs is fun and all but honestly, there is more to making a good kitchen than a good ROM.
I'm using what is easily the best ROM right now. It's fast, has all I want, is stable and does what I need it to: That ROM is one I threw together.
No one's ROM that I have tried here comes close to what I have, because this is what I want. And really, 90% of people enjoying someone else's custom ROM is them just liking the way it looks, has the stuff they want, etc. It's like movie reviews.
With the advent of a visual kitchen (e.g. SSK or Calkulin's for TP2) there is no reason for people to necessarily try all these ROMs. The ROM chefs aren't really doing any magic--it simply comes down to having the right "ingredients" in your kitchen. You have those and anyone can throw a solid ROM together in minutes.
And it's easy. I didn't even read the directions on SSK's ROM and had a nice one in 20 mins. Calkulin's is more advanced but it too is a no-brainer.
Just saying the gap between Chef and End-user/flasher is very narrow these days. Once you grab the latest WM source files, you too can be running the latest OS.
Some chef's do stand out for their custom graphics, or quick fixes and that's to be commended. But after one week, I'm pretty much done with using other people's ROMs and just pay attention to using a kitchen and (with baby steps) going further into understanding how it all works.
Everyone should do themselves a favor and just download a kitchen and spend 30 minutes looking over it. It's like an Ã* la carte menu--just pick and choose. Cut out the middle man, you'll be a lot happier. And "tip" yourself when you're done.
|
Sure using some ones canned kitchen is easy, but if your not that great at it troubleshooting even a single issue can be a nightmare. and then your back to waiting for the kitchen chef to correct this error just like a custom rom. To create your own kitchen from scratch with all the packages you take, allot from other devices they may not have been designed for takes a fair bit of skill. its not just extract rom - drop in packages - click cook.
There are registry entries that need to be fixed, things that have to be stripped out. Clean up and an initflashes.dat to manipulate. A single error in the initflashes can cause mass failure in a rom. A single typo in a provxml you edited for the device is a show stopper for the whole routine it executes.
Then there is cleaning out the crapola from the operators that can be tedious, (especially since we found that Telus and VZW now get sneaky with tethering tracking) and leaving in only the essentials. Otherwise you break stuff like sprint tv which i might add was a pain to get going
Then, and only then you might get something usable, that is until you drop in that new leo package and find out that it depends on half the leo EXT
then you put it in and find out u break just about half your rom easy. a few hundred small changes here some hex editing, resigning, massive file, directory and registry comparison and dll and exe dependencies tracking and there and you back in business.... for now, untill then ext thing u want to throw in lol.
so i agree with some of what you said. you have to agree there is a huge difference between what allot of chefs and kitchen cooks do here and the average user who grabs a canned kitchen and clicks a few buttons.
