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

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

[Kamokazi]

Originally Posted by FormerPalmOS

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.

So what you are saying...would it be beneficial to use as stripped a ROM as possible and install cabs instead of OEMing the files? So they install to Program Files and not Windows? Or is there a way to OEM them in and install to an alternative directory?

Also, can some basic WinMo programs be moved out of the Windows directory and still work?

[FormerPalmOS]

Originally Posted by Kamokazi

So what you are saying...would it be beneficial to use as stripped a ROM as possible and install cabs instead of OEMing the files? So they install to Program Files and not Windows? Or is there a way to OEM them in and install to an alternative directory?

Also, can some basic WinMo programs be moved out of the Windows directory and still work?

Most programs originally written to be installed as a cab will install their files to something in \Program Files. When you turn them into OEMs, unless you take the time to build an initflashfiles.txt to move them, they end up in \Windows. I personally strip the ROM and install everything as a cab after the fact. Not to mention that for things that can be updated, it's much easier to update a cabbed in app vs. baked in.

On moving some WinMo apps out of \Windows, a properly written app may require a DLL but should check \Windows for that DLL instead of checking . If it checks ., it may fail unless you also move said DLL to wherever you are moving the app.

I'd look at apps that have a boatload of ancillary files (like HTC Keyboard) as things to move - but then again, HTC Keyboard was never designed to be installed as a CAB - so moving it could have issues.

Sorry - not a terribly useful response.

[Kamokazi]

Originally Posted by FormerPalmOS

Sorry - not a terribly useful response.

Not at all...you pretty much gave me the exact answers I was looking for.

[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

[thefiverivers]

Ok so installed the TLR manilla. I noticed a lot of slowdown versus just the regular TF3D in the standard ROM, dunno if that is normal or not. I really love the flip clock! Will try the other themes as well. So as i am typing this there is a definite slow down in opening things and what not, almost like the stock ROM pre-flash, which is kinda weird. Did i do something wrong scotty? I soft reset too but to no avail. Im gonna uninstall and see if there is a difference.

Edit: Another thing i noticed with the TLR manilla was that the touch sensitivity was vasty inferior, even after i re-callibrated. It seemed like i had to push so hard with my finger and stylus. Do not know if i am just tired or that was really happening lol. Just uninstalled TLR and gonna see if things speed up and what not.

Edit 2: ok things are definitely faster after uninstalling TLR and going back to the stock TF3D that came with the standard ROM. The sensitivity is also back to being normal. Very odd.
Also did the soft reset to see if the "start" clicking sound went away and its still there. Dunno. Gonna try the other themes now.

[scrosler]

Originally Posted by thefiverivers

Ok so installed the TLR manilla. I noticed a lot of slowdown versus just the regular TF3D in the standard ROM, dunno if that is normal or not. I really love the flip clock! Will try the other themes as well. So as i am typing this there is a definite slow down in opening things and what not, almost like the stock ROM pre-flash, which is kinda weird. Did i do something wrong scotty? I soft reset too but to no avail. Im gonna uninstall and see if there is a difference.

Edit: Another thing i noticed with the TLR manilla was that the touch sensitivity was vasty inferior, even after i re-callibrated. It seemed like i had to push so hard with my finger and stylus. Do not know if i am just tired or that was really happening lol. Just uninstalled TLR and gonna see if things speed up and what not.

Nope you keyed in on it firs time.

TLS Manila is SLOW by far. No questions asked. Also reports of keyboard lag and all sorts of stuff..... Yeah, thats normal. Sad to say. Someone put up a new version that compressed all the files to make it faster. HOWEVER: If you cook it in its not as bad! Im not going to go into the Why's.... But just trust me on this ;c)

Dont uninstall.. Hard reset man... It will be faster and more stable

[thefiverivers]

Originally Posted by scrosler

Nope you keyed in on it firs time.

TLS Manila is SLOW by far. No questions asked. Also reports of keyboard lag and all sorts of stuff..... Yeah, thats normal. Sad to say. Someone put up a new version that compressed all the files to make it faster. HOWEVER: If you cook it in its not as bad! Im not going to go into the Why's.... But just trust me on this ;c)

Dont uninstall.. Hard reset man... It will be faster and more stable

Ah ok that makes complete sense then. So I already uninstalled which took forever! haha thanks for this info after the fact lol. So ill re-install and hard reset. What is faster though? If i cook it into a custom ROM (which i will prob do later) or install on the standard ROM and hard reset?

Thanks again for the help man. Appreciate it!

[scrosler]

Originally Posted by thefiverivers

Ah ok that makes complete sense then. So I already uninstalled which took forever! haha thanks for this info after the fact lol. So ill re-install and hard reset. What is faster though? If i cook it into a custom ROM (which i will prob do later) or install on the standard ROM and hard reset?

Thanks again for the help man. Appreciate it!

The gains are marginal but tyou will get better results if you cook in using the OEM.


Here is what needs to be kept in mind:

The animated maniula is version 1.0
The current version is 1.3

Yeah...

[thefiverivers]

Originally Posted by scrosler

The gains are marginal but tyou will get better results if you cook in using the OEM.


Here is what needs to be kept in mind:

The animated maniula is version 1.0
The current version is 1.3

Yeah...

Aitez. Thanks for the update! Gonna try the other themes as well and see whats up. Appreciate it bro.