yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] pfcsabre:
eras2rs' on a roll, why don't you release your own ROM, hmmm...? :rolleyes:
[Touch Pro, Fuze ROM Development] andyle2k:
OMG thanks so much you are my hero!!

Can't wait to chuck the new Rhodium TF3D on this thing, anyone else think that thing is more trouble than its worth? Seems so slow and full of bugs atm.
[Touch Pro, Fuze ROM Development] nnkumar73:
Thanks eras2r, appreciate it. As others suggested may be you should have your own ROM. :)
[Touch Pro, Fuze ROM Development] Captain_Throwback:
Or, at the very least, maybe you should start a new thread for your kitchen, since the one in the first post is WAY outdated now. It would make it a lot easier to find the most recent version (I mean, it doesn't even include Da_G's most recent version - but I understand this thread isn't his main concern, w/new WM6.5 builds coming out weekly & his grandma recently having been in the hospital). So then, as you make updates, you can just update the first post.
[Touch Pro, Fuze ROM Development] nnkumar73:
eras2r, when I opened up buildOS the version said 5.05, but I know it is just a number and doesn't mean much. But may be you want to update it in your next release. :)
[Touch Pro, Fuze ROM Development] lavike:
eras2r & Da_G - Great work! Thanks!

I think I've got a different battery icon issue than other folks.

I'm using the 21032 build and when I either put it on the charger or connect it to my PC to sync (I've enabled it to charge when I sync) I get the charging icon. When I remove it, the charging icon remains the same until I power cycle the phone.

Any ideas why the icon doesn't change to show the batter level instead of the charging icon even when its not on a source that can charge the phone?

Thanks!
[Touch Pro, Fuze ROM Development] Da_G:
Good point, i updated the op with a link to eras2r's update.. crediting him of course :)
[Touch Pro, Fuze ROM Development] eras2r:
My bad. When I upgraded all of the packages from 5.05 to 5.08 I missed that ATT used a different phcanOverbmp.dll with different battery values. Here's a cab that will resolve this. This only matters if you built a ROM without the 3NewIcons package and your experiencing what lavike described above. Don't install this if you are using the NewIcons package. It will screw up yer battery icon.
[Touch Pro, Fuze ROM Development] player911:
Yea I just used your AT&T S2A Phone Canvas you posted back a few pages which was causing my problems. I editted the RGU file and was going to post my findings, but you already did.

Also I found another minor error in the "3 New Icons" package (I don't know who posted it) but it adds a funky Key file in the registry (last entry in the RGU file). The funky Key is supposed to be a Dword, which is already assigned a few lines up. Fortunately it doesn't affect anything, but when there were battery icon issues before and your trying to fix it... things were all crazy.

All it takes is changing the BatteryIconMax (or whatever) and changing it from "21" to "101"... and a power reset.

The new Manila 2 is publically available in beta phase. Most of the pre-released bugs we were experiencing should be cleaned up with the new build. At this point I only see it as 3 separate CAB installs.
[Touch Pro, Fuze ROM Development] eras2r:
Thanks for the invalid reg entry in the RGU. Looks like I shouldn't completely trust the auto packaging and Provxml Translator tools :) That entry can be safely deleted.
[Touch Pro, Fuze ROM Development] xboomer55:
I was struggling with this too. phcanOverbmp.dll in the ATT Phonecanvas pkg has the standard 21 battery/charging icons...1 charging and 20 battery level icons (decimal 21 or hex 15). A phcanOverbmp.dll that supports 1% battery level icons has a total of 101 icons, 1 charging and 100 battery level (decimal 101 or hex 65).

Good grief!...icon trivia!...

All good now.

Thanks
[Touch Pro, Fuze ROM Development] illi:
Hi Da_G

I am attempting to cook based on the recently HTC released WWE/Asia ROM 5.07.707.2. I want to achieve what you have done to 5.05.405.1:

ROM's cooked with this package will not have an SPL, Radio ROM or Splash Screen.

ULDR has been reduced to save approx. 3MB.

nk.exe has been no-certificate patched to allow loading of unsigned drivers.

Page Pool is set to 6MB. It has been unlocked and can be changed with the pagepool changer tool.

DataCacheSize in XIP has been increased from 2048 sectors(2048*2048=4MB) to 4096 sectors(4096*2048=8MB)

Several Packages have been updated from their original versions.

Manila has been CFC compressed.

Default Theme is HTC Black.

Recommend keeping Connection Manager in the ROM as I have not set up any default settings for data.

Security settings have been relaxed to allow RAPI and Unsigned CAB installation.

My questions are:

1 - what are the files from your ROM that I should port over?

2 - what are the files from WWE/Asia that I should remove?

3 - As for Manila, I have one specific jpg file that I want to use; which is the clock. How can I include it in your compressed CFC Manila?

FYI I have cooked before but for the Tornado Smartphone. While mentioning about the Smartphone, the Tornado has a very good security feature. When the phone is locked, the homescreen can still be viewed. Thus, there is no need to unlock to view, eg appointments, clock, number of new emails, etc. I wished I could port this feature to the Raphael.

Your assistance is very much appreciated.

illi
[Touch Pro, Fuze ROM Development] eras2r:
Updated Kitchen - Rhodium 21040 XIP/SYS - 5.08.502.1

...More toys for all you girls and boys!

Finally got an official shipped Rhodium ROM to play with. So here's the new update to Da_G's kitchen:

XIP/SYS updated to 21040 Rhodium Release

XIP optimized and ULDR partition reduced

XIP patched for Cert and 24MB PagePool

XIP contains WM6.5 DDI.DLL

shell32.exe patched for timebomb

New package for MSVC

New package for WindowsLiveIM

NewIcons split into 2 Packages (should resolve battery icon issues)​

Link: http://rapidshare.com/files/213266955/eras2r-21040-kitchen-5.08.rar

As always special thanks to Da_G!

...now get cooking :D
[Touch Pro, Fuze ROM Development] dizzyraider:
Awesome eras2r! Already on top of it :)
[Touch Pro, Fuze ROM Development] crazyC:
Another release - I am still on the 21032 version! Do you know if there are going to be more releases soon - I am trying to customize this one a bit and it seems quite stable and reliable and so unless there are big reasons to change I might leave it a week or two as I just cannot keep up with your pace. (Thanks for all the effort and releases by the way)
[Touch Pro, Fuze ROM Development] fcuk:
Sorry for silly question, but is it safe to remove folders with games, welcome center, and transcriber inside SYS?
[Touch Pro, Fuze ROM Development] Merdinh:
Yes its safe to remove those folders.
[Touch Pro, Fuze ROM Development] player911:
There aren't any major improvements from what I can see.

I typically bounce back and forth between WM6.1 and WM6.5 (WM6.5 being my fav) and try to find something that has all the latest features... and stable. Once I find a build that has all the features, runs great, and stable... I'll sit on it for a while.

I'm using WM6.5 21193 with the HTC Menu enhancements and Notification manager cooked in... and it works fantastic. I have all the packages I need installed and working perfectly.

So do what you want. Unless the Rhodium ROM has any newer drivers that are beneficial, I'm not moving.

[EDIT]

Great work eras2r. Glad someone is keeping this up. I'm sure it helps out Da_G tremendously. I think everyone is waiting to hear whether or not the new Rhodium rom has any new drivers we could use.
[Touch Pro, Fuze ROM Development] Da_G:
I've been plonking away at the rhodium drivers in addition to working with wm6.5 and collaborating with alot of other chefs on IM to spread the knowledge :)

So far I know that the ddi.dll from rhodium won't be helping us (it doesn't boot, unless I missed something)

The GPS drivers are also not compatible.

It uses the new widcomm bluetooth stack rather than msft's bluetooth stack, to support 2.1

as to illi's question:

If you use the \ROM\os.nb.payload from the kitchen, you'll get the first 5 improvements you listed.. the others are in the packages in \Packages (which eras2r has updated, once again :))

As far as what to remove from the ROM, i haven't looked at it closely yet, so i'm not entirely sure on that. But if you use a program like beyond compare to compare the dumped wwe asia rom to mine, you should be able to see which packages were removed, etc. I recommend this program (not free), it really makes cooking easier :)
[Touch Pro, Fuze ROM Development] hilaireg:
Package Consolidation Clarification

I'm going to refer to the PACKAGE_Raphael_AdobePDF to make it easier for me to understand ;)

Most chefs typically move the PACKAGE_Raphael_AdobePDF to the Packages folder and provide and OPTION.XML to allow the package to be selectable during the cooking process. When examining the PACKAGE_Raphael_AdobePDF package, it becomes apparent that the _0409 package has been consolidated into the package.

1) What is the downside of keeping the two folder separated - i.e not consolidating the contents and simply moving both folders to Packages?

2) Assuming the answer is to avoid having to create an additional OPTION.XML that could accidentally be forgotten during the cooking process, why is the .DSM file from the _0409 package omitted?

Appreciate any insight (or link).

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
Do we need to roll-back the GPS-related drivers to a version from a previous 'eras2r' kitchen?

Cheers,
[Touch Pro, Fuze ROM Development] Da_G:
The reason to consolidate is so you don't have 2 checkboxes to add for each package in buildos.. there's nothing lost by consolidating the packages other than not having 2 seperate folders :) The reason for them being seperated in the first place is that when building the rom the 'main' package is common and inserted into any language rom, but the _0409 package is specific to english, _0804 would be for chinese simplified, etc. - So when creating a multi language ROM, it makes that part easier.

As far as the .dsm goes, it doesn't really serve any purpose for our needs (and you can only have one .dsm per package) so we use the main package .dsm only. It could be modded using dsm builder to incorporate the new files, etc. - but that's only necessary if you intend the ROM to be dumpable from its cooked .nbh state. Again that doesn't really serve a purpose in our case as we all share our kitchens freely, right? :)

So the .dsm's get stripped from the final ROM anyway, in the interest of speeding it up by not having tons of random files strewn about the filesystem :)

Re: the drivers, i don't believe eras2r used any of them, i'm just sharing my experience from trying them myself :)
[Touch Pro, Fuze ROM Development] hilaireg:
As always, the knowledge transfer is much appreciated!

As for sharing ... absolutely; building up my knowledge so that I can possibly put another one of those TUT's together ;)

Cheers,
[Touch Pro, Fuze ROM Development] eras2r:
As for drivers, none were added from the 21040 Rhodium ROM. As Da_G stated, the new DDI.DLL doesn't work :( ...GPS didn't either, bummer.

\OEM is still the same and stable from the 5.08 ATT ROM. I must say this build is fast :) Please try to use as many features as possible and report on any problems.

-e
[Touch Pro, Fuze ROM Development] hilaireg:
Few observations; non-critical, IMHO:

- The audio adjustments to the CSV seems to impact VoiceCommander (not VoiceSpeedDial) - I'm sure minor tweaking of the CSV(s) will deal with that.

- TF3D still has "hooks" into the Opera Browser; haven't figured out which registry changes to make (or is it in the Manila pages).

- TF3D Programs has a broken shortcut; JETCET Print & GoogleMaps.

- The "Curtain" in call is driving me batty; like the feature but it would be nice to have it a) not automatically invoked, b) transparent (i recall trying a version where it was) - I'm sure a registry tune-up will deal with that

- BUTTONS: I deliberately installed TouchPRO instead of FUZE to avoid the extra "clutter". So of course, PTT doesn't work and the keyboard isn't happy - easy fixes.

BTW: Did a post a little while back on button mapping to see if someone with some WinMO coding experience could put something like this together; here's the thread in case someone is interested: http://xdaforums.com/showthread.php?t=486742

... love the new icons; was worried at first that they might break something - so far so good

... on the performance side of things, one word: F-A-S-T
[Touch Pro, Fuze ROM Development] Da_G:
Broke more windows stuff out into packages, added a bit more, gwes.exe/mui fix, updated htc volume control

http://rapidshare.com/files/185797714/DaGsKitchen-v4.rar

Now over 400MB free on a clean install with all packages unchecked :)
[Touch Pro, Fuze ROM Development] ecltech:
HTC Black.tsk

If anyone is interested in changing to the flat black theme while cooking, place the attached .tsk file in OEM\OperatorPkg (rename "HTC Black.zip" to "HTC Black.tsk"; DO NOT UNZIP).

Make the following changes to "OEM\OperatorPkg\config_operator.txt" file:

LOCK:Enabled
TSK: \WINDOWS\HTC Black.tsk
LOCK:Disabled
EXEC:\Windows\SDAutoRun.exe

Hope it's helpful.
[Touch Pro, Fuze ROM Development] ecltech:
Da_G's Simple ROM Kitchen Wiki Page

Hi all,

I have created a Wiki page for Da_G's Simple ROM Kitchen. Will try to keep this page updated as possible. If anyone wants to add anything, please do so.

Da_G's Simple ROM Kitchen Wiki Page
[Touch Pro, Fuze ROM Development] gravesy56:
Hey Da_G,

I'm using your 2.05 ROM/OEM/SYS package and your latest kitchen and get a couple of errors when attempting to buildos and do some cooking.

1. I get messages saying there are duplicate registies -for HTC GPS Too, .NET 3.5, and FM Radio. I removed from the Package folder and error no longer occurs

2. I uncheck the .bat exe box below, check off the apps that want (99% of them) and then click GO.

3. It starts to build and then it states it can't find the /ROM folder and errors out and retries to build each time.

Any thoughts on what's going is it more? Possible snaphoo? I'm attempting to attach the image of the error I get but image upload doesn't always work for me.

Thanks!
[Touch Pro, Fuze ROM Development] kiru:
Is it possible to add the Fido/Rogers rilphone.dll to this kitchen?, if so, can someone do a quick how to.....thank!
[Touch Pro, Fuze ROM Development] RebelShadow:
try changing HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GPSOneDevice

PollInterval = 1000 to 500 and see if that helps.
[Touch Pro, Fuze ROM Development] lotion:
Hi Da_G...

Your InCall Recorder package is missing a a few files.

First of all, the in-call indicator icons (Thumb_ON.bmp, Thumb_OFF.bmp) don't appear to be showing up. Additionally, the ICR program to liste to calls doesn't seem to be there.
[Touch Pro, Fuze ROM Development] atsitalian:
I noticed this as well and merely installed the in call recording cab to get the rest of the files. Unfortunately while everything "works" the volume of the person on the caller side is so low it is really unusable. Is that the way it is supposed to work? or is this because I have a Fuze and not a Touch Pro so the hardware is different?
[Touch Pro, Fuze ROM Development] Da_G:
gravesy56: the problem comes from trying to use my packages with another OEM/ROM/SYS, my OEM/ROM/SYS has been stripped down and the components split into packages, whereas any other donor OEM/ROM/SYS will not be split into packages. This will cause conflicts because my packages will have the same guid as packages already in the ROM, etc, etc, causing that problem.

If you remove my packages folder, you should not have a problem using the kitchen to build the rom, but then you'll have to determine which of the packages are not already in the rom and insert just those..

kiru: place the dll in \OEM\OEMDrivers, overwriting the one already there. done!

nuttsp: v5 should be fine, I rolled the GPS settings back to what it was in 2.06 (where evyone seemed to get the best response) - it'll be out after i flesh out a few more packages.

lotion: i used the in_call_recording package monx made, wasn't aware of it missing any files. can you point me in the direction of the source rom?

atsitalian: or maybe you could point me in the direction of the cab..

thanks! i've already added a few more packages since v4 :)
[Touch Pro, Fuze ROM Development] lotion:
I made that determination based on a comparison of Monx's package. I've flashed since then but I believe Thumb_ON.bmp and Thumb_OFF.bmp, while in Monx's package, were not on my device after cooking the rom with ICR included. I put them on but forgot and flashed another ROM before seeing if that fixed.
[Touch Pro, Fuze ROM Development] Da_G:
Hmm, well i just checked my phone, and it has both Thumb_ON and Thumb_OFF, and they are both in the icr package, i just extracted monx zip and added option.xml.. maybe there's something different in the .cab?
[Touch Pro, Fuze ROM Development] player911:
You mean the Wireless Connection Manager? It's the default Windows manager... not the HTC version. I like it because it is simpler and only has what I really need.

Also... Da_G - I know there is now a WiKi which is GREAT but it would be nice to keep an updated link to the latest Rom Kitchen and to the Wiki in the first post.

I see that each version is a full download. Isn't the purpose of having a Rom kitchen to reduce the downloads? Do you think it would be easier to provide "updates" that over write faulty or old files and install new ones? Sorta like a patch if you will?

I think a good idea would be to have a "Core Kitchen" then link the Packages individually so people can download what they need. Of course we could create "Packs" which could vary; such as "Complete Full Pack" or "Stock HTC Pack".

This would make it a lot easier to keep the packages updated especially if someone else updates a package. Then they can upload and update the Wiki without the need for you to repackage the entire build. Also providing a link to the needed tools required to convert cabs into packages would help too.

This will give you time to solely focus on the updates of the kitchen to include more functionality, leaving us to convert our favorite games and apps to packages for all to share.
[Touch Pro, Fuze ROM Development] norkoastal:
I second this idea or would think placing the version of the kitchen into the title of your thread would work good as well...
[Touch Pro, Fuze ROM Development] gravesy56:
Hey Guys,

A couple of quick things for a newb from this newb:D... I'm noticing that I can't use the ATT Fuze stock ROM extracted and split with Raph Kitchen in this latest update to Da_G's kitchen can anyone else verify this? It doesn't throw the /ROM error and cook's fine but when you attempt to flash it, it hangs at the boot screen. Any thoughts?

Also I'm unable to use Da-G's ROM pack too although he explained the reasoning but any ideas of alternatives since his was so clean it was perfect I have a few other ROMs but they are pretty custom and I wanted a bit more of a shell from something although in retro I could always remove stuff from the OEM however didn't really want to toy with much of that because I'm still learning.

Stock ATT build I'm using is version 1.95.502.5 from our site I extracted from the exe file changing the file to a rar. find it here:D

Thanks!

-Gravesy
[Touch Pro, Fuze ROM Development] player911:
Whatever is easier Da_G. After thinking about it, separating the packages from the actual Kitchen probably wouldn't really differ much in regards to size. I think the fact it actually comes with the various builds is what causes it to be so large.

I'm just thinking of ways to simplify the process of updating packages without having to rebuild and redownload EVERYTHING. I dunno, it's late. I'm just trying to help. Let me know if you need anything Da_G.

The Cab-OEM conversion looks complicated (more than it should). The actual instructions are buried in the middle of the OEM Package Tuturial Wiki page.
[Touch Pro, Fuze ROM Development] lotion:
Yeah, my apologies ... The 'thumb' bmps don't seem to be the issue. I'll look into it tomorrow and let you know if I find anything.
[Touch Pro, Fuze ROM Development] player911:
I saw there is a Windows Mobile 6.5 Professional build out there for the BlueAngel. Any way we could extract the new rom and use with your Kitchen?

http://xdaforums.com/showthread.php?t=428030

I can't make heads or tails from it what the guy posted.
[Touch Pro, Fuze ROM Development] Da_G:
Sure, as soon as someone posts up a link I can get it from, i'll wrap a kitchen around it and post it.

Let's keep that to another thread though, let's call this thread the 'stable' build, i'll make another one for the kitchen wrapped around the 'bleeding edge pre-6.5 dogfood build' :)
[Touch Pro, Fuze ROM Development] ectopic:
Yea, me too. As a newbie, I'm having a ball playing around with this kitchen. I've been trying to figure out how to add the slide to unlock (w/o curtain) like in the ATT test rom. I tried using a cab, but I couldn't get it installed without screwing up the dialer. And I still got some reading to figure out how to add packages to the kitchen.

Much props to Da_G and eras2r for kitchen. roms are blazing.
[Touch Pro, Fuze ROM Development] eras2r:
The Curtain is simply a registry entry:

[HKEY_LOCAL_MACHINE\Software\HTC\PHONE]

"PhoneLockEnable"=dword:00000000

Set that key and it will disable curtain. Or for perm fix, edit the *.rgu in PACKAGE_Raphael_PhoneCanvas_Slider_With_Curtain and set the value there. Then it's already set each time you cook.

If you want the ATT dialer though, it depends on PTT as well as Videoshare. You'd have to include all 3 packages and well... PTT sucks :)
[Touch Pro, Fuze ROM Development] DANDANA:
21042 on http://xdaforums.com/showthread.php?t=497586
[Touch Pro, Fuze ROM Development] eras2r:
Already on it :) Hopefully some more goodies come out of this one
[Touch Pro, Fuze ROM Development] eras2r:
So after working with the 21040 SYS, I see that there are some issues that can't seem to be fixed. The big one... if BT is turned on DNS resolution doesn't work... so no data :( Several chef's have been trying to resolve this, but I believe it goes back to what Da_G stated earlier that the Rhodium is not based on the MS Bluetooth stack. I would suggest everyone drop the 21040 like a bad habit and let it die.
[Touch Pro, Fuze ROM Development] eras2r:
Updated Kitchen - 21040 XIP / 21042 SYS - 5.08.502.1

Ladies and gentlemen, fasten those seat belts cause this one is FAST!

My bad on releasing that last kitchen full of nasty nasty's. But hey, we're all here to share, learn and test right? This kitchen is based on the 21042 SYS. Unfortunately the XIP for this build was incomplete so I am sticking with the 21040 XIP as that was a full XIP and ported by me so I know exactly what's in there.

All XIP/Packages are the same as the 21040 release. In case you forgot:

Changelog:

XIP/SYS updated to 21040 Rhodium Release

XIP optimized and ULDR partition reduced

XIP patched for Cert and 24MB PagePool

XIP contains WM6.5 DDI.DLL

shell32.exe patched for timebomb

New package for MSVC

New package for WindowsLiveIM

NewIcons split into 2 Packages (should resolve battery icon issues)​

Also

SYS updated to 21042 build​

Special thanks to pudelmuetze for the SYS source.

So far I have not found any bugs in this one. And I mean it when I tell you that this one screams! You better put on a helmet before you start cooking :D

Link: eras2r-21042-kitchen-5.08.rar
[Touch Pro, Fuze ROM Development] dizzyraider:
Hahahah, eras2r is the man who doesn't sleep. Thanks for this release, I'm dusting off my helmet and putting it on right now!
[Touch Pro, Fuze ROM Development] hilaireg:
@eras2r:

Bluetooth stack working on this version?

Cheers ... as always, awesome work!