yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] eras2r:
herg62123's opera 15613 works for me and is pretty fast: http://xdaforums.com/showthread.php?t=484704&highlight=opera
[Touch Pro, Fuze ROM Development] The Jack of Clubs:
alright i got bored and installed the cab. that worked. thanks so much. :P

edit: i actually like this alot more than i thought i would. the sound is a bit clearer and crisper.
[Touch Pro, Fuze ROM Development] slimshadee:
Thanks, eras2r...I had to hard reset, then install the Opera cab you pointed me to as the first installed software. I think my iGuidance was creating the conflict, but now both are installed and working.
[Touch Pro, Fuze ROM Development] tassadar898:
eraser do you mind zipping up your version of da_g's kitchen and posting it? its weird because on your ROM everything seems to work flawlessly but when i make my own even with the new audio file you gave us my speakerphone works quirky, and opera seems to glitch out. it would be much appreciated! Especially since the TP2Manilla comming out soon and I want to cook that baby in! Thanks.
[Touch Pro, Fuze ROM Development] rmanaka:
Everything working great for me & my fuze!

Reporting that everything seems to be working on my fuze that was cooked with Da_G's 5.08 kitchen, eras2r's modified packages and the eras2r supplied Arup_Tweaked_Louder version of audiopara3.csv! MSCV working both through microphone and through BT headsets.

I have loaded:

Resco Registry Add-in

Siber Systems AI RoboForm PPC

Windows Theme

CoPilot Pocket PC (Version 7)

Omega One 1-Calc

AT&T Navigator

Google Maps (with latitude)

Ilium Software eWallet

Chi-Tai Dang SecondToday

Andreas Falke Weather Database Editor

burt iContactBE (6.4.5 VGA)

Opera Software Opera 9

Skyfire Browser

J.S. Advanced Configuration Tool 3.3

Sushi's DIamond TF3D Config

Montecristoff Diamond Tweak

iDevelopStuff changeScreen

SBSH.net PocketWeather

Resco Explorer

still have 298724K of Total storage memory available...

makes my Fuze rock!!!
[Touch Pro, Fuze ROM Development] player911:
Does this kitchen not include NET 3.5?

I'm using the 5.08 packages plus Manilla and the Notification Panel from the TP2... Manilla tries to run but errors out and says I need a newer version of .NET

[EDIT]

I downloaded 3.5 and everything starts working. Hmmm.....
[Touch Pro, Fuze ROM Development] rmanaka:
VERY strange because Advanced Config requires NETCF3.5

That IS very strange as I've used the basic kitchen without modifications other than eras2r's updated packages, and Schap's Advanced Config 3.3 (which I believe requires NETCF 3.5) runs just fine on my phone...
[Touch Pro, Fuze ROM Development] player911:
Yea I dunno. It is working now though. Probably because I deleted the Packages folder from the kitchen and replaced it with the 5.08 packages because I was getting all kinds of duplicates and it kept crashing. I don't think the 5.08 ATT rom comes with NET 3.5 by default.

The new Notification panel was what I was really after. The newer Manila isn't what its all cracked up to be. The only thing I really like about it is the calendar tab.

I think I might build another rom using the latest 5.08 Manila from the ATT rom and the Notification panel; leaving the TP2 Manila out because it is still rather flaky.
[Touch Pro, Fuze ROM Development] xboomer55:
You could bring in the manila (PACKAGE_Raphael_Manila) and communications manager (PACKAGE_Raphael_CommManager) packages from the DagYo 6.22 (05.05) kitchen and use these instead. I prefer them for the time being. The 05.05 comm manager will also solve the cosmetic issues with the ATT themed comm manager in the 05.08 kitchen, assuming that you prefer the diamond theme.

There will be .rgu/.dsm/options conflicts with all manila packages in the kitchen, so pull the others out and stash them in another folder (i.e. Removed Packages) before building the rom.

This is working for me, and the 05.05 manila is just as nimble and responsive as I found it in the older kitchen.
[Touch Pro, Fuze ROM Development] wshader:
How can I fix this?

Completed successfully

Microsoft (R) RGUComp Version 1.0.000

Registry file processor and hive builder.

Copyright (C) 2004 Microsoft Corporation All Rights Reserved.

built: Nov 19 2004 15:17:13

importing registry file ".\boot.rgu"...

importing registry file ".\Registry\8be73c02-3437-4c06-88c9-0a2e25bfaf2c.rgu"...

wmain: (RGUComp) !ERROR failed building DEFAULT hives

And then a bunch of Build registry errors
[Touch Pro, Fuze ROM Development] eras2r:
Most likely an error in that rgu file. Seach for that file and see what package it's part of. There's prolly a syntax problem. The errors should tell you about where in the file it is. Or simply post the rgu and I can take a look at it for you.
[Touch Pro, Fuze ROM Development] player911:
I started over and removed the older packages as I replaced with the new ones (I figured it would just over write the old, but figures not).

Works like a champ. I cooked in the Notification Manager and Menu replacement from the TP2. Works very well.
[Touch Pro, Fuze ROM Development] eras2r:
Did you have to modify anything in your build to support the TP2 packages?

Are those packages straight from the Dev/Hacking thread or elsewhere? Could you post the source to them? I'd like to try them out as well.
[Touch Pro, Fuze ROM Development] player911:
Notification Manager.cab http://xdaforums.com/showthread.php?t=491676

Menu Enhancement.cab http://xdaforums.com/showthread.php?t=491457

A bunch of other Cabs http://xdaforums.com/showthread.php?t=486866

I didn't convert these into packages... I found them in those threads. The only ones I've cooked in was the Notification and Menu Enhancements. The other cabs I went without. The Manilla2 conversion isn't done yet... and the Package I got my hands on was chalk full of quirks. Manilla2 kept restarting constantly. I won't post it because it isn't worth posting. They're pretty close to completing Manilla2 for VGA and should be released any day now.

The new Menu's work perfect and the Notification Manager only has a few little graphical issues left but worth it.

-------------------------

One thing I'm finding out is my battery is all goofed. It maxes out at 20% on a full charge and works its way down from there. Anyone have the older battery program files?
[Touch Pro, Fuze ROM Development] crazyC:
Cheers for that.

Agreed - the menu enhancement is good - no issues so far. I will make that into an OEM I think.

The notifications are a good idea but visually there are glitches as you mentioned. Maybe I will uninstall that till it is fixed.
[Touch Pro, Fuze ROM Development] crazyC:
What exactly are you looking for? the stuff within settings/power or the battery icon on the top bar? not sure I understand. Is it just a display problem or does the battery really never clear 20% charged?
[Touch Pro, Fuze ROM Development] xboomer55:
Locking volume buttons

I prefer that the volume buttons are locked out when the device is locked. Previous Da_G simple kitchen releases included a regedit to lock volume buttons:

[HKEY_CURRENT_USER\ControlPanel\Keybd]

"DisableVolumeKeyDuringLock"=dword:1

This and other tweaks were at \OEM\AddedStuff\c9bea43e-3dd8-4983-8c5b-de86267d459c.rgu in earlier kitchens. This file is empty (and commented as empty) in DagYo_-21028-kitchen-5.08-new-ddi

I have moved the .rgu over but not yet used it. Looks harmless and you'll recognize other enhancements in the file.

Manually adding the key to the device also works.
[Touch Pro, Fuze ROM Development] eras2r:
Depending on what dll yer using for taskbar icons, it's prolly just a simple registry adjustment. Here is what I have:

[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]

"BatteryIconLevels"=dword:00000065 ; (101 in decimal)

"BatteryIconIdStart"=dword:000003e9 ; (1001 in decimal)

"BaseDll"="phcanOverbmp.dll"

"BaseId"=dword:00000000

Check yours... it's prolly the one of the first 2 entries.

-e
[Touch Pro, Fuze ROM Development] eras2r:
Fixed Taskbar Overlay in YouTube

So everyone knows that there is an issue in the current kitchen with YouTube with the keyboard slid out where the taskbar shows up on top of the YouTube app. Well I found out that it's not just YouTube, but any app that uses fullscreen in Landscape mode.

After much trial and error and flashing back and forth for several days, I have found the culprit dll file. It's the LargeTitleBar.dll that is part of PACKAGE_Raphael_EnlargeTitleBar. This file from the 5.08 ATT leaked ROM is what causes the issue.

I am attaching the stock HTC 5.05 version of this DLL below. Simply replace the file in PACKAGE_Raphael_EnlargeTitleBar and yer good to go.

For others not using this kitchen you'll find the LargeTitleBar.dll in \OEM\OEMDrivers.

-e
[Touch Pro, Fuze ROM Development] player911:
Well the problem is that when the phone is fully charged... it reads 20%. When the battery is half dead... it reads 10%. Really weird. I'm using the latest kitchen 5.08 files with the upgraded packages from post #539 (or something). I followed the post exactly, removing the old packages before copying over the updated ones. On top of that I'm using the TP2 Menu Enhancements and Notification manager OEM packages.

Included in post #539 is some updated taskbar icons as well. I'm also using the Manila HD which sometimes uses a unique battery icon.

Anyway. I compared those registry settings with my own. I didn't even have "BatteryIconIdStart=1001". So I added it. I also have 1 extra:

[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]

BatteryIconLevels=21

I changed "BatteryIconLevels" to "100" after adding the "BatteryIconIdStart" Dword.

Seems to have done it. I had 2% before a reset and 8% after (my battery is almost dead). I'll know more about it after a charge.

[UPDATE] I see what happened: The BatteryIconLevels=65 is added as a Key value with a bunch of those Dwords in there as well. Seems one of the packages I installed created a Key instead of a Dword which screwed it up. I added all the values to the Bitmaps key for the win! Now I just have to find the whacko config in one of the OEM packages.

Another weird problem, which isn't bad... but my alarm clock app "freezes" up while in standby. I use CradleAlarm which has a custom snooze setting set in seconds. I have "600" seconds = 10min.

The alarm goes off at the right time, but when I hit snooze and turn my screen off the countdown stops. When I finally wake up (late) I notice it only counted down 10 seconds before the screen went off. lol. That'll teach me to hit the snooze!

Never had a problem before and unfortunately it is one of the few (only?) alarm apps that actually work the way I need it to. It's like when the screen goes off it goes into a deep sleep and the program stops.
[Touch Pro, Fuze ROM Development] jblakk:
I had that problem when I installed one of the dialers. but when I uninstalled it I got the 100% battery back. I think some dialers have battery icons built in.

As for the alarm clock, I would recomend trying Klaxon. Im using that, and it's fantastic. I travel alot, and live by my alarm clock on my phone. You can even shake it to turn it off, and flip it over to snooze.
[Touch Pro, Fuze ROM Development] hilaireg:
Few Questions

@eras2r:

Thank you for taking the time to extract the differing packages. I haven't looked at the ROM you posted yet but had a few questions:

1) Are you using the 21028 portion of 5.08 or are you still using 5.05 portion.

@Other Chef's

1) There's alot of DEBUG stuff in the OEM folder in Da_G's 5.08 kitchen that doesn't appear in the RUU that I extracted.

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

How are you dealing with the DEBUG stuff?

2) DDI.DLL vs HTC_D3DM.DLL vs ATI D3D

Which one should be used, does the DDI.DLL "break" any applications? Am I confusing DDI with HTC D3D/ATI D3D?

Cheers,
[Touch Pro, Fuze ROM Development] eras2r:
hilaireg,

For Da_G's 21028 0 5.08 kitchen I simply:

Extracted the Da_G base kitchen for 5.08 (21018 XIP/SYS and 5.08 OEM)

Extracted the leaked 5.08 ATT ROM

Created a new \Packages dir structure based on the 5.08 OEM (I learned alot doing this)

However, currently I am running a 21032 XIP/SYS with the 5.08 OEM. I ported 21032 Topaz with the help of Da_G, pfcsabre, arupenthal and qsqa. 21032 is very fast (21018 was too). But in reading through some of the Topaz info, for 21032 in the boot.rgu, I set:

"DataCacheSize"=dword:00000000 ;Let System Decide

"FatCacheSize"=dword:00000000 ;Let System Decide​

...and it seems to work nicely.

If anyone is interested, I can post the ROM/SYS folders for 21032. Just let me know.

-e
[Touch Pro, Fuze ROM Development] hilaireg:
Just going through it now and was considering doing the same.

Same as the one from the link in my previous post?

In process; assume you're trying to keep some 'sequencing' logic to make it easier to debug.

Haven't tried my hand at a XIP port yet; possible to point me to the 21032 RUU that you used as your baseline? BOOT.RGU settings remind me of the Virtual Memory option in XP.

I personally, would appreciate it ... feel kinda guilty though, cause it looks like you've done *all* of the work that I'd end up doing.

Cheers,
[Touch Pro, Fuze ROM Development] pfcsabre:
e,

I'm not sure about this but I think there should also be a new boot.hv mirrored from your boot.rgu that you've edited :rolleyes:

cheers,

-a :p
[Touch Pro, Fuze ROM Development] hilaireg:
Radio 1.12.25.19 & RILPHONE2.DLL

Currently on the WWE 5.05 version of the radio - 1.11.25.01.

After reading through the GPS-releated threads and some of the supporting posts here, I downloaded the RAPH_Radio_1.12.25.19 radio package from the radio thread. After unpacking it, I noticed that the package contains the radio .NBH and a RILPHONE2.DLL.

Could someone confirm that I will need to place the RILPHONE2.DLL in the OEMDrivers folder?

Also, I seem to recall that some changes were needed registry-wise to point to the new RILPHONE2.DLL ... but I can't seem to find the threads that spoke to this - probably imagining it

*UPDATE*

According to slawcop's post; the registry change is when one is not replacing rilphone.dll - i.e. using rilphone2.dll with rilphone.dll as a fall back.

(http://xdaforums.com/showpost.php?p=3407403&postcount=808)

So I guess my question is ... does the 5.08 Da_G XIP contain a version of the rilphone.dll file already? I'm guessing yes since the radio wouldn't come online otherwise and that the rilphone2.dll file in the extracted package isn't required.

Advance thanks,
[Touch Pro, Fuze ROM Development] eras2r:
1) There's alot of DEBUG stuff in the OEM folder in Da_G's 5.08 kitchen that doesn't appear in the RUU that I extracted.

What you'll notice going through a shipped ROM is that in \OEM there are lots of packages that are the same. However there are some that are unique to each ROM and Provider (like AT&T/Telus etc...) These dirs contain how that ROM is configured and they are off the top of my head:

ConfigAP

OperatorPkg

OperatorPkg_PT

Da_G removed all of the unneeded crap in the *.rgu and *.provxml files. He also split some this out into other dirs:

1TouchPro

2Fuze

so that ppl can choose the device. If you want to understand what he did then you need to compare the 5 dirs I listed above to the 3 dirs that exist in \OEM from the 5.08 ROM. Evey chef has their own way of doing things. I suggest you grab NATF's kitchen and also dump qsqa's Proven ROM. You'll begin to see how to customize a ROM by looking at what each does in those dirs.

The really big pain is the OEMDrivers dir. That's where you figure out what drivers work best and replace files to fix issues. Also, the 5.08 ROM has lots of files in OEMDrivers. Da_G split some of them out into packages that are selectable in BuildOS (like CommManager). Some shipped ROMs when dumped break things out very nicely. Others are a pain to pick apart. Pfcsabre told me to look through the oldest Blackstone ROM. That one is broken out very nicely and shows what files need to be included in certain packages when migrating them from OEMDrivers to it's own package.

2) DDI.DLL vs HTC_D3DM.DLL vs ATI D3D

DDI.DLL is actually inside of the xip.bin and I belive is the main video driver. In the 5.08 kitchen Da_G used a ddi.dll from a WM6.5 build.

As far as the d3d drivers... the ati drivers work much better than the default htc driver. If you look in the rgu you'll see that there's a registry entry to use the ati driver.

Same as the one from the link in my previous post? YES

In process; assume you're trying to keep some 'sequencing' logic to make it easier to debug.

I was referring to making selectable packages from the ones that exist in \OEM and \SYS. That's why in my packages post a while back there were overlapping directories in the kitchen that need to be removed.

possible to point me to the 21032 RUU that you used as your baseline?

I used XIP.BIN from HERE

I used SYS dump from HERE

does the 5.08 Da_G XIP contain a version of the rilphone.dll

rilphone.dll is in OEMDrivers, and yes Da_G's kitchen uses the rilphone from the 5.08 ROM. No need to change anything.

-e
[Touch Pro, Fuze ROM Development] eras2r:
pfcsabre,

I ported the 21032 XIP.BIN using XipPorterEx. Also patched for Cert/PP and set PP to 24MB. For the boot.rgu that I'm using, I dumped the original 21032 xip.bin and used it's boot.rgu as the template. Then I added to it all reg entries from the other rgu's. The resulting file I placed in \ROM\XIP.

1) Did I do that correctly? (or should I have copied boot.hv from the 21032 xip.bin into the OUT dir of my ported xip.bin before rebuilding it to xip_out.bin and inserting it into os.nb.payload?)

2) If you add things to the \ROM\XIP dir, will that override what's inside of xip.bin/os.nb.payload?
[Touch Pro, Fuze ROM Development] hilaireg:
Cheers 'eras2r'

... appreciate your time and clear explanations.

:)
[Touch Pro, Fuze ROM Development] Captain_Throwback:
Yes, you are correct - Da_G's 5.08 Kitchen already includes the rilphone.dll for the 1.12.25.19 radio. So you're good to go! :)
[Touch Pro, Fuze ROM Development] pfcsabre:
I haven't used Da_G's kitchen but what I do is:

edit boot.rgu from OUT of xip.bin

generate new boot.hv via rgucomp

overwrite old boot.rgu with new boot.rgu

generate xip_out.bin
[Touch Pro, Fuze ROM Development] eras2r:
Updated Kitchen 21032 - 5.08

For those interested, here is an updated version of Da_G's 5.08 kitchen:

* XIP/SYS updated to 21032 Topaz build

* Timebomb removed from OS

* XIP patched for Certs w/24MB PagePool and reduced ULDR partition

* Cache size set to 0 in boot.rgu - this lets windows decide (testing this out... seems good)

* AudioPara3 updated to support MSVC (includes volume boost)

* LargeTitleBar.dll downgraded to 5.05 - fixes landscape overlay issue​

Link: http://rapidshare.com/files/211213474/eras2r-21032-kitchen-5.08.rar

Special thanks to Da_G, pfcsabre, arupenthal and qsqa for putting up with the swarm of PM's :D

-e
[Touch Pro, Fuze ROM Development] m_reyna_16:
can this kitchen or any of da_g's kitchens work with cdma touch pros?
[Touch Pro, Fuze ROM Development] eras2r:
It doesn't contain the TP2 menu's or notifications - it is ready for them if you want to cook them in.

CDMA is a no. This is a GSM kitchen. Sorry bud.
[Touch Pro, Fuze ROM Development] hilaireg:
BOOT.RGU

The Da_G kitchens I've been working with so far always have a consolidated BOOT.RGU file in the .\ROM\XIP folder. When I cook the ROM, I notice that PackageBuildOS 5.3 runs RGUCOMP and I see the filename for BOOT.RGU appear as one of the items being compiled.

When I check the registry on the device, the changes I made in the BOOT.RGU file found in the .\ROM\XIP folder seem to be there. Seems like there may be two acceptable method of changing BOOT.RGU:

- .\ROM\XIP folder if one is using the same XIP for old & new

- Inside the XIP file if one is porting a different XIP O/S revision/build

Any insights from the masters on this? :)
[Touch Pro, Fuze ROM Development] player911:
I snagged your updated kitchen files, eras2r. I'm testing the latest WM6.5 build right now but even the updated Wm6.5 menu's aren't as easy to use as the Menu Enhancements of the TP2.

I'm gonna see how long I can stand WM6.5 before flashing back to Wm6.1.
[Touch Pro, Fuze ROM Development] Merdinh:
For the people that already are using the eras2r modified kitchen, did you guys find any phone ringing issues, or any other problems phone related.
[Touch Pro, Fuze ROM Development] atsitalian:
Sorry or shoulkd I say gladly, no ringing problems here. try a reflash and just in case... remember to hard reset again the first time it comes to the align screen screen.
[Touch Pro, Fuze ROM Development] rmanaka:
I only had one, and that is SPB Weather did not display images when loaded on a Second Today screen. Haven't reflashed so I can't say that it was a flashing issue.

I didn't have this issue with a ROM cooked from Da_G's original kitchen, nor does it appear in my just flashed RRE 5.5 ROM.

Awesome ROM, however. Extremely fast (guess the huge PP really helps) and GPS synchs in 3-5 seconds.:)
[Touch Pro, Fuze ROM Development] hilaireg:
@Merdinh:

I ran into Phone Ringing Issues after flashing Radio 1.12.25.19 ... and I haven't flash eras2r on my device; so I'm pretty sure it's not the ROM and/or Kitchen. After the radio update, the lights would flash but the phone would not ring. Turning off/on the device seems to have resolved the issue (although I probably should have performed a hard reset after the update).

I've also notice that if I call from my land line or using my other cell phone to the device, at least three rings occur before the lights flash - the ring starts on the fourth. This is twice as many rings as before.

*UPDATE* Just performed a hard reset - looks like that cleans up the ringing delay. Still need to flash the ROM ...

I'm hoping to have some time in the next day or so to flash a ROM built from the Kitchen - I'll post an update afterwards.

Cheers,
[Touch Pro, Fuze ROM Development] Merdinh:
thanks for the replys, i was asking because on another 21032 source i had the ringing issue, and could not figure out what was causing it, i downloaded this one, and it works pretty good, very fast, now just to test the ringer, hopefully it works.
[Touch Pro, Fuze ROM Development] dizzyraider:
Thanks for the updated kitchen eras2r! Do you know where I can find a working black dialer with these 5.08 roms?
[Touch Pro, Fuze ROM Development] andyle2k:
eras2r, thanks heaps for the updated kitchen. I tried it with the new notifications both as a cooked in package and also post cab install. Both didn't work! I had to update the gwes.exe to the 21038 version for it to work properly.

Anyways, any chance of you guys releasing a 21038 kitchen or you don't think it's necessary.
[Touch Pro, Fuze ROM Development] eras2r:
Rhodium Menu and Notification

I have the 2 Rhodium addons working just fine in 21032. Below I am attaching the OEMs for them. These OEMs were not made my me, but they do work as far as I can tell. A bit of advice - the notifications seem to work better if you do not install LargeTitleBar. Just extract and drop them in the Packages directory of the 21032 kitchen.

As for 21038 - I am working on this now. I have been going back and forth with a few different chefs regarding 21038 XIP/SYS. I have it working on my phone, and am currently testing it. If everything goes well, I'll post an updated kitchen in a few days.

-e
[Touch Pro, Fuze ROM Development] tassadar898:
=) Your the man! Da_g's ultimate sidekick!
[Touch Pro, Fuze ROM Development] eras2r:
Updated Kitchen Build 21038 - 5.08

I updated the Da_G kitchen to XIP/SYS 21038. I am still trying to tell which build is faster, but 21032 and 21038 both seem fast and stable. Thanks to qsqa for the 21038 source.

*Changes

Moved HTC Calculator to a selectable package

Included OEM Packages for Rhodium Menu's and Notifications

XIP - patched for Cert / 24MB Page Pool

Please test this one out and post whether you think 21032 or 21038 is faster or if you have any issues with either of them. I really need another Fuze so I can test side by side :D

-e

Link: http://rapidshare.com/files/212466714/eras2r-21038-kitchen-5.08.rar
[Touch Pro, Fuze ROM Development] Da_G:
Rockin'!

Thanks eras2r :)