yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] hilaireg:
Visual Kitchen: Application Packs

The Kitchen Application Packs includes additional applications that have been tested in the Ervius Visual Kitchen. The packages have been organized (sequenced) so as to ensure that the ROM produced by this kitchen is the same as the Package Builder (legacy) kitchen.

The pack applications have all been set to Unselected (False) - a package must be double-clicked to include the package during ROM compilation. The PACKAGES.TXT files in each PACK will overwrite the base kitchen version - providing a description for each package.

The .TXT files attached to this post contain the list of packages that are in the corresponding kitchen pack.

Visual Kitchen PACK 1, 29 MB, 13.06.2009

Visual Kitchen PACK 2, 28 MB, 13.06.2009

Visual Kitchen PACK 3, 30 MB, 26.06.2009

Visual Kitchen PACK 4, 50 MB, 16.08.2009

Visual Kitchen PACK 5, 05 MB, 16.02.2010

Post-Download Instructions:

Extract the contents of kitchen pack archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.

Copy the contents of the extracted kitchen pack to the kitchen .\EXT folder.

Tip

The archive folder structure matches the kitchen folder structure that corresponds to the build on which the package has been tested.

Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.

The applications in these packs were tested using the Customized Device profile (DEVICE_CUSTOMIZED).

Recoded Modules Application Packs (Optional)

Although Windows Mobile 6.1 improved Virtual Memory (VM) by providing SLOT 60 and 61, modules can not be allocated in SLOT 60/61 - only files. Current kitchen relocation tools did not require any changes as SLOT 1 and 0 are the only slots where modules can reside. Device stability is compromised however, when there are too many modules as "spilloff" occurs into SLOT 0 resulting in reduced available memory which causes the device to report memory errors (even if it's not truly out of memory) or erratic application functionality.

RECMOD Application Packs contain versions of packages that appear in the kitchen and existing kitchen packs. These packages have had their modules recoded; the package names have _RM appended at the end of the name. When using RECMOD packages, it is important to remove the non-recoded version from the kitchen to avoid ROM compilation errors.

Visual Kitchen Recoded Modules PACK 1, 15 MB, 16.08.2009

Visual Kitchen Recoded Modules PACK 2, 05 MB, 16.02.2010
[Touch Pro, Fuze ROM Development] hilaireg:
Visual Kitchen: OEM Packs

Chefs looking to simply update their existing kitchen OEM folder without having to download an entire kitchen can now do so with an OEM pack. The OEM Packs include the OEM folder for specific builds of Windows Mobile 6.1 and have been tested in the Ervius Visual Kitchen. The OEM pack also includes a corresponding optional DEVICE_* and OVERRIDE_KEYPAD_* package.

The DEVICE_* package contains all of the files that were removed from the original OEM folder. Closely examine the contents of the package before use as it contains untouched stock files that were found in the released ROM.

The OVERRIDE_KEYPAD_* package contains a copy of the the KEYPAD.DLL file from the .\OEM\OEMDrivers folder and can be used to ensure that the desired KEYPAD.DLL is installed during ROM compilation.

A text (.TXT) file appears in the .\DOCS folder of each OEM pack which details changes that have been made. As a result of a limit to the number of post attachments, only the latest versions of the OEM pack change logs have been added.

OEM: 5.12.206.1 (20779), 06 MB, 30.07.2009

OEM: 5.11.502.2 (20771), 22 MB, 30.07.2009

OEM: 5.05.405.1 (20764), 08 MB, 30.07.2009

Post-Download Instructions:

Extract the contents of OEM pack archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.

Copy the contents of the .\OEM\Raphael\.VM\ folder in the kitchen to the extracted OEM pack .\.VM\ folder (ex: C:\XDA\VISUALKITCHEN-OEM-PACK-20771\OEM\Raphael\.VM\).

Rename the existing .\OEM folder in the kitchen (ex: OEM.20771 or OEM.precopy).

Kitchen Conversion Instructions:

Copy the contents of the extracted OEM pack, which now includes the contents of the .\OEM\Raphael\.VM\ folder, to the kitchen folder (ex: C:\XDA\My_Visual_Kitchen\).

Rename the .\OEM.<buildnum> folder copied to the kitchen to .\OEM (ex: OEM.20771 to OEM).

Tip

The archive folder structure matches the kitchen folder structure of the legacy kitchen found in this thread.

Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.

Note

The DEVICE_* and OVERRIDE_KEYPAD_* packages will be set to Selected (True) - a package must be double-clicked to exclude the package during ROM compilation.
[Touch Pro, Fuze ROM Development] hilaireg:
Visual Kitchen: ROM/SYS Packs

The ROM/SYS Packs include the ROM and SYS folders for specific builds of Windows Mobile 6.1 and have been tested in the Ervius Visual Kitchen. The ROM/SYS also includes corresponding base ROM compilation profiles, pre-configuration (ERV) files, that have been tested in the kitchen.

Chefs will find untouched versions of the base XIP.BIN and OS.NB.PAYLOAD (no imgfs) as well as the donor XIP.BIN and OS.NB.PAYLOAD (no imgfs) - when available.

A text (.TXT) file appears in the .\DOCS folder of each ROM/SYS pack which details changes that have been made. As a result of a limit to the number of post attachments, only the latest versions of ROM/SYS pack change logs have been added.

SYS 21056, ROM: 21056/20779, 37 MB, 17.01.2010

SYS 21056, ROM: 21056/20771, 37 MB, 17.01.2010

SYS 21056, ROM: 21056/20764, 37 MB, 17.01.2010

Post-Download Instructions:

Extract the contents of ROM/SYS archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.

Rename the existing .\OEM\Rapheal\.VM folder in the kitchen (ex: .VM.20771 or .VM.precopy).

Backup the existing .\ROM\Raphael\ files (.TXT, .BIN. PAYLOAD) in the kitchen. The files to backup are:

INFO.TXT

OS.NB.PAYLOAD

ROMHDR.BIN

XIP.BIN

Kitchen Conversion Instructions:

Copy the contents of the extracted ROM/SYS pack to the kitchen folder (ex: C:\XDA\My_Visual_Kitchen\).

Tip

The archive folder structure matches the kitchen folder structure of the visual kitchen found in this thread.

Use a file comparison utility to ensure that you do not lose any changes you may have made to existing packages in the kitchen.

Note

.NET Compact Framework (NetCF) is a merged version of 2.0 & 3.5.

The following applications have been removed from the SYS folder and placed in the kitchen EXT folder; they are also available in an Application Pack and the Package Repository noted in the first post of this thread.

- Auto Data Config (ADC)

- Adobe Flash

- Infrared Data port (IrDA)

- Live Search

- Modem Link

- Remote Desktop Mobile

- Voice Command (MSVC)

- Voice Over IP (VoIP)

- Windows Live (MSN)

- Windows Media Player (WMP)
[Touch Pro, Fuze ROM Development] wmserver:
Emulator

Da_G,

Thanks for the kitchen.

Just wonder if there's any good ROM emulator to test any mod before flashing into a real life device?

This will hopefully prevent bad ROM and bricking phone.
[Touch Pro, Fuze ROM Development] Da_G:
With HardSPL, you stand little chance of bricking the phone, you can always return to bootloader and flash a working ROM. But as to an emulator, yes there is one, but it does not emulate the hardware the Raphael has, so for that purpose it would not work, none of the drivers would load up and the emulator would not boot. You would have to create a special version without drivers - but then, you aren't really testing the important part :) As long as you have HardSPL, you can flash without worry.

As for a guide to mashing things up before cooking, i'm putting together a large collection of packages.. choosing what you want in the ROM will be as simple as checking boxes.. as far as editing the registry goes, you need a program that can open/save in unicode.. i personally use EmEditor..
[Touch Pro, Fuze ROM Development] kk0813:
Thanks Da_G. This one is working great. I checked with base OEM/ROM/SYS folders. If I want to include any cab files how can I include them? I tried to copy a cab file in packages folder and it didn't pick up. Is there any thing I need to do? Actually my idea was to include some cab files in the rom instead of using UC while flashing.

Thanks
[Touch Pro, Fuze ROM Development] btprice2001:
You have to convert the cabs to packages first.

http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
[Touch Pro, Fuze ROM Development] gravesy56:
You're the man I wait with great patience going to also try the idiots guide as well as building in PPCKitchen as we speak I've had some issue getting the ROM to build... do I need Visual Studio as my backend dev box? I have 2003 Visual Studio but I'm thinking I need a newer version as for EmEditor; I'll grab that too. Thanks for the coaching, I hope to churning the buttah lik you my friend lol.
[Touch Pro, Fuze ROM Development] Da_G:
You need the .NET 3.5 runtime for windows (not .NET CF 3.5 for windows mobile), you can find it at microsoft's site. I believe that's the only requirement for the apps in the kitchen to run..

I'm about half-way done on the packages, archive is only 55mb so far.. gonna post a pre on my ROM thread since it's based on my ROM.
[Touch Pro, Fuze ROM Development] LazPL:
Thanks a bunch Da_G! I feel tempted to cook something. Do you also have a package that can give a man more time? Now THAT would be useful! :)
[Touch Pro, Fuze ROM Development] Da_G:
No packages for more time, sorry :)

Here's the first version of all the packages i've made thus far: http://xdaforums.com/showpost.php?p=3176535&postcount=1498

You don't need the kitchen from the first post, i included it in the package there.. same steps to follow, but i've included a good amount of packages.. of course there will be more coming soon, rome wasn't built in a day :)

Don't forget to scroll down on the list of packages, it goes off screen in buildos :)
[Touch Pro, Fuze ROM Development] gravesy56:
Da_G YOU RULE BRO!
[Touch Pro, Fuze ROM Development] Da_G:
Posted a Diamond Phone canvas + Slide 2 Answer package, you can get it here - thanks to player911 for fixing it all up :)

It will of course be included in the next revision, but here it is now :)
[Touch Pro, Fuze ROM Development] qsqa:
Quick question - why don't you use original Diamond package (called "PACKAGE_Diamond_PhoneCanvas_Slider") for S2A taken from 2.03 Diamond rom? - it's working perfectly in my PROven
[Touch Pro, Fuze ROM Development] Da_G:
Dunno, figured there was some issue with it? I don't use it.. when i tested it shortly it seemed to work fine, is there a difference from the package I posted?
[Touch Pro, Fuze ROM Development] Da_G:
I've updated several of the packages in the kitchen with new builds from the just-released diamond gsm rom, and added a couple more new packages. still no scripting to select the os version you want, but it'll come :)

On my way out the door, so no time to upload now.. hopefully tonight :) Gonna test them while i'm out.
[Touch Pro, Fuze ROM Development] gravesy56:
Da_g kitchen works great still don't know what I'm doing or what's going but how do I change manila's and stuff? I want to use the confuzed backgrounds and colorings.

Thanks!
[Touch Pro, Fuze ROM Development] Da_G:
The easiest way to do that is to ask monx if he can share his customized packages, you can then just drop them in the \Packages folder and select them :) (providing he has made an option.xml to go with it)
[Touch Pro, Fuze ROM Development] Da_G:
Nope, the sms/mms thing is an issue with the build i used, i fuddled something up..

both issues are fixed locally here, just gotta do the localization to en-us and then it's all good unless you have run into any more issues? :)

I think i'm going to move all Touch Pro specific stuff to a checkbox and all Fuze specific stuff to a checkbox.. hardware keyboard, device name, sms/mms settings etc.

That way I don't have to cook connection setup in to get my stuff set up :) (my motivation is laziness!)
[Touch Pro, Fuze ROM Development] ibrythill:
I'm getting the SMS/Email bug too and changing the localization didn't change anyting. Another thing is that, when I'm trying to read an SMS and on the white screen I tap the right softkey I get this error message: "The message cannot be signed and/or encrypted".

Is it only me?
[Touch Pro, Fuze ROM Development] player911:
Everything runs really well. Lets hope that after those bug fixes that it'll still be running as great. I haven't used Manilla in a long time because of the lag, but it really runs well with this version.

I agree about separating the Fuze and TouchPro stuff. The mouseover descriptions can get annoying too, which some are wrong, but nuff said.

Do we even need the that new network customization app to select AT&T? I've included it every time I install it just incase but I'm curious if anyone else has set it up. One would think that if AT&T wanted HSDPA disabled... that the AT&T Preset settings would have HSDPA disabled as well.

I'm at home now, the V5 and V6 hybrid kitchen are at work... so instead of downloading both kitchens again... I'm just going to wait for your update tonight.

FYI I'm getting awesome PocketGBA speeds around 23-26fps.
[Touch Pro, Fuze ROM Development] Da_G:
Connection Setup Wizard only sets up the apns, and any possible proxies.. it doesn't make any changes to the advanced network configuration where it would disable HSUPA :) That's controlled via provxml's in htc's setup (and is enabled by default in this rom)

In the current version you need it installed as there is no connections setup by default. But in the new version i'm making simply selecting "ATT Fuze" from the device menu will load all that stuff up, so you don't need to cook it in :) "Touch Pro" will remain as-is.

testing a flash now.. if all the known bugs are fixed it'll be uploading shortly :)
[Touch Pro, Fuze ROM Development] hilaireg:
Thanks,

Any possibility of separating the Comm (AT&T Connection-specific) stuff in the new Fuze section? That way, one can skip the Comm Configuration and apply all the other Fuze related goodies.

Sent u a little 'something' for u'r time ... cheers!
[Touch Pro, Fuze ROM Development] crazyC:
If at all possible, as I am off to bed (gone midnight here and need to be up early), if the SMS bug can be fixed by just putting a new dll or file in, could someone upload it for me? I would be keen to update my kitchen tomorrow just for that change as well, if Da_G could explain what the change is.

I exclude connection setup when I cook the ROM as I use a cab to set all my network stuff up and I got a funny result from connection set up the first time I used this kitchen - lots of screen flickering and confusion although after a while it seemed ok.

Excuse the rambling - had a glass or two or wine....probably best I dont try any cooking tillt he morning!
[Touch Pro, Fuze ROM Development] hilaireg:
FYI,

The In-Call Status Screen Off behavior is still present - i.e. off after 5 secs. The 'No Sleep Raph' cab has an incorrect registry entry in the RIL section for Fast Dormancy ... even with the correct entry it's still unpredictable.

[EDIT] Changes to Backlight (HKCU), Phone (HKCU), and RIL (HKLM) are fine /w reset. Different behavior from a Power Off - i.e. Instant Screen Off

Curious,

Has anyone ever figured out how to get the Screen Lock to behave like the Smartphone? On the Smartphone, one is presented with the Password PIN after pressing the Unlock SK. The Today screen is always visible.

Cheers,
[Touch Pro, Fuze ROM Development] Da_G:
Much appreciated :)

Testing now, things look good.. changed touch pro locale to en-us, fuze was already set that way.. oh, let me add the agps config panel back while i'm at it..

I just observed the connection setup flickering too. this version behaves a little differently than previous versions, previous versions wouldn't do anything on the first boot and prompt you to setup on the 2nd boot..

this one seems adamant to prompt you on the first boot, and if you don't do anything (because sdconfig is running or w/e) it'll just sit there until the phone reboots.. then prompt you on the 2nd reboot as normal. so its a cosmetic issue, seems.
[Touch Pro, Fuze ROM Development] Da_G:
Well, everything's fixed and good to go except the SMS page.. wtfamily!

Not sure what's up with that.. tried 3 different versions of arcsoft sms/mms, its not that.. i take it this works fine in the stock rom (never tried)
[Touch Pro, Fuze ROM Development] hilaireg:
First time I tried it in the stock ... it sent the SMS but indicated that it did not.

I used the Phone settings to perform a 'Get Settings' of ALL the Rogers Network options and haven't experienced the problem since.

Here's a copy of the Registry Dump off the ROM (fresh Hard Reset) - no SIM in place during the entire process and the only application installed was PHM Regedit after completion ... not sure if it's of any help.

If u need one with a SIM in place ... let me know.

HTH,

[EDIT] .REG export in WinXP format option using PHM Regedit

[EDIT] Added one with a SIM
[Touch Pro, Fuze ROM Development] Bizybone:
WLM 10.6.48.1500 doesn't work for me. Neither does setting up an email account. I'm going to try and recook with the older WLM version. Unless it has something to do with me cooking rom with .NET 3.5 as oppose to 2.0.

Edit: Heh just read that others are also having Email issues.
[Touch Pro, Fuze ROM Development] player911:
I couldn't get .NET 3.5 nor 2.0 working.

Wierd that this rom is giving so many problems.
[Touch Pro, Fuze ROM Development] Da_G:
Wiiierd. something was up with the NetCF35 .dsm, i re-created it and all is well now.

o.O

Uploading!
[Touch Pro, Fuze ROM Development] Bizybone:
Is that link anyway with the WLM not working? No biggie for me, I installed WLM I had from a cab awhile back and all is working again, it even synced my mail.
[Touch Pro, Fuze ROM Development] Da_G:
The problem appears to be that when I was messing with the newer Kitchen, it created real .dsm's for each folder I had.. then I renamed the folders after in the process of splitting things up.. since the foldernames no longer matched the .dsm's it wasnt copying any files :(

Quite annoying! This affected many packages so i'm going through now and re-creating all the .dsms to avoid any issues. I'll re-upload after that :)
[Touch Pro, Fuze ROM Development] player911:
cool so that sounds like that will fix the SMS problem, right?
[Touch Pro, Fuze ROM Development] Da_G:
I won't say yes until I flash a ROM with it fixed :) But it should. Either way I won't be uploading 6.1 til that last bug is squashed.
[Touch Pro, Fuze ROM Development] eras2r:
What the....

Damn... put in some serious hours the last few days at work so no time to play with my phone. Come back and there's a new HTC ROM released and new kitchen being worked on already here. It's like Christmas! Da_G you are a machine!

Thanks again for your hard work and all that time you spend on this stuff so that people not nearly as smart as you (me) can spend all my time messing with this stuff too :)

-e
[Touch Pro, Fuze ROM Development] Da_G:
Ugh, ok, I finally fingered out the sms issue after I noticed it affected email too..

I'll do myself a favor and NOT share with you what I did to break it, lmao :(

Suffice it to say I should sleep before creating a kitchen from scratch :)

I expect this next test flash to go perfectly and I should be uploading shortly :)
[Touch Pro, Fuze ROM Development] DrzNight:
Da G, if you have a chance do you mind telling us how we would go about flashing the matching Radio for this rom base? as well as where is it that you replace the rilphone.dll in the kitchen when cooking? Thanks a lot man.
[Touch Pro, Fuze ROM Development] Da_G:
rilphone.dll goes in \OEM\OEMdrivers

there's a couple ways to flash the radio rom.. you can flash a standalone package that someone created.. thats probably the easiest (see the radio thread for that)

Or you could just flash the leaked rom this kitchen is based on, and then flash over that with whatever ROM you like.. that'll leave you with the Radio ROM and the Splash screen from the leaked ROM. :)
[Touch Pro, Fuze ROM Development] Da_G:
http://rapidshare.com/files/194520587/DaGsKitchen-v6.1-HTC_WWE_5.05.405.1.rar

This version still has the sms/email white page bug, but i fixed enough other bugs to warrant uploading it as-is.. maybe one of you can help me find the sms/email glitch because it's evading me!

That's the only issue I know about with this build.

Edit: Don't forget the instructions have changed since v5, check the first post! :)
[Touch Pro, Fuze ROM Development] player911:
when I build the ROM, I'm still getting "Some of the files encountered inside project was not found: C:\Users\bla bla bla\Desktop\Kitchen\os-new.nb"

This occured when replacing the g'reloc.exe with another in v6... all seems well but it fails to produce a nbh file.
[Touch Pro, Fuze ROM Development] Da_G:
Please list the exact steps you are following as well as pasting the last 20 or so lines of the log in the lower half of the buildos window, thanks :)
[Touch Pro, Fuze ROM Development] player911:
open command, launch ralphaelkitchen.cmd, click build tab, uncheck bottom checkmark, click Load Rom, select packages, click Go, wait for the process to end, close program, ERROR about os-new.nb, watch clean up process. The command windows says the nbh file is in the base directory and press any key to continue... but it isn't there. The original version 6 was doing this to me on my XP work PC after I replaced the g'reloc.exe file with another version.

Here is the entire log from the kitchen.

I don't even see it producing an os-new.nb file like other Kitchens do. Again, loading the OEM/SYS/ROM/Packages through v5 works like a champ. os-new.nb gets created, then nbh after that.
[Touch Pro, Fuze ROM Development] Da_G:
Ah, you missed this part of the new instructions on page 1 :)

Optionally check box "All Packages to One" for a faster ROM. Leave "Execute Create_ROM_***.bat" checked.

I can see from the log that's your problem.

Also, you don't need to open command first, you can just double click raphaelkitchen.cmd :)

Reason it worked in v5 kitchen for you: RaphaelKitchen.cmd in v5 contains and executes Create_ROM_***.bat itself, which is why you need to uncheck the box (or it would be trying to do it twice and failing)

Now those commands are moved to Create_ROM_Raphael.bat where they should be, so no unchecking is required :)
[Touch Pro, Fuze ROM Development] player911:
Ahhh force of habit I guess. I didn't notice it was different. I normally launch the raphaelkitchen.cmd directly. I'll try it again after I test the bare rom I made in v5 using the stuff from v6. I want to see if SMS works out of the box and if anything being installed is breaking it.

Yea that was it Da_G. v6 is working now. Still no SMS/Email though.
[Touch Pro, Fuze ROM Development] Da_G:
Every time i've flashed with this 5.05 version, it's shown my battery as full right off the flash.. seems this battery driver takes a bit to calibrate.
[Touch Pro, Fuze ROM Development] player911:
You can sync and get SMS/Emails... but try open one up to read it through the Messaging app. The bug just displays a white screen. Not such a big deal if you have Manilla... but you can't reply to emails/sms at this point since the reply screen is also white.

Da_G... Didn't the original leaked rom have PIE4? I wonder if IE6 is messing up SMS. Doesn't the messaging app rely on IE in some regards?
[Touch Pro, Fuze ROM Development] Da_G:
Yep.. and it's baffling as to why that happens. o.O

Although I am pretty braindead from court. I managed to fix the rest of the bugs at least :P

Maybe after I sleep on it..