yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] PythonFanTN:
Yeah, sounds like I'll just need to use the existing .cab of the AT&T Dialer from before if I decide I want to go back to it then. While I have a basic level of technical savvy enough to comprehend and interpret some of this stuff without having to ask too many questions and certainly enough to follow the instructions of folks like you that do all such wonderful work to the benefit of us all, I'm nowhere near savvy enough to figure out how to extract something like that from an existing ROM. *g* Thanks for spelling out the options for me!

Thanks a ton for this clarification....without it I'd have probably stuck with the AT&T Config Profile because of having a Fuze in addition to my misunderstanding of what the default profile says on the mouseover tooltip (I'd gotten the impression it was meant mainly for higher level chefs intending to create highly customized ROMs based on these kitchens, far moreso than what I'd be doing, rather than normal folks just looking for the latest simple/clean kitchen ROM kitchen). I'll leave that option as-is now when I finally do my ROM cooking. :)
[Touch Pro, Fuze ROM Development] hilaireg:
Don't hesitate to post questions in this thread about something you're unclear on with the kitchen(s) ... we'll do our best to try and help out best we can.

One of the best tool to get, if you haven't already, is a file comparison utility. In the case of the DEVICE_* packages for example, you can use the file comparison utility to look at the differences and only transfer across those changes that you feel you require.

Cheers,
[Touch Pro, Fuze ROM Development] PythonFanTN:
Well, since you invited questions :) One more I was curious about, on the 4 optional 'audio parameters' packages towards the top....do these all just make the audio output in general louder across the board, except to varying degrees between each one? And if so, what is the difference in real-world practice between the default setup, Da_G's, Eras2r's, and the lesser of the 2 (i.e. not the 'VERY loud') arrupenthal versions?

I'd very much like to increase the volume potential, particularly for hearing during calls, by perhaps roughly 35-40%...and just (a.) wanting to make sure I understand the differences any of the above makes, and (b.) determine which one might best fit my desired results.
[Touch Pro, Fuze ROM Development] hilaireg:
When HTC and AT&t released earlier versions of the stock ROM's, the general conscensus was that it was next to impossible to hear the other party during a call.

It appears that in the AT&T 5.11.502.2 stock ROM, the volume parameters have been adjusted such that I find them acceptable. The various audio parameters packages are adjustments that have been made by those noted.

If you find that the audio is unacceptable using the stock setting, try selecting one of the OVERRIDES and test it for a few days. That said, Arrupenthal's "louder" is a popular favorite.

HTH,
[Touch Pro, Fuze ROM Development] PythonFanTN:
Awesome, exactly what I was looking for. Thanks hil :)
[Touch Pro, Fuze ROM Development] hilaireg:
Uploaded

@all:

KITCHEN-FIXPACK_27062009

http://wiki.xda-developers.com/index.php?pagename=Da_G's Simple ROM Kitchen

KITCHEN-PACK3

http://wiki.xda-developers.com/index.php?pagename=Da_G's Simple ROM Kitchen

VISUALKITCHEN-FIXPACK_27062009

http://wiki.xda-developers.com/index.php?pagename=Da_G's Simple ROM Kitchen

VISUALKITCHEN-PACK3

http://wiki.xda-developers.com/index.php?pagename=Da_G's Simple ROM Kitchen
[Touch Pro, Fuze ROM Development] PythonFanTN:
Just making sure, but I'm assuming the Fixpack adheres to the same directory structure as do the regular packs and one only needs to copy the contents over in parallel fashion after extraction?

Edit: Nevermind, I didn't notice the corresponding .txt file at first, sorry.
[Touch Pro, Fuze ROM Development] PythonFanTN:
Hil or possibly Da_G (if you happen to catch this and this jogs your memory):

Got my ROM cooked and flashed successfully, everything seems otherwise absolutely perfect and functioning as I expect or want....except for one tiny issue. I did indeed go back to the AT&T Dialer as I mentioned above, for 2 reasons. For one, the bottom left bar in the included dialer by default showed "Video Share", and I couldn't find any way to configure it otherwise (I prefer the Contacts option being there and I have no need or desire for Video Share in most cases). Installing the AT&T Dialer cab from Da_G's original Clean Fuze ROM thread took care of that.

The second and only remaining issue I'm missing is, with the stock AT&T setup/dialer/etc, when you go into your Contacts list....instead of the 3-character shortcut bar at the top (i.e. #ab, cde, fgh, etc), there's a neat black sidebar with every single letter of the alphabet A-Z that you can use your finger or stylus to cycle through your contact list with. Now, I know I didn't dream this....I remember reading where this same issue came up somewhere back months ago with someone else missing it and mentioning it to Da_G back then, and I was thinking he came up with a cab specifically for that little bar or something. But for the life of me, I can't seem to find it or even the posts about it in searching. I did an advanced search on the entire ROM development forum using Da_G as the post author and 'contacts' as a search term but couldn't find it.

You guys have any idea where to find that or how to get that back? Thanks in advance.
[Touch Pro, Fuze ROM Development] PythonFanTN:
Whoops, nevermind, I finally found it, wasn't even anything AT&T branded or dialer related at all. HTC RandomAccess was what I was looking for.
[Touch Pro, Fuze ROM Development] jmckeejr:
To have contacts on left soft key you need to add the key:

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\PHONE]
"LSKContact"=dword:00000001

The bar you are refering to is "Random Access". Should be a package in kitchen.
[Touch Pro, Fuze ROM Development] hilaireg:
Correct ...

The "LSKContact" get changed via an operator PROXVML if I recall. A quick search for "LSKContact" text through .RGU/.PROVXML should yield the cultprit(s).

:)
[Touch Pro, Fuze ROM Development] PythonFanTN:
Ah thanks, I may have to cook another ROM anyway as I do have one more minor issue, if there's no other way around it then I'll edit the registry with that and use the RandomAccess cab I have, the dialer otherwise looks pretty much the same honestly.

Anyway....is there any way to either change the size/font size or otherwise disable the Menu Enhancement from the Rhodium? I'd left that in there not knowing exactly how it looked in practice, and while it does look really nice and makes the menus easily navigated with the fingers, at the same time I personally don't like the fact that they take up the entire screen and would like to either be able to make them smaller or else go back to the default menu style. Is cooking/flashing a new ROM without it being included my only option, or is there a registry key or something that could help me here as well?
[Touch Pro, Fuze ROM Development] PythonFanTN:
I went back and looked, and there is indeed a kitchen option for RA....but for whatever reason, it wasn't actually implemented in my ROM somehow, and I know I didn't uncheck it either. The sidebar never showed up until I used the RA .cab from Da_G's original Clean ROM kitchen thread.
[Touch Pro, Fuze ROM Development] hilaireg:
Random Access is already in the kitchen; I'm looking at my device and the size seems fine.

There may be a way of making the menu smaller but I haven't personally looked as I prefer the larger menu. You will need to have a look the RGU files in the packages - also take a moment to search through the entire kitchen RGU/PROVXML files as a recall seeing some other RGU/PROVXML that adjust font sizing for menus.

There's a VB script in the kitchen that you can use to extend the Search Companion ... here's a link to the thread:

http://xdaforums.com/showthread.php?t=490216
[Touch Pro, Fuze ROM Development] hilaireg:
All of the packages in the Kitchen Packs are set to False (unselected) by default. I suggest making all your selections and then Saving the ROM profile; this way, you can reload the profile after loading the rom.

HTH,
[Touch Pro, Fuze ROM Development] PythonFanTN:
RandomAccess is a default kitchen package though and checked by default. I'm just going to cook a new ROM and re-flash without the Menu Enhancement anyway and leaving out another package or two as well this time...I'll see if RA implements properly this time around in the new ROM.
[Touch Pro, Fuze ROM Development] hilaireg:
Against my better judgement; I'm attaching the ERV profiles that I use to build my device. :)

Assuming you have the fix pack, updated tools, and all application packs applied to the kitchen, this should yield a functional ROM. My kitchen is in:

Legacy: C:\XDA\My_Kitchen

Visual: C:\XDA\My_Visual_Kitchen

If you haven't altered the structure of the kitchen, the ERV profile should load without too much trouble. Worse case, use Notepad to look at the file and make the same selections.

If you're not on the Rogers network, you could deselect the RILPHONE override although it shouldn't cause adverse effects.

Try compiling an image for your phone and see how it goes ... that should give you a baseline to compare functionality against.

Cheers,

PS: these files are unsupported. ;)
[Touch Pro, Fuze ROM Development] PythonFanTN:
Well, now I feel bad lol. I appreciate the trouble you went through to come up with that and post it, but actually the new ROM came out fine, RandomAccess is in there as it should be and my menus are back like I prefer. I think I'm good now actually....I truly appreciate the assistance nonetheless though.

On that note, you seem to do a ton of work/contribution here, not only in this thread even....but I don't seem to see any donation means on your posts/sig. I'd be happy to pay a little tribute for my appreciation if you have such and I've just missed it somehow. :)
[Touch Pro, Fuze ROM Development] alcadeias:
awesome work with the kitchen hilaireg. now i have a small bug which i would like to take care of now that i am cooking my own rom. here it is: i like to text a lot, and by that i mean about 1000 sms/ month ( no i am not kidding). problem is sometimes the tmail application becomes really sluggish and unusable, also after i close a thread ( i have about 4-5 in total) it takes a little time before the screen changes completly ( the lines where inbox is written get refreshed later, i can still see fragments from the messages in the thread i just closed there). another weird thing is that sometimes shell32.exe goes nuts and starts using about 50% cpu power and doesn't stop. this also happens with transport.exe which uses 100%. only way to fix is a soft reset. is this because i have too many msgs in my inbox (current count is at about 2600). if this is indeed a problem with tmail, is there an alternative i can use? sorry for the long post.

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
WOW! You are a "text'er"; now I know who to go to for stress testing texting. ;)

I'm not sure the fine folks who coded TMAIL factored in such a high count. If there is a fix/workaround, I've not come across it personally - doesn't mean there isn't one out there.

Even MS Outlook starts to misbehave when there's that many messages in the Inbox. Now, I'm not a CE database expert by any stretch, but I'd be inclined to suspect that you may be exceeding limits of a .VOL file.
[Touch Pro, Fuze ROM Development] hilaireg:
You know ... you're not the first to mention the Donation button thing. I do this because it's an opportunity for me to learn as much as it is to help others.

I appreciate the kind words ... maybe I should look to add a button.

:)
[Touch Pro, Fuze ROM Development] alcadeias:
sure, i'll stress test anything related to texting... oh well too bad. i had this problem with every win 6.1 build and in 6.5 it was actually worse :p i'll try the 21051 build now, the issue i was telling you about i have now on my personal 21046 rom. thanks for your quick reply, i appreciate your help.

also since hilaireg posted his .erv files i will do the same in case someone is remotely interested

Cheers,
[Touch Pro, Fuze ROM Development] Nixeus:
Hellow my friend and thanks for this kitchen.

On my 21051 rom, the new IE is very slow.

Any idea ?

thanks a lot
[Touch Pro, Fuze ROM Development] Da_G:
Typically overwriting icons is controlled through a file named phcanoverbmp.dll.

The dll contains each icon stored inside as a "resource" - each resource is numbered in a special way so that when you tell the system to use the dll as an icon replacement, it overwrites the proper icons.

A registry key is needed to go along with the phcanoverbmp.dll, to tell the system to look there for icon overrides.

Easiest way to start is grab someone elses, open the .dll up in a program that lets you export/import resources like PE Explorer, export a couple icons, edit them in an image editor, and re-import them..
[Touch Pro, Fuze ROM Development] imisim:
I have unchecked MS Voice Command but it's still get installed in the latest kitchen v.5. I haven't tried the other kitchen; therefore, I don't know if will behave the same or not.
[Touch Pro, Fuze ROM Development] player911:
I figured out my problem, which I posted over in the Ralphael thread. Explorer was crashing. I couldn't use Windows Update, Mobile Device Center, or installs.

The fix was a few registry edits and a fresh re-install of the latest Mobile Device Center.

Connecting to the phone while in bootloader mode installed the correct driver for flashing.
[Touch Pro, Fuze ROM Development] nuttsp:
This worked and fixed my connection issue. I still have lag and at this point I am assuming that everyone else does as well.

This really is my last issue I would like to have fixed with this device.
[Touch Pro, Fuze ROM Development] Da_G:
Huh, pollinterval=500 makes sense from a conceptual point of view (that's why i suggested this setting in the first place many moons ago)

But when I looked at the debug log, at pollinterval 500 it polls twice a second and every other poll returns no data.. so it doesn't really make sense that it would fix that problem, but it must cause the GPSID to behave differently.. either way the only harm in doing it is some wasted cpu cycles for an extra poll every second, and well, they aren't wasted if it fixes the issue, so i'll set it back to 500 :)

imisim: have you possibly modified the \SYS folder, perhaps with another build that has Voice Command? On my side MSVC does not build in when the box is unchecked.

player911: i blame vista. :) glad you got it working!
[Touch Pro, Fuze ROM Development] nuttsp:
I set it back (reset) and now it still works. I don't know what the heck is going on......
[Touch Pro, Fuze ROM Development] Da_G:
I stopped trying to make sense of the GPS in this thing a while ago :)

Now i'm focusing all my efforts into getting into the radio ROM.. i'm convinced the key to getting our devices to play nicely is in there..

Already bricked it twice playing around, thankfully I have the proper tools to restore :)
[Touch Pro, Fuze ROM Development] RebelShadow:
One possible bug I am having iwht v5 is I don't think the phone is going into sleep mode or waking up correctly. I use flexmail to check mail every 10 mins and it will wake up the device to check but with v5 it seem that the phone is in a deep sleep or something as the phone won't wake up to check. I didn't have this happen of 2.06 or older roms.
[Touch Pro, Fuze ROM Development] gadgetdad:
I also have this issue, and FM Radio shows the same issue.

Is there anything in the works for a new version with more packages and tweaks any time soon?

Have you had any luck (or even tried) to get the new ie6 from the 6.5 rom into a package that would be usable for this rom?

I came across a great version of Quick Menu 2.8 OEM Package that I have been using on this build for a week now and works great. No pop up issues on reboot or any other 2.7 related issues for quick menu. I found the package here... post 6

http://forum.ppcgeeks.com/showthread.php?p=647607
[Touch Pro, Fuze ROM Development] player911:
WM6.5 has IE8... which is supposedly fully working in the leaked beta build. I know there was some talk about ripping IE8 out for older builds but there seems to be deep roots within WM6.5 that is making it really hard. I tried WM6.5 but because of the beta's other bugs, I'm holding off.

Quick Menu looks neat. I don't keep anything in my start menu except Today, Programs, Settings. OCD thing.
[Touch Pro, Fuze ROM Development] Da_G:
I pulled out a couple updated packages from the xperia rom that was just released, adobe reader 2.5 has reflow support from that one.. seems to be faster too. updated htc randomaccess and a couple others..

it has a new version of touchflo too but it doesn't play nice with the youtube app and other touchflo-aware things because it's modified for xperia..

gotta do a bit more testing on them before i release :)

IE8 will never work on WinMo 6.1 because it relies on some features in XIP.. and WinMo 6.1 doesn't boot with WinMo 6.5 XIP.

I suspect we'll get a newer, more stable build of 6.5 coming along soon anywho.. :)
[Touch Pro, Fuze ROM Development] Da_G:
As promised;

Adobe LE 2.5 updated from the xperia ROM..

Among other things, this version of Adobe LE 2.5 supports Reflow, which is nice :)

http://rapidshare.com/files/190838701/PACKAGE_Raphael_AdobePDF_0409.rar
[Touch Pro, Fuze ROM Development] skyfox99:
I am trying to cook into the ROM the touch response newer version. And for the life of me I can't get it to work. I am new to the cab>package thing and would assume that is where I am doing something wrong. But I have followed the instructions to a T and dotted all my "i"s. The cab works just fine, but when I create the package and cook it in, the settings and things are there in start>settingsm but there is no actaull touch response.

I know there must be steps in the package creation progress since I am trying to get the htc black bars to cook in and that doesn't work either. Could someone take a look at my packages at please tell me what I am doing wrong?
[Touch Pro, Fuze ROM Development] Da_G:
IRT TouchResponse: That cab has a setup.dll routine, which contains much of the setup for registry entries and whatnot; the package creator cannot directly convert such packages. You'll need to install the program via cab with RegLogger running, note the registry entries you need to grab, and put them in an .rgu manually.. or poke at the setup.dll with a hex editor and grab the registry entries from there.. or just poke around the registry after it's installed, find the registry entries, and export them.. any way you go, not an automatic process :)

I don't recommend using the package creator at this point in time, unless you are aware of it's shortcomings and are able to work around them.. it's got a few bugs (registry entries aren't created correctly, mishandles setup.dll cabs)

Your package for the theme looks fine, did you edit one of the config*.txt's to call config_theme.txt though? The system won't execute that automatically, it has to be chained in the config*.txt sequence. (Like how you have it calling config_end.txt at the end, whatever config called config_end.txt before needs to call config_theme.txt now)
[Touch Pro, Fuze ROM Development] skyfox99:
Ah, well that would explain alot. And thanks for letting me know that you don't reccomend the cab>package... none of the cab I convert work, and I thought it was something I was doing wrong. I guess it was, just not my fault. Is there any software that I could use to do this process. I searched google and XDA and couldn't find anything else besides that program.

I have not edited any conig.txt to call anything... I was under that assumption that using the cab>package would create a package that I could just drop in the kitchen's packages folder... So I would have to edit a config.txt to call config_theme? Which one would I have to edit? I am semi-familiar with sdconfig, is it something along those lines, where there is a master config.txt file somewhere and I need to edit to call upon the specific file?
[Touch Pro, Fuze ROM Development] Da_G:
Here's the flow of the config files on first boot:

CheckAutoRun.exe runs on first boot, waits for the right signal to kickstart the autorun process, runs the program found here:

[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Windows\\autorun.exe"

AutoRun.exe runs, checks the following registry key:

[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Windows\\config_operator.txt"

Then it pulls up that config and follows the instructions given there (works exactly the same as sdconfig)

In this case, config_operator.txt is in \OEM\OperatorPkg, and contains the following:

LOCK:Enabled
LOCK:Disabled
EXEC:\Windows\SDAutoRun.exe

You'd want to change it to read:

LOCK:Enabled
CFG: \WINDOWS\config_theme.txt

Now, change your config_theme.txt to read:

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

Note that if you make the change and don't include a config_theme.txt, the autorun sequence is going to be stuffed up :)

As for cab > package, don't know of an automated tool other than ervius' tool. Maybe we should gently nudge him to update it :)
[Touch Pro, Fuze ROM Development] skyfox99:
Worked perfectly (i didn't really have any doubts, since the info came from you).

So out of curiousity, I have noticed with a few others roms that it appears they have the actual .cab files saved to the ROM and they have the cab installed upon the initial customization, instead of a package. Is there a benefit to this? I assume I can do this by using the confog_operator to call upon CAB: \"insert cab name here" but I am curious as to if this will work (for a possible work around instead of having to add packages) and where would I insert tha .cab file in to the kitchen?

and on a side note. I wanna config my own welcomehead for the start up. I know how to do it post install of the ROM (real easy just replace the file with my own .png) but How would I do it in the kitchen? And I guess it isn't the welcomehead I am talking about... Like the screen where you have it say "midgets are..." how would I go about changing that to my own design on the initial load of the ROM?
[Touch Pro, Fuze ROM Development] Da_G:
Yep, you can stick the CAB: call in any config*.txt in the chain, and it will execute it. Just note it has the same restrictions as sdautorun (cab's that require user input will stuff up the process) - You can stick the cab anywhere you like in \OEM, during the cooking process, every file gets inserted into \Windows, and optionally copied out from there. It's easiest for organizations sake if you keep the .cab in the same folder as the config*.txt that calls it, makes it easier to diagnose issues later on :)

if you have to install a cab that requires user input, precede the CAB: line with:

LOCK:Disabled

and follow it with:

LOCK:Enabled

That releases the progress bar screen from being on top and allows the cab to come to the front so you can input whatever info is required by the cab's setup routine.

The only downside to doing it this way is now you have more data being used in your internal storage - you've gotta store the cab, and then the stuff it installs. Other than that, no harm done other than a longer initial startup :)
[Touch Pro, Fuze ROM Development] skyfox99:
As far as for taking up storage... Is there any difference in size between using the cab method and creating a package when it comes to taking up system storage memory? And you post so quick, did you catch my edit of the post above?

you mentioned lock and unlock above... do I need to use any hide command like in SDConfig to be able to select what the user input is for? I probably won't use too many cabs that do, but just want to know in case.

and when using your kitchen, I try to use the update ROM version and date on the left panel and it gives me an error saying certain file not found... I do I go about changing the ROM date? I saw above where I can edit that .provxml for the name (although it still says WWE next to it, wanna get rid of that too)... is there a similar option for the date?