yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Hey ndn...(or anyone else who knows the answer)...

In considering cooking an HTC release there are two things about the HTC ROM that I would want to change from the default and I can't figure out how to do so.

1) The virtual keyboard SIP. I think that it uses the same DLL as the AT&T, which is ok... I want to keep the keyboard as the default. HOWEVER, is there a way to change the layout of the keyboard? In the AT&T ROM when you pull up the SIP the layout has numbers on the top rom like a normal keyboard. In HTC you need to press the number key to bring up a keypad layout. I really prefer the AT&T. Any idea how to change?

2) I don't like the HTC dialer and would actually prefer to put back in the blue dialer skin that is on this AT&T ROM (at least for my personal use). I don't really know too much about replacing dialers. I know there is a reg key under security\phone\skins or something like that which points to bitmaps. I don't know exactly how the naming there works and how to map to keys (or even add new keys). Also the options that come up when you press the "menu" key in the phone are different. I would hope that I can install the PTT cab onto the HTC and get the PTT options in that menu screen too. If you or anyone has good experience with this, let me know.

thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kwickone:
Yep. I sync with Exchange and it enforces a password policy (simply that I have one...does not care what timeout: mine is set to 24 hours since I use ThrottleLock).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Cool...yeah..I'll have some more info on this up soon..probably start a new thread to detail specifics. I don't know if I will have a fix, as I have a feeling it is built into a dll somewhere. However I might be able to narrow down the exact issue and solidify a 100% workaround.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] drunkbastard:
3G connection fixed

I was having a huge 3G issue with my Tilt - stock ROM, no 3G connection, could only connect on EDGE. Tried different cooked ROM / radio / HardSPL combos to no avail. This ROM with the 1.71.09.05 (?) radio has given me my 3G back.

Donation is forthcoming, thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
That's interesting. This ROM shipped with the stock ROM that the AT&T build shipped with... 1.65.21.18. So I assume you are getting that 1.71 from somewhere else?

I wonder have you ever tried the full official AT&T 6.1 release (which this is built off of) and had the same issues? I don't think there is anything I would have done that would have helped you on this...but I am glad it works for you!

No donations necessary, but you can contribute to any charity (can use link in sig) if you desire!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] drunkbastard:
Flashing the stock AT&T 6.1 was the first thing I tried. The original problem had to do withusing GPS - whenever I activated it (TT7, GPS Tool, etc.) my 3G went away. I reflashed the stock ROM and it was fine, but the same GPS problem popped up. After that, the reflash did nothing to solve the 3G issue. I got the 1.71 radio off the Ultimate Radio post, it helped clear up reception issues (my boss now doesn't whine that he can barely hear me). I know that the ROM is just a bare version of the stock, honestly I can't explain it, all I know is that I had no 3G for a week, AT&T had no reports of a 3G outage in the area, no one else had complained of the same issue in my area, so unless the guy I was talking to was a complete idiot (very likely, but giving the benefit of the doubt), I could only hold my phone to blame. Going on 12 hours now without a glitch. Just keeping my fingers crossed that the gremlin is gone for good.

Again, thank you, sir.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Bengalih,

I tried the Voice Command cab and it's working well, but one thing is strange:

I have always been used to having the following files in the Win directory in ROMs

including VC:

voicecmd.exe

VoiceCmdRes_PPC.dll

voicecommand.lnk

VoiceCommand_PPC.cpl

VoiceCommandWMP.dll

After installing your cab I can only find the cpl file.

As I said, VC is working well, but the reason I'm posting this is that I can only use VC

in batch files if I've got voicecmd.exe/lnk, which is missing in your cab

install.

- Is there any reason for this and can you include these files also?

- Or is there any other way of calling VC in a batch file?

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dma1965:
I am running the version called:

SJ_HTC.Home.v2.1.1005.722.Directory.And.Brightness.Fix.schen.updated.cab

I have attached it to this post, along with a screenshot. I really love the default icons it comes with.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Like all the CABS I create, I do not place files in the ]Windows directory whenever possible. Some applications, like HTC home require their files in \Windows. Others require some DLLs to placed there. For MSVC, for instance only the CPL file must reside in the windows directory.

To better organize the programs on the device I place each program in it's own directory.

Check under \Program Files for a sub directory which has all the relevant files.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
gotta reply quick, still at work... as far as i know, these are just reg settings (like the tilt keyboard fix), all of the key mapping for the device should be handled there except for the hardware part of the power button. the dll should just be the driver for the sip, and there should be a graphics file (cant remember what it is).

i've never worried about what the dialer does, just replacing it. when you don't use the phone canvas registry setting (so it's the "stock" dialer) it uses the Phone, *_DPI_96, Lang_0409, etc... folders... this is usually what i replace, but you should make sure the actual phone canvas is gone. i replace those folders with extracted cabs or regular phone OEM packs. you need to make sure everything looks the same though, and completely search the hives and rgu files for references to any of the dll's in those folders or having to do with the phone canvas... it really is a ***** to do full removal and replacement, so i usually just replace the phone canvas (actually i usually just install a cab during customization, it's much easier :)

looking at the reTOUCHed_dialer2 pack from alex's kitchen, there's a DPadMenu.dll, which i'm assuming takes care of the menu's you are talking about. the different graphics names are specified in the rgu, and if you look at an example rgu, there are ton's of settings for the phone. best bet is to use an OEM canvas, or cab it... you can also cab2OEM... btw the canvas file is phcanOverbmp.dll usually about 500k, if you search the hives you'll find references to it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
copy and paste from a PM i sent to another member from the wizard forum awhile ago... sorry it's so short and convoluted, i'll expand on it tomorrow if you have questions... this applies to replacing just about anything in the rom, including .net 2 or WMP, they're both referenced everywhere...

_______________________________________________________________

with removing packages, it is definitely not just deleting the folders :eek: that works for easy add-ons in OEM, but not for the real ROM files.

the quickie way is to convert the hv files to rgu's and then look at the folder you want to delete. search default.rgu for each file in there (if they all start with a common part, sqm, wlm, you can just search for that) and remove _all_ references. sqm is easy to remove, WLM more of a *****, .NET is lots of fun :) i have been stripping tons of roms and only gotten good at it recently.

the hard and best way (because some rgu's reference the folders you'll delete)

search on the kitchen folder for *.rgu

copy all of those into a temp folder along with default.rgu and user.rgu.

use PSpad to create a project and populate using the folder to load all the files. (this requires changing around the default format that pspad uses to unicode-16)

you are then able to search all files simultaneously, so repeat the same searching procedure as you will find strange references in other rgu files.

the annoying part: when deleting a reference that has a CLSID (the long number) in any of the rgus, copy the CLSID and do a global search again, there's usually obscure references that don't have file names (just like CLSIDs in Windows).

then there is the matter of making sure all the changed files are copied back to the correct directories and in the right format (hex editor compare) and that the default and user files have REGEDIT4 and the line break at the end and saved as unicode and you don't get any errors when converting back to hv

then editing initflashfiles.dat to reflect the changes and removing the first part with a hex editor.

i don't always, but to be really anal, open the dsm's in directories that you've removed files (like the crap in OEMapps) and using a hex editor to manually remove the references.

make sure the hv files and initflashfiles are copied to the metadata and OEM lang folders, and build

definitely not the easy way :D

if you are masochistic and ever want to try this way, let me know...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
This is exactly my opinion also and I do this whenever possible in my standard desktop Win apps.

But in Win Mobile apps I got so used to the stupidity that nearly every cab is cluttering up the Win directory that it comes completely unexpected to see that there are still people doing it the right way.

Thank you and keep it up that way!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
i see you're pulling sqm and musicid in the next one... i've never used musicid, but i sounds cool, i opened it from this rom though and it talks about a subscription so i thought it was a pay deal...

sqm is Service Quality Monitoring and it's the report home thing that we were all worried about initially when working with these roms. even if the service and HKLM\init entry is removed, it gets loaded into memory somehow and so should always be removed. just deleting the directories doesnt seem to be enough in my experience.

i know that sqlcemobile is supposed to be for sql connectivity, but i administer sql databases at work as well and haven't found a use for the thing :) anyone ever actually use it for something? i'm curious because i've never seen a definitive answer...

i would hope that it just checks a registry key, but from what i've seen, the dll gets loaded at boot whether it's turned on or not, so it may get parsed even though the reg key is removed. i've noticed improved rotation times (subjectively) from removing it. i've never found a cab for it though, it'd be nice to be optional...

the camera deal was if i was cooking in a new one, which applied alot to the wizard. when you run buildos with a new oem camera pack, you have to delete a lot of rom files that are already cooked in. a full removal was my way of making it clean, but it might not be necessary... i just cab them now...

input from other members about using .net 2.0? i'd be nice to know if anyone has encountered this problem with recent software...

side note, i live in seattle and work a few miles from MS. went there on friday for a usability study and got a free copy of project 07 that went on craigslist. :cool: i'd like to find a way to get in with the mobile development team, since im pissed that google is f**king up android, and our only hope is WM7... i'm betting that i shouldn't put xda developers on my resume if i want to get a job there :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I don't know how much they cause problems... I'm sure in some cases that's true. Usually if a regkey exists, but no files referenced do, it doesn't do much harm to have the keys there. And, when/if you install another version, it will update those keys. But, yes our procedures here are similar and I agree I'd rather have stuff out of the registry if I've removed the files.

I just opened up my edited initflashfiles.dat in a hex editor and you are right that it does start with FF FE, where the original does not. However, I have never edited this value out.. I just edit the file in notepad and save it, and it appears to compile without any issues. I am curious what the need to edit this in hex is?

Ok, now this is something I have to start a "debate" on... because my own experiences (and another test I just ran) don't show what you are saying to be wholly accurate.

When you extract a ROM (again I use kaiserkitchen) it creates the ROM, SYS, OEM directories. If you search through these for *.hv files you will find 3 or 4 (default, user, boot, and there is one other I believe). However these files ARE NOT used to rebuild the ROM.

I just proved this by extracting my RUU_Signed.nbh, deleting these .hv files and then re-cooking my ROM. My new RUU_Signed.nbh was identical to the original.

I am 99.9999% sure that all the .hv files are built at real time from the .RGU files. As such, I don't see any reason to edit the .hv files directly. I think this may be a misconception from some cooks who get rid of .rgu and .dsm, etc and so when a ROM decompiles you dont' have these files to edit. With our method however there doesn't appear to be any purpose to edit these .hv files (again, as my experiment shows these files don't even need to exist, and thus aren't used when re-cooking).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I'm still not sure on this. If you open up the MusicID application it never talks of billing, you don't have to accept any terms or anything, and it works...so I don't know. If however you use #43 (preloaded contact) for MusicID it tells you it will charge you 99 cents for every identified song. However it sends you a text message, where the application doesn't send a text message. I don't think I ever saw a charge on my bill for using th application, but I only tried it a few times.

Yeah, I looked it up after your posting on it... no2chem has a dummy file which I integrated which returns 0 values to the queries coming into it. Apparently you can't fully strip it out as in 6.0, you need this dummy file in there.

Yeah I figure it is like odbc drivers and such.. but I couldn't find any mobile app which depends on it to test it to one of my own server, anyway I'm stripping it and will include the cab.

Well I am striping sliding sounds as well, and my external CAB does work to add it back in. It is strange because there is no DLL for sliding sounds on this ROM... there is just an .EXE and the registry entries for the control panel applet. I'm not exactly sure how it knows, i have a feeling that whatever dll controls sliding/rotation also automatically looks to the reg keys for sliding sounds...so you probably can't rip it out directly without possibly replacing a dll from something else.

To be honest, I don't like the idea of using hacked or other ROM's dll files, it begins a frankenstein approach, and I'd like to keep the ROM pure. I made an exception with SQM because the nature of what it does. But, for anything that taps into the functionality of the device I want to keep clean.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
well i have learned by screwing around and getting as much info as i can, so i know im wrong with a lot of my preconceptions...

i always thought that you had to remove the FF FE from initflashfiles.dat... it's in one of the wizard cooking guides... since you can build it without doing that, i wont do it anymore :)

you can build it after deleting default.hv and user.hv out of Metadata? holy crap! seriously, it really seemed that they were used when i was cooking wizards... even to the point that i would change something in the hives and then move them to Metadata, rebuild, and the rom would be different! rgucomp would even ***** if i didn't edit the hives correctly (FF FE) converting the hives to rgus and back was part of the kitchens we used however... damn, i've wasted hours of my life :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
sounds good to me, that approach is great since we need stable clean roms rather than crazy xip ported hacked ones... i have to rethink my whole cooking process now :eek: this was just how i was used to doing things for so long, i stopped trying to figure out other ways... i'm glad you've shared this with us...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Well I don't think you're the only one. First let me say that it is still possible I am wrong, but I just did these tests and they show what I have said. Problem is we all learn from picking through old data and even some of the people who are nice enough to write guides may not always know the proper way (as they themselves have pieced it together).

I would love independent confirmation on this so next time you cook do some tests. Also please anyone else chime in to confirm if this is the case (i.e. *.hv files are build at cook time from .rgus and do not need to be edited manually).

Also, I'm still trying to get confirmation on my suspicions about mxip* files. No one has reponded in a few days, so I want to say that no one can prove me wrong :). Thead here.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
you're very right, i just built one and deleted the hives... damn! i'll post my input on the next one, i have to find something to be helpful with :)

i really do like being proved wrong, its the only way to learn!

and i hope others chime in here, many points of view are alway welcomed...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
BRR 2.0 and associated SPF CAB Pack is now up. Check first posts.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cushcalc:
Why leave radio in?

You do leave the Radio in, though? I know that's a stock item, not a customization - but it is something that is frequently changed, usually until one settles on a preferred radio for his locale and needs.

This means that an additional Radio flash is necessary to get back to an individual's preferred radio version. (Although I stripped radio out with HTCRomImageEditor, not everyone is familiar with that).

Please comment.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Because a radio flash is something I consider a simple change.

In additon, settling on a radio has more to do then just locale and needs, it also has to do with a radio that works properly with a particular ROM.

I like to provide a complete package that is guaranteed to work well together, that includes a radio.

I can offer a version w/out radio if feedback warrants it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cushcalc:
Well, it's just that I haven't heard anyone have much good to say about the 2 radios that come with the AT&T 3.57 ROM! Also, there's usually plenty of good alternatives that are known to work properly with a particular ROM.

No big deal, just curious about your feeling on it as much as anything, but if I had my druthers, I'd prefer no radio inclusion with ROMs offered.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Honestly, I haven't had much to time to mess around with radios so I don't know what the current thought is on what is good or not.

I tend to have the viewpoint that neither AT&T not HTC nor Microsoft are going to release something to the public that is wholly unfunctional.

I realize that all have released products with bugs, but the point I am trying to make is that sure, there may be a way to hack any aspect of the device to make it improve better, but at what cost? In some cases there are no drawbacks, in other cases there are. Sometimes these drawbacks aren't easily apparent (for instance a radio provides awesome GPS fix, but sucks battery in two hours, or provides awesome battery, but horrible GPS fix).

I do believe that these large companies (for all the "big-brother" or animosity we may have) have decent QA departments that ensure that what they release meets 95% of the needs for 95% of the people. Most (but not all) of the people on these forums do very informal testing (meaning they don't properly QA all fronts) and then say a radio is good or great with a particular ROM/device. I don't want to put a radio on my phone that some user says is awesome on recpetion and battery life only to have to stuggle through and discover on my own that it is causing the unresponsive screen taps I've been seeing (just an example...).

All that being said, there may indeed be a radio available that is on all fronts better than what was shipped. However this radio was pulled from a different ROM or even device then what this ROM was meant for. That could mean possible issues on other fronts.

Since I am trying to provide a good stable base, I felt obligated to provide a radio which was shipped and QA'ed to be stable.

I welcome feedback in this thread as to what radios are working with this ROM and what the pros and cons are, especially on the stock radio.

Because I am starting with a clean-stable base for all to use, I welcome customization talk that all users can share. Some of that customization may be built into later builds, as long as it doesn't violate my cooking principles from the first post.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] eknutson:
I'm trying to figure out where I stand with the radio in regards to the RAW philosophy. I certainly see including it as being a nod towards stability... however, I did test many radios here where I live and found that the Polaris was what worked the best. The 20.29 and 24.36 were also very good.

But I have to say, that even though the 1.65.21.18 wasn't too bad, all 3 of the previously listed radios were better for me. (that's in regards to what I do with my phone / how I use it) than was any of the 3 AT&T radios I've tried (12.11, 21.18 and 21.14).

My vote (if there is such a thing) is to have the radio separate. I already have to flash my animation / splash screen of choice as a matter of preference, I feel that a radio has as much to do with location and user as it does with the ROM it shipped with originally (if not more so).

BTW - I'm about to flash BRR 2.0 with my selection from the SPF as soon as I fill in more in SASHIMI. I've been using SASHIMI since early summer and I just LOVE it =) I'm getting into some of the more hard-core flasher uses, so setup is taking just a tad longer. Hope to report back shortly with how it goes.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
i understand about the separate radio, and i initially thought so too... but at the same time, i always flash down to stock, then a rom/radio/splash... so the extra radio doesn't necessarily hurt...

i'm taking a look at this version now and the only thing i see right away is the comm manager shortcut, it's not mapped by default, but button 6 isn't mapped to anything.

haven't figured out whats up with the installing new dialers just yet, the opal one never works. but i can get the minimal and poorlyduck dialers to install if i delete _phcanOverbmp.dll from OperatorPKG and phcanhtc.dll, phcanOverbmp.dll and phcanrc.dll from OEMAPPS, which usually allows 3rd party dialers. i'm going to compare this with roms that let the opal dialer install and see what the difference is...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] adstevenson:
Windows mobile 6.1 troubles?

I flashed your latest ROM and I love it. Also like the boot screen. I'm having a problem. When I went in to owner info to fill it in, i can type with the keyboard or with the stylus keyboard(?) and nothing shows up, but when I go back to the today screen, the information i put in is there! Anyone else had this problem? I was using wm 6.0 before the flash, and I didn't have sushumi installed.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] adstevenson:
I also can't sync. my pc doesn't recognize my tilt.:mad: