WM 6.5 Kitchen QVGA and VGA Developer Edition

[joojoobee666]

Originally Posted by dan-htc-touch

add to option.xml <PatchOEM>guidtobepatched</PatchOEM>

i.e.
<PatchOEM>d0b41563-b345-4444-aa15-986e7c7fff99</PatchOEM>

this will overwrite files/ modules, anything with same filename

Sweet. Thanks for the info.

[dan-htc-touch]

yeah, makes alot more types of oem's possible, including taskbar icon oem's with modules, and saves tons of time upgrading to the next build

[vin255764]

Originally Posted by dan-htc-touch

add to option.xml <PatchOEM>guidtobepatched</PatchOEM>

i.e.
<PatchOEM>d0b41563-b345-4444-aa15-986e7c7fff99</PatchOEM>

this will overwrite files/ modules, anything with same filename

OMG ! thank you

[vin255764]

Originally Posted by joojoobee666

Ok, I got it working. It was the reg keys. The cab installer does NOT change these keys. I manually put in the necessary info given by you and rebooted, then *POOF*, I got the hookup on the icons.

Thanks

If you put those entries into rgu they may not show up after flashing.keep an eye on it after every flashing,or you can modify carriers mxipupdate_oemoperators_101.provxml i think,I dont remember for sure.did this too long ago.

[dan-htc-touch]

here is a complete list ofall the tags you can use in oem's for inclusion, auto inclusion of other oems, patching, whatever you need to do

http://www.ppckitchen.org/forums/showthread.php?t=512

[joojoobee666]

Originally Posted by vin255764

If you put those entries into rgu they may not show up after flashing.keep an eye on it after every flashing,or you can modify carriers mxipupdate_oemoperators_101.provxml i think,I dont remember for sure.did this too long ago.

That was my plan. I was going to add them in to the provxml that OEMizer makes.

[gguruusa]

Originally Posted by anryl

cause on bepe tools kitchen the roms are much faster

Nonsense. ROMs built from the same base are the same, regardless of what you use to cook them (errors in assembly aside).

Originally Posted by AndrewSh

Guys you should know - even if you cook same rom twice in 10 minutes with one PC, one kitchen, same settings - you will hardly obtain the same rom. I don't know why it happens - but I know for sure - roms can be different in performance, amount of bugs, battery consumption and so on. During last three days I was playing with Titanium cpr-s and recooked the same 21501 maybe 10 times in one configuration. The results were different all the time - believe me. So it's nothing to do with that, rainabba

Totally wrong. The ROMs are identical, if you didn't change anything. Any differences you observe in behaviour are symptoms of how your phone started up, which you can more or less control.

Originally Posted by rainabba

I ask because I've got a Vogue running my custom rom based on 21210 and a Touch Pro running my custom rom based on 21501 (can't get it to build 21210 with the same selections), and my vogue is visibly faster, smoother, and less buggy. When I say visibly, I mean side-by-side and I know this just should be the case. My TP is a Sprint branded one (288MB RAM, 512MB ROM).

That doesn't make much sense, rainabba. First, why can't you build with the same selections? Second, if you can't build with the same selections, then is that maybe why you observe a difference in performance? Furthermore, you're comparing a vogue to your verizon-ified touchpro - there could be bunches of reasons why you observe performance differences, that have little to do with the rom. As a simple example, the tpro is VGA and the vogue is QVGA. Your tpro is shoving around 4x as much graphics data.

[dsi76]

Jdume,

Your dialer is working very nicely, check it out:




And when screen is locked:

[AndrewSh]

Originally Posted by gguruusa

....Nonsense.....
....Totally wrong.....
.....That doesn't make much sense...

Sorry that we had necessitated you to waste your time and to disavow the messages of totally dumb outsiders
But usually I think before I write about rom cooking. And usually it's not only my private experience.....

[dsi76]

Originally Posted by ksrikanth

Yes, me too facing same problem. ICR and HTC Volume Control works fine with phone canvas only. If I use other dialers, In ICR I cannot see "start record...." in menu while calling/talking and cannot see incall volume slider in HTC Volume Control while calling/talking.

An solution? phone canvas is make my roms very slow.

If you want In-call Recording, just enable this in the registry.... It doesn't require the ICR OEM; however, you can only save to My Documents\Notes with this fix:

; Default in-call recording for AKU 1.4 and higher
[HKEY_LOCAL_MACHINE\System]
[HKEY_LOCAL_MACHINE\System\AudioRecording]
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\Software\Microsoft]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Voice]
"EnableCallRecordMenuItem"=dword:00000001
"AllowInCallRecording"=dword:00000001