yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] DHSoccer4:
haha thanks man, ur too qucik for me but that did the trick now only when i type C and click enter it says "my ROM is available in the root kitchen folder as RUU_shipped.nbh" press a key to continue and it brings me back to the beginning screen and it keeps cycling me in a circle. I might have to do some reading apparently
[Touch Pro, Fuze ROM Development] r.camies:
@hilaireg:

Thanks. It now enables the headset and gives me the dialer. still no cyberon Voice Speed Dial though... But I'm rebuilding the ROM using the posted 21042 eras2r kitchen to see how it turns out then.

Did you actually build in MSVC as well and install the cyberon apps as cabs later on, or built them in in the kitchen?
[Touch Pro, Fuze ROM Development] hilaireg:
Built three ROMs in the kitchen: R1) MSVC, R2) CVSD, and R3) CVC cooked in ... flashed each one to the device for the test.

Copied the .DLL and modded the .REG onto the device post-flash.

I don't believe CVSD or CVC are part of the kitchen; you can get them from the Raphael OEM Repository in the Raphael ROM Development forum (one of the top links).

Cheers,
[Touch Pro, Fuze ROM Development] LcBoi:
Error, any ideas?

Hey, I'm sorry for bothering you guys but do you think you can take a minute or two and help me out?

When ever I try to cook a 6.5 rom with touchflo using the latest kitchen from this thread I always get the following error:

Does anyone have any ideas about this?
[Touch Pro, Fuze ROM Development] r.camies:
Ok. Just rebuilt with CVC, which worked flawlesly thanks to the dll. currently rebuilding using CVSD.

actualy, CSVD IS in the kitchen, but deselected by default (MSVC is selected by default).

Also, the replaced dll is actualy 1 kb larger than the one we use now (which is the one from 5.05). The newer one is the same in the kitchens for 81038, 81040 and 81042, but I don't know why it is larger/what has changed internally.

Edit: Rebuild with CSVD now also works. Going for rebuild of my customized kitchen
[Touch Pro, Fuze ROM Development] hilaireg:
I'm not sure you'll get much success with TouchFLO and many of the components in this Kitchen with WinMO 6.5. Many of the libraries are different; you may want to post this question in a WinMO 6.5 Kitchen.

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
Would appreciate it if you could put the BT through its paces so as to ensure that we don't require other .DLL's.

Are you saying that the .DLL's found in the 81038, 81040 and 81042 (ROM's or Kitchen?) are identical to the .DLL in the .ZIP I supplied from the 5.05.405.1 Official HTC ROM?

Cheers,
[Touch Pro, Fuze ROM Development] Da_G:
The particular error you've pasted shows that you've gone beyond the maximum size of the ROM though, remove some components or trim some images, sounds, etc. :)
[Touch Pro, Fuze ROM Development] hilaireg:
I knew you were "hiding" in the sidelines :) So TouchFLO WILL work with WinMO 6.5 ?
[Touch Pro, Fuze ROM Development] Da_G:
TouchFLO works, but it doesn't cooperate well, if you get it running it takes over all of WM6.5's native touch scrolling.. you can sort-of work around it by touch-and-hold-then-gesture'ing... but it's awkward! I suppose you can call that 'works' :)
[Touch Pro, Fuze ROM Development] r.camies:
You need to use newer imgfs*.exe tools (I found those in a rar file labelled visualkitchen_v_4_0_only_exe_+_Tools_folder.rar, but I cann't remember where I got it from. At least it's from somewhere of the xda-developers foorums.....)

they actually allow you to create ROM images larger than 128MB (which is the size limit you're running into)
[Touch Pro, Fuze ROM Development] Captain_Throwback:
Is this it?

(because I'm running into that problem in the 6.5 kitchen)
[Touch Pro, Fuze ROM Development] r.camies:
@hilaireg:

I'm sorry.. I meant the 21042 one when refering to the newer one. The one put in the zipfile (the one from ROM 5.05) is NOT the same as the one used in the newer eras2r kitchens.

They are actually quite different when compared with windiff. It looks like there are some internal changes as to which registrykeys are checked, etc. in the newer one.

Currently building my changed kitchen, in which I've replaced the 5.08 file with the 5.05 one (not renamed. replaced in the kitchen itself, which worked properly for the previous two tests).

I'll do some additional testing with other bluetooth functionality (ftp, activesync/Vista devicecenter, as an internetgateway to my laptop, bluetooth printing, etc.) and report it back (might take me some time tough.. my wife wants me to get to bed... while you're just finishing your morning, so don't expect any testresults within the next couple of hours...)
[Touch Pro, Fuze ROM Development] r.camies:
Yes, that's the one, altough I was using the 4.0 version of this file. I only took the IMGFS files and copied them over the ones of eras2r's kitchen. they are actually different in filesize, but had the same version number (2.1c etc).

hope you'll get them working for your coocking needs, and maybe eras2r/hilaireg/DaG can look into the vrsions they currently supply in their kitchens and wheter they need replacement as far as they are concerned.

Edit: Just built a new ROM sized 134 MB with the IMGFS tools from the 4.0 package, so definitly it's possible using these newer versions.
[Touch Pro, Fuze ROM Development] hilaireg:
@r.camies:

Just chatting with Da_G/ERAS2R about refreshing the Kitchen ... can you .ZIP or give me the extact filenames I need to pull down? I'll do a quick confirmation test on my end and make sure they are included in the "refreshed" kitchen.

Cheers,

I usually end up sleeping on the couch if I crash too late ... dog takes my spot ;)
[Touch Pro, Fuze ROM Development] LcBoi:
Thanks for all of the quick responses, I actually meant to post it in Da+G's 6.5 kitchen, I'll try the newer files. I'm just building personal rom's right now and thought it would be nice to experiment with 6.5.
[Touch Pro, Fuze ROM Development] r.camies:
Hilaireg, I've zipped and attached them. Some are actually the same as in your kitchen, some are different (especially the newer ones), but the included readme is not updates, so I don't know what's actually different besides the filesize and the end-result with ROMS larger than 128 MB.

You now understand why we don't have a dog... I can at least still have my wife keep me warm at night... ;)
[Touch Pro, Fuze ROM Development] r.camies:
@LcBoi:

Please let us know your results with the newer IMGFS files
[Touch Pro, Fuze ROM Development] LcBoi:
@ r.camies

It worked fine, just got to finish a new boot splash and use the htc rom tool to put it all together. :)
[Touch Pro, Fuze ROM Development] oaa8:
If your using vista, Disable UAC and restart
[Touch Pro, Fuze ROM Development] crazyC:
Looking forward to you kitchen refresh - I think I might finally jump up from 21032 for this one.

Is it me or after a little flurry of new builds have things quietened down? Is there likley to be much more in the way of new 6.1 builds or is the focus firmly on 6.5 now?
[Touch Pro, Fuze ROM Development] hilaireg:
[REF] 21042 SYS and XIP from Topaz WWE to Raphael

@All,

ERAS2R posted a timebomb-patched 21042 Rhodium port of the XIP & SYS a few post-pages back that I've been using in the Kitchen - using the 6.5 DDI version.

Any value in looking at the XIP & SYS from this ROM?

http://xdaforums.com/showthread.php?p=3594946#post3594946

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
Can you try Windows Media Player video playback; specifically the HTC Welcome video or the Kids At The Party video? Media Player hard crashes about 3 seconds into the video on 21042. Works fine on the "stock" HTC ROM.

Noticed the same. I'm sticking to WinMO 6.1 for now until a "Shipped" version is released. That said, quickly took Da_G's TEST2 for a road test ... can see the appeal.
[Touch Pro, Fuze ROM Development] crazyC:
I will have a look, but I think I may have ripped those out of the kitchen in a tidying up spree.

Indeed, if you can uplaod the file I will check, but I am sure I have played around with some vid files on WMP and it was fine. I read an interesting thread about WMP natively supporting the QTV hardware, but coreplayer is also fine for me.

TBH the only issue I have really had with my setup is the problem with the messaging app becoming unresponsive. I went and installed via cab all xboxmods stuff and so far have had no such problem for a few days (touch wood).

If this continues I will recook over Easter and see if I cannot fix my Rhodium packages etc, as well as add a few more things I wanted in.

I have spent a bit of time modifying some of the dll's etc in my current setup and am loathe to have to change everything over to a new build without any known advantages.

6.5 looks good but I rely on Phone Alarm and am not sure if it will work, Bruce won't support it until it gets a little less beta.
[Touch Pro, Fuze ROM Development] hilaireg:
I've been keeping a change log of what i've changed since the beginning. I'd be more than happy to pass it along to you once the refresh has been uploaded.

Cheers,
[Touch Pro, Fuze ROM Development] crazyC:
Thanks, but the problem is that I have been lazy and haven't kept a change log!

I will have a think and try and create a list of what I need to bring with me so to speak.
[Touch Pro, Fuze ROM Development] hilaireg:
Bug: Media Player (AT&T)

FYI:

Looks like the Media Player decoders on the AT&T test build (MediaOS packages) are buggy ... had to roll-back to the Official HTC version to prevent hard device crashes when playing back media such as video.

Cheers,
[Touch Pro, Fuze ROM Development] NotATreoFan:
I'm using the MediaOS packages provided with the 21042 kitchen. If those are the bugged ones, which ROM version did you grab good ones from?
[Touch Pro, Fuze ROM Development] hilaireg:
Media Player (5.05.405.1)

I ended up rolling back to the Official HTC 5.05.405.1 WWE ROM version ... should be the same ones in the first post of this thread - Da_G's ROM Kitchen 6.21.

Here's a list of what I rolled back:

.\SYS

MediaOS

MediaOS_dpi_192_resh_480_resv_640

MediaOS_Lang_0409

MediaOSFiles

.\OEM\OEMDrivers

QTV.dll

qtv_mp4_decoder.dll

Symptoms included Hard Crash 2-3 seconds of playback of Album_Sample_04.3gp and/or ToucPro.3gp videos when launched directly from Media Player - worked fine via TF3D player.

HTH,
[Touch Pro, Fuze ROM Development] NotATreoFan:
Thanks! I've got the 5.07 Asia files on my HDD, so I'm going to try those.
[Touch Pro, Fuze ROM Development] Da_G:
Hi guys, i've just done some testing re: In Call Recording and it's ability to record both sides of the conversation, I posted about it in the "Raphael" forum, but since this kitchen includes the ICR and PhoneCanvas package I felt it worthy to post here:

Attached is the latest blackstone wavedev.dll, with ICR support. It's the key component to being able to hear both sides of the conversation in a recorded call... drop it in \oem\oemdrivers and cook away!

It may have some side effects (previously when we used a blackstone wavedev.dll it caused mp3 playlists to crash)
[Touch Pro, Fuze ROM Development] teixeirabmb:
Thanks DaG you're da man. I will cook this on my next release for sure.
[Touch Pro, Fuze ROM Development] hilaireg:
I attached the ones from the Official ROM to my previous post in case you need them; same ones I am using now.

Cheers,
[Touch Pro, Fuze ROM Development] NotATreoFan:
Thanks again. I'll be sure to try them if the 5.07 files suffer from the same bug.
[Touch Pro, Fuze ROM Development] xboomer55:
Been following your posts on this issue. I checked and had a WMP hard crash first time playing TouchPro.3gp but can't reproduce it again. Will probably roll back too.

Yes. It seems that HTC did quietly include h/w support for .mp4 video, including h.264. Hands down, HTC Album and WMP are the two most powerful video playback apps for this format. Performance comparisons with other media playback apps is probably not worth the effort since they don't have access to the h/w. Album and WMP are the only apps that can play higher res (640x4xx) .mp4 (h.264) video podcasts that are increasingly common and targeted at iPod/iPhone, Zune v2 etc.
[Touch Pro, Fuze ROM Development] NotATreoFan:
The files from 5.07 WWE are working great, but I'm having trouble with the new Rhodium Comm Manager. None of the new Bluetooth of Wi-Fi menus are showing up. :confused:

I tried cooking in the package posted here on XDA, but then the whole Comm Manager wouldn't work. I was able to get the main screen to function by installing the CAB posted here.
[Touch Pro, Fuze ROM Development] hilaireg:
@NotATreoFan:

I've cooked the two Rhodium packages (incl. in 21042) and the Comm Manager in Settings and the Communications panel in TF3D seem to behave as expected.

What's version is Media Player reporting in the About box?

Appreciate the link to the new panels however; was looking for those "enhanced" panels ... I'll pull them down and give them a try - much nicer looking than the AT&T world globe.

Cheers,
[Touch Pro, Fuze ROM Development] NotATreoFan:
Windows Media Player 10 Mobile for Pocket PC - Version 10.3 Build 20764

RE: Comm Manager - The Comm Manager itself works, but the new settings pages for Bluetooth and Wi-Fi aren't working.
[Touch Pro, Fuze ROM Development] hilaireg:
Looks like the core player components are the same ...

5.05.405.1

Windows Media Player 10 Mobile for Pocket PC - Version 10.3 Build 20764

Yup, you're absolutely right ... hadn't realized they were missing.

:)
[Touch Pro, Fuze ROM Development] NotATreoFan:
I wonder if we're missing some files that the new menus depend upon. Da_G, anyone?
[Touch Pro, Fuze ROM Development] Captain_Throwback:
The files are there, but the registry entries appear to have disappeared when I made a package out of the cab I found here on xda. But I know what those reg entries are:

HKLM\\Software\HTC\CommManager\1

if the only key there is "Default"="Phone",

then add key: "Execute"="CMPhone.exe" (that file should exist under \Windows - its part of the new Comm Manager cab)

HKLM\\Software\HTC\CommManager\2

if the only key there is "Default"="Bluetooth",

then add key: "Execute"="CMBluetooth.exe"

HKLM\\Software\HTC\CommManager\3

if the only key there is "Default"="WLAN",

then add key: "Execute"="WiFiNetwork.exe"

Those keys should get you the Phone Settings, Bluetooth, and WiFi menus from the Topaz (at least they're working for me after adding them).
[Touch Pro, Fuze ROM Development] xboomer55:
I just did a hard reset. TouchPro.3gp crashes WMP on first attempt. All good after a soft reset. I am using MediaOS etc. from 21042. Don't know what it means. Just passing it on...
[Touch Pro, Fuze ROM Development] NotATreoFan:
Those entries are all there... :confused:

-On Third Thought-

I realized that tapping on the Bluetooth section, away from the slider, brings up the new menu. But tapping Settings -> Bluetooth (or Wi-Fi) still brings up the old menus.

So it is working, just not as I expected. :)
[Touch Pro, Fuze ROM Development] Captain_Throwback:
As far as I know, that is how its supposed to work. You can actually remove the "Settings" soft key from the Comm Manager that links to the old menus by changing the key HKLM\\Software\HTC\CommManager\EmptyMenuBar from 0 to 1. That's how mine is set up.
[Touch Pro, Fuze ROM Development] hilaireg:
Was seeing the same thing happen; hard reset = hard crash on playback, soft reset = 50/50, power off/on = 50/50.

It's been stable since I rolled the packages back to the stock version (the ones from a few posts back).

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
Hi Da_G,

Does this mean that the version currently in the kitchen does not support ICR? Or is this a newer version of the file?

*EDIT* Figured it out ... need the new .DLL to enable ICR - the one currently in the kitchen doesn't support ICR.

Cheers,
[Touch Pro, Fuze ROM Development] crazyC:
I have tested ICR on my 21032 build and it records both sides (without adding anything). Dunno about mp3 playlists - haven't tried them as don't use them.

Will try and have a look.
[Touch Pro, Fuze ROM Development] hilaireg:
Interesting; I couldn't get it to work on 21402 without adding the new 'wavedev.dll' :confused:
[Touch Pro, Fuze ROM Development] r.camies:
@Hilaireg:

Hi, Just a quick note. The issue with the headset and bluetooth we discussed a few pages back is in deed solved using the file you supplied from 5.05 stock.

I also can confirm that ICR works out of the 21042 kitchen without replacing the 'wavedev.dll' file. no problems recording both sides of the conversation.
[Touch Pro, Fuze ROM Development] hilaireg:
Good to know ...

This is going to sound N00B'ish; would you mind giving me the step-by-step so that I can replicate? With the new 'wavedev.dll', I see a pink square box in the upper right-corner when I choose record from the menu - not seeing that with the "stock" (21042) version.

:confused:

On a separate note, I found a way to allow selection of the "stock" or "blackstone" version during cooking so both files will be available. I've also set the kitchen up to do the same for the Bluetooth and Rilphone.

If all goes well, I'm hoping to hand off the kitchen to Da_G so that he can post it up to the first thread ... afer he's taken it for a road test.

;)
[Touch Pro, Fuze ROM Development] Da_G:
pip pip, cheerio!

i wasn't able to get both sides of the caller recording working without this new wavedev.dll either, (in 6.5, but i know from past trials in 6.1 too)

maybe there's a hardware revision difference or somesuch?

when you guys test that, have you tested both handset, speaker, bluetooth to ensure it really is recording other side? not questioning your statements just want to be sure :)
[Touch Pro, Fuze ROM Development] hilaireg:
Good point ... I only tested Headset. I'll have to test Bluetooth and Speakerphone.

Cheers,
[Touch Pro, Fuze ROM Development] crazyC:
I just made a call, recorded it (yep the pink square) and then played it back and heard both sides of the conversation.

Did not try bluetooth or anything else.

Wife and kids are limiting my time for stuff like this at the moment.
[Touch Pro, Fuze ROM Development] r.camies:
Tested it using bluetooth, and got the pink square. Recording using bluetooth and playing back let me hear both sides of the conversation.

FYI: I'm running the kitchen (5.08, 21042 base build) on a T-mobile Vario IV (Which is a T-mobile rebranded touchpro, known as Raphael 300). Using radio 1.11.25.01, default rilphone.dll, default wavedev.dll from kitchen, only using OEMAGW.dll from 5.05 build due to CVSD not working with newer version.
[Touch Pro, Fuze ROM Development] crazyC:
ICR

I am using the 21032 kitchen posted by eras2r - no changes relevent to this issue (AFAIK)apart from now using the latest 1.13 blackstone radio, was using the 1.12 latest blackstone radio and it worked then as well.
[Touch Pro, Fuze ROM Development] xboomer55:
I have included ICR since using your kitchen starting at 6.22 (DagYo). My only success with ICR has been with this kitchen. I am now using a basically stock 05.08 21042 kitchen, including updates from eras2r and hilaireg. Am using 05.08 DDI version of os.nb.payload. I did not cook in either CSVD or MSVC. I use the supplied packages with the following exceptions that I've kept from earlier kitchens or added in:

05.05 Manila

05.05 Comm Manager

1% green battery package (modified phcanOverbmp.dll and regedits).

Current rom image was cooked/flashed on 4/05. I hard reset yesterday.

ICR appears to work. Pink recording icon, shrill wavefiles at start/end etc.

Handset:

The only issue is that the fuze microphone is not muted from ICR when muting the phone. Fuze audio is muted towards the other (called) phone as expected, but ICR still records near end sounds from the fuze micrphone very clearly.

I have also taped the fuze handset speaker to eliminate the possibility that audio is being picked up from the fuze speaker and then captured from the ICR open mike (even when the fuze is muted). Audio playback of recorded calls suggests that the audio was recorded internally and not picked up over the fuze handset speaker/microphone). Echo effects when the far end phone is in close proximity to the fuze confirms this. ICR is recording the far end internally and also picking up the same audio from the fuze microphone (even when muted) when the called handset is in close proximity, causing echo effects.

Bluetooth (Motorola S705):

Recording works as expected. Muting the fuze audio via the bluetooth headset also mutes fuze audio from ICR.

Third party apps:

Not much success with Resco Audio Recorder. It does record (.mp3) and will also auto-record all calls but there are intermittent quality issues.

ICR app:

There is some difficulty changing the audio format from AMR to Wave. The selection defaults back to AMR but eventually sticks. In my experience, Wave produces better quality but the recording file size will be larger.

My fuze is not a daily phone, and I have not done much testing, so I can't comment on how stable ICR is. It appears to be working at the moment.

I will try the new .dll next time I have a chance to update the kitchen and re-cook.

By the way...I lazily and stupidly copied the new .dll to the handset yesterday. This killed all audio. Writing the original .dll back to the handset did not fix. This was the reason for the hard reset yesterday.

LOL...like I said...it is not a daily use phone...
[Touch Pro, Fuze ROM Development] hilaireg:
FYI: Long End Key & Keypad.dll (AT&T)

Interesting discovery during some testing I've been doing.

The Long End Key application ceases to function when installing the KEYPAD.DLL file from the 2Fuze package; works fine using the KEYPAD.DLL from the 1TouchPro package.

I only copied the KEYPAD.DLL, did not bother with the rest of the files, is it as a result of the .DLL different calls to ATT_LINK.DLL for PTTMOD.EXE :confused:

If not, I'm beginning to question the value of the 2Fuze package ... yes, it will still be in the upcoming refresh/rollup.

Cheers,
[Touch Pro, Fuze ROM Development] Da_G:
keypad.dll in /2fuze is modified for and depends on pttmod, thats why its in the same package :) long end function will not work without pttmod (use stock att 19971 build keypad.dll if you don't want pttmod)
[Touch Pro, Fuze ROM Development] hilaireg:
Cheers, suspected it might be the case.

:)
[Touch Pro, Fuze ROM Development] NotATreoFan:
Anybody else notice MSVC running a little goofy on 21042?

It seems to be a crapshoot with regards to announcing incoming calls. It will either announce the person by their name in Contacts, or just say the number. The person's name is displayed, just not spoken. :confused:
[Touch Pro, Fuze ROM Development] hilaireg:
@NotATreoFan:

Noticed the same; I switched to using Cyberon Voice Command (not SpeedDial) as I find MSVC didn't provide sufficient time to issue commands while I was driving ... and was getting tired of repeating myself.

I recall a number of posts back in this thread that eras2r had to make some changes to the AudioPara3.csv file in order to get MSVC working. Here's the files from the previous posts in this thread a-la-OEM in case you want to have a look at them. Remove the one from the SYS folder and add these to PACKAGES ... u'r a seasoned chef so i'm sure u know what to do ;)

@all,

On a separate note, I'd like to add GoogleMaps+Latitude and Opera95 to the PACKAGES folder. Before I go ahead and make the OEM's of the ones I currently have, GoogleMaps_Latitude_3.0.1.4.cab and WM6_PPC_HTC_Opera9-build_15954_WWE_VGA.CAB, , anyone happen to know where I can find recent OEM's for these?

Cheers,
[Touch Pro, Fuze ROM Development] NotATreoFan:
Thanks for the file. I'll take a peak at it later tonight.

RE: Separate Note - Opera does not work when cooked into the ROM as a package. It has to be installed as a CAB. [NOTE: If this has changed, I would love to be corrected] I believe that Google Maps suffers the same fate. :(
[Touch Pro, Fuze ROM Development] aruppenthal:
They will work but the packages must be made by hand. The package creator messes up the rgu files.