.......................

[bengalih]

..........................

[bengalih]

...............................

[bengalih]

................................

[bengalih]

...........................

[bengalih]

...............................

[bengalih]

.....................

[met3ora]

Looking forward to this release, and will definitely flash it as soon as it comes out!

[zoserguerrero]

But must wait a day :eek:

[overhaulengines]

But must wait a day :eek:

Bengalih, i dont know you, but i love you:D, i love everything you have done, i have used SASHIMI from the first version. i am ready to try your RAW Rom.

Lupe

[mbarvian]

bengalih

i must say that this sounds great

i'm a huge fan of those principles of raw cooking, thanks for posting those ;). I think that if every chef on here followed those then we'd have new rom chefs popping up just about every day

thanks for your contributions, people like you make this a great place to spend some free time ;)

[fmg9800]

You did great with SASHIMI and so I am looking forward to what you come up with.

[rkrasny]

Bengalih:

If you bring half the brilliance of Sashimi to the RAW ROM then it will be fantastic. Seriously, I can't wait (and I'm ready with Sashimi to painlessly change ROMs).

RK

[gfreek]

bengalih I look forward to your ROM:) and I agree to with most part however there are some good ROM chefs out there and in some ways you've reminded me of LVSW's the mans a legend IMHO one of the best ROM chef back in the Hermes days!! to this day I'm still using his WM6 rom on my old hermes which is now collecting dust. I wonder what he's up to these days??

[bengalih]

Thanks for the support guys.

Not to get your hopes up too much...but if you read the principles, you will see that this ROM will be a fairly simple ROM.

The Official AT&T base stripped down, with separate CABs available for installation.

The first ROM probably won't have too many tweaks, and I will solicit input for those later (please don't post them now!).

One cool thing, is that in addition to UC compliance, I will be making this the first SASHIMI compliant ROM! It will run your copy of SASHIMI (from storage card) automatically upon first flash!

Thanks again for the support... hopefully this will (eventually) live up to expectations.

[mbarvian]

One cool thing, is that in addition to UC compliance, I will be making this the first SASHIMI compliant ROM! It will run your copy of SASHIMI (from storage card) automatically upon first flash!

Thanks again for the support... hopefully this will (eventually) live up to expectations.

that sounds amazing man, you've got to post a tutorial on how to make our ROMs sashimi-compliant ;)

[v1xz]

Cant wait to use your RAW ROM, i also think you did a wounderful job with Shahimi. Just one suggestion though, would you consider maybe in the future to possibly make a RAW HTC ROM?

Kind Regards

[zero0zero]

I am looking forward to your new cooked ROM and trust your product. I am a fan of your SASHIMI. it is very good one..

I will be a pilot user for testing your ROM.....

Thank you!

[schizo]

I always see you as the most organized, neat and systematic person here, Mr. Bengalih tiger. Always looking forward to your new creations.

Just one thing, any particular reason to pick the AT&T build except being the latest official build? Actually I also wish that you took from latest HTC build too. Thanks.

[bengalih]

I always see you as the most organized, neat and systematic person here, Mr. Bengalih tiger. Always looking forward to your new creations.

Just one thing, any particular reason to pick the AT&T build except being the latest official build? Actually I also wish that you took from latest HTC build too. Thanks.

Yes...the fact that it is the latest build.

Also the fact that I am an AT&T Tilt user.

I am building this mostly for my own use, however I wanted to share it, and the methodology with the community.

In the future we can discuss doing an HTC build.. but this is the first one.

I don't expect to be an incredibly busy chef like some others here on the forums, but we'll see what happens.

[Moe5508]

Great work buddy - will definitely keep an eye out for an HTC build!!!

[zero0zero]

OK, I got your attachment......

ready to flash.

[ndn715]

i agree 100% with the principles you listed... very refreshing to see :)

rather than playing xip ports and all the really "fun", i'm going back to customizing stock roms. yes there are bugs like any other, but they are the most stable, they work as intended, and can be changed to how we like them.

tearing it apart, you left all of the stock MS stuff in, so for my personal use, i'll be stripping all of that out, update .net to 3.5 etc etc etc... i have my own way i like them :)

but as you said, this is a base and you've done most of the hard stuff stripping the stock apps, i appreciate it very much... i was going to start stripping the stock one for my own use, so this saves tons of time...

thanks for this post and contribution, i really enjoy the point of view...

btw, i love the boot screen :)

[goestoeleven]

<disregard>

[bengalih]

tearing it apart, you left all of the stock MS stuff in, so for my personal use, i'll be stripping all of that out, update .net to 3.5 etc etc etc... i have my own way i like them :)

but as you said, this is a base and you've done most of the hard stuff stripping the stock apps, i appreciate it very much... i was going to start stripping the stock one for my own use, so this saves tons of time...

thanks for this post and contribution, i really enjoy the point of view...

btw, i love the boot screen :)

Thanks.

Yes these are good topics that I would like to discuss with the community.

I left NetCF in there because I consider it failry "integral" to the working of many apps. In addition, it can easily be upgraded to 3.5 and in fact both can co-exist and be "toggled" on the same install.

Also, the reason I strip out applications is not just to free up space. To be honest, even with a loaded ROM, there is generally enough space to load integral apps. Anything else (like data) can be stored on the Storage Card.

I strip out the extraneous stuff more for purposes of organization and utility. Since I see NetCF as having utility (and being upgradable) I left it in. Also, there really isnt' an alternative to NetCF. Unlike applications which have an alternative like Zip (RAR) or Mobile Deskop (VNC) which provide similar functionality.

I try to provide the best balance between function and customizability to provide the most options to myself and the user base.

Basically I ask myself:
"Would someone use another app to do this?" If so, then I stripped it out
Also, I ask:
"If I had to reset my phone without access to my CABs, what do I need to have all the basic phone functionality?" This includes real basic apps (like calc, photo viewer, browser) and built in functionality like phone, camera, gps, etc.
"Will adding this cause someone NOT be able to upgrade or install an alternative?" If so, I strip it out.

So, by all means share your input as I can always be swayed by a good logical argument. :)

[ndn715]

Yes these are good topics that I would like to discuss with the community.

I left NetCF in there because I consider it failry "integral" to the working of many apps. In addition, it can easily be upgraded to 3.5 and in fact both can co-exist and be "toggled" on the same install.

this is a good question for me to ask then, have you had _only_ 3.5 installed and have anything not work right? i've been replacing 2 with 3.5 for a while and never noticed any problems, but that doesn't mean 2 isn't needed for some things... even though both can co-exist just fine, it seems that 2 doesn't need to be there and you still have 2 sets of reg entries that are referenced with the .net module. this seems to be why that fix of installing .net config and setting 3.5 to be the default seems to speed things up...

curious what other members' take is on this...

Also, the reason I strip out applications is not just to free up space.

agreed, rom space is not an issue, and even free mem is not a major factor. however, i like to pull everything that isn't used as it means the OS gets polled less and does not need to load anything that is not needed. just an example of what i'm referring to: (my personal preference, i also wonder if people find any of these useful)

From this ROM:
AUTOUPDATE, Catalog, Transcriber (can be a cab), SqlCeMobile (what do people actually use this for?), SQM (completely), WelcomeCenter, MusicPlayer, TaskManager (X-button, cab, i use pBar), i usually pull the sliding sound module as well, but some like it :), RealPlayer.exe, MusicID (subscription right?), cellular video, music player (i know some use, but there's better ones, cab)

for instance, if the sliding sound module is still there and you dont use it, even if it is set to off, the OS is having to check that each time you slide open the keyboard.

if i'm bored, i pull the camera, comm mgr, phone gfx, and mms (thats a b****). i use cabs for all of these, and the extraneous entries left by the stock parts are referenced in the hives so they have be checked by the OS at some point. these parts are really tricky and take a long time to get right and the benefit usually doesn't outweigh the work...

i think there should be more talk of these things on this site as i think we all hunt in the dark quite a bit :) i'll try to find my quickie guide i wrote another member about how i strip things, its a real PIA, but very comprehensive :) maybe others have input on that as well...

thx for the reply

[bengalih]

this is a good question for me to ask then, have you had _only_ 3.5 installed and have anything not work right? i've been replacing 2 with 3.5 for a while and never noticed any problems, but that doesn't mean 2 isn't needed for some things... even though both can co-exist just fine, it seems that 2 doesn't need to be there and you still have 2 sets of reg entries that are referenced with the .net module. this seems to be why that fix of installing .net config and setting 3.5 to be the default seems to speed things up...


Personally...no. However I have read posts in the past where people had stated some stuff didn't work with 3.5 and only 2.0. If that is the case, it is probably poor code on the part of the developer...but I think there are some cases. I actually stripped out 2.0 and made a CAB initially, but then decided to leave it in.


From this ROM:
AUTOUPDATE, Catalog, Transcriber (can be a cab), SqlCeMobile (what do people actually use this for?), SQM (completely), WelcomeCenter, MusicPlayer, TaskManager (X-button, cab, i use pBar), i usually pull the sliding sound module as well, but some like it :), RealPlayer.exe, MusicID (subscription right?), cellular video, music player (i know some use, but there's better ones, cab)


Yes I have already ripped out Transcriber (thought I personally use it) and Welcome center for the next release. SQLCE is for SQL connectivity (ODBC drivers I believe basically). What is SQM? I wasn't sure.
RealPlayer I keep along with cellular video because I find them a neat utility, although this can probably be made a separate CAB. Music ID for the same reason, although I haven't got any confirmation that this is a PAY service or not. It never prompts you when you are using it to accept any charge, and I don't have it on my service...yet it works. If anyone can confirm this is a PAY service I will strip it out.


for instance, if the sliding sound module is still there and you dont use it, even if it is set to off, the OS is having to check that each time you slide open the keyboard.

Possibly...I haven't looked into that one yet. Sometimes all a poll may be is to check a registry key..so in many cases that is such nominal overhead it couldn't be measured in any real terms.


if i'm bored, i pull the camera, comm mgr, phone gfx, and mms (thats a b****). i use cabs for all of these, and the extraneous entries left by the stock parts are referenced in the hives so they have be checked by the OS at some point. these parts are really tricky and take a long time to get right and the benefit usually doesn't outweigh the work...

Yes, I try to be pretty good about ripping out all the reg entries and not just the files. I haven' t looked at those above... what is the reason to rip the phone and camera? Are there other alternatives to those other than cross-porting from another platform?


i think there should be more talk of these things on this site as i think we all hunt in the dark quite a bit :) i'll try to find my quickie guide i wrote another member about how i strip things, its a real PIA, but very comprehensive :) maybe others have input on that as well...
thx for the reply

That's one reason I made this ROM and posted...so we can all learn more about this and take the mysteries out of what's on the devices!

[hjlow]

http://kaiserroms.blogspot.com/

[bengalih]

http://kaiserroms.blogspot.com/

Thanks! I will probably be updating a new version within the next day or two as I had a modification to the cooked in SASHIMI Compatability that needed to be addressed.

[hjlow]

Thanks! I will probably be updating a new version within the next day or two as I had a modification to the cooked in SASHIMI Compatability that needed to be addressed.

np, let me know if you want old version deleted, otherwise both will sit there for a while :)

[kwickone]

Nice one bengalih!

I would be curious if this ROM suffers from the now infamous 10 second backlight issue, or if you somehow removed that issue in your chef-dom (NOTE: the stock ATT ROM and NATF's ROM do have this issue (For me at least)).

It appears to be related to syncing with Exchange and some type of policy....in my mind, it is one of the most annoying things ever! :eek:

Can someone confirm this for me? Just reflashed to ROMeOS and am feeling lazy :D

[bengalih]

Nice one bengalih!

I would be curious if this ROM suffers from the now infamous 10 second backlight issue, or if you somehow removed that issue in your chef-dom (NOTE: the stock ATT ROM and NATF's ROM do have this issue (For me at least)).

It appears to be related to syncing with Exchange and some type of policy....in my mind, it is one of the most annoying things ever! :eek:

Can someone confirm this for me? Just reflashed to ROMeOS and am feeling lazy :D

I don't know of the issue (as I am really coming back to the ROM scene after not even looking at a new ROM for a couple months). If you explain the behavior I can see if it exists on my ROM. My guess is it probably does since I didn't do anything special that would have most likely removed it. Also, are you aware of a fix avaialble? If so I can look at possibly implementing it.

[_fm]

Congratulations for the release bengalih,.

Keep success sir !!!,.



Warm Regards

Garmin


God Bless You

[kwickone]

I don't know of the issue (as I am really coming back to the ROM scene after not even looking at a new ROM for a couple months). If you explain the behavior I can see if it exists on my ROM. My guess is it probably does since I didn't do anything special that would have most likely removed it. Also, are you aware of a fix avaialble? If so I can look at possibly implementing it.

It is a very odd, and annoying one. Not sure if you sync with Exchange or not. But you set the Battery and AC Backlight timeout to be say 30 seconds and 1 minute respectively.

You wait a while (maybe after a sync) and ta-da. Your backlight is back to 10 seconds. Some have "claimed" to have fixed it. I have tried all the supposed fixes to no avail. It ALWAYS will revert to 10 seconds.

Thus I am back to the ROMeOS...which does not have this issue.

Hopefully you can find the culprit. Thanks.

[dma1965]

It is a very odd, and annoying one. Not sure if you sync with Exchange or not. But you set the Battery and AC Backlight timeout to be say 30 seconds and 1 minute respectively.

You wait a while (maybe after a sync) and ta-da. Your backlight is back to 10 seconds. Some have "claimed" to have fixed it. I have tried all the supposed fixes to no avail. It ALWAYS will revert to 10 seconds.

Thus I am back to the ROMeOS...which does not have this issue.

Hopefully you can find the culprit. Thanks.

Here is what seems to have worked for me:


With the device connected to external power, go to the backlight settings/external power tab.
Change the "Turn off backlight if the device is not used for" to 10 minutes. Make sure it is checked and completely exit out.
While it is still connected to power go back in and make any changes you like, and then exit out.
I don't know why, but this seems to eliminate the 10 second backlight timeout.

[dma1965]

I have to say, I am thrilled with this ROM for one very specific reason...YOU LEFT CINGULAR VIDEO IN.

Cingular Video is free with the data plan and works splendidly for when you want a short news video clip. I have not seen any ROM anywhere for Windows Mobile 6.1 which would allow me to add this in. Sure, I could install RealPlayer and download the RAM file and then play it, but that meant 3 clicks to do what can be done in one with the stock application.

And although I normally hate custom splash screens I LOVE THE DEATHSTAR (my 4 year old son is a major Star Wars fan and has been since he was 2 1/2)

I also love the fact that I can install one of the custom HTC home versions which has the music tab built in.

With everything installed that I normally install, I still have 70 megs free. With my AT&T stock rom I had about 32 megs free.

So far everything seems to be working splendidly.

Thanks for keeping it lean!

[tchavei]

Basically I ask myself:
"Would someone use another app to do this?" If so, then I stripped it out
Also, I ask:
"If I had to reset my phone without access to my CABs, what do I need to have all the basic phone functionality?" This includes real basic apps (like calc, photo viewer, browser) and built in functionality like phone, camera, gps, etc.
"Will adding this cause someone NOT be able to upgrade or install an alternative?" If so, I strip it out.

So, by all means share your input as I can always be swayed by a good logical argument.



Wow. Finally someone that thinks exactly like me :D
I've been postponing installing cooked roms exactly because there isn't a single one that uses every app like myself. There is always something I wish that would be included and other stuff I don't even like.

Please consider a HTC Rom version for your next release :)

Thank you

Tony

[bengalih]

Here is what seems to have worked for me:


With the device connected to external power, go to the backlight settings/external power tab.
Change the "Turn off backlight if the device is not used for" to 10 minutes. Make sure it is checked and completely exit out.
While it is still connected to power go back in and make any changes you like, and then exit out.
I don't know why, but this seems to eliminate the 10 second backlight timeout.


I have been doing some research on this and the popular consensus is that this issue is caused when you are syncing to an exchange server that ALSO enforces password policy on your device.

My own tests so far have been inconclusive, but I think it is more related to whatever system is responsible for bringing up the password authentication and possibly even tied into the backlight system itself. I at one point was able to recreate this issue without syncing to my server (although I can't seem to systematically recreate it anymore). Even when synced to my server the problem was intermittent and couldn't be re-created at will.

I was just curious if you are indeed syncing to an exchange server with password policy? Others have reported the issue on 6.1 ROMs and there may be more than one culprit.

[bengalih]

I have to say, I am thrilled with this ROM for one very specific reason...YOU LEFT CINGULAR VIDEO IN.

Cingular Video is free with the data plan and works splendidly for when you want a short news video clip. I have not seen any ROM anywhere for Windows Mobile 6.1 which would allow me to add this in. Sure, I could install RealPlayer and download the RAM file and then play it, but that meant 3 clicks to do what can be done in one with the stock application.

And although I normally hate custom splash screens I LOVE THE DEATHSTAR (my 4 year old son is a major Star Wars fan and has been since he was 2 1/2)

I also love the fact that I can install one of the custom HTC home versions which has the music tab built in.

With everything installed that I normally install, I still have 70 megs free. With my AT&T stock rom I had about 32 megs free.

So far everything seems to be working splendidly.

Thanks for keeping it lean!

Thanks yes...I tried the app and thought it was a nice free tool.

I will most likely rip it out in the next release, BUT I will provide a single CAB to add the full functionality back in, so you can even put it on other ROMs if you so choose.

I don't take credit for the splash... found it somewhere on this site, and just always liked it.

I ripped the original HTC home from the CAB myself...which CAB version are you running with the music tab? (link if you can?)

thanks.

[bengalih]

if i'm bored, i pull the camera, comm mgr, phone gfx, and mms (thats a b****). i use cabs for all of these, and the extraneous entries left by the stock parts are referenced in the hives so they have be checked by the OS at some point. these parts are really tricky and take a long time to get right and the benefit usually doesn't outweigh the work...

i think there should be more talk of these things on this site as i think we all hunt in the dark quite a bit :) i'll try to find my quickie guide i wrote another member about how i strip things, its a real PIA, but very comprehensive :) maybe others have input on that as well...

thx for the reply

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!

[kwickone]

I have been doing some research on this and the popular consensus is that this issue is caused when you are syncing to an exchange server that ALSO enforces password policy on your device.

My own tests so far have been inconclusive, but I think it is more related to whatever system is responsible for bringing up the password authentication and possibly even tied into the backlight system itself. I at one point was able to recreate this issue without syncing to my server (although I can't seem to systematically recreate it anymore). Even when synced to my server the problem was intermittent and couldn't be re-created at will.

I was just curious if you are indeed syncing to an exchange server with password policy? Others have reported the issue on 6.1 ROMs and there may be more than one culprit.

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).

[bengalih]

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).

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.

[drunkbastard]

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.

[bengalih]

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.

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!

[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.

[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

[dma1965]

I ripped the original HTC home from the CAB myself...which CAB version are you running with the music tab? (link if you can?)

thanks.

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.

[bengalih]

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

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.

[ndn715]

1) The virtual keyboard SIP. 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?

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).


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.


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 bitch 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.

[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 bitch, .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...

[bengalih]

copy and paste from a PM i sent to another member from the wizard forum awhile ago...

Thanks for the response... but is seems your methods for doing most of this work are overly complex. Just to give you a comparison of what I do:

1) Extract the ROM using KaiserKitchen
2) Create a "Removed" structure that mirrors the OEM and SYS structure. I don't mess with ROM...since I am not modifying the XIP. Any file I remove I place here, or if I modify it (like an .RGU), I place an original copy here.
2) Go through the various OEM directories and remove the files I want. Check the .RGU files and .XML files in each directory where i removed a file to see if it references any of the files I removed, if so modify them. Most things in OEM directories are not referenced outside the directory that they are in (e.g. OEMAPPS).
3) SYS is a little bit more difficult. In general just remove the SYS directory that you want (and the associated lang) for each element you want to remove. Like OEM, most of the entries for SYS are self contained in the .RGU files in their respective directories. Sometimes the .RGUs in the OEM directories will contain references, so you can look for those.

I just use windows search (with full indexing for all file types turned on) to search for references within the whole structure (that way I am not copying/moving stuff around and modifying and puttng it back).

I also use plain old notepad to edit everything. I have found nothing that requires the use of a hex editor. I don't mess with .DSM files as I don't believe there is anything in a DSM file that is going to be loaded into the system. From my understanding the .DSMs are to help loading the XMLs, and have nothing in themselves that they will load into the system.

4) Initfiles.dat - which I also edit with notepad without any issues. Clean up anything in here.

With just that things for fairly easily and you strip out 95% of what you need. It is true that some registry entries may remain, but these are not harmful. Yes they might take up another 5K in the registy, but just because a reg entry still exists that references an HTCHome setting lets say, it isn't going to affect the operation of the device (not slowing it down), it also will be overwritten if another piece of software wants to overwrite it.

I do like to go back and clean stuff up more if I can...but it isn't really necessary other than, as you said, to be anal.

So you seem to be using another cooking method (one that requires manual extraction of hv and rgu files)? I don't need to do any of that with the way I have learned... You're also not the first i have seen that talks of using hex editors on initflashfiles and other files... I don't see the need for them, these are text files to the best of my experience.

Sometimes I have some issues when stripping things out. Like, when i stripped out PTT all of sudden the Dialer menu appeared slightly strange (like you could see the contact as if there was no skin applied) and all the menu choices weren't in the dialer. It turned out that a PTTDialer wrapper needed to be installed in order for it to work right, so I had to copy that single dll back.

I also have issues in building my CABs, mostly because I don't like installing everything back to the windows folder, so it takes more work to find out what can survive outside \windows and modify where the registry looks for stuff.

Anyway, I'd still like to get some help with the keyboard and dialer issue. I did replace the .dll for the SIP from the ROM, but the keyboard layout was the same... so I don't think it is in the .dll. Also, I don't think it is the same as the tilt fix, as that is to re-map the hardware buttons, where what I am wanting is to change the virtual keyboard map layout.

For the dialer...if you could link me to a good dialer CAB that works on this AT&T stock I can probably learn from that what all goes into a dialer package and from that reverse what I need to take out to create one from the stock AT&T.

thanks again!

UPDATE:

Well going back and looking at some stuff I think maybe I don't know what I thought I did about putting this together... so clarify for me.

Are the .hv files built from all the RGU files? If you look at both pretty much everything in the RGU files is in the .hv files. So do I need to modify the individual RGU files (which is what I have been doing) or do I need to extract, modify, and rebuild the .hv files?

[asango]

Like all the CABS I create, I do not place files in the ]Windows directory whenever possible.
To better organize the programs on the device I place each program in it's own directory.


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!

[ndn715]

Thanks for the response... but is seems your methods for doing most of this work are overly complex.


you're very right :D. that method was from when i was learning to cook with my wizard, and it does make for a very thorough and clean rom... but the extra steps are not needed, and the benefit is not there... way too complicated...

the .dsm files help describe the oem and sys packages, so editing them is only useful if you really change the rom and want everything to extract back out correctly from a kitchen. but for the most part, things are in the right spots anyways...

here's just a few comments about i've come to cook now:

i still copy all the rgu files into a directory and use pspad to search all when i remove a file. it doesn't take any longer and it sounds like your windows searching method. you'd be surprised at what references remain in disparate files. removing the extra reg entries is not about cleanliness or optimization, but if you've removed sqm, netcf or sqlcemobile, you know that they're ref'd all over the place and can cause problems if they're not removed (esp sqlcemobile and netcf).

every file i remove i also put into a new directory so that i can search in pspad for each (it would be nice to have an automated way to do this, but it's not too bad)

editing the initflashfiles.dat i do in notepad, and the hex edit of it is just to remove the two bytes at the beginning. if you look at the file structure with a hex editor you'll see FF FE (i think) at the beginning. the same with the hive files if you edit them as rgu files. you'd have to edit the dsm files with a hex editor, but there's no reason to touch them.

there is a major component here if you're not checking it... when the rom is cooked initially, the hive is built (i think it might be from just all the rgu files, but don't quote me on that, i imagine theres a "base" hive that is used by the developers that has extra information). BUT when you extract the rom, those hive files still have all the entries that you're removing with rgu files. so when the rom is cooked again, the rgus get dumped back in, but things aren't removed from the hive. this is very important with dialers, sqm, voice command, netcf, WMP, sqlcemobile, comm managers, and definitely arcsoft mms...

it's easy to make sure that you're editing everything out though with the way you are doing things. (if you don't already) use rgucomp to convert both hive files and put them in the directory that you search when you're removing rgu entries. there's a lot of stuff in there that should come out. also, if you've ever changed something like key mapping and then cook and wonder why it didn't really change, thats the hives at work...

i didn't really think about the fact that you said SIP as you are right about the tilt fix and the registry... not really sure how that's mapped, maybe tearing apart the pocketcm keyboard and looking at what types of files are the same with the stock sip? i'm guessing there's more .dll files that it uses...

i've been trying different dialers, i use the poorlyduck dialer right now, but i'm looking to have the opal dialer working well... also the big button dialers are pretty good, it might just come down to preference... at some point i'll decide on what the "ultimate" dialer is for me :cool:

i'm glad you started this thread and we've been able to compare cooking methods... if anyone else wants to talk about their way, it would be great to get more opinions, i haven't found much of this type of discussion on xda, so many of us "stumble in the dark" until something works :eek:

looking forward to your 2.0 rom, i'll play with it and let you know if i see anything... i'm going to have time to start cooking at night this week, and since you've done a very good job with the hard part :) it makes for the best base i've seen yet.

btw, sashimi is the sh**!

[ndn715]

SQLCE is for SQL connectivity (ODBC drivers I believe basically). What is SQM? I wasn't sure.
RealPlayer I keep along with cellular video because I find them a neat utility, although this can probably be made a separate CAB. Music ID for the same reason, although I haven't got any confirmation that this is a PAY service or not. It never prompts you when you are using it to accept any charge, and I don't have it on my service...yet it works.

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...


Possibly...I haven't looked into that one yet. Sometimes all a poll may be is to check a registry key..so in many cases that is such nominal overhead it couldn't be measured in any real terms.

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

[bengalih]

i still copy all the rgu files into a directory and use pspad to search all when i remove a file. it doesn't take any longer and it sounds like your windows searching method. you'd be surprised at what references remain in disparate files. removing the extra reg entries is not about cleanliness or optimization, but if you've removed sqm, netcf or sqlcemobile, you know that they're ref'd all over the place and can cause problems if they're not removed (esp sqlcemobile and netcf).


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.


editing the initflashfiles.dat i do in notepad, and the hex edit of it is just to remove the two bytes at the beginning. if you look at the file structure with a hex editor you'll see FF FE (i think) at the beginning. the same with the hive files if you edit them as rgu files. you'd have to edit the dsm files with a hex editor, but there's no reason to touch them.

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?


there is a major component here if you're not checking it... when the rom is cooked initially, the hive is built (i think it might be from just all the rgu files, but don't quote me on that, i imagine theres a "base" hive that is used by the developers that has extra information). BUT when you extract the rom, those hive files still have all the entries that you're removing with rgu files. so when the rom is cooked again, the rgus get dumped back in, but things aren't removed from the hive. this is very important with dialers, sqm, voice command, netcf, WMP, sqlcemobile, comm managers, and definitely arcsoft mms...

it's easy to make sure that you're editing everything out though with the way you are doing things. (if you don't already) use rgucomp to convert both hive files and put them in the directory that you search when you're removing rgu entries. there's a lot of stuff in there that should come out. also, if you've ever changed something like key mapping and then cook and wonder why it didn't really change, thats the hives at work...


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).

[bengalih]

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...


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.


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.

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.


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...

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.



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...

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.

[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 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?.

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 :)


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).

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 bitch 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

[ndn715]

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.

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...

[bengalih]

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 bitch 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

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 (http://forum.xda-developers.com/showthread.php?t=430234).

[ndn715]

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).

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...

[bengalih]

BRR 2.0 and associated SPF CAB Pack is now up. Check first posts.

[cushcalc]

. . . ROM should not include any customization which cannot be changed easily by the user. This includes, dialers, SIPs, etc that are cooked 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.

[bengalih]

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.

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.

[cushcalc]

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.

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.

[bengalih]

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.

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.

[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.

[ndn715]

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).

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...

[adstevenson]

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.

[adstevenson]

I also can't sync. my pc doesn't recognize my tilt.:mad:

[bengalih]

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.


I also can't sync. my pc doesn't recognize my tilt.:mad:


I think something else is going on with your device other than this ROM.
I did another clean flash to confirm your issues and I don't see them.

I can sync without any issue and I have no problems typing on any screen, owner included.

What SPL are you using? I am using the 3.56 Hard as that, I believe is the recommended one for this AT&T base.

I am going to flash with the original HardSPL and see if I have any issues like you describe.

[bengalih]

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.


I'm not sure what you're saying the issue is here ndn...

Do you mean that since nothing is mapped to button 6, I might as well map it to Comm Manager?

Currently, Comm Manager is available in Control Panel > Connections.

I always install MSVC after a flash, so I map that over to 6.

[adstevenson]

I think something else is going on with your device other than this ROM.
I did another clean flash to confirm your issues and I don't see them.

I can sync without any issue and I have no problems typing on any screen, owner included.

What SPL are you using? I am using the 3.56 Hard as that, I believe is the recommended one for this AT&T base.

I am going to flash with the original HardSPL and see if I have any issues like you describe.

Sorry, got everything going.
Thanks!

[ndn715]

I'm not sure what you're saying the issue is here ndn...

Do you mean that since nothing is mapped to button 6, I might as well map it to Comm Manager?

Currently, Comm Manager is available in Control Panel > Connections.

I always install MSVC after a flash, so I map that over to 6.

just usually that the comm mgr is mapped there, but i see it was mapped to voice command originally... i know you have a thing for it :) personal preference i guess, so no biggie.

i'm working on the dialer though, unless you have any ideas about it... just tested that the original rom exhibits the same behavior, so i just removed the dialer, testing...

EDIT: removing the dialer works well, and every dialer i tried besides opal work perfectly... btw, the stock dialer is grey and goes great with your theme bengalih :)
there's some file thats conflicting with the opal install, common files are VTKey.exe, waitingtone.wav, DPadMenu.dll, ddcall.dll... the dll's should stay, so more testing

[bengalih]

just usually that the comm mgr is mapped there, but i see it was mapped to voice command originally... i know you have a thing for it :) personal preference i guess, so no biggie.

i'm working on the dialer though, unless you have any ideas about it... just tested that the original rom exhibits the same behavior, so i just removed the dialer, testing...

EDIT: removing the dialer works well, and every dialer i tried besides opal work perfectly... btw, the stock dialer is grey and goes great with your theme bengalih :)
there's some file thats conflicting with the opal install, common files are VTKey.exe, waitingtone.wav, DPadMenu.dll, ddcall.dll... the dll's should stay, so more testing

It's actually mapped to PTT by default, not Comm Manager... but I think that's a good idea. No need to leave it sitting there by default... I will map it to Comm manager and then put in the PTT and MSVC cabs to remap it.

I had some weird issues with the dialer when I attempted to remove PTT...that might be causing you issues.

When I took out all of PTT I got like a half normal dialer/half skin look... basically you could see the contacts about 1/3 way down the screen (which is how it looks when no skin is present). It turned out that PTTServiceWrapper.dll had to remain in the ROM or the dialer wouldn't appear properly. Not sure if this is related to what you are doing, but it might help out.

[bengalih]

Ok, I have mapped the Comm Manager to the PTT button for the next release.

Something else I just noticed. My screen rotation from portrait to landscape was taking about 5 seconds. Going back to Portrait was only about 1 second. Last time I tested this it was taking only 1 second in either direction. I realized the last thing I did was pull out sliding sounds. So, indeed keeping sliding sound in serves to speed things up!

Sliding sound doesn't need to be enabled...but if the EXE and reg keys are absent it seems to be timing out looking for it. I will add this to the known issues, and I am probably going to cook Sliding Sounds back in for the next release, because I don't think anyone would choose to NOT have it if it means a 5 second screen rotation!

Also, I am interested in hearing any other tweaks, especially for performance that people recommend to be cooked in. Since registry entries are easily changed I don't mind cooking in a few entries that the end user can change/remove if they don't like.

[ndn715]

Something else I just noticed. My screen rotation from portrait to landscape was taking about 5 seconds. Going back to Portrait was only about 1 second. Last time I tested this it was taking only 1 second in either direction. I realized the last thing I did was pull out sliding sounds. So, indeed keeping sliding sound in serves to speed things up!

just verified that by adding it back in... problem solved. i'm not sure how the drivers call the thing, but i have seen it work very well without the control panel, so i'm guessing that the icon is usually just set to be hidden... sorry for the confusion on this...


Also, I am interested in hearing any other tweaks, especially for performance that people recommend to be cooked in. Since registry entries are easily changed I don't mind cooking in a few entries that the end user can change/remove if they don't like.

hopefully others will chime in too :) one reg tweak i always wonder about is the power saving settings... i usually turn them all on (i think most of us do), but stock roms always have them off and some of my coworkers run the stock 6.1 and generally have the same battery life with similar usage...

can't get the opal dialer cab (all three different ones) to install, but other dialers work fine, so i might just cook the oem pack in for my own use... it's bugging me though, because i can install the dialer on most other roms. do you know if anything gets logged when an install was unsuccessful?

[bengalih]

just verified that by adding it back in... problem solved. i'm not sure how the drivers call the thing, but i have seen it work very well without the control panel, so i'm guessing that the icon is usually just set to be hidden... sorry for the confusion on this...



hopefully others will chime in too :) one reg tweak i always wonder about is the power saving settings... i usually turn them all on (i think most of us do), but stock roms always have them off and some of my coworkers run the stock 6.1 and generally have the same battery life with similar usage...

can't get the opal dialer cab (all three different ones) to install, but other dialers work fine, so i might just cook the oem pack in for my own use... it's bugging me though, because i can install the dialer on most other roms. do you know if anything gets logged when an install was unsuccessful?

Which power savings in particular... describe as if setting them from Control Panel.

I'm doing some more work on the dialer stuff now... Trying to pull out the entire dialer (actually trying to transplant the AT&T dialer over to HTC ROM). I'm confused how some of these dialer CABs function, because it seems many of them try to replace files which are cooked into the ROM and therefore would not be able to install properly.

[ndn715]

Which power savings in particular... describe as if setting them from Control Panel.

just the ones when you start up Advanced Config, like sd card, activesync, l2tp, etc... they all have power saving modes that are usually turned on in custom roms and i've always turned them on because they say "power management" :)


I'm doing some more work on the dialer stuff now... Trying to pull out the entire dialer (actually trying to transplant the AT&T dialer over to HTC ROM). I'm confused how some of these dialer CABs function, because it seems many of them try to replace files which are cooked into the ROM and therefore would not be able to install properly.


yeah i really don't get what is getting in the way of the opal dialer tho... if the cab is just a straight skin (like the minimal dialer with graphics only) it usually just installs the new graphics and then points the registry to them. more involved dialers (like the opal) write crap all over the place and i think even some registry settings during install can mess it up in addition to trying to overwrite cooked files.

i think the phone module from the stock rom is hardcoded to use a certain kind of skin. when i use the opal oem pack and remove the duplicate stock files, i kind of get the skin at the top, but the buttons pull up as the stock dialer. still looks like this:

http://forum.xda-developers.com/showpost.php?p=2707191&postcount=86

it just doesn't make sense if i've replaced every file i thought was associated with the phonecanvas. must be missing something, so im going through the cab's install package and trying to see where it would hiccup...

edit: looking at the opal thread and thinking about the fact that this still has come att customizations in it (provxml), security settings are probably to blame... heading in that direction.

[bengalih]

yeah i really don't get what is getting in the way of the opal dialer tho... if the cab is just a straight skin (like the minimal dialer with graphics only) it usually just installs the new graphics and then points the registry to them. more involved dialers (like the opal) write crap all over the place and i think even some registry settings during install can mess it up in addition to trying to overwrite cooked files.

i think the phone module from the stock rom is hardcoded to use a certain kind of skin. when i use the opal oem pack and remove the duplicate stock files, i kind of get the skin at the top, but the buttons pull up as the stock dialer. still looks like this:

http://forum.xda-developers.com/showpost.php?p=2707191&postcount=86

it just doesn't make sense if i've replaced every file i thought was associated with the phonecanvas. must be missing something, so im going through the cab's install package and trying to see where it would hiccup...

edit: looking at the opal thread and thinking about the fact that this still has come att customizations in it (provxml), security settings are probably to blame... heading in that direction.


I don't think it's the security settings. What is the problem still with the dialer? Link me to cab and I can install it and see what you are getting.

I just successfully ripped out the HTC dialer from the HTC 6.1 Official and transplanted the AT&T dialer over to it. Infact I have made a cab of both dialers and can switch between them.

I am thinking of moving over to an HTC base as alot more people I think will use it. Also there are some weird backlight issues (like a double press of power required to come out of sleep) that seem to be a problem with the official AT&T 6.1 base I used. They aren't a big deal..but they kind of bother me and I don't know of these issues with the HTC base.

Speak up if you know of any problems with the Official 6.1 HTC that are above and beyond what the AT&T 6.1 has.

[drunkbastard]

Curious - which SPL works with this? I have 3.56Hard now. What I thought was a 3G fix was just the 3G failing slower than usual, just trying to get everything set right and hope it doesn't explode before AT&T releases the Fuze or Mirage.

Thanks

[bengalih]

Curious - which SPL works with this? I have 3.56Hard now. What I thought was a 3G fix was just the 3G failing slower than usual, just trying to get everything set right and hope it doesn't explode before AT&T releases the Fuze or Mirage.

Thanks

I'm using the 3.56 as I believe that the official AT&T base shipped with 3.56.

[ndn715]

I don't think it's the security settings. What is the problem still with the dialer? Link me to cab and I can install it and see what you are getting.

I've been working with the cabs from the Opal thread.

http://forum.xda-developers.com/showthread.php?t=430354

Probably not the security settings as there are posted versions that are signed and they still don't work. I tried replacing the dialer from other roms and didn't get very far... This and the double press wake up are the only things I see wrong with this version, and both are problems with the official ATT release.


I just successfully ripped out the HTC dialer from the HTC 6.1 Official and transplanted the AT&T dialer over to it. Infact I have made a cab of both dialers and can switch between them.

sweet, I've never been able to do that... i'd be curious to see your cabs if that's cool... i wonder if using the htc dialer allows the install.


I am thinking of moving over to an HTC base as alot more people I think will use it. Also there are some weird backlight issues (like a double press of power required to come out of sleep) that seem to be a problem with the official AT&T 6.1 base I used. They aren't a big deal..but they kind of bother me and I don't know of these issues with the HTC base.

sounds good to me, it seems like ATT did some funky stuff with their version, and the HTC build should be a very stable base as well... i'm going to try working with the last WWE HTC version...

EDIT: stock htc rom shows the same behavior, with the white background and stock letters... at least for three opal cabs, including the security settings. im going to compare the dump with dk's kitchen as that one works...

[bengalih]

New AT&T Build is up, as well as brand new HTC build.

Lots new.

Will be upping the SPF CAB Pack for the HTC build shortly, when my internet bandwidth comes back!

[daigoro64]

New AT&T Build is up, as well as brand new HTC build.

Lots new.

Will be upping the SPF CAB Pack for the HTC build shortly, when my internet bandwidth comes back!

What can I say: thank you very much indeed for all your work, sir! :)

[Moe5508]

Thanks indeed - time to join this fray!!! fantastic work as usual Bengalih especially for pulling the HTC builds through into your releases!

[bengalih]

SPF CAB pack for HTC is now up.

[ralpheboyo]

The best thing after sliced bread!!!!! NIce work....keep it up...r

will report my findings after 48 hrs...in the mean time some screen shots just to show how easy it really is to create your rom......(feel like a chef and in reality i am just a flashaholic...thxs once again!!!!)

[gmitch]

Thank you for Sashimi! What a time saver. And delighted to see it work so well with BRR Roms, (what should I expect).

I like your guiding principles for cooking. With Sashimi it is no problem adding in what I want.

You are a rare chef! I appreciate your approach, "If you appreciate my efforts...make the world a better place." Thank you for your hard work and may you be richly blessed.

Flashing 2.5 right now. Can hardly wait to see how it works.

[JFX]

DUDE. You are awesome.

THis is what i was looking for, then I noticed your original stock/lite thread where you were starting up curious and newborn on the subject. Then I saw you have these roms, killer man.

I am ultra new on custom roms but I just did my first, a dutty rom, the latest, and though it's nice, it's loaded with crap, so I instantly knew all I wanted was the fastest litest simplest to use, least amount of apps yet still basic functions and reg tweaks, and low and behold we got you out there doing what I want, and many others it want it seems)..

Thanks for your interest and work, flashing NOW.

[dma1965]

When I try to run Cingular Video on this, I get an error "Media File Cannot Be Read". Version 2 worked fine with the Cingular Video CAB.

Version 1.0 works perfectly in nearly every way. I initially had a problem when I installed your Office installer, where if tried to open an office document from an email I would get an error. It seems that your installer was not making the file association, because once I used Resco File Explorer to set the file association, it worked fine. Alternatively, Office works flawlessly if I install the "official" CAB.

In any event, I have 2 Tilts, and I have kept version 1.0 on one of them, and have tried all other variants of the RAW Roms and the Roms of other chefs as well, and your version 1.0 ROM is truly the most stable ROM I have used which includes a fully working Cingular Video installation. It is also the first ROM I have EVER used where I can literally go for days without a need for a reboot.

I almost deemed the version 2.5 ROM perfect, but the Cingular Video error had to rear its ugly head.

Nonetheless, this is only my opinion and thank you for the great work.

[veyron3]

I am unable to run Schap's Config tool or Home Customizer, I get the error the application is not signed with a trusted certificate. I have checked my security policies in the registry and its set to allow all. I using Schaps_AdvancedConfig_v2.0.2.0.CAB
and
HHCv10Final.CAB both are installed to the phone memory not SD card.

[ralpheboyo]

I am unable to run Schap's Config tool or Home Customizer, I get the error the application is not signed with a trusted certificate. I have checked my security policies in the registry and its set to allow all. I using Schaps_AdvancedConfig_v2.0.2.0.CAB
and
HHCv10Final.CAB both are installed to the phone memory not SD card.

....for shaps you need netframework 3.5 on device....

http://www.4shared.com/file/65529618/81e5eccd/NETCFv35wmarmv4i.html

[veyron3]

....for shaps you need netframework 3.5 on device.... DOH!! I Read that!! Thanks!!

[bengalih]

When I try to run Cingular Video on this, I get an error "Media File Cannot Be Read". Version 2 worked fine with the Cingular Video CAB.

Version 1.0 works perfectly in nearly every way. I initially had a problem when I installed your Office installer, where if tried to open an office document from an email I would get an error. It seems that your installer was not making the file association, because once I used Resco File Explorer to set the file association, it worked fine. Alternatively, Office works flawlessly if I install the "official" CAB.

In any event, I have 2 Tilts, and I have kept version 1.0 on one of them, and have tried all other variants of the RAW Roms and the Roms of other chefs as well, and your version 1.0 ROM is truly the most stable ROM I have used which includes a fully working Cingular Video installation. It is also the first ROM I have EVER used where I can literally go for days without a need for a reboot.

I almost deemed the version 2.5 ROM perfect, but the Cingular Video error had to rear its ugly head.

Nonetheless, this is only my opinion and thank you for the great work.

Thanks dma. I am going to look into the cingular video and see what's up. There is no reason why it should need to be cooked in like in the 1.0, so I will see what's needed to get it running right.

Also, does the office problem still exist on 2.5? I think there was an association issue I fixed in the CAB.

Make sure you download the newest CAB pack with the 2.5 release.

I am going to test both again and report back.

[ndn715]

bengalih, thanks for the htc version... these builds are great and stable for most users, but i keep running into roadblocks with them when cooking in new packages. so i'm using the 3.29 rom (build 20275.1.3.3) as a base and cooked a personal one with all the opal stuff... it's running great so i think i'll stick with that for now, i was just trying to get a good base for my personal use anyways... let me know if you ever have questions, hopefully i'll actually have good input in the future :)

[tinmanuk]

Hi there - like you much prefer original roms but i do like manilla. uisng a cooked rom at present as i cant seem to find a 'good' cab for manilla. is this something you could add here as I guess a lot of other users would like an 'original rom' but also the latest look of manilla.

thanks

[bengalih]

bengalih, thanks for the htc version... these builds are great and stable for most users, but i keep running into roadblocks with them when cooking in new packages. so i'm using the 3.29 rom (build 20275.1.3.3) as a base and cooked a personal one with all the opal stuff... it's running great so i think i'll stick with that for now, i was just trying to get a good base for my personal use anyways... let me know if you ever have questions, hopefully i'll actually have good input in the future :)

What types of issues are you having? This is a very clean strip...I leave all dsm, rgu, provxml, etc in tact. The only thing I can think of is that I removed some files for things like .NET or the dialer which might be needed by what you are cooking in.

You can see all the removed/modified files if you look at the removed file list.

So, let me know, I'm curious if it is something with these ROMs, or whether you have a problem cooking these things in general.

[JKingDev]

I have a question. Does the HTC Camera 6.8 CAB install without a problem on this ROM? Cant wait to try this with SASHIMI!

[bengalih]

When I try to run Cingular Video on this, I get an error "Media File Cannot Be Read". Version 2 worked fine with the Cingular Video CAB.

Version 1.0 works perfectly in nearly every way. I initially had a problem when I installed your Office installer, where if tried to open an office document from an email I would get an error. It seems that your installer was not making the file association, because once I used Resco File Explorer to set the file association, it worked fine. Alternatively, Office works flawlessly if I install the "official" CAB.

In any event, I have 2 Tilts, and I have kept version 1.0 on one of them, and have tried all other variants of the RAW Roms and the Roms of other chefs as well, and your version 1.0 ROM is truly the most stable ROM I have used which includes a fully working Cingular Video installation. It is also the first ROM I have EVER used where I can literally go for days without a need for a reboot.

I almost deemed the version 2.5 ROM perfect, but the Cingular Video error had to rear its ugly head.

Nonetheless, this is only my opinion and thank you for the great work.

dma. I just tested CV on 2.5 and it works fine. Please ensure you download the new SPF CAB Pack for 2.5. Even though the files may look the same, the CABs in the 2.5 pack have been updated with any issues I have found while making 2.5 ROM better.

I guarantee that if you use 2.5 along with the CV CAB from the latest 2.5 SPF pack that it will work!

[ndn715]

What types of issues are you having?
So, let me know, I'm curious if it is something with these ROMs, or whether you have a problem cooking these things in general.

i can cook everything just fine with this rom, it works great being cleaned up... but i'm lovin the opal dialer and have not been able to cook it in (or fully remove phonecanvas during cooking and then cab after) without getting this:

http://forum.xda-developers.com/showpost.php?p=2725749&postcount=173
:confused:

and pretty much gave up... there's a lot of great dialers out there, but i like this one. and if i can cook with another build thats pretty close to spec (not crazy xips or builds that we sometimes play with) then it's good enough for me.

i'm not sure why the opal dialer wont work with the stock rom, but i've checked all of the files in the phone folders and oem files that i know are associated with the phone. what's strange to me is that the opal dialer is more than a just skin, with different and additional menu bar icons, but those parts install fine, its just the phone canvas part that doesnt work, and if you boot up without a sim, you get a different stock dialer, so it's very thorough with replacing things. i haven't been able to find any file or registry differences between these roms and the ones where it installs just fine and got tired of looking. i even went though the xml install file and files to compare and got no where... i'm sure it will be solved at one point, it just doesnt make any sense...

[bengalih]

i can cook everything just fine with this rom, it works great being cleaned up... but i'm lovin the opal dialer and have not been able to cook it in (or fully remove phonecanvas during cooking and then cab after) without getting this:

http://forum.xda-developers.com/showpost.php?p=2725749&postcount=173
:confused:

and pretty much gave up... there's a lot of great dialers out there, but i like this one. and if i can cook with another build thats pretty close to spec (not crazy xips or builds that we sometimes play with) then it's good enough for me.
...

Can you link me to the ROM that you are successfully cooking the opal dialer into? Is it a stock ROM (not "official", but stock) or is it cooked at all?

Also, are you using just the OEM files that are provided in the opal dialer thread?

Detail for me the process you used. Did you just extract the ROM, add in the OEM, cook and get it working?

Probably best to move this to a PM, and I will take a look at why the dialer is working with that ROM, and maybe get it working on this one.

[bengalih]

Thanks to ralpheboyo for pointing out an issue with the camera in the HTC ROM.

Please download the camera fix cab on the HTC ROM post!

[dma1965]

dma. I just tested CV on 2.5 and it works fine. Please ensure you download the new SPF CAB Pack for 2.5. Even though the files may look the same, the CABs in the 2.5 pack have been updated with any issues I have found while making 2.5 ROM better.

I guarantee that if you use 2.5 along with the CV CAB from the latest 2.5 SPF pack that it will work!

Correct you are, sir !!! It does work perfectly. I was using the version 2 cab before. Version 2.5 works.

Another thing I noticed is that it seems you have been able to accomplish the impossible with your Windows Live Cab (from the HTC CAB collection). With the CAB I was using before, I could not get MSN Messenger to work properly (I could not tap on the instant messenging portion of a contact and have it open MSN messenger). Your CAB works as it should.

I have to say that version 2.5 is perfect!

[bengalih]

Correct you are, sir !!! It does work perfectly. I was using the version 2 cab before. Version 2.5 works.

Another thing I noticed is that it seems you have been able to accomplish the impossible with your Windows Live Cab (from the HTC CAB collection). With the CAB I was using before, I could not get MSN Messenger to work properly (I could not tap on the instant messenging portion of a contact and have it open MSN messenger). Your CAB works as it should.

I have to say that version 2.5 is perfect!

Did you download the latest version of Live that I mention in the Tips section of the ROM? I assembled that CAB as well and I believe it should all work correctly and is even newer than the version that ships with HTC (the one available in my CAB pack).

[dma1965]

Did you download the latest version of Live that I mention in the Tips section of the ROM? I assembled that CAB as well and I believe it should all work correctly and is even newer than the version that ships with HTC (the one available in my CAB pack).

I do not care for the CAB which installs both Windows Live and Live Search. The CAB from the link you provide installs an older version of Live Search than I had on my device (yours is 3.0 and the newest is 3.5). I also prefer to install Live Search on my MicroSD and Windows Live in main memory.

Nonetheless, the "outdated" version in the HTC CAB pack works perfectly.

[sirooga]

Can anyone confirm on the ATT version if Button 6 and Button 6(hold) are cooked in? Or if not cooked in will registry changes stick? I don't want to flash this ROM only to find out those won't work. Thanks :)

[bengalih]

Can anyone confirm on the ATT version if Button 6 and Button 6(hold) are cooked in? Or if not cooked in will registry changes stick? I don't want to flash this ROM only to find out those won't work. Thanks :)

By default the AT&T has button 6 mapped to Comm Mgr and 6(hold) to record. If you install MSVC or PTT it will map button 6 to that (which can be changed back if you like).

[JFX]

Hey beng thanks again for your work, your ATT rom is my default now. Love the splash screen too. But an issue, i read the previous posts but didn't notice anything said on it, for the messaging default app, for aim yahoo and msn which was on my 6.1 rom from att, isn't in the pack for the ATT, am I missing it? I probably am just overlooking it.

Also, i've seen some stuff said on HTC version of your raw rom is better than the ATt one? I haven't tried but what do you suggest being the creator of both rom packages, Begalih? or anyone

THanks for your work.

[bengalih]

Hey beng thanks again for your work, your ATT rom is my default now. Love the splash screen too. But an issue, i read the previous posts but didn't notice anything said on it, for the messaging default app, for aim yahoo and msn which was on my 6.1 rom from att, isn't in the pack for the ATT, am I missing it? I probably am just overlooking it.
I just posted it for you on the SPF CAB Pack post. Please be advised that it requires NetCF installed in order to work.


Also, i've seen some stuff said on HTC version of your raw rom is better than the ATt one? I haven't tried but what do you suggest being the creator of both rom packages, Begalih? or anyone
THanks for your work.

The AT&T ROM has a few minor issues that it inherited from the official ROM. These have to do with backlight issues. Occassionally, when you press the power button the screen will flicker on and off real quick and you will need to press it again. Also, if you are using password protection (as happens alot if you are syncing to a corporate exchange server) there are some issues with the backlight always being set back to 10 seconds. If you aren't seeing these issues, or they don't bother you then I would recommend sticking with the AT&T ROM if you are a Tilt user.

[JFX]

Excellent, wicked fast reply thank you. I have noticed the backlight issues but it doesn't really bother me at all. Thank you for the messaging cab!

[JFX]

Another quick question, I noticed a user in another thread asking about adding icons to the today screen, which I'd like to add a couple. Someone answered him saying you go into file explorer and tap-hold an exe to add a shortcut to the today screen. But that's not possible with the rom, is this bogus or is that possible somehow?

[bengalih]

Another quick question, I noticed a user in another thread asking about adding icons to the today screen, which I'd like to add a couple. Someone answered him saying you go into file explorer and tap-hold an exe to add a shortcut to the today screen. But that's not possible with the rom, is this bogus or is that possible somehow?

There is no way to add a shortcut to the today screen. If perhaps some special today screen plugin is used maybe that functionality exists. Also maybe with something like the new Manila interface it is possible. But it isn't possible in the stock AT&T or HTC 6.1 ROMs, nor my versions of them.

The only thing you can add to the today screen is a plugin, which you do from Settings > Today > Items.

[selyb]

I really wish I had read through this thread earlier :-/

I am completely against including the radio in the rom.
I do understand the reasoning but consider it this way: it is much easier for an end user to flash the rom and flash a separate radio than to remove the radio before flashing.

About cooking in tweaks and optimizations: I think you are slightly veering away from your original idea. I believe that if it doesn't have to be cooked in, then it shouldn't be. I think you should release advised and/or commonly used tweaks/changes separately.

[bengalih]

I really wish I had read through this thread earlier :-/

I am completely against including the radio in the rom.
I do understand the reasoning but consider it this way: it is much easier for an end user to flash the rom and flash a separate radio than to remove the radio before flashing.

About cooking in tweaks and optimizations: I think you are slightly veering away from your original idea. I believe that if it doesn't have to be cooked in, then it shouldn't be. I think you should release advised and/or commonly used tweaks/changes separately.

The radios are no longer included which is why I link them separately in the thread.

I disagree both about including tweaks and the fact that it is in contradiction with my ideas.

Cooking in registry tweaks to improve the performance (in any way) of a ROM I believe are fine and don't violate any principles I offer provided that:
1) Whatever tweaks are done are included in the release notes, so users are aware.
2) Whatever tweaks are done can easily be changed back by the user should they not want them.

The multiple data sessions hack that I include is a great example. There is no good reason why multiple data sessions should not be enabled. It is disabled by AT&T (for whatever reason), but it has only benefits and no drawbacks.

I believe that certain tweaks must be looked at carefully if they have a downside and if so should be wary of inclusion of them.

[selyb]

Well, I guess I should have opened the rom before I hit the reply button :-p

I should have known better than to post around here. I feel like one of those people I look at and call an idiot for trying to jump into a conversation as if he/she know everything about it and then is shown that he/she knows nothing about what is going on.

Just for statistics though, I have been using TNT Vanilla 19202 for several months now. I will try the AT&T base and if I have issues, I will try the HTC base.

[JimmyMcGee]

I'm not sure what's going on with this thread.

I am Locking it until The Original poster PMs me telling me whether the change was intentional or there was a password "incident"