yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] btprice2001:
Hello. For anyone who's interested, the two files attached will make it so the title on the manila Programs tab will change to the name of the program highlighted when scrolling through the icons. This is a feature in the AT&T Fuze manila. Just copy the files in the zip to the windows directory or add/replace in the package folder before cooking.
[Touch Pro, Fuze ROM Development] DrzNight:
Maybe this will help?

I did some mix and match with you kitchen and NATF's and the bug with sms/mms/email was gone. All I did was replace the oem and Package folders and the bug was gone. I might have broken something else but maybe knowing this helps you understand something that I don't. I'm going to run this "hybrid" all day tomorrow and see if the bug comes back of if I notice anything else and maybe I can spend sometime tomorrow finding exactly what replacement did the trick. Thanks a lot for the hardwork Da G:cool:
[Touch Pro, Fuze ROM Development] Da_G:
Well yeah.. I already knew it was in OEM (that's where 99.9% of the changes vs. any other ROM are)

The question is, what? :)

I'm sure i'll be able to figure it out tomorrow on a fresh nights sleep.. the only question is.. are there any OTHER bugs that need to be addressed :)

Hope to bring you a bug-free kitchen in the morning. :)
[Touch Pro, Fuze ROM Development] crazyC:
Thought I would just dump my V5 OEM folder in to v6 (but still have the white screen issue). Have also tried just changoing the lockstream package to the one I knew was working in V5, but have now given up and reverted to V5 full till the master awakes.....
[Touch Pro, Fuze ROM Development] gadgetdad:
You aren't the only one getting inventive this morning trying to get up and running. I attempted to use the xip he posted in the leaked rom page and all the dll's from oemdrivers in my old v5 rom and could not get past the initial boot splash page. :) Question for all out there - was it the new xip drop from the new rom or was it taking all the dll's out of the new rom and replacing it into my old kitchen?
[Touch Pro, Fuze ROM Development] crazyC:
Well, the new leaked rom in its entirety does not apparently have this bug. At the end of the day it might be a case of dumping the new rom, and changing it one package at a time to see what breaks it - there are numerous blackstone/Diamond packages in the kitchen....But Da_G will sort it once he has had some rest, if no one else does.
[Touch Pro, Fuze ROM Development] hilaireg:
[N00B] OEM/ROM/SYS Comparison Question

I downloaded 'Raphael_ROM_Kitchen_v0.62.rar' from the following topic;

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

Extracted the contents to 'c:\xda\raphael' and placed the 'RUU_Signed.nbh' in the '.\BaseROM' folder and ran the 'RaphaelKitchen.cmd' file, selected option A (extract) and then exit.

I then downloaded 'DaGsKitchen-v6.1-HTC_WWE_5.05.405.1.rar' and extracted the contents to 'c:\xda\Da_G'. When I ran a binary & file comparison tool (BeyondCompare 2), I noticed that there were several differences between the OEM/ROM/SYS folders.

- I understand why new files in the 'Da_G' folder; extras.

- I understand newer/older file dates of some files in the 'Da_G' folder; more 'stable' version, security removed, page pool, ULDR, etc.

- I understand why some files appear in 'Packages' instead of OEM/SYS; selectable extras

What I'm not sure I understand is why some files from the 'Raphael OEM/ROM/SYS' aren't in the 'Da_G' folder. Were they intentionally stripped out (by experience) or is it that the extraction process in the 'Raphael_ROM_Kitchen_v0.62.rar' isn't compatible with this ROM level.

:confused:
[Touch Pro, Fuze ROM Development] player911:
Something in this rom is eating my battery alive. I noticed it this morning. I unplugged my phone, got a shower. When I got out the phone read 90%. at 11:30am i'm down to 25%. I haven't used the phone at all. I noticed the phone is getting pretty hot in my pocket also.

There aren't any running apps in the background and I haven't installed any extra apps except my old resco explorer and a PIMBackup restore. I reset once this morning after I saw a 10% drop while in the shower.

Still dropping like a mofo. This could just be a whacked out battery driver issue or perhaps its something cooked in that is sucking it up. I had stellar battery life using the leaked rom yesterday.

All of this is using the new Radio which was coupled with the leaked rom.
[Touch Pro, Fuze ROM Development] Da_G:
Good Morning :)

Hilaireg: Which files are missing? Anything that's removed from OEM should be in Packages, the only thing that should be completely missing is the .cab's from the original rom and some sample images/ringtones.

player911: I didn't make any changes that should affect the battery usage. Since i'm flashing the original leaked rom to do some comparisons i'll check out TBattery and see what the draw is compared to my modded one..

Edit: Oi! that frickin autover.exe takes decades..

On a side note while I do all this flashing, I was able to port 90% of IE8.12 to WM6.1.. the remaining 10% is the UI and it's kind of useless without that as it renders zoomed out and won't let you zoom in to click stuff.. :P
[Touch Pro, Fuze ROM Development] hilaireg:
Hi Da_G,

Not sure why but every single .DLL in the OEM folder under OEMDrivers show as a Binary Compare mismatch even though the File Size matches.

In the SYS folder, .EXE and .DLL are missing in the Da_G Kitchen but are present in the .62 Rapheal extraction.

If you like, PM me with an FTP point and I will upload the .PDF report that shows the comparison results ... report too big to post on the forum :)

Report Legend

Red = Newer

Light Gray = Older

Blue = On one side but not the other

[EDIT] Wonder why I didn't think of it sooner

http://rapidshare.com/files/194802602/BC2_Report_5.05.405.1_52.58.25.30_1.11.25.01.zip.html

Cheers,
[Touch Pro, Fuze ROM Development] Da_G:
.dll's show different in a binary compare because they get relocated. this is the function of g'reloc and is expected behavior. relocation is required to port dll's from another device (as their memory locations would overlap otherwise, causing a no-boot situation)

You have to be able to look past the relocations when comparing, otherwise almost every file will be different in a binary comparison :)

.exe and .dll are missing? do you mean from folders like filename.dll\filename.dll and filename.exe\filename.exe? with s000 s001 etc in folders, if so, this is also expected, these are modules, raphaelkitchen has recmod.exe in \tools folder, (stands for "Re-Construct Modules") if you remove it, you will find these modules do not get re-created into files. it is not neccessary to have them as both files and modules (as only the modules get cooked in) only reason to have them as files is to move them to another rom/device/etc by just copying them in rather than cooking..
[Touch Pro, Fuze ROM Development] Da_G:
OK, fixed the stupid sms issue, was a newer package i brought in from blackstone, note to self, newer not always better :)

uploading v6.2 which afaik works 100% now :P btw there was a power management change i made that could have caused the power issue. i reverted it for this build.
[Touch Pro, Fuze ROM Development] player911:
super sweet. The power drain didn't occur in the original v6... only in the recent v6. Glad you found it cause my battery is dropping like 1% every couple minutes. It completely died around 12:30pm with absolutely no use today, off a full charge at 8am.

Upload that sucker and I can be happy!

[Edit] I was thinking. This build is 20764, which is older then what we've used in the past... right..... just with newer drivers? If so I wonder if anyone has tried to use the updated packages with 21014 or something.
[Touch Pro, Fuze ROM Development] Da_G:
Sure, you can easily swap around the packages and whatnot (or easier, just swap /SYS for 21014, and the update the various packages in \Packages)

I decided not to as 21014 is a pre-6.5 build and I already have a pre-6.5 kitchen :)

Besides, 21154 or newer should be leaking soon.. but i digress.

No issues so far in my testing, this build is looking great! I took the liberty of enabling the new "Information" tab in power options, but it doesn't look functional yet. (see screenshot)
[Touch Pro, Fuze ROM Development] Da_G:
Posted:

Da_G's Kitchen v6.2

This one works fine, i swear! :) Don't forget the instructions in post one which are now DIFFERENT than Kitchen v5
[Touch Pro, Fuze ROM Development] crazyC:
Now if someone could just find a way of stopping the damn screen turning off during a call.....(have tried all the cabs/reg fixes I have seen)
[Touch Pro, Fuze ROM Development] Da_G:
I know how to set the timer to a ridiculously long time for incoming calls, but it will still eventually turn off.. and outgoing turn off immediately. it's perplexing why they coded a feature that's so difficult to disable :P
[Touch Pro, Fuze ROM Development] hilaireg:
Agreed,

Two biggest beefs:

1) Lack of In-Call Screen off control

You'd think it would have been coded with a Property page or something to allow customization.

2) Security

Nothing more anoying than having to key in the Password PIN just to look at the Today (Home) screen. I know, some of the XDA folks have created applets for this S2U2, TouchLockPro, etc. but you'd think someone at M$ would have figured that folks might want to see Today without having to unlock ... or at least offer a feature to display Today/Password screen when device is locked.

My Motorola MPx220 Smartphone (WM2003SE) locks the keyboard and still displays the Today (Home) screen. When pressing the Unlock SK, it displays the Password PIN screen.
[Touch Pro, Fuze ROM Development] player911:
Doesn't that "NoSleep.cab" for the Raphael's work? I've heard good things about it... although I've also heard that the NoSleep.cab doesn't work in this newly released rom. It is annoying to hit the power button every few seconds to turn on the light to press the 7 key to delete voicemails. I understand the point, so your not pressing buttons with your ear. But the Slide2Answer fixes a lot of those issues.

The Samsung Epix did this... but at least the power button was on the side where your fingers are normally anyway.

[EDIT] @above - I know what you mean. I guess they have the white lock screen because the today screen displays schedules and information that may be deemed private. Would be neat, just so you could check if you had notifications without actually unlocking it.
[Touch Pro, Fuze ROM Development] hilaireg:
Hi player911,

Not any more ... BTW, notice that the key in the CAB (at least my version of NoSleep.cab) differed from what was in the stock version of this ROM.

Noticed that pressing the Action (?) [center button] now activates the screen.

[EDIT] Agreed on the Privacy point ... but an option to show/not show would have been appreciated.
[Touch Pro, Fuze ROM Development] Da_G:
Now that I got a good bug free version out, i'll take a look at disassembling this new rilphone.dll and see if there isnt a good way to control the 'auto sleep'
[Touch Pro, Fuze ROM Development] player911:
I noticed my screen came on during a call when I pushed the volume buttons while on a call. I hadn't noticed the Action button does it too. At least thats a doable solution. Trying to manipulate my hand to finger the power button is awkward.
[Touch Pro, Fuze ROM Development] Da_G:
Here are the keys relating to dormancy, they look to be fed to the radio rom by AT command during initialization:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"FastDormancyRule"
"FastDormancyTimeout"
"EnableFastDormantDisplayDuringCall"
"EnableFastDormancy"

Seems that support for fast dormancy can also be shut off per-operator with a registry key under that operators MCC-MNC, "SupportFastDormancy" - not quite sure where that one goes.
[Touch Pro, Fuze ROM Development] hilaireg:
Thanks Da_G,

Still ramping up on WinMO knowledge; if this was a WinXP box, I'd run Dependency Walker, Filemon, and Regmon to see what gets called. :)

I'm not certain the RIL key is the culprit; i've a feeling the Light Sensor & G-Sensor both play a part in what's happening. I've been experimenting with the HKCU Backlight registry key values and I suspect some of those values are bit flags (ex: 0000 0101) as opposed to numbers (ex: 5).
[Touch Pro, Fuze ROM Development] crazyC:
From looking at the various cabs, there are a number of places that could trigger it, including light and G sensors, as well as under phone and power I think. perhaps it needs all of them dealt with to work.
[Touch Pro, Fuze ROM Development] btprice2001:
Hi, Da_G. Do we still have to add back htcmdp.dll with 6.2? If, so is there a particular version/file we should use?
[Touch Pro, Fuze ROM Development] player911:
Yea I can't quite figure it out. Sometimes when I dial VM... if I don't put the phone to my head... it stays on longer. The moment I move the phone towards my face the screen turns off.

It is a really neat feature but the power button placement is horrible for its use. All of the buttons should bring it back to life during a phone call. At least it would make it somewhat easier.

Doesn't the iphone detect the placement of your ear to distinguish when to turn the screen off? This would be next to impossible on our phones with the lack of MultiTouch.
[Touch Pro, Fuze ROM Development] Da_G:
no, htcmdp.dll is present :)
[Touch Pro, Fuze ROM Development] wmserver:
Da_G,

I got "Double package or .DSM found!!! copying only from Packages Folder!!!"

error from PkgToolsBuildos-5.3

I click "Go" after loading the Rom with all the default selection.

When I click "ok," I got "data exception" error.

Any ideas?

Thanks.
[Touch Pro, Fuze ROM Development] Da_G:
A duplicate error just means it's not copying in the file because it's already in the image in \temp\dump. It copies out files in alphabetical order (ie. NetCF 35 comes before NetCF 2 in the list because there's a duplicate mscoree.dll file, NetCF35 is first so it keeps the newer one.) Or was it a duplicate .dsm error? I don't see any duplicate files, did you unrar it into a clean folder? I don't see any duplicates for that package.
[Touch Pro, Fuze ROM Development] ragpaoa:
Same here.

Unrar'ed to a clean folder.
[Touch Pro, Fuze ROM Development] aruppenthal:
Do a search with windows for the dsm that it is referencing. It will show the double. Be sure to use advanced search and the all files option.
[Touch Pro, Fuze ROM Development] Da_G:
oh doh, i see what the problem is, when i added the files to the archive there was already an archive there so instead of creating a new one it updated the existing one.. and i had changed the dsm name so now there's 2 :P

Delete these 2 files from \Packages\HTCWallpaper\

eabf93f0-f32b-11dd-87af-0800200c9a66 (note there are 2, delete the one with no .dsm on the end)

d187c66c-5fa0-446b-ac1e-fc04dcf8266f.dsm

that'll fix ya right up :)
[Touch Pro, Fuze ROM Development] ragpaoa:
Thanks Da_G, I'll give it another go. Also, thanks for making the OS builder that much easier.
[Touch Pro, Fuze ROM Development] wmserver:
RE: Double package or .DSM found!! error.

Like player said, removing HTC Wallpaper package seem to resolved that.

Build successfully. Will see if it flashes.

Thanks.
[Touch Pro, Fuze ROM Development] eras2r:
Am I doing something wrong?

When I cook v6.2, in Ervius I have selected:

Device Type: ATT Fuze (removed check on TP option)

Windows Mobile Components: Removed both MS Live check boxes

Voice Recognition: MSVC (removed check on CVSD)

The nbh builds fine and I flashed from SD. I Hard Reset after initial boot, and then setup the screen etc...

So when the phone is up for the first time, I see:

* Device still has TP keyboard Layout

* Windows Live is installed (build .1900)

* MSVC is not installed but CVSD is

* Button remapping only has Button 1 available

* Data was not setup for wap or isp.cingular

...All which are default values?

During cooking I left the "All packages in one" checkbox enabled. I did not see the "1 file(s) moved." at the top when complete as stated in the directions. At the bottom of the log screen in Ervius I just see a bunch of Done statements and the toolbar next to Go|Stop says done. I assume that it completed fine, cause I see no errors and th nbh builds just fine.

I have tried this twice with the same results. Am I doing something wrong? Sorry guys still pretty new at this.

Thanks,

-e
[Touch Pro, Fuze ROM Development] Da_G:
eras2r: are you by chance unchecking 'execute create_rom_***.bat'?

from your description it sounds as though that batch file isnt getting executed after buildos completes it's internal process.
[Touch Pro, Fuze ROM Development] eras2r:
That box is checked by default, and I left it that way. Should I try removing the other checkbox for All Packages as One?

-e
[Touch Pro, Fuze ROM Development] propofokgov:
The Dialer

On the dialer loaded with the kitchen, does it have the SLIDE_TO_ANSWER feature, or is it the normal answer key?

Also, do you think this build will solve the problems I've been having with Microsoft Live Mesh and Windows Live Search (the map program)?
[Touch Pro, Fuze ROM Development] Da_G:
It's an almost-official leaked build, so it's got the best chance of NOT having problems :)

eras2r: after you get "done" in the kitchen, try manually executing Tools\Create_ROM_Raphael.bat.. when it's done, close the buildos window..

For some reason that .bat isn't getting executed, so your os-new.nb isn't getting updated, which is why your options aren't taking effect (you're actually flashing an older rom, whatever's in os-new.nb)
[Touch Pro, Fuze ROM Development] propofokgov:
Here's one for you...

...I just tried to build a ROM, with HTCWallpaper checked off... and it STILL tried to load it into the ROM.

Does this sound familiar?
[Touch Pro, Fuze ROM Development] Da_G:
Yes, i put the fix for it a few pages back.. no worries tho, i'm uploading 6.21 which won't have that problem :P Be done soon.

Re: HTCAPM, yes, it looks like this driver tries to determine if the phone is up to your ear, and triggers the backlight shutoff if it is.. it reads the registry keys under HKLM\Software\HTC\HTCAPM\Phone to set parameters for g-sensor values for 'left ear' and 'right ear'.. also a limit on the light sensor (probably a threshold, under x amount of light and within y bounds we are up to the right ear, disable backlight) simply removing the package from the rom may do the trick of disabling fast dormancy.. or you may have to remove it and also use the other registry settings.. but it does play a part :)

Also, there's a new key in the FM Driver, HKLM\Software\Drivers\FMS - FMMode

Duno what it does, maybe controls the bands available to tune?
[Touch Pro, Fuze ROM Development] Da_G:
Fixed all up: v6.21
[Touch Pro, Fuze ROM Development] ragpaoa:
Okay, flashed my first build.

I am on an AT&T Fuze and everything seem to flash okay. Everything I checked was installed properly. I have flashed the original HTC 5.05 official leaked ROM so I can get the new 1.11 radio, plus I wanted to try out the stock for a day before trying this one.

Two minor thing:

- The data connection icon on top is a bit smaller or 'thinner' the new 5.05 ROM. And when you click the task bar to show all the icons, I only show a 3G icon instead of the H icon, even when H is showing in the upper task bar. No biggie.

- In Call Recording does not work. When I am in the call, and I press 'Start Recording' nothing happens, and no recordings are saved.

Requests:

- Can you give the option to install the Opera 9.5 5.306 version that comes with the original 5.05 ROM. I have played with this version for a bit and it appears fast and stable, and more importantly, works with the tilt sensor.

Question:

- Are there any GPS tweaks installed?

Other than that, I'll continue to test, but so far so good. As of now, I don't notice any speed difference from the original ROM. Both are very fast.
[Touch Pro, Fuze ROM Development] Da_G:
Opera came as a cab, as in all the other roms, i can post the cab for you to install but I don't like adding cabs as packages (adds time to the initial startup, isn't any different from you installing the cab yourself through sdconfig.txt)

if someone can make an OEM out of it, sure :) I too noticed ICR not working, i see in the debug log it's not loading, might not be compatible with this dialer version.

The icons are tied to phcan*.dll, which are part of the HTC Dialer package.. the thinner H icon is part of that.. you can delete.. phcanoverbmp.dll i believe, and it'll go back to stock WM6.1 icons :)

Re: GPS tweaks, no. For the most part these are placebos.. from my extensive side by side testing with a bluetooth GPS unit.
[Touch Pro, Fuze ROM Development] Da_G:
18:17:56.000 PHONEAPP: Load ICREngine.dll failed

Looks to me like its failing to load because of dependancies on the voMHub package, which is used in blackstone roms, raphael roms use mHub.. incidentally i used voMHub in my v5 kitchen so that's probably why it worked. if you snag the voMHub package from a blackstone rom, i betcha it'd work.. i'll give it a shot in a bit :)
[Touch Pro, Fuze ROM Development] eras2r:
I ended up moving the kitchen to another Windows XP box I have and cooking works just fine. I believe it may be an issue with AVG antivirus. In any case, all is good. Thanks everyone!

-e
[Touch Pro, Fuze ROM Development] Da_G:
Glad you got it sorted eras2r, I had to remove Windows 7 from my computer for the same reason, some of my tools dont work with it :(

Re: In Call Recording, it's dependant on the file attached to this post.. drop it in the \Packages\PACKAGE_BlackStone_InCallRecorder folder and it'll work fine :)
[Touch Pro, Fuze ROM Development] eras2r:
Da_G,

I cooked in voMHub from v5 kitchen and Call Recording is working. I added it to the OEM folder as you suggested. My question is, I did not remove the mHub package so could this cause conflicts by having both cooked in?

Also, could you post the opera cab from the original HTC Rom? I have not made it as far as deconstructing ROMs yet :)

Much Appreciated!

-e
[Touch Pro, Fuze ROM Development] Da_G:
The DShow package and the mHub package are paired, if you're using the DShow package from raphael, it will make calls to the mHub package.. if you're using DShow from blackstone it'll make calls to the mHubVO package :) So no harm in having both other than using up a bit more space than you need to just to get ICR to work :)

Gimme a min to rar up all the .cab's and i'll post em up!

Here ya go, all the cabs ripped from the ROM: (note htcmms cab is cooked in)

http://rapidshare.com/files/194974808/HTC_WWE_5.05.405.1-cabs.rar
[Touch Pro, Fuze ROM Development] btprice2001:
Hi, I'm seeing this issue too, but it looks like it's stuck showing 100% and I also see another issue that's probably related. When I plug my Fuze into USB to charge or to the computer, the battery/charging icon disappears and does not come back until after a soft reset.
[Touch Pro, Fuze ROM Development] crazyC:
Hi Da-G

Did you change the version of HTC rom tool between kitchens? Avast pulled up an issue and I just thought it was the usual customruu thing but it relates to HTCRT, and it clears all the versions of htcrt in all previous kitchens, except for this one (6.21), and the file size seems larger as well?
[Touch Pro, Fuze ROM Development] mhumphrey:
If anyone is looking for the file to flash just the radio, I posted that and a link to a post with the original HTC roms on the Wiki.
[Touch Pro, Fuze ROM Development] gadgetdad:
exchange activesync

What are the dll's and files for activesync in the rom? Out of the box I had issues with the exchange server timing out and not being able to complete syncing. I swapped out the asyncmac.dll with the stock fuze version and now it will complete the initial sync without timing out. Yet the push email is still about a minute slower then what I had with v5. I would love to be able to play between my stock fuze/v5/v6 oemdrivers to get the fastest sync again. Thanks for the guidance!