yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] adstevenson:
Sorry, got everything going.

Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
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
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
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?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
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" :)

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://xdaforums.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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] drunkbastard:
SPL?

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
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I'm using the 3.56 as I believe that the official AT&T base shipped with 3.56.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
I've been working with the cabs from the Opal thread.

http://xdaforums.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.

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.

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...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] daigoro64:
What can I say: thank you very much indeed for all your work, sir! :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Thanks indeed - time to join this fray!!! fantastic work as usual Bengalih especially for pulling the HTC builds through into your releases!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
SPF CAB pack for HTC is now up.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ralpheboyo:
Errhhhhh

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!!!!)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dma1965:
Still Like 1.0 Best

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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ralpheboyo:
netframework

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

http://www.4shared.com/file/65529618/81e5eccd/NETCFv35wmarmv4i.html
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] veyron3:
DOH!! I Read that!! Thanks!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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 :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] tinmanuk:
manilla

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
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ndn715:
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://xdaforums.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...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dma1965:
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!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dma1965:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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 :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I just posted it for you on the SPF CAB Pack post. Please be advised that it requires NetCF installed in order to 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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
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.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 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.
[Treble-Enabled Device Questions and Answers] dilarakhatun:
Please anyone suggest me some best ROM for a64-ab.
[Treble-Enabled Device Questions and Answers] Hsnmastoor:
dot os 5.1

find your devices | dotOS

dotOS | HomePage

A beautiful custom ROM based on AOSP, which endeavors the essence of Simple, Unique, Secure.

www.droidontime.com
[Treble-Enabled Device Questions and Answers] Hsnmastoor:
May - dotOS v5.1 Mega Release

dotOS 5.1 release - May Security patches, New UI, FaceUnlock, Applock and much more

blog.droidontime.com