"filesys.exe" and CompactionPrio256 - Are we close to fixing WM5?

i discover something insteresting about DELET some registry values ... it's just that we have to wait a little before soft reset ... when i use resco explorer to tweak the registry i FILE-EXIT first and wait a little (about 1 or 2 minutes) before soft reset
if do not do this the registry values come back after a soft reset

you can turn off the device, wait a few seconds and turn it on, and then you can do a soft reset. If you do a soft reset by software you will have more chances of keeping your changes. Another thing that helps is to change the registry type to File. Something that you can do using Tweaks2k2 or manually using the info at my site.

Deleted both, major speed increase. Nice work!

Anyone done benchmarks?

That's a good question. :approve:

[jcpfish]

With both keys set at 255 and WiFi running, I get the following battery performance.

1.) With the CPU fixed at 208 ~3.5 hrs.
2.) With the CPU set on AUTO ~2.75 hrs.

In both cases I notice that filesys.exe runs about 15 min. every 35 to 45 mins. This is clearly the main cause for the difference in battery times.

[UnLoGiC]

With both keys set at 255 and WiFi running, I get the following battery performance.

1.) With the CPU fixed at 208 ~3.5 hrs.
2.) With the CPU set on AUTO ~2.75 hrs.

In both cases I notice that filesys.exe runs about 15 min. every 35 to 45 mins. This is clearly the main cause for the difference in battery times.

Any chance you could try and remove both keys and try the benchmark again?

Removing the keys made my X50v alot faster!

[DrBios_2005]

can any one check fylesys.exe in wm2003? to see if it has the same behavior that WM5

[mrcaze]

Another thing that helps is to change the registry type to File. Something that you can do using Tweaks2k2 or manually using the info at my site.

That's a good trick. I suggest to do switch to file-based registry right after hard reset as it solves some of the problems with incompatible software.

[desa42]

One thing that no one has mentioned is that that the default value of CompactionCritPrio256 of 4294967295 (0xFFFFFFFF) is also -1 as a signed integer. This is more likely the intended value. Not that it helps fix our problems, but it may explain the default value.

[UnLoGiC]

One thing that no one has mentioned is that that the default value of CompactionCritPrio256 of 4294967295 (0xFFFFFFFF) is also -1 as a signed integer. This is more likely the intended value. Not that it helps fix our problems, but it may explain the default value.

Good point!

[jcpfish]

With both keys set at 255 and WiFi running, I get the following battery performance.

1.) With the CPU fixed at 208 ~3.5 hrs.
2.) With the CPU set on AUTO ~2.75 hrs.

In both cases I notice that filesys.exe runs about 15 min. every 35 to 45 mins. This is clearly the main cause for the difference in battery times.

Next, I changed the Registry Type to "File", removed both Compaction keys and Soft reset. I then double checked to make sure these registry changes where still in effect after the soft reset and they were. Then I let the Axim run to see what happened. The results are:

With WiFi running and the CPU set to AUTO, I get the following:

filesys.exe runs for about 18 min every ~29 min.
The approx. battery time for the standard battery is ~2 hr 40 min.

It seems that I am getting about the same results no matter how I set the Compaction keys. In all cases when filesys.exe is not running at 100% the system is very responsive, but when it kicks in there is always a delay in the system.

[UnLoGiC]

Next, I changed the Registry Type to "File", removed both Compaction keys and Soft reset. I then double checked to make sure these registry changes where still in effect after the soft reset and they were. Then I let the Axim run to see what happened. The results are:

With WiFi running and the CPU set to AUTO, I get the following:

filesys.exe runs for about 18 min every ~29 min.
The approx. battery time for the standard battery is ~2 hr 40 min.

It seems that I am getting about the same results no matter how I set the Compaction keys. In all cases when filesys.exe is not running at 100% the system is very responsive, but when it kicks in there is always a delay in the system.

Thank you, with this info we should be able to figure out what to do next :approve:

Ok, here is a little tool that will allow those who are afraid of messing with registry to delete and restore those keys.

This is a freeware.

I forgot to mention. No install. Just unzip it and copy the exe file to any folder in your X50.

[Li0rE]

can this help an x51v at all?

can this help an x51v at all?

those keys are not located in the X51v because that device use a different ROM type. The program that I made will check the device and wont run in the X51 serie.

[TalynOne]

Deleting these keys (yes I've verified they're gone after a soft reset) does nothing for me. Filesys.exe takes up 95% CPU about every 5 minutes..... And runs after every soft reset, power on/off. I've also tried running the hacked ROM that turns off polling for 18 hours. No effect.