How To: Kitchens - Page 52

**Drybonz** · #**511** (**permalink**) 12-01-2008, 12:06 AM

Quote:

Originally Posted by fr4nk1yn

I agree with tobeychris.
Some of these issues, including a few of mine, aren't related to the kitchen itself but the changes or programs we're installing.

It takes a lot of "playing" to get a mixed and matched OEM running. I have bits from Calcu & PPCKitchen in mine now.

The only question is where to post once we run into the "strange" problems.
Start a new thread? Or post in the Kitchens thread?

One thing that would really help, and I understand this would probably take a good bit of effort to compile, is a description of the components in the OEM, etc, and a list of know bugs for the different versions so people would have something to go by.

Just a thought.

**tobeychris** · #**512** (**permalink**) 12-01-2008, 12:10 AM

Haha, I wish I knew all the bugs in each version.

The best I can do is the list of version numbers, if a bug comes up, I (along with the rest of the community) will try to fix it.

nttdemented · #**513** (**permalink**) 12-01-2008, 12:52 AM

Heh, so many versions of things flying around it's making my head spin. It pretty much up to everyone to try things out and chime in. I'm about 75% done with a Kitchen setup of a very stable personally configured ROM mixing and matching things, doing my own custom OEMs and reg tweaks. You do need some time on your hands I've spent all afternoon and night today learning to do some things.

I'm still stuck on one particular thing I've been trying to OEMize, and that's Touch Response v0.02.2. Got everything in their respective locations, all the registry settings I've been able to find in the registry post-manual installation, checked to see if it's setup as a service, etc... no go on the cooked version for me. Don't know if anyone else is trying but then again I'm still pretty new to this.

Thanks to Tobey for getting me started in a couple things

**Trident** · #**514** (**permalink**) 12-01-2008, 01:12 AM

Quote:

Originally Posted by tobeychris

I really wish people would stop trying to mix and match kitchens. Calcu's Kitchen is based off of this, but the changes that are made to not coincide with ours. You cannot just take ROM essential elements out of that one and drop them into this one. If you do that and you have a problem, it's up to you to fix it, or use the one's I've posted.

I'm just trying to use the tools provided to make something that works well for me. I'm not complaining or being negative about this or any other kitchen.
If you'd prefer, we can start a new thread for these "hybrid" kitchens... I just thought that since the majority of the tools used were from this Kitchen, it would be most helpful to post here.
I'm very satisfied with what I have now. I compressed it and made a version without my personalizations in it... I'd like to share it if I can figure out how to upload it... or if anyone would want it.

The only think I'd ask for is what I mentioned earlier. It would be nice to have a way to record what selections are being made so it would be repeatable and reportable for others.

**tobeychris** · #**515** (**permalink**) 12-01-2008, 01:59 AM

Well, I didn't make buildOS, so that won't happen.

As for the 'starting from scratch' all you have to do is edit the options.xml in each oem folder to true or false, depending on your preference. If it doesn't have one, it's for a reason.

Now, I could theoretically change the entire OEM folder to one option.xml like in the SYS, but I have no intention of doing that, because it makes no sense to change the way the tools work.

**Drybonz** · #**516** (**permalink**) 12-01-2008, 11:52 AM

Quote:

Originally Posted by tobeychris

Haha, I wish I knew all the bugs in each version.

The best I can do is the list of version numbers, if a bug comes up, I (along with the rest of the community) will try to fix it.

Yeah, I figured it would be far fetched to compile. Just trying to think of a way to eliminate some of the trial and error.

nttdemented · #**517** (**permalink**) 12-01-2008, 01:35 PM

Quote:

Originally Posted by Drybonz

Yeah, I figured it would be far fetched to compile. Just trying to think of a way to eliminate some of the trial and error.

Trial & Error R007Z J00!!! 477 Y0UR B4S3 4R3 8370NG T0 US!!

**Drybonz** · #**518** (**permalink**) 12-01-2008, 02:07 PM

Quote:

Originally Posted by nttdemented

Trial & Error R007Z J00!!! 477 Y0UR B4S3 4R3 8370NG T0 US!!

Yeah. I got to the rom I am using now thru trial and error and I am starting to think it just might be a keeper.

nttdemented · #**519** (**permalink**) 12-01-2008, 02:42 PM

I'm getting ever so close to my perfect ROM now that Touch Response is working 95% consistenly and FlipIT gave us Landscape Manila.

I spent a lot of time in the weekend polishing it up. Still got a few kinks to iron out but I'm almost there. I'm willing to share it to a few Sprint testers to see if its worthy of a release.

kaiguy · #**520** (**permalink**) 12-01-2008, 08:10 PM

I haven't been following this thread as usual since I've been out of town, so I apologize if this has already been covered (I tried searching, and came up with nothing). I wouldn't consider this a bug, but for full disclosure:

Kitchen: 5.0
OEM: 3.0
SYS: 20931 v5a
Stock settings, Sprint Carrier

How do I disable the vibration when the hardware keys are pressed? I thought it might have had something to do with the vibration setting in TouchFlo, but that doesn't seem to make a difference one way or another. I hate asking what should be an easy question, but I just can't seem to figure it out.

Thanks!

EDIT: nttdemented, I'm down to test out your ROM!