yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] Noonski:
The script processing is already handled in that previous package with SDAutorun & XDA UC as it needs Mortscript to parse the installer scripts inside the .XDAS files. And of course native support for Mortscript. So it will recognize .XDA, .XDAS, .XDAZ, .XDAI, .mortrun & .mscr files with that package.

The Keys and notifications i delete are:

(Script style but they make sense)

RegDelete( "HKLM", "\init", "Launch100")

RegDelete( "HKLM", "\init", "Depend100")

RegDeleteKey( "HKLM", "\Services\SqmUpload" , TRUE, TRUE )

RegDeleteKey( "HKLM", "\Drivers\BuiltIn\SqmEngine" , TRUE, TRUE )

RemoveNotifications( "ceipui.exe" , "AppRunAfterSync" )

RemoveNotifications( "ceipui.exe" , "AppRunAtNetConnect" )

RemoveNotifications( "repllog.exe" , "AppRunAfterTimeChange" )

RemoveNotifications( "sqmevent.exe" , "AppRunAtTime" )

As i don't know a way of removing Notifications through xml files

And the changed regs are:

[HKEY_LOCAL_MACHINE\System\SQM]

"Enabled"=dword:0

"UploadEnabled"=dword:0

"EnableUI"=dword:0

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\State\ScreenOff]

"upt1:"=dword:0

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\State\Unattended]

"upt1:"=dword:0

Was just about to flash a test package with all of these and the Dummy CustStat.dll.

I was confused, but the Dummy was only in the 6.5 Kitchen.
[Touch Pro, Fuze ROM Development] hilaireg:
If they are registry entries, then we can skrog them via .(PROV)XML and/or RGU.

If not, I'd suggest running with what you have.

:)
[Touch Pro, Fuze ROM Development] Noonski:
No the notifications are set in the mxip_initdb.vol.

The old/other/previous and more error prone way was to delete notifications from that file.

That's why i put all into the script, also because of using the RGU way to delete from the registry has given me a sour rom sometimes (bit back in time)

Also because the only way i could for instance cook Butler, was when i added the service at second boot, instead of from the first boot. And i needed to time when the butler.exe started after booting so it would not result in a Freeze at the Welcomehead Bootscreen.

After that i stepped over to the dark side and didnt go back to using RGU files to delete.

Second test now on the package, no fun without the Booboos.

Looking Good SQM looks to be completely Bye Bye. (not all the files but it actually running in any kindof way).

I have separated the Packages

1. Remove SQM, extra Active Sync Start and Customer Experience. Services, Drivers, Init's and Notifications.

2. Regular default allready Present SDAutorun V2

3. XDA UC Silent Install and File support, DotFred Taskmanager & Mortscript.

The last i can't separate as XDA files need to be able to use some advanced tricks from the Taskmanager & Mortscript, like registing DLL files, parsing Provisioning.xml files, parsing .reg files, Stopping and Starting Services etc etc everything one actually needs to make a sort of Open Source-ish installation and tweak file.
[Touch Pro, Fuze ROM Development] hilaireg:
@Noonski:

Just downloaded the .ZIP; I'm going to put it at the

top

of the PACK3 queue to complete so as to ensure that they are available ASAP.

* EDIT *

Dude ... awesome work! LOL; you even aligned them to the kitchen format; TOO AMAZING :D
[Touch Pro, Fuze ROM Development] tassadar898:
can't wait! what kitchen do you suggest a newbie use. legacy or the visual?
[Touch Pro, Fuze ROM Development] tassadar898:
eta on the links? I spot an "uploaded" but no link. :)
[Touch Pro, Fuze ROM Development] hilaireg:
Should be up now.

... let the cooking begin.

:)
[Touch Pro, Fuze ROM Development] tassadar898:
any chance on releasing pack3, i'd really like those "gps enhancements"

edit: or maybe a cab that will add all the enhancements? the fastest gps locks ive gotten after trying nearly every rom out there was da_g clean 6.5 rom so i trust da_g
[Touch Pro, Fuze ROM Development] hilaireg:
[KITCHEN][WWE]: Windows Mobile 6.1 21051 Kitchen for Raphael GSM

Kitchens and packs are finally uploaded; this post marks the beginning of posts related to the kitchen.

I'll see what I can do. If all goes well, I should be able to get to PACK3 this upcoming week - I'm after those as well.

... I promised to finish an XIP Porting Guide.

Cheers,
[Touch Pro, Fuze ROM Development] Noonski:
I Saw a SimmManger 6.6.0 in the OemDrivers Folder.

Here's 6.6.4.

No that's not the official Icon It's a personal version.

I don't use the new Manilla Start Menu or Programs Tab but actually replace all icons in the actual apps. Saves me space from actually cooking all those QTC files.

There actually is an official SimmManager Thread but not a lot of people post the latest SimmManager to it.

Tommorow i'll cook up an OEM with the Ati d3d drivers including a Script to switch between the default HTC d3d Driver and Ati's.
[Touch Pro, Fuze ROM Development] rockuman_ex:
i have a problem with roms created by visual kitchen (not the latest version, but the one before today's).

all the roms created all seems to be working fine, but after a while (within 2-3 weeks), TF3D seems to stop working.

I have soft reset etc, TF3D seems doesn't want to load.

I get the HTC logo on my Today screen, but nothing else.

I've disabled it from the today screen, then reenable it again, but still fail.

I try not to reflash it again, is there a way to fix it?

never had any problem with original firmware or those roms cooked by other people, it's just those roms cooked from the visual kitchen.

any help given is appreciated :)

Thanks
[Touch Pro, Fuze ROM Development] hilaireg:
That's one of the many problems I was experiencing with my ROM's. Try compiling a ROM using the new kitchen. I know it's a drag, but I suggest even running a compiled ROM for the same period of time to see if you experience the same problem.

If all goes well, slowly migrate your packages/changes over to the new kitchen afterwards.

Cheers,
[Touch Pro, Fuze ROM Development] rockuman_ex:
looks like i'm not the only one having the same problem :(

is there a fix?
[Touch Pro, Fuze ROM Development] rockuman_ex:
can someone please upload the kitchen to somewhere else, not RS?

i'm having problems with RS, keep stopping at 17% :(
[Touch Pro, Fuze ROM Development] rockuman_ex:
how do i disable the video shown on first boot? (in visual kitchen)?

Thanks
[Touch Pro, Fuze ROM Development] rockuman_ex:
looks like everytime tf3d 1.2 is started, it's trying to play a video which doesn't exist.

how do i disable this? kindda annoying :mad:
[Touch Pro, Fuze ROM Development] SamsungGalaxySamsung:
Hey Chefs,

great work you have done.

But the most important one. What about dutch .mui :D

I want to cook a dutch wm 6.1 rom

Thank you very much for your help.

Greetings Shazad
[Touch Pro, Fuze ROM Development] Noonski:
Disable PlayShow in Visual Kitchen.

This should only happen Once.
[Touch Pro, Fuze ROM Development] hilaireg:
When I was having my TF3D issues, I enabled debugging, via the Debug Tool, and noticed that TF3D always performs a check for the video. Seems like HTC hard-coded the Sample Video as part of TF3D - so I left it in.

The packages to look at are:

- PlayShow

- SampleVideo

HTH,
[Touch Pro, Fuze ROM Development] hilaireg:
Hi Shazad.K,

As a quick test in the Visual Kitchen, make a copy of the 0409 folders and rename to your language code (OEM/SYS/EXT) - should be able to select the language at build time. Afterwards, change the content of the "new" language folder to have the files specific to your language.

Unlike 6.5, the various languages were never available.

HTH,
[Touch Pro, Fuze ROM Development] alcadeias:
first of all congrats on the release of the new kitchen, awesome work. two small questions: do you have an eta on visualpack3? and also is it enough just to overwrite the old sim manager in oem drivers with the one posted by the mod? what is your advice? replace it or just use the one already in the kitchen?

regards
[Touch Pro, Fuze ROM Development] Noonski:
You can run the new Sim Manager from any location on the device and test if it loads contacts quicker and such.

You can simply replace the one in OEMDrivers.
[Touch Pro, Fuze ROM Development] hilaireg:
My intention is to finish my work on PACK3 this upcoming week.

I suggest making a SIM Manager OVERRIDE package similar to what I did with the ATI Video driver, RILPHONE, etc. so as to avoid contaminating your OEM folder as it is stock AT&T 20771.

In the case of an entire package, I normally compare the desired package against what I have. Note the differences, make any package changes to standardize it to my format, and then add it to the kitchen for testing.

This ensures that I remain in control of my kitchen. I also keep a Change Log for troubleshooting purposes.

IMHO, all chefs should follow a similar practice with any package they want to use.

HTH,
[Touch Pro, Fuze ROM Development] Noonski:
I got some Dutch MUI's all separated up. And even some that don't exist.

For those that i haven't had the time i use the English version renamed to 0413.

I don't know If hilaireg wants to add more languages, but all my resources belong to us.

But haven't updated all my Dutch separated Mui's to Raphael most of them are from the Diamond but that shouldn't spoil the fun.
[Touch Pro, Fuze ROM Development] hilaireg:
@Noonski,

Maybe we should look to insert a Post #8/#9 and insert all the Languages you have there.

Your thoughts?

:)

@all:

VISUALKITCHEN-TOOLS-UPDATE-10.2(1.2), 25 MB, 14.06.2009

http://xdaforums.com/showpost.php?p=3776578&postcount=4
[Touch Pro, Fuze ROM Development] Noonski:
Right now i don't have it planned in the near future to make them all fit into this kitchen, im have to be realistic.

But this kitchen will be around for a year or so, there's enough time ;)

Right now i'm trying to port the new Fullscreen Topaz Connection setup to VGA for you.
[Touch Pro, Fuze ROM Development] hilaireg:
np ... once PACK3 rolls out the door, i'll look to get the languages you have and see if we can "modualize" them like the ROM/SYS and application PACKS.

Chefs could then be able to download the language they require and overlay it onto their kitchen.

BTW - if some senior chefs would like to contribute to this initiative, let us know. We most certainly would appreciate the help as it is

a lot

of work keeping this going.

Awesome ... keep me posted.
[Touch Pro, Fuze ROM Development] alcadeias:
There already is an option in the kitchen to use the ATI d3d driver

EDIT: just realised it would be kinda neat to switch between the two drivers on the phone after flashing... looking forward to your release
[Touch Pro, Fuze ROM Development] hilaireg:
Select the package during ROM compilation, that will add the ATI driver - the HTC driver is named differently.

Look at the ATI package .RGU to see what registry key(s) are changed. Then you can run a script, .XML, or Regedit the key(s) to switch between the two drivers. That way, you don't have to worry about driver signing issues since the file is part of the ROM. You will likely need to power on/off your device afterwards.

When the driver name is identical, you will need to run a post-installation .XCAB/.CAB (should be signed) to install the driver.

HTH,
[Touch Pro, Fuze ROM Development] Noonski:
Finished Rhodium Connection SetUp VGA Skin.

Pfew that took a bit longer then i had planned.

Damned Fullscreen connection ony shows up after Flash.

Portrait is fully done, Landscape has one little offset mistake i can't fix but it's readable and useable.

It has fake Mui files in English for German and Dutch.

http://rapidshare.com/files/244579415/PACKAGE_Noonski_ConnectionSetup_0000_2_7_37392_4.zip

In my SeTup it doesn't ask to restart, which is exactly the way it should be.

And also Finished and Tested the Display Driver Switching OEM package, I included the needed DLL files.

You can Switch Back and forward, and it will then reboot. The script will be added to the ControlPanel System Settings.

Time For A Break.
[Touch Pro, Fuze ROM Development] alcadeias:
took a quick look at your switching package and i don't get something. is default_d3dm.dll used for anything? i am not familiar with that file and i don't see any reference to it in the script u wrote. sorry if this is a noob question i am just starting to learn more in depth things about flashing. also the connection setup package doesn't seem to be in the necessary format for the visual kitchen, can u give me a few hints on how to make it compatible?

All the best
[Touch Pro, Fuze ROM Development] Noonski:
Well that's a good one that i don't have a direct answer for.

But that driver might not be needed at all.

But i left it in for safety.

I'll do some tests about that in a few days.

And do some Benchmarks to.
[Touch Pro, Fuze ROM Development] hilaireg:
AT&T added both of those D3DM drivers to the 20771 rom. From what I see, the "default" D3DM driver is not in use.

They may have left it behind in case of issues or it may be a software based driver.

Cheers,
[Touch Pro, Fuze ROM Development] rockuman_ex:
thanks a lot! :D
[Touch Pro, Fuze ROM Development] hilaireg:
Have a look at this post; should get you going.

http://xdaforums.com/showpost.php?p=3893696&postcount=1102

:)
[Touch Pro, Fuze ROM Development] B4PJS:
Or just use these tools...

http://xda.b4pjs.co.uk/Kitchen%20Convertor.zip
[Touch Pro, Fuze ROM Development] alcadeias:
awesome! thanks a lot man!

Regards,
[Touch Pro, Fuze ROM Development] caeci11ius:
If you want to remove the video, I did it in the 21046 kitchen as follows (you can't disable the PlayShow package it's part of as the ROM won't boot):

* Open the package folder and remove the video (in 3gp format from memory)

* Edit either the registry for the package. It contains two references to video files labelled either 0 and 1. Just remove these references. It contains a third key that says something like PlayVideo = 0x...01 or something like that. I changed this to 0xxxx00.

* Open the ProvXML for the PlayShow package and remove everything in the first <Characteristic> section (where it makes a directory and copies the video into it...the bit you should get is:

<characteristic type="FileOperation">

<!-- MKDir -->

<characteristic type="\Content\Video" translation="install">

<characteristic type="MakeDir" />

</characteristic>

<!-- Copy -->

<characteristic type="\Content\Video\Touch_Pro_GettingStarted.3gp" translation="install">

<characteristic type="Copy">

<parm name="Source" value="%CE2%\TouchPro.3gp" translation="install"/>

</characteristic>

</characteristic>

</characteristic>

After that I had a rom which was 5MB smaller and didn't play the annoying video on boot.
[Touch Pro, Fuze ROM Development] hilaireg:
You can even go one step further and add the registry entries to change in the .PROVXML in question ... this ensures minimal change to the default values in the .RGU file.

There are some initiatives underway regarding updating packages in ROM via FW Update by Da_G - avoids having to reflash ROM on the device. One of the requirements is .PROVXML's as the update mechanism is designed to only apply .RGU changes once per package.

Cheers,
[Touch Pro, Fuze ROM Development] Noonski:
To Prove my point about the Whole XDA file thingamabob.

Here's an XDAS file made from the Opera Package i found in the Kitchen.

It takes 4,13 MB of space in compared to the 8,46 of the OEM package.

And installs twice as fast as a cab file.

And off course only leaves 1 file in the Windows folder/ROM memory.

Just drop it into any folder that is being cooked with the XDA Service Checked in the Kitchen.

http://rapidshare.com/files/245316354/Opera9.xdas
[Touch Pro, Fuze ROM Development] hilaireg:
Agreed;

When I implemented the "package" version, my mindset was around having everything in the Windows folder pre-expanded. This would allow for a full device hard reset without having to worry about locating .CAB's to run, risking that a .CAB fails to install, or other unknown "vendor" reason.

... in the case of applications like Opera however, which change often, it's the way to go IMHO.

Excellent!

:)
[Touch Pro, Fuze ROM Development] Noonski:
Cabs are the root of all evil that is called Windows Mobile Marketplace.:D

The last year cooking i preferred having a SDConfig.txt file that only contained.

EXEC: \Windows\SDAutorun.exe

Cabs like to leave behind a little temp file to restore the system to pre installed state.

BTW do you know what the new Topaz Package PACKAGE_Topaz_RestoreGPS is good for?

(yes being lazy here)
[Touch Pro, Fuze ROM Development] hilaireg:
Da_G had a post a while back on the thread about those "GPS Restore" packages ... all they do is purge the ephemeris GPS data from NVRAM - a tool that we already have floating around in package form.

HTH,

@all:

VISUALKITCHEN-TOOLS-UPDATE-1.3 aka 10.2(1.3), 17 MB, 16.06.2009

http://xdaforums.com/showpost.php?p=3776578&postcount=4
[Touch Pro, Fuze ROM Development] Noonski:
I tested setting the default_D3D.dll drivers in the registry.

And the device was still running correctly.

If anyone's adventurous to do some Benchmarking on that, have fun.

I'm currently involved in something else.

Good News stopped being involved in something else.

Found a missing Registry key looking through icr.exe with hex edit.

[HKEY_LOCAL_MACHINE\Software\HTC\ICR]

"Bluetooth"=dword:00000001

And geuss what it works dammit, now i can finally have my dinner.

Dammit the registry key isn't actually needed but it does add control over the behaviour.

Sory for the excitement.
[Touch Pro, Fuze ROM Development] hilaireg:
Nice find; for those who want to incorporate this additional registry value, the package is:

InCallRecorder_1_0_1821_2426
[Touch Pro, Fuze ROM Development] Noonski:
One more extra for the Kitchen.

I attached the Compressed Phone Canvas Graphics.

Around 75% less then the regular Bmp versions.

And it knocked of 200 kb of memory usage on my Cprog memory usage.

(hoped for a bit more)

And maybe it's just psychosocial But the dialer does feel a bit lighter and more responsive ;)

I made the BMP's into 95% compressed Jpg files so there could even be more reduction to be made.

I have a test for the coming days where I will try them as 8 bit's Adaptive colour match PNG files renamed to BMP to see if they also get accepted.

( i use this compression on most non transparent PNG files unless you can see the quality loss i switch to Exact colour match)
[Touch Pro, Fuze ROM Development] hilaireg:
Update 1: PACK3

@all:

Quick update for those who are monitoring (care about, interested in, etc.) the progress on PACK3.

So far, i've ported the following applications for PACK3 - Legacy & Visual ktichens. Applications in blue have been fully tested:

App. Name Version
--------------------------------------------------------------------------------
[COLOR="Blue"][B].NET Compact Framework 3_7_8345_00[/B][/COLOR]
[COLOR="blue"][B]AdobeFlashLite 3_1_9_1_122_90[/B][/COLOR]
[COLOR="blue"][B]AdobePDF 2_5_1_0_378273_00B[/B][/COLOR]
[COLOR="Red"][B]Album 3_0_1914_2626_0[/B][/COLOR] ... requires more work
[COLOR="blue"][B]Arcsoft_MMS 5_0_27_116b[/B][/COLOR]
[COLOR="red"][B]Camera 6_16_34566_0[/B][/COLOR] ... requires more work
[COLOR="Blue"][B]ConcurrenceMgr 1_5_19113219_0000[/B][/COLOR] ... required for YouTube
[COLOR="Blue"][B]Da_Gs_GPS_Toolkit 6_5_21815_0[/B][/COLOR]
[COLOR="Blue"][B]DisableCustsatSQM 0_0_0_0[/B][/COLOR]
[COLOR="Blue"][B]DShow 2_00_19151432_0[/B][/COLOR] ... required for YouTube
FacebookEngine 1_0_19151532_00 ... required for Album
[COLOR="blue"][B]Field_Test 2_19_0_0[/B][/COLOR]
[COLOR="blue"][B]HTCFontLink 1_0_19132133_1[/B][/COLOR]
[COLOR="blue"][B]JBlendJava_6_1 0_0_20090402_6_1[/B][/COLOR]
[COLOR="Blue"][B]JetCet_Print 5_2_1014_02[/B][/COLOR]
[COLOR="blue"][B]JetCet_Presentation 5_2_1043_00[/B][/COLOR]
[COLOR="Blue"][B]mHubVO 1_75_090515_X0[/B][/COLOR] ... required for YouTube
[COLOR="blue"][B]MicrosoftFacebook 1_0_0_7[/B][/COLOR]
[COLOR="Blue"][B]MortScript 4_2_0_0[/B][/COLOR]
[COLOR="blue"][B]Opera_Browser 9_50_16643_0[/B][/COLOR]
[COLOR="Blue"][B]OutlookEnhancement 1_1_1822_3121[/B][/COLOR]
[COLOR="blue"][B]QuickMenu 2_8_414_1614[/B][/COLOR]
[COLOR="blue"][B]SIM_MGR 6_64_0_0[/B][/COLOR]
[COLOR="blue"][B]SIM_MGR 6_68_0_0[/B][/COLOR]
[COLOR="Blue"][B]SIMLock 4_24_0_1[/B][/COLOR]
[COLOR="blue"][B]SmartTouch 1_2_19132028_1[/B][/COLOR]
[COLOR="Blue"][B]Teeter 1_6_19142724_00[/B][/COLOR] ... removed, missing dependency
[COLOR="Blue"][B]TouchInCallScreenTweak 1_1_2_0[/B][/COLOR]
[COLOR="blue"][B]XDA_UC 1_0_0_1[/B][/COLOR]
[COLOR="Red"][B]YouTube 2_5_19151528_0[/B][/COLOR] ... requires more work

I've corrected deficiencies that I discovered during porting and the remaining shortlist should be done within a day or so. I'll perform some final stress testing over the next few days and hopefully, I will be able to post PACK3 before the end of the week.

Unless an application fails miserably, this is what you can expect to see in PACK3.

Cheers,
[Touch Pro, Fuze ROM Development] Noonski:
UDK just posted a new SimmManager 6.69 ghegheghe.

Was just about to upgrade to that Opera Browser to.

Not tested yet.
[Touch Pro, Fuze ROM Development] jmckeejr:
Sounds good hilaireg. I haven't even had a chance to look at the kitchen, my wife been home forever :rolleyes:

Noonski, did you also try to compress the exe files in dialer? I did with Tachi dialer and works good. This could save you a bit more storage and would leave a smaller footprint(depending on how much it gets compressed). I found the tool in Raph software and started compressing most of the exe files in my ROM. Saved a whopping 12MB :eek::eek: in total, and everything seems to load faster too.
[Touch Pro, Fuze ROM Development] hilaireg:
Had a look @ a SIM_MGR package in an official .NBH - few extra files are present, possible for uDK to provide?

Another fine Opera version that required fixing up. Ping me next time u see me on MSN - i'll pass you the package version for XCAB'ing if you like.

BTW; i've been reading the Opera website 9.7 "known issues" and forum - not positive IMO. I'm going to wait for the next beta before I entertain any post-Opera development debugging effort.

:)
[Touch Pro, Fuze ROM Development] hilaireg:
Linky please ... :o
[Touch Pro, Fuze ROM Development] jmckeejr:
http://xdaforums.com/showthread.php?t=493628&highlight=compression

Will not work on all exe's, but most. I put my new exe's near end of compilation and overwrite the old ones. This way if there's a problem can always revert. I just put em all in one package(at least frequently used ones)
[Touch Pro, Fuze ROM Development] Noonski:
What's different from this to The Old UPX-INg from the HyperCore Kitchen's?

It used to be that Load Times would actually take a bit longer.

Because i like to Do a lot of Icon work myself, my experience was that either i could not add new icons or resign the exe and dll files after compression.

And as i tend to go for speed VS space i try to use modulated Files when it comes to apps that are frequently used or constantly in memory to speed them up.

And if i remember right compressed files can't be turned into modules anymore.

But haven't used UPX compression for a year or so now. (Tested it and most UPX-ed files can't be turnd into modules anymore)

Did some more compression on some of the PNG file total OEM package size now 1,03 MB. See if it actually works and if there's any noticeable benefit.

But still it's a must have tool to add to the Kitchen.

And a nice Ressource editor would also be nice.

I know there's a lot of them out there, but i'm so used to the familiar ResHacker that i haven't been convinced to switch to something else.

I did like CFF ExplorerSuite as it integrated nicely into Windows Shell to and has some other interesting stuff over ResHacker.

All of these are free off course, and then there's IconFX which i can't live without in the live of Customizing everything that crosses my path.
[Touch Pro, Fuze ROM Development] alcadeias:
what happened to the .net cf 3.7? i thought it was going to be included in pack 3...

Regards