yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] aruppenthal:
As far as I know NRG is correct. The only working package I have seen for it was made by him. At least until proven otherwise I would give NRG credit :p
[Touch Pro, Fuze ROM Development] hilaireg:
Any possibility of getting you to post up your version? Would help ensure that all the files required are present and accounted for.

ok, ok ... that way I could get my grubby little paws on it and use it in my kitchen.

:)
[Touch Pro, Fuze ROM Development] jmckeejr:
Prolly right. I'll add that to the post ;) Thanks NRG. Fine work as usual.
[Touch Pro, Fuze ROM Development] hilaireg:
OEM Package Name : Windows Live + Messenger

OEM Author : aruppenthal, hilaireg

OEM Description : Includes Windows Live Hotmail, Messenger, Contacts and Spaces.

OEM Version : 10_06_0046_0800

OEM Date if aplicable : 25/05/2009

Application author : Microsoft

OEM Requirements : N/A

OEM Issues : N/A

Compatible Devices : N/A

OEM: Yes

Visual Kitchen: Yes

Weblink : http://www.4shared.com/dir/12314954/9a1ec6bc/sharing.html

Notes:

Creates Hotmail account in Messaging applet.

OEM Package Name : Windows Live + Messenger

OEM Author : aruppenthal, hilaireg

OEM Description : Includes Windows Live Hotmail, Messenger, Contacts and Spaces.

OEM Version : 10_06_0052_1300

OEM Date if aplicable : 25/05/2009

Application author : Microsoft

OEM Requirements : N/A

OEM Issues : N/A

Compatible Devices : N/A

OEM: Yes

Visual Kitchen: Yes

Weblink : http://www.4shared.com/dir/12314954/9a1ec6bc/sharing.html

Notes:

Creates Hotmail account in Messaging applet.
[Touch Pro, Fuze ROM Development] jmckeejr:
OEM Package Name: htcaddictsCleanRAM

OEM Author: jmckeejr

OEM Description: Used to free up extra RAM and cleanup cache. Said to help avoid resets

OEM Version 1.3.6

OEM Date if aplicable: fresh off the press 5/25/09

Application Author: htcaddicts

OEM Requirements (does the package need other packages?)

OEM Issues (are there know issues with the package?) check app.dat to place appropriately in your own folders.

Compatible Devices (will this work on other devices?) sure

Visual Kitchen: YES

Package Name: DebaRRON Opera Backup

OEM Author:jmckeejr

Description: This is a script to backup\restore opera passwords, cookies, etc. Added Backup all and restore all. I added a custom icon and shortcut points to \programs\tools\backup.

OEM Date: 5/24/09

Requirements: Having Opera is a plus :P

Visual Kitchen:YES

Notes: Will be working on a script to run at customization phase to restore automatically.
[Touch Pro, Fuze ROM Development] jmckeejr:
OEM Package Name: TF3D2 Tweaks

OEM Author: jmckeejr, At0mang, Danny_and_2

OEM Description: Scripts to enable/disable diferent features of Rhodium manila

OEM Version

OEM Date if aplicable:

Application Author: At0mang, Danny_and_2, with some mods by me

OEM Requirements (does the package need other packages?) Rhodium manila, menus, notifications, etc. MUST HAVE Mortscipt cooked in or installed.

OEM Issues (are there know issues with the package?)

Compatible Devices (will this work on other devices?)

Visual Kitchen?YES

NOTE: I altered these to giv a choice in reseting, also to choose whether to apply or cancel, etc.
[Touch Pro, Fuze ROM Development] annonymouse:
facebook app packaged

hi there,

thanks to whoever made this wonderful app

ive packaged it while i was messing around with da_g's awesome kitchen in the rapheal forums so as lots of people helped me i thought iwould share,

sadly as im so green i dont know the specs :(

really sorry for lack of info but i hope some one finds useful

OEM Package Name: Facebook

OEM Author:unknown

OEM Description: Facebook

OEM Version ?

OEM Date if aplicable: ?

Application Author: unknown

OEM Requirements (does the package need other packages?) a phone i guess it works on a rapheal but should on most i assume oh a facebook account data connection

OEM Issues (are there know issues with the package?) um none that i know off

Compatible Devices (will this work on other devices?)

Visual Kitchen? unsure

mousey
[Touch Pro, Fuze ROM Development] annonymouse:
link to packages

hi there, dont know if this is relevent or what but i found this link looking around the forum

hth sorry if not relevent

l
[Touch Pro, Fuze ROM Development] jtvgeo:
OEM Package Name : Google Maps /w Latitude 3.0

OEM Author : N/A

OEM Description : Google map and friend location/status message application.

OEM Version : 3_0_1_6

OEM Date if aplicable : 19/05/2009

Application author : Google

OEM Requirements : N/A

OEM Issues : N/A

Compatible Devices : N/A

OEM: Yes

Visual Kitchen: NO
[Touch Pro, Fuze ROM Development] B4PJS:
OEM Package Name: Keyboard Switcher

OEM Author: B4PJS

OEM Description: Mortscript to switch between fuze and touch pro layouts

OEM Version: 1.0

OEM Date if aplicable: 28/05/09

Application Author: B4PJS

OEM Requirements (does the package need other packages?): Mortscript Required

OEM Issues (are there know issues with the package?): Let me know ;)

Compatible Devices (will this work on other devices?): ONLY for FUZE/TouchPro

Visual Kitchen?: Yes
[Touch Pro, Fuze ROM Development] jmckeejr:
OEM Package Name: Skyfire_v1.0

OEM Author: jmckeejr

OEM Description: newest Skyfire internet browser

OEM Version

OEM Date if aplicable: 5/29

Application Author:

OEM Requirements (does the package need other packages?) X

OEM Issues (are there know issues with the package?) Not sure, but let me know. I have something causing ROM to stop building through NBHUtil, dont know if it is this or something else.

Compatible Devices (will this work on other devices?) All

Visual Kitchen? YES
[Touch Pro, Fuze ROM Development] 12aon:
OEM Package Name: Finger Keyboard v2.1

OEM Author: 12aon

OEM Description: FingerKeyboard v2.1 best WinMo typing experience! (set as default keyboard)

OEM Version: 1.1 (bugfix)

OEM Date if aplicable:

Application Author: Rozenthal, Giannis86 (skin) Sleuth (Sip change)

OEM Requirements (does the package need other packages?)

OEM Issues (are there know issues with the package?)

Compatible Devices (will this work on other devices?)

Visual Kitchen? YES

NOTE: I deleted all the unnecessary stuff, and paired it with sip change so its automatically the selected keyboard

Edit bugfixed the last version all should work now, 12
[Touch Pro, Fuze ROM Development] Mr. Makk:
i added your package in my kitchen. and cooked it. on bootup it says sipchanger not found. why so??
[Touch Pro, Fuze ROM Development] wingman_214:
12 is it also possible to include the black ice skin as default?

thanks 12aon, wingman
[Touch Pro, Fuze ROM Development] 12aon:
just replace the skin files in the oem with the skin you like, everything else will still be the same, 12
[Touch Pro, Fuze ROM Development] wingman_214:
finger keyboard issues

12, i was still having problems with your finger keyboard 1.1 oem having errors so i have made a few modifications to you package and it is now working correctly.

Note i am not the author of this package 12aon is. i have just fixed an issue i was having with this package and posted it here for everyone else.

OEM Package Name: Finger Keyboard v2.1

OEM Author: 12aon/wingman_214

OEM Description: FingerKeyboard v2.1 best WinMo typing experience! (set as default keyboard)

OEM Version: 1.3 (bugfix)

OEM Date if aplicable:

Application Author: Rozenthal, Giannis86 (skin) Sleuth (Sip change)

OEM Requirements (does the package need other packages?)

OEM Issues (are there know issues with the package?)

Compatible Devices (will this work on other devices?)

Visual Kitchen? YES

NOTE: I deleted all the unnecessary stuff, and paired it with sip change so its automatically the selected keyboard

EDIT: new version fixed the sipchange.exe popping up after every reset.

View attachment 12aon-wingman_214_FingerKeyboard.zip
[Touch Pro, Fuze ROM Development] B4PJS:
Opera 9.7b1

OEM Package Name: Opera 9.7b1

OEM Author: B4PJS

OEM Description: Latest Opera Mobile Browser

OEM Version: 1

OEM Date if aplicable: 09/06/2009

Application Author: Opera

OEM Requirements (does the package need other packages?): Nope

OEM Issues (are there know issues with the package?): Its a Beta!!

Compatible Devices (will this work on other devices?): Should do

Visual Kitchen? YES

Link as I cant seem to upload:

http://xda.b4pjs.co.uk/operabrowser_wm_97b1.zip

*********EDIT*********

Not fully working on my ROM atm, anyone else confirm?
[Touch Pro, Fuze ROM Development] kk0813:
Is there any way to identify which package from this thread goes to which folder in the visual kitchen? or does all the packages here goes to Raphael_External_Packages folder?

Thanks
[Touch Pro, Fuze ROM Development] konker:
Hi hilaireg,

Could you kindly explain how I can integrate either of the abovementioned packages into my running AT&T Fuze loaded with HTC Touch Pro stock ROM? I wanted to be able to map the PTT button & did everything according to the basic requirements of loading the files & registry but after I restarted the phone, it hung at the Touch PRO boot screen & repeated reboots did not resolve the problem. I had to hard reset the device but thankfully I performed a backup of the whole system already so that was easy to recover.

I appreciate you help in pointing me in the right direction.

Thanks in advanced!

Konker
[Touch Pro, Fuze ROM Development] hilaireg:
Hi konker,

Quick confirmation; the packages are intended for use in a kitchen.

Some work would be required to convert them to .CAB for installation to a device as the package(s) replace the keyboard.dll and that would require a .CAB with a certificate (driver signing).

The .RGU file contains the default entries that appear in the Buttons Applet. The .PROVXML is intended for chefs to use as an override to the default as opposed to editing the .RGU file.

The "Enhanced" version of the package also includes mapping for the Fuze physical keyboard. The "lite" package only provides mapping for the PTT Button.

HTH,
[Touch Pro, Fuze ROM Development] konker:
How do I build a cab installation file from these? Any advise?

Regarding how I incorporated the package files into my AT&T Fuze, here's what I did:

Saved the following to the \Windows directory:

Contacts.lnk

keypad.dll

long_PTT.lnk

PTTMod.exe

PTTMod_readme.txt

PTTMod_icons.dll

short_Calendar.lnk

short_CellularVideo.lnk

short_Contacts.lnk

short_InstantMessaging.lnk

short_Messaging.lnk

short_PTT.lnk

short_SMS.lnk

short_Web.lnk

8c1d0f1c-db1d-4f29-bb4c-45975b7e2bcd.dsm

8c1d0f1c-db1d-4f29-bb4c-45975b7e2bcd.rgu

Saved _SMS.lnk to the \Windows\AppButtons directory

Used CeRegEditor via ActiveSync to import the 8c1d0f1c-db1d-4f29-bb4c-45975b7e2bcd.rgu registry contents to the phone's registry.

Did not know what to do with these:

mxipcold_xcsmd_PTTMod.provxml

mxipupdate_xcsmd_PTTMod.provxml

option.xml

I was able to immediately see the PTT button reassignment & keyboard reassignment in the Settings | Personal | Buttons.

I even played with it & was able to see the PTT button reassignments take effect.

I proceeded to turn off the phone & booted the phone again.

That's when the phone hung at the Touch PRO boot screen.
[Touch Pro, Fuze ROM Development] hilaireg:
Unfortunately, I have other commitments on at the moment which are consuming a significant amount of my time. In the past, a few folks on the forum have graciously provided CAB's for OEM's; here's one link I found for one such member:

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

If you're after learning how to do it yourself, try searching these keywords on the forum:

Set 1: driver sign chainfire

Set 2: cab oem sztupy

Set 3: cab oem ervius

:)

The .PROVXML is intended for chefs to use as an override to the default as opposed to editing the .RGU file. The OPTION.XML is cooking related.

At first guess, I'd look for another application on the device that affect button assignments.

Cheers,
[Touch Pro, Fuze ROM Development] TehPenguin:
I confirm that its not working.

(WM 6.5 21731, via Da_G's Kitchen)

It displays the same symptoms as 9.5 did when I tried to convert the cabs into OEMs (ie splash screen, then nothing)
[Touch Pro, Fuze ROM Development] wingman_214:
OEM Package Name: hdWobble

OEM Author: elAlem/Wingman_214

OEM Description: iboobs for WM

OEM Version: .5.3446.26966

OEM Date if aplicable: 06/10/09

Application author:elAlem

OEM Requirements :NA

OEM Issues: NA

Compatible Devices : QVGA, WQVGA, VGA, WVGA

xda seems to be having issues with the upload

Click Here.
[Touch Pro, Fuze ROM Development] B4PJS:
Do you know who managed to fix this? It would be good to get a working OEM so that it can integrate properly with TF3D. Though I guess for now can install via cab in UC then run a mortscript to copy the operaL and the opera9-ml to the windows folder
[Touch Pro, Fuze ROM Development] hilaireg:
I've noticed that happens if the OPERA.INI is not in the correct encoding. Some of their files indicate the encoding required in a comment line at the top of the file.
[Touch Pro, Fuze ROM Development] B4PJS:
Cheers mate :D just found opera.ini and userstyle.ini were incorrctly coded, watch this space for a 9.7 that works with tf3d (just a couple of bugs to sort left :)

EDIT::

Not even converting to UTF-8 helps :( here is a cab that saves to \windows\ to work with the launching from tf3d (havent managed to get the bookmarks working though)

http://xda.b4pjs.co.uk/opera9.7.zip
[Touch Pro, Fuze ROM Development] konker:
hilaireg,

I went to the thread you provided & ather90 graciously agreed to help me put together the cab file (http://xdaforums.com/showpost.php?p=3943081&postcount=50).

However, I think the certificate part is missing.

When I install the cabinet file, the following error message appears:

"Installation was unsuccessful. The program or setting cannot be installed because it is not digitally signed with a trusted certificate."

How to include the certificate (driver signing) that you mentioned in the cabinet installer?

I'm still waiting on ather90 to provide an update.

Thanks!

Konker
[Touch Pro, Fuze ROM Development] Noonski:
Just A Quicky before i forget.

Rhodium ConnectionManager VGA Skin.

OEM Package Name: Rhodium Connection Setup Noonski's SPeCial VGA Edition

OEM Author: Noonski

OEM Description:

More Eycandy When Swishing SimmCard or Roaming

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

OEM Version: 2_7_37392_4

OEM Date if aplicable: 06/15/09

Application author: HTC

OEM Requirements :NA

OEM Issues: Rebooting is for Sissies ;)

Compatible Devices : VGA

http://rapidshare.com/files/244579415/PACKAGE_Noonski_ConnectionSetup_0000_2_7_37392_4.zip
[Touch Pro, Fuze ROM Development] hilaireg:
Hi Konker,

Is this an official ROM or a compiled (cooked) rom?

If it's a cooked ROM, do you know if the rom is NoCERT patched? Also, did you verify the Policies key in the registry to ensure that the security policies are sufficiently relaxed?

In the interim, here's a link to Chainfire's Driver Signing tool:

http://xdaforums.com/showthread.php?t=495145
[Touch Pro, Fuze ROM Development] konker:
hilaireg,

I'm using the Stock HTC Touch Pro ROM (RUU_Raphael_hTC_Asia_WWE_5.07.707.2_Radio_Signed_Raphael_52.58.25.30_1.11.25.01_Ship.exe) & I've already turned off security warning via Advanced Config 3.3.

Which policy in the registry are you referring to? I can take a look at it if you can specify the exact registry value.

Thanks for the tool...I'll pass that on to ather90 to take a look.

Best regards!

Konker
[Touch Pro, Fuze ROM Development] hilaireg:
Ok ... so stock rom.

Here's a link to look at;

http://xdaforums.com/showpost.php?p=3944378&postcount=422

You'll need to read down a few posts from that point.

HTH,
[Touch Pro, Fuze ROM Development] jmckeejr:
OEM Package Name: htcaddicts CleanRAM

OEM Author: jmckeejr

OEM Description: newest release

OEM Version 1.5.5

OEM Date if aplicable: 6/17/09

Application Author: htcaddicts

OEM Requirements (does the package need other packages?) nope

OEM Issues (are there know issues with the package?) got me

Compatible Devices (will this work on other devices?) any device

Visual Kitchen? Yes, EXT package

OEM Package Name: streams T-PDA

OEM Author: jmckeejr

OEM Description: another widget for 6.5 to stream video,music, etc.

OEM Version 1.4

OEM Date if aplicable: 6/17/09

Application Author: Themuzz

OEM Requirements (does the package need other packages?) Include widgets from SYS in build

OEM Issues (are there know issues with the package?) check to make sure it does not conflict with other widgets. ie: if you have 4 widgets you would need to change the info in this package to install to program files\widgets\user\5 instead of 4. There are also references in app.reg that would need changed.

Compatible Devices (will this work on other devices?) VGA only

Visual Kitchen? yes, EXT package

OEM Package Name: cinemo_setup

OEM Author: jmckeejr

OEM Description: view your local movie times right from your device.

OEM Version

OEM Date if aplicable: 6/17/09

Application Author:

OEM Requirements (does the package need other packages?) nope

OEM Issues (are there know issues with the package?) got me

Compatible Devices (will this work on other devices?) any device

Visual Kitchen? Yes, EXT package
[Touch Pro, Fuze ROM Development] hilaireg:
I'm beginning to dislike Opera ... well, at least the development people over there. The problem with Opera displaying the Splash Screen and then "dying" is definitely the OPERA.INI file.

4 hours of d!ck!ng around with this app:

Tried ANSI,

UTF-8

(

with

/without

sig

), UTF-16, Unicode, Unicode BOM, Unicode BE BOM ... no go. :(

Tried removing the attribs (-S - R -H) ... no go. :(

Placed the entire application back in "\windows\opera9" with my old B16277 OPERA.INI ... it works :confused:

Tried modifying the file to add the entries for B16643 ... no go :mad:

Put the B16277 OPERA.INI back in .. it works :confused:

Used ABOUT:CONFIG to enter the entries via Opera and copy the updated OPERA.INI back to my PC ... hard reset, try it again with the updated OPERA.INI ... it works :confused:

Performed a HEX compare on the "good" and "bad" ... the same :confused:

Hell if I know what they've done; I'm convinced it's something with the encoding - I would have expected a Hex edit to reveal that. At the moment, unless the changes are made via the browser it just "ain't" gonna work.

In summary; if a chef is really insistent on an OEM: install Opera 9.5/9.7 to the \windows\opera9 folder, make sure it works, add the extra entries to OPERA.INI via ABOUT:CONFIG, copy the INI to your PC, and pack the b@stard up.

Alternatively - use the .CAB; cr@ppy browser ... yes, i'm annoyed
[Touch Pro, Fuze ROM Development] jmckeejr:
OEM Package Name: Opera build 16070

OEM Author: jmckeejr

OEM Description: UPX compressed version, realexit, mort install saves about 7MB total :eek:

OEM Version 16070.1

OEM Date if aplicable:

Application Author: Opera Mobile

OEM Requirements (does the package need other packages?) Mortscript is required to be cooked in

OEM Issues (are there know issues with the package?)

Compatible Devices (will this work on other devices?)

Visual Kitchen? Yes(add2config.txt)

http://www.4shared.com/file/114626252/e2743e78/Opera_16070.html

OEM Package Name: wifi monster(compressed)

OEM Author: jmckeejr

OEM Description: mort install using add2config

OEM Version latest as of 6-27-09

OEM Date if aplicable: 6-11-09, updated 6-27-09

Application Author:

OEM Requirements (does the package need other packages?) mortscript

OEM Issues (are there know issues with the package?)

Compatible Devices (will this work on other devices?)

Visual Kitchen? yes, uses add2config.txt

http://www.4shared.com/file/114626470/3ac14164/WiFi_Monster_Mortscript_Required.html

OEM Package Name: Bing 2009

OEM Author: jmckeejr

OEM Description: new version of Livesearch(now Bing mobile)

OEM Version

OEM Date if aplicable:

Application Author: M$

OEM Requirements (does the package need other packages?)

OEM Issues (are there know issues with the package?)

Compatible Devices (will this work on other devices?)

Visual Kitchen? Yes
[Touch Pro, Fuze ROM Development] jmckeejr:
OEM Package Name: Opera 16643

OEM Author: jmckeejr

OEM Description: Compressed .exe's, mort install, same skin as 16070

OEM Version 16643.1

OEM Date if aplicable:

Application Author: Opera

OEM Requirements (does the package need other packages?) Mortscript

OEM Issues (are there know issues with the package?)

Compatible Devices (will this work on other devices?)

Visual Kitchen? YES

http://www.4shared.com/file/114637807/6722f5b1/Opera_16643_Mortscript_REQUIRED.html
[Touch Pro, Fuze ROM Development] konker:
hilareg,

I have not been able to use the cab package that ather90 put together.

However, I managed to manually install the basic PTT package without the keypad.dll.

It worked flawlessly.

I think the basic package does not require the modified keypad.dll since it's intended for the re-mappable keyboard instead of the PTT button.

FYI & those who want to still be able to use the PTT buttons with non-AT&T Fuze ROM.

Konker
[Touch Pro, Fuze ROM Development] hilaireg:
The Basic PTT Mod package provides limited assignement to the PTT button. If you try the various FN button on the Fuze keyboard however, you're likely to get no response or incorrect behaviour.

The Enhanced PTT Mod package provides full customization as the keypad.dll file had been modified to ensure proper function of the Fuze keyboard FN keys.

HTH,
[Touch Pro, Fuze ROM Development] konker:
hilaireg,

Thanks for the clarification. I'm well aware of that...and posted that information in my 1st post to this thread. But since my Fuze cannot start after applying the manual installation, I'd just have to live with this basic PTT function for now until a solution is found to resolve the certificate error.

Was wondering what would happen if I manually applied everything in the enhanced package without changing out the keypad.dll & just stick to the original one in the HTC ROM...would it work?

Konker
[Touch Pro, Fuze ROM Development] hilaireg:
Unfortunately not, the keypad.dll file is the file that is most required from the entire package as it has been altered to accomodate the functionality. This is one of the reasons the OEM Repository was created - some packages are just too unpredictable in CAB form. :(

IMHO, you may have reached a point where you may want to consider compiling your own ROM with all of the components you require. Have a look at the 21051 WinMO 6.1 kitchen that is stickied in the Raphael ROM Development thread. It contains everything you need to get make a custom ROM for yourself.

All you need to do is ensure that HardSPL is applied to your device and optionally, you may wish to SIM unlock if you haven't already. Once these steps are done, make a list of all of the applications you currently use/have on your device ... i've included text files that list all of the applications in the kitchen.

HTH,
[Touch Pro, Fuze ROM Development] fb401:
Here are a few I use:

# OEM Package Name: Facebook

# OEM Author: fb401

# OEM Description: Official M$ Facebook app

# OEM Version: 1.007p

# OEM Date if aplicable:

# Application Author: M$

# OEM Requirements: n/a

# OEM Issues: n/a

# Compatible Devices: All

Attached below

# OEM Package Name: Tachi Phone Canvas

# OEM Author: fb401

# OEM Description: Official M$ Facebook app

# OEM Version: n/a

# OEM Date if aplicable:

# Application Author: MikeKnoop

# OEM Requirements: don't know

# OEM Issues: no landscape, slider can be flaky. for more info see http://xdaforums.com/showthread.php?t=499076

# Compatible Devices: Diamond and Touch Pro

Attached: http://www.4shared.com/file/114891364/f1f5ca61/Tachi_Phone_Canvas_Knop_v2d.html