To cook or not to cook?
 

Just curious, now that the PPCGeeks Official Kitchen supports the 6.1 w/ GPS/REV A......will you cook your own rom, or will you continue to use a custom rom cooked by your favorite chef? I need to clean up my hard drive, gotta bunch of roms that I could delete, lol.

Re: To cook or not to cook?
 

I wonder if the role of a chef might simply change ...

Provide a set of "personal OEM's" and a selections.txt file so that folks could still benefit from the work of a chef (unique skins come to mind) but also take advantage of the flexibility and customization available in the PPCKitchen.

Re: To cook or not to cook?
 

If it's really as simple as checking what I want and unchecking what I don't, I'm definitely going to make my own rom. If I still can't get it right then I'll go back to my favorite chef's rom.

I think this will be great and hopefully people will stop asking Chefs to put in all the little things that they use and not necessarily everyone else.

Re: To cook or not to cook?
 

I agree, I might try it now that the kitchen is out, but I'm also hesitant because I've had so much luck with some of these ROMs that you guys have made for us.

It never hurts to try though. I know if I can get this to work, then there would be no need for UC because I'll just cook everything into my ROM.

Re: To cook or not to cook?
 

omj ur my fav cooker, and ur roms are just amazing...ill always use urs rather than cook my own (call me lazy) =P but uve got an amazing mind man...keep up the good work

Re: To cook or not to cook?
 

All the chefs do great work, but to me there is always a few things I dont' like in each rom, or some things that are missing. So to me cooking your own rom is the only solution to getting exactly what you want.

Re: To cook or not to cook?
 

Yes, OMJ, you still need to cook! Maybee not to such a broad audience, or carriers.

As far as that goes, romchefs could start providing their zzzzzzuserwhatever OEM the oemizer makes and some other files that complete their package. This could somehow be incorporated into the new ppckitchen.org kitchen. Something where the updater updates the omj_whatever.txt and omj_rom.rar into the kitchen and that would be their customization.

But on the other hand, I'm sure that there is a higher percentage of users that are more comfortable with just downloading, and flashing. The just 'Get-er-Done' guys and gals still need taken care of as well.

Re: To cook or not to cook?
 

That's why OEM roms are always a crowd pleaser. I don't know about everyone else, but the idea of having a clean 6.1 with GPS/Rev A and the essentials (touch keyboard, sprint tv, office, etc...) makes more sense. That way I can add my own programs and then delete them if they fall out of favor. See with a ROM the apps are built in so if I want to use Resco Explorere over Total Commander then I am screwed because it is burnt into the damn thing. The idea of being able to get rid of apps is nice; uninstall! The roms are a great way to try out a bunch of programs I would normally not use though. Just my two cents.

Re: To cook or not to cook?
 

I'll be cooking my own rom everyone has there own personall prefrences, and the only way to statisfy that is by making your own rom.

Re: To cook or not to cook?
 

I already cooked one, and loaded it. Now I'm about to re-flash with OMJ.WM6.1.GPS.Sprintv2.
I loved cooking my own roms on the 6700, but I haven't figured out all the reg hacks the chef's are using, and I don't really have the time to do it right now.

The rom I cooked has everything I wanted, but the UC didn't work, and it's seems very slow in response time when I try to open a program.

For now, I'm sticking to the stuff that already exist, and maybe down the road use the kitchen.
The nice thing about the roms you guys make is that there are several people using it.
When/If a issue comes up, several people see it, and work on a solution.
On my personal cooked rom, I'm the only one fixing the issues, and it get tiresome.

Re: To cook or not to cook?
 

is the kitchen gui interface ?

Re: To cook or not to cook?
 

unless a certain chef has an extremely made over rom that cant be done with the kitchen then i'll be cooking my own.

ive come from the apache kitchen scene, so this is my preferred method.

Re: To cook or not to cook?
 

Well I just read in the main kitchen thread and saw that the current HTC touch keyboard in the kitchen isn't working right but will be fixed in the update so I'm going to use my favorite chef's rom until then. The HTC keyboard is a deal breaker for me.

Re: To cook or not to cook?
 

Yes, beyond what you can imagine.
I had a friend w/ a titan, and I was trying to get him to try a custom rom.
He had no clue how to do any of this stuff. I showed him some threads about unlocking the titan, and then pointed him to the PPCKitchen.
He had a new rom the same day, and has not had any problems.

Even if you don't use the kitchen for you own rom, you should definitely install it and look at it. It's awesome what they've done.:headbang:

Re: To cook or not to cook?
 

I had to do some manual manipulation to get UC to work along with the animated boot splashs for each carrier.

Re: To cook or not to cook?
 

I would make my own ROM but it seems like a whole lot of work to figure out the technical side of ROM making.

Re: To cook or not to cook?
 

probably because the default page pool is only 4MB right now - next release has it updated
Not true...the kitchen has the broadest userbase of all. Sure, some minute problem might be just you working on it, but as for general functionality, you have thousands of users across multiple devices working on it...and you don't have to read all the threads, because updater will bring the fix to you.

Re: To cook or not to cook?
 

It's trivial to make a ROM using the kitchen. Even a fairly pimped one.

Re: To cook or not to cook?
 

I'm running my own cooked ROM right now. Love it!

Now if I could only figure out how to make OEMs for my Cubes. Anybody know how to convert a CAB to an OEM?

Re: To cook or not to cook?
 

That's the right idea. The kitchen is already set up to accept add on packs from chef's, making tailoring of your favorite chef's rom an easy thing. For the most part, this is a matter of educating chef's on how to package their stuff. On the plus side, once you learn how to package using the new buildos, a chef's customizations are easily transported from rom to rom, device to device.

Re: To cook or not to cook?
 

OEMizer is your friend, for simple cabs. Complex cabs require effort.

Re: To cook or not to cook?
 

I can oem them for ya. The iCube oem'd up just fine, and created the dir structure you need. I'll attach this one, then do the rest from your sig when I get home.

Here are the Cube OEM's I zipped up:
4thsideonly, iCube, MacFlo, MacFloSuperNova, MinimalCube.

Minimal cube had a duplicate in it qdbkgd.brn, you might check it the cab...

Re: To cook or not to cook?
 

Thanks! I found Ervius's package creator, so I'll try and do a couple myself if that's okay. I don't mind doing my own work. Unless you just really want to do it. :-)

Re: To cook or not to cook?
 

Yeah, got MacFlo Big Button SuperNove as an OEM!

Put the folder in your USER_OEM directory and it'll show up in the kitchen.

Re: To cook or not to cook?
 

This poll is better than the current democratic race! Get out and VOTE PEOPLE!

Re: To cook or not to cook?
 

That's because it's easy to see the logic in going either choice in the poll, whereas in the democratic race, neither choice is logical, unless you are looking to move closer to a Marxist / Socialist government. ](*,)

Re: To cook or not to cook?
 

Can I vote for both? :)

Re: To cook or not to cook?
 

amen to that my friend...

Re: To cook or not to cook?
 

Woo hoo! The self-sufficient have taken the lead!

Re: To cook or not to cook?
 

Seriously... Where is that option...? :mrgreen:
I am using OMJ's latest ROM now and extermely happy with it.

I am interested enough that I will likely look at cooking my own in the future...
It's like your computer, you customize it to what you want... No matter how good they are you are unlikely to find someone that cooks a ROM exactly the way you want... :)

Re: To cook or not to cook?
 

Like what was said in post#2, what really be nice if if the chef's would release kitchen compatible config packs...then people can have the best of both worlds.

Re: To cook or not to cook?
 

This poll is more of a question of time. If you're on this site, chances are good that you would cook your own rom if you had the time for all that it takes to accomplish this. The learning curve is much much less than it was just 12 months ago. However you still have the troubleshooting issues to work out, which is far more time consuming when you're doing it alone, rather than having a rom provided to you along with others feedback here.

In reality, we're all in the same boat...just some may wish to say they "cooked up their own rom", but that's still just a matter of pulling together a collective knowledge.

Some time ago I tried to initiate a snowball effect in leading towards the kitchen team as it's known today. All it takes is one good idea and it can stand on it's own merit and create it's own momentum. Whether it would have happened regardless or was already underway somewhere incognito is yet unknown.

I'll say this though...I've learned as much from feeding on the roms as I have from cooking them. Tasted more flavors than I could have reasonably had time to cook myself. And with that, I've had forced on me some setups which otherwise I wouldn't have ever used again, yet that were better than what I had used before. For instance -
I had given up on OperaMini, but then seen it in a new rom and tried again - this time it was working flawlessly - apparently using the latest version coupled with the es-Java made it absolutely perfect for what I was needing.
Without using someone else's rom I might never had tried it again, nor a number of other apps such as htc-home or Ultimate Launcher, etc, because it takes too long for me to repeatedly test every possible scenario/setup with each new app update.

Other than the Kitchen Team (and a few others) -I think that the stage that it's at now most people just consider "cook your own rom" to just mean changing theme stuff and adding some programs...

It's mostly been just time-management for me though.

Re: To cook or not to cook?
 

I wouldn't go overboard with the ROM cooking, it's pretty pointless just to cook one rom to the next just to try out configuration, that's what Add/Remove programs are for. Rom cooking meaning it's something you want to add/remove permanently.

Re: To cook or not to cook?
 

So true. That's why I wish the ROM makers out there would do kitchen packs instead of roms...would make building on each others knowledge so much faster/easier, not to mention standardizing the process.
I can answer that - it was already going on incognito.

Re: To cook or not to cook?
 

Very true. It is nice to have everything loaded just so, however. Cooking got started back when permanent storage was rather scarce, and wasted ROM space was exactly that - wasted. These days, unused ROM space get's added to the storage pool, making add/remove more attractive for a lot of things. Throw in a tool like tautoinstall, and the need to cook constantly goes way down. It is fun though :).

Re: To cook or not to cook?
 

You are either a true chef or a grateful cheerleader. I second the time constraint issue...
So with that in mind... "Rah Rah" and thanks!!

I say keep moving forward and clean out your hard drive.
Like most excellent software, you usually want the latest version! (Windows Vista excluded... Ha!)

DJ