yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] skyfox99:
YEAH, thanks to NATF, DA_G, and Arrup I have finally been able to create a working package that is semi useful (I am just learning).

This is the updated TouchResponse in OEM_Package form for all the chefs and wannab chefs such as myself

This update allows more customizable settings

More info can be found here

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

This is verified working for my Fuze
[Touch Pro, Fuze ROM Development] skyfox99:
OK. Last three things I need to get my PERFECT ROM together for me.

GPS LAG Gone (no setting I choose fixes it, I have given up on it for now)

Cellular Video/ mobit tv Will Not work. When I use Opera, I get the website does not exist. Using IE6, it navigate to the media net home no probs, just doesn't show any CV link. And when I navigate to cingularvideo.cingular.com it displays a weird huge length of xml coding... I have the user agent set to HTC-P4600 as I should, and have tried everything from the opera.ini fix to other tweaks. I am clueless here, don't even know where to start,

and the damn t9. All I want is the black box gone and the auto suggestion from the settings to work. I don't know if that is the t9 thing, but I am used to my Tilt and when I type with that, words pop up in a list as i am typing and I can than click on what I want... just want that futionality back
[Touch Pro, Fuze ROM Development] aruppenthal:
Unfortunately thats not the answer for my rom :( ive been trying to fix it for over a week. Back to the oemdrivers folder for me :p

@Da_G

Ill start packing up OEMs. Ill start posting them to a wiki page as soon as I get some ime. I gotta work straight through till next weekend. 14 day stretch this time :(
[Touch Pro, Fuze ROM Development] Da_G:
re: cv you need the opera.ini with the at&t proxy in it (open it in notepad and check for this)

[Proxy]
Use Proxy On Local Names Check=1
HTTP Server=wireless.cingular.com
HTTPS server=wireless.cingular.com
Use HTTP=1
Use HTTPS=1
Enable HTTP 1.1 for proxy=1

Then you need the streamingplayer .exe from the thread in this forum that talks about working CV etc. on cooked roms (for some reason the newer one in my kitchen doesn't work, i think it can be enabled with a reg key though)

It sounds like you want xt9 gone completely. Why not just not cook it in? The default IME (CompIME) has that list of words that pop up as you're typing..
[Touch Pro, Fuze ROM Development] aruppenthal:
Shep211 posted a fix for cellular videos. Ill throw the link in this post in the morning if you dont find it.

Disable xt9 will get rid of the bar and revert to the old style. However it sometimes breaks the compact qwerty. Theres a cab for the disable xt9 floating around.

Or what da_G said since hes faster than me :p
[Touch Pro, Fuze ROM Development] skyfox99:
I thought suggestion was apart of t9, am trying not cooking it in right now! except I think I put ezinput in, oh well... just testing anyway. I thought I say a post somewhere that sad working cv and mobitv, couldn't find it anywhere!! damn forum search... lol. Anywho, my problem with opera is that it won't even go to the media net home page, and is the fuze not designed to play the cellular video through ie? That's what I am used to from the kaiser. Cause the CV won't work in either IE or opera, which is leading to me to think that I have done something else somewhere else
[Touch Pro, Fuze ROM Development] Da_G:
CV works fine with IE if you load the hidden proxy and if you set the MSHTML registry setting to 0.. but that makes it load in the old IE Mobile engine :)

You can get it to work with IE 6/8 by setting it to desktop view rather than mobile view.. problem is, it changes the user agent when you set it to desktop view.. ive gotten it to work after switching back and forth a few times..

If we can finger out where IE 6/8 stores it's Desktop user agent, then it would work jussa fine :)
[Touch Pro, Fuze ROM Development] TheDeadCPU:
You are a god! Thank you!
[Touch Pro, Fuze ROM Development] gilmorej:
Hi guys. I am having this issue where once I have an incoming call and try to answer it, either by pressing the talk button or using the slide-to-answer, there is a chance the phone will never respond to the actions and I will miss the incoming call even though I was pounding away at the talk button.

Any advice? I am using the latest kitchen.
[Touch Pro, Fuze ROM Development] hilaireg:
Hi gilmorej,

Launch the kitchen and save your ROM profile. Afterwards, ZIP the ROM profile (.ERV) and Build Log file and attach them to a post in this thread so that I may look have a look at them.

Cheers,
[Touch Pro, Fuze ROM Development] gilmorej:
Here are the files and a bit more information concerning the circumstances.

I flashed this new version of the ROM because the ROM I had been running developed the same issue (not accepting calls). I figured some files must have gotten corrupted, or something, and instead of just doing a hard reset I would check out the latest developments on this project. However, once I flashed the new ROM and discovered it was also doing this I started to think about what had changed around the time this issue arose.

The only thing that changed before I started having this problem was that my area now has a 3G signal. I don't know what this may have to do with the problem, but we started getting 3G service here within days of me first noticing this issue. Nothing else has changed about my phone other than that. I never had my phone not accept a call when we were still on EDGE service.

This may not have anything to do with the issue, however it seems suspicious to me and I guess any information I can give may be of some help.

File james_custom.rar is the ROM I currently have on the phone from kitchen build 21056.

File james_custom_older.rar is the ROM I had running when the issue first arose, from kitchen build 21054.

At any rate, thank you for looking into this. And thanks for still devoting time to this project. I really like this kitchen and how simplistic I can customize my phone to be without totally making it bare-bones.

P.S.:

Those two RAR files are zipped into the attached ZIP. I wasn't aware the forums didn't allow attachments of RAR files. I wonder why that is?
[Touch Pro, Fuze ROM Development] hilaireg:
@gilmorej:

I'm attaching an .ERV profile for you to test with; changes to note:

Removed .NET 3.7 (known to be problematic)

Changed the volume control package

Added missing dependency packages

Added Manila for the time being, disable via Settings -> Today -> Items -> TouchFLO 3D

I recommend working off a clean kitchen so as to leave your existing kitchen untouched. You can always copy in any additional changes you have made.

Please follow this procedure for your new (clean) folder - ex: C:\XDA\My_Visual_Kitchen:

Download Visual Kitchen 6.1.21056

Download & Apply Pack 1

Download & Apply Pack 2

Download & Apply Pack 3

Download & Apply Pack 4

Download James_Custom_ERV_Revised.zip

Compile a ROM using the Revised ERV Profile -

do not

change selections.

Backup the build log.

Test the ROM on your device for a week or so.

If you are still experiencing the same problem, post separate .ZIP files that contain the logs for each of the ROM compilation/test along with any scenarios that you think I can try to simulate.

NOTE:

I'm currently using the attached revised profile on my device.

The kitchen I used to compile the ROM is exactly as noted in the steps above - no additions/removals/changes.

Running kitchen on Windows XP SP3.

HTH,
[Touch Pro, Fuze ROM Development] gilmorej:
All right, first off let me apologize for taking so long to make a response.

However, after continuing to have issues I have done more experimenting and have come up with some insights..

It does have something to do with 3G as I thought. I found that the issue only occurs when the phone recieves an incoming call when it is in standby state on H or 3G mode. When the phone wakes up to ring, unless it is answered almost immediately, the phone will not pick up the call when you try to answer it.

I tried disabling HSDPA but was still getting the issue when in 3G mode. So I selected GSM band in phone settings to disable 3G altogether. When phone is in EDGE mode this problem does not occur.

I tried manually selecting WCDMA mode to see if the Auto band selection is what was tripping it up but still had the problem.

So, since I need my phone to work as a phone foremost, I am running in forced EDGE mode. This is not ideal and I don't want to have to keep my internet gimped just so that i dont end up missing important calls.

I am not sure how further to proceed with the troubleshooting. But given this new information perhaps you will now be able to reproduce the problem, or maybe you already have an idea what is happening?

I want to thank you again for your continued support.
[Touch Pro, Fuze ROM Development] hilaireg:
Interesting,

I'm not experiencing that issue on Rogers; what radio version are you using? Did you change the RIL file?

Few options for you:

1) Have a look at the .provxml files in the Custom Profile package as they contain many carrier related "bug fixes". All of the entries are commented; see if one of the entries "stands out".

2) Download the SYS 21056, ROM: 21054/20779 pack and inject it in a copy of your kitchen so as to build a 21054 (21055/21056=DFT, 21054=Da_G) ROM - see 1st post of this thread for link to wiki. The ReadMe in the pack provides instructions on what to do.

3) RAR up your kitchen and get it over to me and I'll compare it to mine - if you're using a free service, 200MB is the max. Remember to delete the TEMP and the RAPHIMG.NBH to keep the size down. Worse case, split the kitchen in parts and send me a PM with the link(s).

Cheers,
[Touch Pro, Fuze ROM Development] gilmorej:
FWIW, I am on AT&T.

I am using radio version 1.14.25.35 and I didn't mess with the RIL file at all.

I'll look through the .provxml files later, over the next couple of days, as I get some free time off work. But I'm not exactly sure what I'll be looking for. Maybe it will be obvious.

Also, I'll try the SYS pack suggestion and let you know if that changed anything.

As far as my kitchen goes, I am simply using the "WWE Visual Kitchen 6.1, OEM: 5.12.206.1 (20779), SYS: 21055, ROM: 21056/20779, 158 MB, 17.01.2010" kitchen that you posted in the first message plus all (five now) package files. I haven't done any file editing at all, so I'm not sure how much it would help to RAR all of that up for you since it's basically an exact copy of what you put up. But I will do it if you still think it could be helpful.
[Touch Pro, Fuze ROM Development] hilaireg:
You're using the same Radio version I am and I suspect the RIL is fine if you haven't added any of the RIL override packages.

The comments are straight from those found in the stock AT&T ROM. Have a look through to see if any of the comments pertaining to 3G/HSPA, or indicate a fix for crashes, etc. It's possible nothing may "stand out"; but in case you see something that triggers a "hey, ya i've had that happen".

I assumed you had followed the steps I previously outlined; something is up, just not certain as to what it is at the moment.

The ROM/SYS pack is a quick way of adding a new/old ROM and SYS to the kitchen without having to rebuild everything from scratch. Alternatively, you can download the 21054 kitchen from the WIKI and build a ROM. You don't need to apply any of the packs, the ROM won't be "pretty" but it would at least help in isolating the issue.

Approach 1:

Build a ROM using only the 21054 kitchen. If you don't encounter the problem, build a ROM using only the 21056 kitchen. If you don't encounter the problem, it's likely something in a package in one of the Application Packs. We can add one pack at a time to find the problematic package.

If you encounter a problem in the 21054 kitchen (without any packs applied), then it's a kitchen package, .rgu/.reg, or .provxml entry that is causing an issue. I'm sure we can isolate the offending setting that is causing the issue.

If you encounter a problem in the 21056 kitchen (without any packs applied), it's could be an issue in the SYS or ROM (XIP) as the packages in the kitchen were not altered - i.e. they are the same as 21054.

Approach 2:

It's possible that the problem is related to SLOT0 containing modules - ideally, SLOT0 should always remain at 0 modules. I posted two Recoded Modules pack at the beginning of this thread for the purpose of ensuring that SLOT0 remained empty. May be worth trying the RECMOD approach to see if that helps.

Either way, keep me posted on your progress and don't hesitate to PM if you need assistance with the RECMOD or other.

Cheers,
[Touch Pro, Fuze ROM Development] osash2000:
may i ask a small Q....regardingthe OEM....

if i want to put an app in my cooke ROM i know that i can covert the app from cab--to---ext..however i can do cab--to--OME and OEM --to-- EXT...what are the different and which is better ??? really need help to understnad this
[Touch Pro, Fuze ROM Development] hilaireg:
Responded to your other post in Chef Central.

Cheers,
[Touch Pro, Fuze ROM Development] hilaireg:
Updated download links to point to new file sharing host.
[Touch Pro, Fuze ROM Development] aruppenthal:
Skyfox a little advice on the search. Always use the one at the top Never the forum or thread search. The one at the tip in the main toolbar yields MUCH better results.

Look at the advanced config xml I am pretty sure it lists the key in there for IE user agent.

<setting key="HKEY_LOCAL_MACHINE\Security\Internet Explorer\User Agent" name="CustomBase" type="string">
<title>User Agent custom base</title>
<description>User Agent string used by Internet Explorer to identify device on Web sites.</description>
<values default="Mozilla/4.0" />
[Touch Pro, Fuze ROM Development] Da_G:
When in Mobile mode it reads that user agent, but not in Desktop mode.. it's got a new key floating around somewhere.. :)
[Touch Pro, Fuze ROM Development] aruppenthal:
Hers all references to user agent

C:\Users\Ruppy\Desktop\RRE Kitchen v1\SYS\BROWSING\b183f2a7-06c3-4f27-9679-7baf97e94efa.rgu(28): [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent]
C:\Users\Ruppy\Desktop\RRE Kitchen v1\SYS\BROWSING\b183f2a7-06c3-4f27-9679-7baf97e94efa.rgu(30): [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform]
C:\Users\Ruppy\Desktop\RRE Kitchen v1\SYS\BROWSINGCORE\d81b11e0-3299-4b65-8305-78f1fa03dc07.rgu(58): [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent]
C:\Users\Ruppy\Desktop\RRE Kitchen v1\SYS\BROWSINGCORE\d81b11e0-3299-4b65-8305-78f1fa03dc07.rgu(65): [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Templates\Same as Windows XP]
C:\Users\Ruppy\Desktop\RRE Kitchen v1\SYS\BROWSINGCORE\d81b11e0-3299-4b65-8305-78f1fa03dc07.rgu(71): [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Templates\Same as Pocket PC]
C:\Users\Ruppy\Desktop\RRE Kitchen v1\SYS\browsingie\f3dfc36d-36d0-4163-8d6f-e1ce5aed8814.rgu(3):	"User Agent"="Mozilla/4.0 (compatible; MSIE 6.0; Windows CE)"
C:\Users\Ruppy\Desktop\RRE Kitchen v1\SYS\browsingie\f3dfc36d-36d0-4163-8d6f-e1ce5aed8814.rgu(1051): "User Agent"=dword:00000000 ; Default User Agent set to UA_MOBILE_DEVICE
C:\Users\Ruppy\Desktop\RRE Kitchen v1\SYS\browsingie\f3dfc36d-36d0-4163-8d6f-e1ce5aed8814.rgu(1066): [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform]

Da_G

I started the WIKI page for Packages. Ill begin editing it tonight with some of the ones I already have ready.
[Touch Pro, Fuze ROM Development] skyfox99:
Ok guys, I will try out that info when I can tonight after get home from the trap of work.

Just a weird thing, something I am sure I did in removing something somewhere. When I go into the device info, it now says expanded memory not present. Where it is and AFAIK everything functions properly. What would cause this, and is there anything I should be concerned about since it is not showing the storage media present?
[Touch Pro, Fuze ROM Development] Da_G:
Device Info reads a key from the registry (under HKLM\Software\HTC\DIM i believe, dont remember off the top of my head)

The key is like.. extromversion=dword:1

If device info reads the key and it's set to 1, it looks for the .dsm in \OEM\ExtendedPkg.. and if you cook the ROM with the "all packages to one" box checked, there's no .dsm there for it to read, and you get that error. :) I have the key set to 0 in my \OEM\OEMDrivers\*.rgu for that reason.

On a side note, I just dropped my fuze onto some nice asphalt, it took it like a champ, but that cruddy extended battery cover that came with the seidio extended battery cracked.. doh.. now its even worse than it was lol :P

What's a fancy phone without a few war wounds anyway!
[Touch Pro, Fuze ROM Development] skyfox99:
Could it be that I am using the 2808 build of opera? I tried using the original opera shipped from the fuze, now media net loads, but I get an error when trying to access CV website videos that says error format not supported or something along those lines, flashing now, so I couldn't tell you exactly what it said. I liked the settings and the zoom slider of 2808, but maybe there is something there in that particular build?

with the sd card... now I notice that the sd card will NOT be recognized unless I boot the phone with the sd card in it... WTF? If I just copy the sddrivers package from my base... would that fix the storage media not present and this issue I have now? aarrrgggghhhh!!

I dread the first time I drop my fuze... although I am lucky if I damage it beyond repair i just go get another one (benefit of the job wit the company!)

*EDIT*

Three different versions of OPERA and three different errors... lol.. I get file re-entry not allowed (and the fix doesn't work), CV is not supported on you device, and not supported media!

DAMN IT... now I get the requested media is not available... or media type not supported!!

Is there possibly a codec or something I am missing?

Would the radio version I am using make a difference? HMM... boggling

other than opera, streaming media, and th proxy, is there anything else that CV requires to run in the ROM?
[Touch Pro, Fuze ROM Development] Da_G:
Just swap out all the drivers in /oem/oemdrivers for the ones that work :) fwiw i just reinserted my sd 3 times and it popped up the autorun all 3 times... using the bstone jan 15 oemdrivers
[Touch Pro, Fuze ROM Development] Da_G:
We'd have to port over so much of the 6.5 system to make it boot up that you might as well use 6.5, because it's going to carry over most of the glitches from it. :\
[Touch Pro, Fuze ROM Development] The Jack of Clubs:
aw i was hoping it would be like a quick cab or summat. how come it seems to work so much better in youtube and tf3d? maybe we just need a new version of touchflo from htc.
[Touch Pro, Fuze ROM Development] skyfox99:
I ported over the drivers from NATF, and still had the same issue, will try again when I get home tonight.

I forgot to ask NATF about this in my PM, maybe you can help, when NATF cooks a ROM, his splash screen is flashed during the install. I only know how to do this post installation of the ROM... I would I put my own splash screen in to my cooking?
[Touch Pro, Fuze ROM Development] Da_G:
The raphael.htcrtproj in the base kitchen folder is a template for HTC ROM Tool (\tools\htcrt.exe) to compile the .nb's into a signed .nbh. The template as-is is set to load up one .nb (os-new.nb) - what you'd want to do is put your splash screen as splash.nb in the rom kitchen root, load up the template in HTC ROM Tool, (Rom Builder tab, "L" button, load raphael.htcrtproj) - where it says "Splash" click the ellipses and point it to splash.nb.. then save the project over itself..

Now every time you compile a rom splash.nb will be in the ruu_shipped.nbh package :)
[Touch Pro, Fuze ROM Development] Da_G:
How odd.. I can't flash from usb anymore after dropping the phone lol, only SD..

What the family! That makes testing new vers a pita..
[Touch Pro, Fuze ROM Development] skyfox99:
Wow, you said you miss your BlackJack... how infrequently I hear that. The forum search at the TOP much better... didn't realize there was a difference between, why I dunno, but anywho...

Anyhow, got CV working through Opera, turns out there is something in the build 2808 that interupts the connection between the NAT firewall and such (or something someone far more knowledgable than me was trying to explain...). I am just wondering, though, why is there no link for CV in the media net homepage? Is there something in the settings I missed for the media net to recognize that the device is CV capable? I know that the TILT had problems with that. you know it VERY weird, is when trying to watch CV via PIE, the page loads as what appears to be xml coding and lots of it... wierdness going on there, eh?

I just liked having th latest version and that as I have come to learn isn't always the greatest... Now on to the XT9 Funtionality focus for me as texting is the next thing on my list of what I want out of my phone. Would the files from the Kaiser (Tilt) for the ROM work in porting over to the FUZE? Both WinMO 6.1 and resolution shouldn't have any effect on something like that,right? I am curious to know where does the files lie for the system suggestion (the ones that are supposed to work in stat>settings>system>input?) Does Xt9 basically overide everything that relates to text entry? And with the GPS, is the lag going to be a hardware limitation do we think? or software, cause software means we may see a fix eventually, but hardware, we are SOL, am I right?
[Touch Pro, Fuze ROM Development] bilbobrian:
Here is a welcomhead image to give Da_G little props for all the mobile goodness he provides.....:)
[Touch Pro, Fuze ROM Development] aruppenthal:
Sys/Redist_dpi_192_resh_480_resv_640
[Touch Pro, Fuze ROM Development] gadgetdad:
Perfect thanks. Got the dump done properly last night also and was able to get rid of my wmp crashing issues.

Last question for you since you are on - how can i create a radio nb to use in NBHUtil?
[Touch Pro, Fuze ROM Development] aruppenthal:
Find a radio .nbh and split it. Inside will be the .nb for the radio. Then you have to edit the project file in the kitchen to use it.
[Touch Pro, Fuze ROM Development] gadgetdad:
can i just let it spit out a rom as is with the osnew.nb in the base folder of the kitchen and take that plus my radio.nb and splash.nb and use nbhutil after the fact to nbh it?
[Touch Pro, Fuze ROM Development] aruppenthal:
Sure that should also work :)
[Touch Pro, Fuze ROM Development] chrisjaffe:
2 questions:

1) What opera build is everyone using with this kitchen. I have only tried 15529 so far and that is pretty buggy for me. I have a 2808 cab thanks to d0ugie and blownfuze that I was going to try tonight. But I was just wondering if anyone had any opinions either way.

2) there was mention a few pages back about a package wiki. Is there a link for that? I would love to see what else I can add to this kitchen.

thanks,

cj
[Touch Pro, Fuze ROM Development] gadgetdad:
I am more a skyfire man myself but when i have to use opera i use the stock fuze cab

Raphael Wiki is here

http://wiki.xda-developers.com/index.php?pagename=RaphaelOEMPackages
[Touch Pro, Fuze ROM Development] player911:
Da_G has an update coming shortly using the latest HTC Raph build posted http://xdaforums.com/showthread.php?t=478657