yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] Noonski:
I didn't get it directly he posted it to the one and Only Official SimmManager update thread.

Have never been in direct contact with UDK.

Returning to UPX my Cprog.exe is now taking 300Kb more memory after adding the UPX-ed version with all Graphics compressed to.

Which sort of confirms my feelings, Apps that always run in memory from start on >> Modules.

Apps you don't use often >> UPX.

At the moment the Phone Canvas Combo i'm using is All Graphics compressed and all DLL files Turned into Modules memory 7785kb vs 8295kb when i used UPX on the dll files (which also crashed my Cprog).

The default dialer had a memory imprint of 8195kb on my machine.

Hope this helps anyone cooking into helping to make the choice wether to use UPX or not.
[Touch Pro, Fuze ROM Development] hilaireg:
Yes it's there ... i'll add the masd to the package.

Cheers,
[Touch Pro, Fuze ROM Development] jmckeejr:
Interesting results. I'll have to have another look at mine now. I am using Tachi dialer, which could make a difference here I'm sure. My cprog.exe is drawing 6663kb. WOW, just looked ay gwes.exe. That baby is sucking nearly 20MB :eek:

What are you using to compress your images? I'm going for bigger storage and not too worried about memory right now. My ROM is so packed with stuff that I only have about 280-290 free of 315MB after flash. Would like to bump this up a bit so I have around 300mb free after customization and all goes through.

Hey I was trying to get the fullscreen connection setup going that you ported, but I can't get it to run correctly. I am still using the one I posted in the repository that NRG resized. Is there a reg entry for the restart thing? I'd like to not have to reset after setup. Maybe I can just change it in my setup. I guess I can compare them, just thought I'd ask.

I never had luck with using exe files after altered with icoFX, but use reshacker all the time.
[Touch Pro, Fuze ROM Development] Noonski:
Nah this version just doesn't have the reset.

Im compared the regs with newer packages but it wasn't there.

the RGU is identical.

Probably as this was a test version was a test version and Hsome HTC developer also got tired of the unneeded Reset. ;)

I tried updating it to a newer version but that had the reset and the new MUI files weren't compatible with this skin messing up the % when changing the connection.

So i stuck with this non reset version.

Could be that you need to change the download service back into a Bootloader Service.

[HKEY_LOCAL_MACHINE\Services\ConnSetupDload]
"DLL"="ConnSetupDload.dll"
"Prefix"="CNS"
"Index"=dword:00000000
"Info"=dword:00000000
"Order"=dword:000000ff

Or

[HKEY_CURRENT_USER\Software\HTC\BootLauncher\ConnSetupDload]
"Module"="\\Windows\\ConnSetupDload.dll"
"Prefix"="CNS"
"Index"=dword:00000000
"Info"=dword:00000000
"Order"=dword:000000ff

I use Fireworks to do batch compression, and a lot of testing of what looks good enough and if the Application accepts renamed .jpg (90 or 95 % quality files to BMP. (But sometimes this trick even works using renamed Flattened .PNG files to .BMP)

Even on 32 bit's transparant PNG files i manage to get some kb's of the file size.

If there's not to much gradient in the PNG file i use 8 Bit Exact or Adaptive (depending on how acceptable the outcome is) and when it loses to much quality i stick to a 24 bit PNG file.

It's amazing how little the Designers at HTC care about compression.

But i think i'm repeating myself here.

I haven't tried the Tachi Dialer, is it compatible with the ICR App?
[Touch Pro, Fuze ROM Development] jmckeejr:
I'll try your version again. You get a good solid connection setup without the reset? Tachi does have the record in th incall menu. Just checked. So, I would say yes its compatible with ICR.

Just looking at your package compared to mine:

-seems you have a few more dll files

-in RGU, mine says:

yours:

Dont know if this little dif was making it not work for me, but I'll burn one and try it later tonight after wifey goes to bed. Did you do the icon work there on connectionsetup.exe? Or is that default? I also noticed an extra "ConnectionSetupAuto.exe.0409.mui" the second has "original" in the title. I didnt see any difference in content. When I looked at I did see all the menu entries, one of which was the reset one. I'll try it with changed reg and if that dont work, maybe just swap out the exe files and masd.

I also uploaded Tachi package for Visual to my FTP, couldn't attatch here :( It has all fixes to date, like GPS icon is removed, fix for call history, etc. Get it here
[Touch Pro, Fuze ROM Development] Noonski:
You got me i forgot to take that out.

The normal one isn't changed.

I was at first changing it so the sentence would fit in the screen but eventually i got the skining to fit so it wasn't needed anymore.

If only i'd know then that it had already been skinned.

Yes i put that icon there it's not original, and the file is signed.

Can you up your Tachi dialer if it's VGA?

I'll see what i can do about the graphics (and maybe even use it myself;))

Edit found the Link, thanks

I could only shave of 1.9 MB of the total Images.

Memory used was 6623KB. But i do get an cprog error sometimes. i think one bmp isn't being accepted.

(look into that tomorow i think it is Assets_dialer_pressed.bmp, i used a PNG instead of JPG)

But the big difference to the Regular Slider Dialer is that the Tachi Package you posted doesn't use the HTC SIM Log In Dialpad:

[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]
"BaseId"=dword:00000000
"BaseDll"="phcanOverbmp.dll"
"BatteryIconIdStart"=dword:000003e9 (Depending on the phcanOverbmp.dll your using)
"BatteryIconLevels"=dword:00000015 (Depending on the phcanOverbmp.dll your using)

Unless you have this set in OEMDrivers.

But adding the above the memory imprint goes down to 5698kb. (MS Sim Log In Dialer is build from seperate images and the HTC from on DLL file)

around 2.5 MB less memory and still a cool dialler impressive HTC.

So this Dialer is looking pretty good on Memory
[Touch Pro, Fuze ROM Development] jmckeejr:
I guess I do have that in OEM, or in another package. I use a custom taskbar, so these may b in the taskbar package. Be sure to upload once you get all the images tested. Like to check it out.

Did notice something strange in my reg. looking for these entries. Looks like a typo.

[HKEY_LOCAL_MACHINE\Security\ResOver\Bitmaps\BatteryIconLevels = (dword) 65]
"BatteryIconLevels"=dword:00000065

I'll have to get it fixed up, unless its required for custom battery. LOL
[Touch Pro, Fuze ROM Development] hilaireg:
That entry is wrong ... should have been:

HKLM\Security\ResOver\Bitmaps
"BatteryIconLevels" datatype="integer" value="101"
"BatteryIconIdStart" datatype="integer" value="1001"
"BatteryId" datatype="integer" value="0"
"BaseDll" datatype="string" value="phcanOverbmp.dll"

Look at the .PROVXML in TSOWENSTaskBarIcons package.
[Touch Pro, Fuze ROM Development] jmckeejr:
Thanks hilaireg. Looks like the correct entries are there, but this one is aded in as well. This is from...uh...maybe.... Da_G's 21042 easybake oven....maybe. I picked up the package somewhere and kept the original "New_Battery_Icon_Reg_Entries". Just donna delete the last part. Which added a new key instead of value.
[Touch Pro, Fuze ROM Development] hilaireg:
The "New_Battery_Icon_Reg_Entries" package had been split into two parts when eras2r was working on trying to fix it.

The TSOWENS package in my kitchens/packs works perfectly.

Cheers,
[Touch Pro, Fuze ROM Development] gtpf_uk:
Good morning. I'm making a new rom for my TP and i would like to ask if somebody knows a good emulator to try my new rom before flashing in the device.Thanks for your time.
[Touch Pro, Fuze ROM Development] hilaireg:
AFAIK, most chefs flash the ROM directly to their devices as the emulators aren't capable of accomodating the physical (driver) nuances of various devices.

As long as you have HardSPL'ed your device, you should be able to recover from any bad ROM flash - radio and boot splash screen excluded.

HTH,
[Touch Pro, Fuze ROM Development] aruppenthal:
That is correct. Youd be wasting your time trying to emulate the rom as it would never act the same on your device. If the boot fails hold volume down and reset to tricolor. Reflash from there. I have at least 3 no boots a week lol.
[Touch Pro, Fuze ROM Development] Noonski:
And if you get hooked to much we always have a clinic called, Rom Flashers anonymous, when you start pulling out your hair:D
[Touch Pro, Fuze ROM Development] gtpf_uk:
thanks for your advices!!:) i will try it to my phone as soon as it gets ready. Have a nice day.By the way does anyone knows the diffrencies between WWE 5.05.405.1 and 5.05.401.1 WWE rom?
[Touch Pro, Fuze ROM Development] alcadeias:
They are identical... 405 was released for uk users, 401 was released for european users. both of them were released at the same time
[Touch Pro, Fuze ROM Development] gtpf_uk:
thanks for your reply:)
[Touch Pro, Fuze ROM Development] Noonski:
Even using the original Images i get Loads of Cprog errors using this Dialer.

I could just upp the images and see how they fare with you?
[Touch Pro, Fuze ROM Development] alcadeias:
@hilaireg

hello. small question the .net cf 3.7 if enabled in the third package will it overwrite the 3.5 one from the other packages (or perhaps the kitchen, i don't remember exactly where it was)? maybe it would be good to create a subgroup and put the two versions there and choose one... we don't need to have both installed (like in win mo 6.5 where u need both 3.5 and 2.0) right?

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
I've got it as a separate package that will be chef selectable in the kitchen.

Personally, I'm using all three (.NET 2.0, .NET 3.5, and .NET 3.7). During ROM compilation, the log shows that the .NET 3.7 files are effectively replacing the older versions (2.0/3.5).

In the registry, I now see the assembly entries for all three (3) versions. This ensures that applications such as Welcome (which requires 2.0) continue to function.

HTH,
[Touch Pro, Fuze ROM Development] B4PJS:
From my build logs (On 6.5 mind) only two files get overwritten, mscoree.dll and cgautil.exe. I have all 3 cooked in.

HTH
[Touch Pro, Fuze ROM Development] hilaireg:
Correct.

IMHO, this also highlights the importance of keeping the previous versions present.

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
Update 2: PACK3

@all:

You will find the results of PACK3 testing here:

http://xdaforums.com/showpost.php?p=3997048&postcount=914

As you can see from the red entries, some applications are going to require further investigation - so they won't be in PACK3. Unless there's a reason for leaving the supporting applications in, I will remove those as well.

Are there any other packages you would like to see in PACK3? If so, this would be a good time to post your request and a link where I can find the package.

Cheers,
[Touch Pro, Fuze ROM Development] alcadeias:
well i wasn't a big fan of the 3.0 album anyway... a shame the youtube app doesn't work... also i vaguely remember .net 2.0 not being included... can you throw that in? some time ago arrup had some problems with the camera app in his rre 6.1 series, he found that the problem was the conncurence mngr, maybe you should leave that in... thanks for all the hard work you have put into testing each package, i really appreciate it.

Best regards,
[Touch Pro, Fuze ROM Development] hilaireg:
.NET 2.0, 3.5 are already in the kitchen. Have a look in the SYS folder (NetCF) RGU.

The Album, Camera, and YouTube apps are working 80% of the time ... not acceptable to my standards. I figure I need a few more days with each one to get them working properly.

Cheers,
[Touch Pro, Fuze ROM Development] DonS:
Just tried the ROM kitchen and have a couple of questions

I just tried this out and I successfully built a custom ROM and flashed it to my device. This is my first time using WM65 and it has some nice looking features. I'm still getting used to things being moved around.

So far everything looks good. I do have a couple of questions.

Does anyone know how to remap the PTT on the AT&T Fuze to be the OK/Close key? I can change it in the settings, but it doesn't work. Is there some other registry hack or something else I need to do? I believe this was the case with the WM61 ROM I was using before. In my version of the ROM I built, I didn't include PTT_3_0_1912_2827 since I don't use PTT. I assumed that was a package that enabled PTT.

Is there a version of TouchFlo for Windows Mobile 6.5?
[Touch Pro, Fuze ROM Development] hilaireg:
This kitchen should produce a 6.1 ROM ... are you sure you didn't accidentally post in the wrong thread? :)

The Enhanceed XCsDM PTT Mod package allows you to assign the button mapping and keyboard mappings via the Buttons applets in Settings. Have a look at this thread; you may be able to accomplish what you're after using this utility - haven't personally tried it.

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

AFAIK, TouchFLO (aka Manila, TF3D) should function on Windows Mobile 6.5 ... how well is another thing.

HTH,
[Touch Pro, Fuze ROM Development] Da_G:
re: the ok/close mapping :

it uses a method that pttmod does not understand (it doesnt execute a command line directly) - so doesn't work. there are about 3 such options that don't work if i recall :(
[Touch Pro, Fuze ROM Development] jmckeejr:
Hilaireg,

Just wanted to say thanks. Finally got a chance to put a ROM together using the 21051 kitchen. Noticed you really went crazy with the provxml's :rolleyes: Any reason you dont use app.dat? Wouldn't it be easier, and also easier to edit? Its not a problem because I am using all my own packages, but can you give any pointers on making and editing provxml? I often end up ruining the whole xml when I try to remove something. Figured you should be a pro after all the ones in this kitchen. Also, do you think they need to be read-only? I always do a search for "provxml" and change attribs of all of them back so I can edit at will, and have no problems doing it this way. Just wondered if there was a benifit to making them read-only(aside from not being able to change them).

For the sdautorun package, we do need to add "EXEC:\windows\sdautorun.exe" to config.txt right? If so, maybe adding a add2config.txt to the package would help new cooks, and reduce the need to edit config.txt(or figure out which to edit since there are 3-4 config files in OEM). Speaking of, for me the config_PT.txt does not seem to run. I ended up getting rid of all but config.txt.

I have been converting all of my cabs to either packages or mortscript install. Pretty nice because I can make a package and just add the add2config.txt so I can choose what to install. Attatched is my Opera 16070 with mortscript install and add2config.txt. Thought it would be a good example of what you can do with mortscript and also the use of add2config. I am not very good at mortscript so it is pretty basic. Most likely only work for wwe ROM. Exe's are compressed, opera set to "realexit", custom opera.ini, etc. This saves a lot of space, and I noticed the initial customization is super fast now(I install Opera through cab usually, due to preferences). This makes it easy to update since the files are not read-only. Maybe Noonski can have a look and improve. He is the mortcooker and my inspriration for moving to these type of packages. I know he did a jam-up job with google maps.

SORRY FOR THE NOVEL, once I get started I cant help myself.

EDIT: just realized I forgot the Opera.lnk. I have custom icons installed through cab, I'll add it and repost tonight.

http://www.4shared.com/file/114274946/92f212c/Opera_16070.html
[Touch Pro, Fuze ROM Development] hilaireg:
LOL ... actually those are all stock .PROVXML's. My goal was to keep the kitchen as "stock" looking as possible as I figured it would help new & intermediate chefs.

Here again, if a "stock" package used an APP.DAT (aka INITFLASHFILES.TXT for old kitchen'timers), I would use one as well to stay in theme with a "stock" kitchen. Here's some info I put together on .PROVXML

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

I had been applying the same practice until recently when I learned that the kitchen extraction process seems to be the source of the 'Read Only' settings. I still leave them as (S)ystem so as to reduce the number of files initially displayed in File Explorer.

AFAIK, "EXEC:\windows\sdautorun.exe" must be in the CONFIG.TXT file found in .\OEM\OPERATORPKG. For others who wish to read up, here's the link:

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

I agree; kudos to Noonski for putting together XDA_UC. Chefs interested in optimizing their ROM's should make time to look at it. What would be k00l to have, is a repository of XDA_UC applications. Folks could obtain packages they require from this central repository reducing the number of "re-work" effort. For others who wish to read up, here's the link:

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

Lastly,

The packages that I included in the kitchen (and PACKS) are intended to get chefs going with a functional ROM. I expect that once comfortable, they will take some of these packages and "optimize" them to their liking.

IMHO, there's a

signifcant

amount of work required to put out a "public" ROM. I receive many PM's requesting that I put out a stock/custom ROM; that's something that I leave to dedicated chefs (like you) to provide. I'll stick to providing a base kitchen for folks to work with.

:)

Cheers,
[Touch Pro, Fuze ROM Development] jmckeejr:
I think that adding the EXEC command in an add2config.txt might help with sdconfig running before config.txt is done. I'm actually gonna give it a try later. I'll keep you posted. Thanks for the provxml info. Looks like I got some reading to do(also for XDA_UC files). Already cooked and flashed for half the day, now I guess I should do something productive(outside of XDA ;) ).
[Touch Pro, Fuze ROM Development] hilaireg:
Reminder: Kitchen DEVICE Packages

Just wanted to emphasize the importance of the following points as it's often easy to spend hours troubleshooting a behaviour and not realize that the problem stems from a .PROVXML configuration change.

The DEVICE_FUZE and DEVICE_TOUCHPRO packages contain the stock files that were found in the released manufacturer/vendor ROMs.

Make sure to closely examine the contents of these packages before using them.

The .PROVXML files contain many final system changes.

Cheers,
[Touch Pro, Fuze ROM Development] alcadeias:
there seems to be an updated version of the visual kitchen available... http://xdaforums.com/showthread.php?t=469420 will you release an update pack just like you did last time the kitchen tools were updated?

Best regards,
[Touch Pro, Fuze ROM Development] PythonFanTN:
hilaireg,

Is Pack 3 going to be finally up for download this weekend? I haven't been around for awhile, had been using one of the original Clean Rom releases from Da_G's original thread from a few months back for a good while but wanted to give the kitchen based on the newest Fuze ROM a go, but had been holding off until Pack 3 got done. Anxiously awaiting its release. :) Thanks!
[Touch Pro, Fuze ROM Development] hilaireg:
@alcadeias:

I'll have a look at the new version that Ervius put shortly; he's made some significant changes and I want to make sure it's not going to "break" functionality.

@PythonFanTN:

Yes; I'm looking to upload PACK3 before the end of the weekend. Just a bit of final debugging thanks to Captain_Throwback's testing.

In the interim, you should be able to download the existing kitchen an packs and use them as they contain all of the AT&T 5.11.502.2 OEM and relevant packages.

Cheers,
[Touch Pro, Fuze ROM Development] alcadeias:
I saw something about the new kitchen being able to correctly identify the build and release date of the 6.5 nk... maybe soon ervius will figure out where the build date for the 21051 build is located so we can modify it (we still can't change it right?... if we can sorry, my bad, i'm outdated). fingers crossed...

Cheers,
[Touch Pro, Fuze ROM Development] PythonFanTN:
Yep, I've got everything else downloaded....was just waiting to download and add in the Pack3 stuff as well before doing any custom cooking :)

One more question: I have the actual Fuze (as opposed to a regular Pro) and have been used to using the original AT&T Dialer even with the first ROM I ever flashed, though not opposed to trying something new by any means.

Anyway, in looking at the existing (legacy) kitchen with Pack 1-2 I have downloaded....if I choose the 'ATT Fuze Configuration' choice for Config Profile, and then decided I didn't care for the single Dialer option that's there and instead wanted to go back to the AT&T branded dialer in my initial ROM I cook, would I simply need to uncheck the 'Dialer Phone Canvas Slider' option, cook my new ROM, and the AT&T dialer would be in by default....or.....would that just get me a ROM without a dialer at all and then I'd still need to use the .cab I have of the AT&T Dialer from Da_G's original Clean ROM kitchen after flashing?
[Touch Pro, Fuze ROM Development] hilaireg:
As you know, the Date & ROM Version information has moved as a result of additional resources that appear to have been added to the latest releases of NK.EXE.

It's likely that we will not see any tools to fix this issue any time soon as everyone appears to be moving to WinMO 6.5.

The latest release of Ervius Visual Kitchen adds support for the legacy (old style) method of compiling a ROM. It adds support for .DSM & .RGU presence in all of the packages folders found in OEM/SYS/EXT.

To add support for the new version, I need to perform the ROM extraction once again to see what appears. From there, I can determine how much work effort to update the existing kitchen.

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
I did not extract (include) the AT&T Dialer Phone Canvas (or Manila). If you decide to omit the one included in the kitchen, you have a few options:

- Download the AT&T 5.11.502.2 official ROM and extract the Phone Canvas

- Use an existing Phone Dialer Package and add it to your kitchen

- Install a Phone Dialer Canvas package during post configuration

When I released the kitchens, I moved the contents of the stock HTC 5.05.405.1 ROM OperatorPkg* packages to the DEVICE_TOUCHPRO. I moved the contents of the stock AT&T 5.11.502.2 ROM OperatorPkg* folder to DEVICE_FUZE. I then created a DEVICE_CUSTOMIZED package based on DEVICE_TOUCHPRO as it was relatively generic. I typically make any additional changes for myself in that package and leave the DEVICE_TOUCHPRO & DEVICE_FUZE as untouched - i.e. reference. What's left in the OperatorPkg* found in the OEM folders are the bare-essentials.

If you decide to use the DEVICE_TOUCHPRO or DEVICE_FUZE package, make certain to become very familiar with the contents - most notably, the DEVICE_FUZE package. AT&T adds a

significant

number of configuration changes to their stock ROM. These configuration changes are intended to ensure that their customer devices function as trouble free (and predictable) as possible. However, folks like you and I who are used to customizing our devices to fit our needs, often find these configuration changes extremely restrictive.

HTH,