How To: Kitchens

[Mr. X]

Originally Posted by leanne

On 20757 all bluetooth function work perfectly.

my rom is also 20757/20757 no issues with bluetooth

[nttdemented]

Hmmm well for the time being I've only really found two bugs in 20931; A2DP and the Volume Up. Volume down works perfectly and if you just tap vol down once and use your finger to change from system to ringer tab and make adjustments it all works fine. But if you hit Volume Up it specifically makes 2 triggers at the same time, vol up and the center select from the dpad. I confirmed this in different apps.

The rest has been pretty good so far, I just used it for a while waiting for my lunch in the restaurant, hammered on Opera (3 open active tabs going through IGN, BluesNews and CNET wich are all heavy content pages), used Sprint TV, used YouTube, sent a few txts, replied to a few e-mails and it has been quite solid, smooth and fast in almost everything.

I didn't get to try the BT headset in the car though. Not counting on it working right.

BTW things I have installed:

-Advanced Configuration (did a quick tweak to my TFlow Finger Preassure and speed preferences and set the end call delay to 0 and status display after ending call to 0)
-Diamond TF3D Config (removed People, Call History and Calendar Tabs, reordered tabs to my liking and changed date display format to include the name of the day)
-SK Tools (must have!, haven't used it for tweaking, just process monitoring and I specifically disabled every SIP except for PCM Keyboard, I also built the ROM without EZ Input nor T9IME so now my only SIP is PCM Keyboard)
-Sprint TV Updated Cab
-Audio Volume Fix (Full Volume)
-Inbox Extender (Mark all as Read/Delete All)
-Power Guard
-Resco Explorer and Registry Editor
-WhiteFinix 1% Battery driver and white battery icon

All that has been working normally for me throughout the day with no crashes. I did notice once that TFlo closed and opened and Opera closed unexpectedly during the first few minutes when I was doing some initial testing right after flashing and before instaling or configuring anything but I did a post flash Hard Reset and I haven't seen any of these two issues during the rest of the morning.

[Donatom3]

I switched to TC's 20757 v3b, and everything is working great. Bluetooth is perfect no problems, and the system actually seems to be faster and more stable. So far in my opinion this is the SYS to go with.

Originally Posted by Juggalo_X

my rom is also 20757/20757 no issues with bluetooth

If there wasn't a 20757 kitchen I probably would be using your rom right now. Feedback from everyone sounds good so far.

[nttdemented]

I'm not gonna lose faith on 20931 just yet. jejejeje

:P

I'll get enough time to REALLY hammer on the phone tonight, if not i'll switch to 20757.

[Donatom3]

Originally Posted by nttdemented

I'm not gonna lose faith on 20931 just yet. jejejeje

:P

I'll get enough time to REALLY hammer on the phone tonight, if not i'll switch to 20757.

Just join the darkside now. I say if 20757 is good enough for the Diamond HD it's good enough for the Diamond.

[leanne]

Quick question for those of you who have been doing this for awhile.

If I run OEMizer, and fill in some of the stuff, like owner info, timezone, mail settings, will it overwrite other kitchen settings already put in by the kitchen creators (ie: reg edits, etc..)

Thanks all, I'm just trying to streamline this as much as possible and figure out how it all works. I've read so many webpages in the past few days, I think I am more confused now, than I was before....

[nttdemented]

Originally Posted by leanne

Quick question for those of you who have been doing this for awhile.

If I run OEMizer, and fill in some of the stuff, like owner info, timezone, mail settings, will it overwrite other kitchen settings already put in by the kitchen creators (ie: reg edits, etc..)

Thanks all, I'm just trying to streamline this as much as possible and figure out how it all works. I've read so many webpages in the past few days, I think I am more confused now, than I was before....

I haven't really played to much with OEMIzer but it does edit some things in the kitchen itself. But everytime you open up OEMIzer it reverts to default settings (unless you specify it not to).

[leanne]

So the regedits and stuff that the authors have already put in will or won't be messed up if i run it?

[Donatom3]

I'm pretty sure OEMizer supplements most of the regedits the authors left in the kitchens. It should only mess with registry changes that you choose it to mess with.

[tobeychris]

OEMizer creates its own folder (based on the name you give it) within the OEM directory. So by using it, you will add your own folder to the 2.03 OEM with all the settings you choose (and also create a nice box for you to check in BuildOS).

This being said, only settings that you specifically define will be altered. You will not change any of "our" settings, but there is possibility they can collide with settings somewhere else.

ie: one oem can't set a registry to 0, and your oem set it to 1. Either buildOS will give you an error building the .hv, or you don't know which one will actually be set.

Ghetto actually worked around this for our settings, so that by selecting "Tweaks - Registry" in BuildOS our settings automatically overwrite any settings set by registry files

This is done by using a provxml. Many folders have them, and they are basically files that add registry settings or modify folders on the initial boot of the phone, as opposed to during buildOS.
This is the same method things like the Carrier folders use, instead of worrying about errors with the registry, they're provxml files that are easily inserted.

That was all really for info, just know that if you try to change something that we already change in the registry tweaks provxml, ours will win.