+Feb 5+ *SSK 1.2 Stable* {CE OS 21109} Kitchen and ROM

[FormerPalmOS]

Originally Posted by scrosler

Want me to make your head spin??????????

Watch this....
mxipupdate_zzPIED_100.provxml - ROM version
mxipupdate_remove_MS_Taskmanger_100.provxml - Remove Task Manager
mxipupdate_oemoperators_107.provxml - Manila type settings
mxipupdate_oemoperators_104.provxml - phone settings
mxipupdate_oemoperators_102.provxml - today screen settings
mxipupdate_oemoperators_100.provxml - start menu settings
I have every single XML and RGU listed like this... I had to do it to keep track.... Man there is a lot of sh1t in there to play wit. I cant even keep up!

Could you post that list as a text file?

[oldman]

Originally Posted by TwoDawgs

Once again Bob is always thinking!

Thanks for the complliment. Always appreciated.
One additional thought for Scott. Someone mentioned about adding WM6.5 to the current kitchen. I have no problem with that except that such items like that should be clearly identified as "Experimental" or "Early Beta". Betas that people run regularly with no problems could be labeled "Stable Beta", and released items could be labeled Released with the version number. With the version number visible, someone could easily search for an updated version BEFORE flashing.

Bob

[FormerPalmOS]

Originally Posted by bast525

SCOTT - I'm hoping... man I hope to God I can get you to take a look at this. One thing I have HATED about the Touch Pro since I got it, and even your ROM didn't fix, is that for whatever reason, the graphics drawing/rendering in Landscape mode is FAR worse than when the phone is in Portrait mode. I had noticed it in Opera Mobile and Mini and a few other apps, and then confirmed it using some benchmarking software (the Bitmap Draw test in SK Tools in particular). The phone renders some 30% slower in Landscape mode! This is noticeable as a drop in frame rate and as Vsync tearing.

At any rate, I ran across a thread on XDA that is about this specific issue, and a few people posted how a new custom ROM from Da_G specifically for the AT&T Fuze, had new drivers that finally fix this problem. Not only is it claimed to fix the Landscape redraw, but it is supposed to be a nice boost in overall graphics performance. I sent him a PM to ask about getting the drivers, but he said the main file which fixes this, ddi.dll (which is from new Diamond official ROMS, and he also apparently uses some Blackstone/Touch HD files), is now part of the XIP and is not a file you can simply post for people to write over their existing driver with. He did say that the file is easily extracted from his XIP for cooking into other custom ROMS.

I wanted to ask... no... BEG... if there is any possible way you can get this ddi.dll (and other graphics drivers such as d3dm_ati.dll and disptools.dll) into your kitchen so that we too can enjoy the increased graphics performance, and, more importantly, no more huge loss in performance in Landscape mode. Is there ANY way you can do this? I would be glad to beta test this... until now I basically treat my TP like a Diamond... I never use the hardware keyboard because the performance in landscape is so bad!

Putting it in the XIP won't make it any faster by itself. Turning it into a module will. Currently, the default d3dm.dll is a module. If you install a cab with a new .dll (like d3dm_ati.dll) it probably won't be any faster since that isn't a module. You would need to make it a module, fit it into the virtual memory space, and cook it into the ROM. Assuming the default d3dm.dll, the d3dm_ati.dll and Samsung Omnia driver (d3dmxsc50pb.dll) are all roughly the same size, you should modularize all of them into the same VM space, then in the kitchen select only one.

But correct me if I am wrong - D3D is for 3D rendering only. What we need to speed up is 2D rendering - and that's DDRAW.DLL (again, already a module). We need a faster DDRAW.DLL. Then again, TF3D makes mostly calls to the 3D rendering DLL (as specified in the registry), not the 2D... So really we need both?

[Kamokazi]

Originally Posted by FormerPalmOS

Putting it in the XIP won't make it any faster by itself. Turning it into a module will. Currently, the default d3dm.dll is a module. If you install a cab with a new .dll (like d3dm_ati.dll) it probably won't be any faster since that isn't a module. You would need to make it a module, fit it into the virtual memory space, and cook it into the ROM. Assuming the default d3dm.dll, the d3dm_ati.dll and Samsung Omnia driver (d3dmxsc50pb.dll) are all roughly the same size, you should modularize all of them into the same VM space, then in the kitchen select only one.

But correct me if I am wrong - D3D is for 3D rendering only. What we need to speed up is 2D rendering - and that's DDRAW.DLL (again, already a module). We need a faster DDRAW.DLL. Then again, TF3D makes mostly calls to the 3D rendering DLL (as specified in the registry), not the 2D... So really we need both?

He is talking about 2D Rendering in Landscape mode...currently there is a major performance hit. And there are some people that have cooked in a newer dll that makes it much faster...ddi.dll from a new Diamond ROM.

[oldman]

Originally Posted by FormerPalmOS

Scott,

I've been studying the performance some more now with the modified XIP. The next low-hanging fruit is the number of files in the \windows directory. With no caching, when you access any file in the Windows directory (or when an application needs a DLL), WM loads the directory from flash, then starts at the top looking for what you need. It isn't stored alphabetically or anything - it's a straight sequential search. The average time of the search is directly related to the number of files in the directory. Once found, a file or module is copied from IMGFS, decompressed and loaded into the pagepool.

Now, you can increase the pagepool size to reduce thrashing within the pagepool, and I can increase the FAT and directory meta-data cache to speed up this overall process - but all is at the expense of memory.

As an alternative, it would be worthwhile to figure out what applications installed in your OEM folders could be installed to directories (\Program Files\{appname} for example) instead of to \windows. Manilla for example has tons of files loaded to \windows. Microsoft is guilty as well - there are a boatload of resources (bitmaps, .pngs, etc) all loaded to Windows.

Note - this also explains why a stripped ROM is so much faster - far fewer files to search through in the \Windows directory.

Also - for chefs - fewer apps go for smaller pagepool (6 would be fine for a totally stripped ROM). Loaded go for 12. Anything bigger than 12 and you are asking for memory problems.

Oh - Scott, BTW - nuke HTC_CM_Guardian from your OEM folders (I already killed it so I can't go searching for it to tell you where to remove it). THis file monitors and resets certain settings back to "carrier stock" - not sure which ones, but it is always resident taking up memory and I don't like that. No stability problems with it killed so-far.

BTW - two other memory hogs that can be killed are SIP_GTAPP and QuickGPS. The SIP app is responsible for the keyboard pop-up that allows you to change pop-up keyboards. It is possible to default SIP to one keyboard (I use Full QWERTY) then blow away the bootlauncher key that auto-starts it. QuickGPS can only be prevented from starting by killing the bootlauncher GPSAUX.DLL service - which also kills the underlying functionality QuickGPS brings. If you want fast locks, this is unfortunately a necessary evil. HTC could have easily split this into two programs so the resident one is much smaller - but they did not.

Fantastic Analysis - i have always felt that app makers should always keep their apps in a "sandbox" (their own folder) and not default everything to either the Windows or System directory. (is the same scenerio applicable to the desktop computer, or is this "search technique only applicable to a Mobile device?)

Bob

[b0bzuruncle]

This ROM rocks especially with the simple kitchen...

It made all the difference between keeping the phone or returning it to VZ

A couple of possible issues

I noticed that the long end hold to lock ceases working when a password is set on the phone

How do you add foreign cities to the weather choices?
Registry hack or is there a file on boot that's loaded?

How do I edit/remove e-mail accounts that don't appear in the menu?

As I have been backing up and restoring settings using Sprite Backup, I've noticed that upon restore, the mail screen will have more than one account that cannot be accessed/edited/deleted from the menu>accounts>accounts

Suggestions?

Thanks!

[phattooth]

Originally Posted by FormerPalmOS

Could you post that list as a text file?

Seconded!
pretty please!

[oldman]

Originally Posted by stanglifemike

I agree dimitri, Sprint Radio 1.11 is giving me the best battery life as well.

Originally Posted by dimitri

For all those that are wondering if they should use the newest Radio with this ROM I say yes. I had the 1.04 telus and tried this ROM. Battery went quick. Then I flashed to the 1.11 Sprint Radio and now my battery is the best it has ever been with this ROM or any other ROM. Just wanted to share my thoughts.

Can you show me some data. All tests I have run say differently. (See Post #221, Pg 23)

Bob

[oldman]

Originally Posted by b0bzuruncle

How do you add foreign cities to the weather choices?
Registry hack or is there a file on boot that's loaded?

Suggestions? Thanks!

Read back...I answered this question in 2 earlier posts in this thread

Bob

[b0bzuruncle]

Sorry... I was being a bit lazy

Thanks