Related
I finally figured out that MS Voice Command is the program that makes the keyboard input box be slow to appear. It was taking like 6 seconds to bring up the list to choose another input method. On my Jamin, I'm 100% sure that MS Voice is to blame. After uninstalling it the delay disappeared. This is a real drag since I used MS Voice all the time for making calls. I wonder if the K-jam has the same problem? Anyone have a work around for this problem?
Well spotted That's always the first step on the way to a solution. I also depend heavily on this software so I hope a work-around's available.
Regards
Could this be the cause of the thumbpad (T9 pad) not coming up all the time, requiring a soft reset? I'm using WM2003SE btw.
I aslo stopped using MS voice command on my JAMin. I did a hard reset and did not install PocketZenPhone, Phone Alarm and MS command.
Now my JAMin runs awesome! I can change the keyboards instantly and I can even use full screen keyboards which never would work before.
I do miss voice command but I can live without it. In fact the built in voice dialer is not bad. I don't miss having to say the full name and then home or mobile or whatever. The less I have to talk to my phone the less crazy i feel. Plus it works better over bluetooth headsets.
MS Voicecommand & slowwww SIP
I encountered this prob about 4 months ago after upgrading my Xda2 to WM5.0. When I upgraded my device to the prophet, the exact same thing happened.
Here's my work-around:
1) Do a hard reset
2) Export the entire registry
3) Install MSVC
4) Import the registry saved in step 2
VOILA... now I have MSVC & a normal SIP change....
This is a great find. I've been trying to find out why my selector take 7 seconds to pull up. I thought it was keyboard skin or some other input program I installed. Didn't realize it was MSVC.
Now only if we can figure out which registry changes are causing this problem...
Re: MS Voicecommand & slowwww SIP
Putra said:
I encountered this prob about 4 months ago after upgrading my Xda2 to WM5.0. When I upgraded my device to the prophet, the exact same thing happened.
Here's my work-around:
1) Do a hard reset
2) Export the entire registry
3) Install MSVC
4) Import the registry saved in step 2
VOILA... now I have MSVC & a normal SIP change....
Click to expand...
Click to collapse
For those of you who don't have MSVC installed already, Step 1 is not necessary, i.e. no hard reset.
All you need to do is export the registry before installing MSVC, install MSVC and restore your registry.
I might have found something
I installed the trial of SKTools and was playing around with the "invalid registry entry" tool and deleted a few entries that were flagged. I remember one that had something to do with VC and started with a weird character "%a" or similar. Sorry that I can't remember better, but I did not realize right away that that fixed the problem, since I was only "cleaning up", but the keyboard selection is working well right now and that was the only thing I changed in the meantime that had anything to do with it. Hope that's the right direction.
Seems to be fine after the newest ROM update
I had the Slow keyboard with older ROM
Phone: JAMin
Some tweaks may solve the problem.
I have a Cingular 8125 with 200Mhz CPU (reportedly running at 180Mhz only).
I use Omapclock to speed up PocketSNES, but it doesn't speed up the keyboard selector at all.
Also tried the Registry trick, but restoring the original Registry after installing Voice Command clears everything, settings, program icon... ... and disable Voice Command.
So it's not a good solution.
Finally tried to tweak the Registry (for generally speeding up WM5).
It's worked so perfectly for me.
The Keyboard Selector menu pops up in 1 second or less, almost instantly.
Before tweaking, even without Voice Command installed, it takes 2 to 4 seconds.
Here are the steps:
---------------------------------------------------------------
I.
Increase cache: Noticable effect on WM5.01. Use any registry editor:
* Go to HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE\
* Change 'limit' to 8192 up to 32768
* Close registry editor (Save)
* Soft reset
II.
Disable Animated Menu (I know, doesn't relate much with the KB selector problem, but it speeds up the whole system anyway)
Use Registry Editor:
* HKEY_LOCAL_MACHINE \SYSTEM\GWE\Menu,
* Change "AniType" from default 6 to 0
III.
Use any add-on that close the programs for real, not just minimize it (SPB Pocket Plus, or PHM Free Utilities, whatever)
IV.
Increase SD card access rate:
Use Registry Editor:
* hklm\drivers\sdcard\clientdrivers\class\mmc_class
* hklm\drivers\sdcard\clientdrivers\class\SDMemory_c lass
Change both BlockTransferSize from 64 to 128 or 256
(I use 256. Don't know if it make the reading/writing process any unstable, but so far no problem for me ever. Plus I have backup, so why worry)
V.
Affects WM5.0 and can increase overall speed up to 20%
Use Registry Editor to change from default 0 to:
* [HKLM\System\StorageManager\FATFS] CacheSize = 4096 EnableCache = 1 * [HKLM\System\StorageManager\Filters\fsreplxfilt] ReplStoreCacheSize = 4096
SOFT RESET
(For me, I did everything before Resetting)
PHM registry Editor can be downloaded from http://www.phm.lu/products
Good luck.
If that does not solve your problem, please tell. Because then I know that I might accidentally did something else that made it work
Chai T
Is there any update on how we can fix this besides importing/exporting the registry after install?
I followed chaintox's directions for speeding up the device, which did seem to speed up some of the menu drawing and a few other things that it should have, but it did not help the speed of the choosing a SIP at all. I've removed all third party SIPs, and also disabled the PhonePad SIP, and it's still very slow (around 15-30 seconds).
I'm not willing to do a hard reset right now... is there anyone that has the registry export from before and after installing Voice Command? That would let me see exactly which keys were created, so I could look at removing some one by one until I find what's causing the slowdown.
Thanks in advance.
I found out that the slow SIP selector bug has something related to AKU2.2 and up...
I reflashed back to the original dopod ROM with AKU 2.15 and my SIP selector is fast even with voicecommand installed.
I'm curious if AKU 3.3 has this bug and whether WM6 has this issue too? This was probably the primary reason for ditching the latest ROMs and sticking with the original.
Well, I installed Voice Command on an WM5.0 (no AKU) emulator image to get the registry diff, and didn't see anything out of the ordinary. Installing Voice Command also did not cause the SIP slowdown on the emulated PPC, so I tend to agree with everyone that it may be AKU2.2 specific. I'm curious to see the answer to mr_yellow's question about AKU3.3 or WM6... I may be willing to upgrade if it fixes this issue.
I just remembered that I did test AKU3.3 (I think i flashed AERGS's AKU3.3 ROM) and it did have the same laggy SIP selector bug/feature... so the only other option is WM6... Does anyone know if you the SIP selector is slow for WM6? This is for a G3 device (dopod818pro)...
Thanks,
doh!...
Hi all,
I have been noticing that my input selector is really slow so after much digging around I came upon this thread and Chaintox's instructions.
However I read his first instruction to increase cache and followed that with a soft reset and now my JAMin isnt completing the soft reset
It is just hanging at the SPB safe mode menu reboot screen.
Is there anything I can do?
please help! and contribute to the forgive-a-noob fund
Cheers
ben
chaintox said:
I have a Cingular 8125 with 200Mhz CPU (reportedly running at 180Mhz only).
I use Omapclock to speed up PocketSNES, but it doesn't speed up the keyboard selector at all.
Also tried the Registry trick, but restoring the original Registry after installing Voice Command clears everything, settings, program icon... ... and disable Voice Command.
So it's not a good solution.
Finally tried to tweak the Registry (for generally speeding up WM5).
It's worked so perfectly for me.
The Keyboard Selector menu pops up in 1 second or less, almost instantly.
Before tweaking, even without Voice Command installed, it takes 2 to 4 seconds.
Here are the steps:
---------------------------------------------------------------
I.
Increase cache: Noticable effect on WM5.01. Use any registry editor:
* Go to HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE\
* Change 'limit' to 8192 up to 32768
* Close registry editor (Save)
* Soft reset
II.
Disable Animated Menu (I know, doesn't relate much with the KB selector problem, but it speeds up the whole system anyway)
Use Registry Editor:
* HKEY_LOCAL_MACHINE \SYSTEM\GWE\Menu,
* Change "AniType" from default 6 to 0
III.
Use any add-on that close the programs for real, not just minimize it (SPB Pocket Plus, or PHM Free Utilities, whatever)
IV.
Increase SD card access rate:
Use Registry Editor:
* hklm\drivers\sdcard\clientdrivers\class\mmc_class
* hklm\drivers\sdcard\clientdrivers\class\SDMemory_c lass
Change both BlockTransferSize from 64 to 128 or 256
(I use 256. Don't know if it make the reading/writing process any unstable, but so far no problem for me ever. Plus I have backup, so why worry)
V.
Affects WM5.0 and can increase overall speed up to 20%
Use Registry Editor to change from default 0 to:
* [HKLM\System\StorageManager\FATFS] CacheSize = 4096 EnableCache = 1 * [HKLM\System\StorageManager\Filters\fsreplxfilt] ReplStoreCacheSize = 4096
SOFT RESET
(For me, I did everything before Resetting)
PHM registry Editor can be downloaded from http://www.phm.lu/products
Good luck.
If that does not solve your problem, please tell. Because then I know that I might accidentally did something else that made it work
Chai T
Click to expand...
Click to collapse
Wow, i forgot about this thread... I found a good workaround/solution. Not sure if it'll work on all devices. but it worked on my HTC Prophet.
Figured out the exact keys in the registry to import/export.
see this wiki page for more details
http://wiki.xda-developers.com/index.php?pagename=ProphetFAQ
This can be done after you've installed VC.
Cool TY for that info !
http://forum.xda-developers.com/showthread.php?p=2946880#post2946880
This fixes the problem PRONTO!
This project is about rebuilding the touch.dll coude from the original dll assembly.
Latest package:
touch.cab
For adding the "developers certificate" ( read side node on update 21/11/08 ) you can use the following tool:
Microsoft Security Configuration Manager
--------------------------------------------------------------------------------------------------
Update 21/11/08:
Ive finally managed to rebuild the touch.dll from assembly and recompiled it and im able to boot the new touch.dll
Ive cleared some of the calls made to some old features implemented in the original file like the touch cube etc.
Be aware that this isnt for daily use and only for testing purposes. But I really need some input on speed and reliability because i cant test everything on my own ( i flash my device every 4 hours or so so not really long testing times ). If you are not affraid of hard resetting your device and are willing to participate in testing current work please do but dont keep me responsible for freezes etc
I have only tested it on udk R4 because its easy for me to test speed on manilla 2d and it gives me a good impression of daily usability. And because i removed almost all calls to the original cube code it wont be any good for cube lovers as and original HTC roms.
Keep in mind that all ive done now has been done during work in a few hours and although ive tried to be on the safe side i cant tell you all is working as its suppose to and I think i havent done more then remove about 20% of garbage out of it.
I know not all is as fast as its supposed to be but like i said im better safe then sorry and i dont wanna hardreset every 2 mins or so... Some good testing can be done in Manila2d like scrolling through images fast and scrolling through the bottom bar. Also ive noticed that scrolling through the normal "All programs" is still on the slow side ( still need to resolve a lot of scrolling issues... HTC has included a lot of codes for all sorts of winmo controls like listviews etc ) but if you open up the all programs in manila from the programs menu u will see what kind of speed it can work at minimum....
As for the priorities mentioned earlier in this thread im going to set both the priority256 and the priorityhigh256 at 109 ( original microsoft value that can be found at msdn ) in the cab file so we can test the touch interface as it was suppose to be set up... you can easily change these values as you like ( read earlier posts ). Setting it lower then 109 will give it an higher priority which will make the device suffer more from touch input... Setting it higher ( upto 255 ) will give the touch input less priority and will make rendering faster but can also come of the cost of reliability.
Side node:
Make sure your rom has the "Sample Privileged Developer" Certificate installed because i signed both the file as the cab with this certificate ( files need to be signed because of being system file and they dont get any trust at boot without a certificate ).
--------------------------------------------------------------------------------------------------
Start 15/11/08:
Ok so because i didnt had much to do this week i started digging into the touch.dll to see if there can be some solutions to the slow scrolling/stuttering etc when touching the screen.
I already found out that the graphics stuttering mostly happens due to the fact that the touch.dll is set to real-time process priority.
WinMo uses priority values from 255 (low) to 0 (real-time).. Normally touch should be set at 109 ( according to msdn ), but because htc put so much garbage in it ( touchflo related ) and it got slow as #@% they put the priority to 0 as a default and deleted the registry entries
Using IDA i found out that those registry values are still being accessed but since they are not there the default of 0 is used.
Just create the following key
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch
And create the following values in it
Name value (DWORD)
Priority256 255
HighPriority256 255
This will not speed up the actual scrolling but it will also not make the device freeze when pressing the screen... So scrolling seems more natural. ( especially in programs folder and file explorer )
So this is not a fix but a good start for now.
Already found out a few things looking at the code that can be dropped out so im going to try to rebuild the touch.dll from asm without most time expensive calls ( hopefully shrike will help me out on this one ).
Let me be the first to say thank you. I am not sure I did the things right, but my Polaris seems more alive than ever. I will post an exported regkey, please confirm that I've done it correctlly.
I have noticed an improvement in sliding in S2U2 and on everything that involves touching the screen. This indeed is a great step forward for Polaris.
Thanks for trying... As soon as development will progress ill create a cab file which will include the registry keys.
Big difference... great job,
I've noticed though that in icontact, when you scroll contacts, the animation has to finish so that it can accept new gesture, so i set it to 109, scrolling is still good and icontact work propertly..
Great find Rogro! Was irritating me how the graphic stutters whenever I scroll in programs and phonebook..
Just wondering though, if it was such a simple fix, why did they remove the reg key to begin with? as far as i can see, the impact on the processor speed seems really minimal..
I look forward to more of your discoveries..
Nice job! Performance is much better... but in the all programs list the icons all still flashing when scrolling, although its much less.
Thank you
Great job in all programme speed seems little better.
nice
thanx
Hey Rog,
Nice to see you're trying different things.
I looked at my HD but it didn't have the slowdown the Polaris has. But it also doesn't have the registry keys... so i added them and soft reset. Now, my HD's TFLO3D is really unresponsive and stutters... So maybe it's only for non-TF3D devices?
Thank's
It's working well in my M-Amine 2.0 Final Rom.
Here is the little Cab.
EDIT: If you install this cab or change the register by hand (Is the same) , the scrolling work well but maybe you will have problems with Igo, TomTom or destinator.
Please take that in your mind.
Thanks a lot Rogro!! It's wonderful for every application that uses touch scrolling.
Why do HTC engineers leave us alone with those awful bugs? Is it so difficult to add those 2 DWORD values?
Actually it fixes the screen response AND the All Programs scrolling in Manilla 2D
thanks for sharing rogro82.
cheers
Thanks rogro82.
It's working
BTW i've notice something,,maybe wrong.
When you scroll (very fast) in file explorer or program folder, stoping it(the scrolling) with a sigle tap it's not so easy. Or when you tap to stoping it ,then turning to another direction(up or down).
Also the icontact scrolling isn't good enough.
I use the "cbolumar" cab.
BTW i've notice something,,maybe wrong.
When you scroll (very fast) in file explorer or program folder, stoping it(the scrolling) with a sigle tap it's not so easy. Or when you tap to stoping it ,then turning to another direction(up or down).
Click to expand...
Click to collapse
Thats because the scrolling is still way off in terms of speed... the only thing that happens when you change the registry settings is that it will not allow touch.dll to eat all resources and hang all other processes..
Maybe you could try to set it to 109 ( what it should be on a normal driver )..
I never use any gestures or whatever so setting it to 255 works for me for now until i can start cleaning code.
TomTom7 with these settings
Nice find. But in Tomtom7 something strange happens. I have to press the screen much harder then without these reg keys. I Use M-Amine's RTM rom.
Anyone else have this or is it just me having this bug?
ViNZ! said:
Nice find. But in Tomtom7 something strange happens. I have to press the screen much harder then without these reg keys. I Use M-Amine's RTM rom.
Anyone else have this or is it just me having this bug?
Click to expand...
Click to collapse
The same bug for me with Navigon Mobile Navigator 7
kr.,
Frepke
Bug with IGO 8
The same for me , i have a lot of problems with the screen in Igo , the problem disappear after delete the register changes.
To delete this, you must go to the register and delete the new values by hand, not the touch entry but the priority entries.
Only uninstalling the cab is not valid because the driver is in use.
Thanks a lot!
It's like early Christmas!
It´s because of people like you that my Polaris is an increasingly awesome machine. Continuing like this in the near future it will teleport me from one place to the other!
Keep up the good work.
Don't ever leave us Rogro!
TT6 don't work
The screen is no usable.
I have delete all the key and now work well
ROM M-Amine 2.0 Final ITA
I've waited for a while to see how everything would develop, but RA2 just remains slow as hell.
I'm getting main memory write of ~1700 and read of ~6100.
Storage card gets stuck at ~650 write and ~ 2600 read.
It's drama. Did anyone find a way to improve this, or must we start PM'ing tnyynt?
All I did was reflash back to the R1 firmware. I didn't see anything in the R2 that was better. So unless I missed something, I just went back to the R1 with the tweaks and it seems to be a lot smoother and quicker than the R2. Just my .02
I think and maybe wrong here, but the r2a roms are using a different memory model, that caches a lot more.
I've found that letting wm control the cache works best.
16mb pagepool is also good
despite the benchmarks I definitely find r2a faster than 1, inclduing sdcard access.
have you tried spb benchmarks "real world" tests, using word etc?
fards said:
I think and maybe wrong here, but the r2a roms are using a different memory model, that caches a lot more.
I've found that letting wm control the cache works best.
16mb pagepool is also good
despite the benchmarks I definitely find r2a faster than 1, inclduing sdcard access.
have you tried spb benchmarks "real world" tests, using word etc?
Click to expand...
Click to collapse
So what exactly did you change?
I haven't tried a SPB benchmark. I know SKtools isn't the most reliable test, but I think that the numbers I gave you tell us enough; it's not good.
Angelusz said:
I've waited for a while to see how everything would develop, but RA2 just remains slow as hell.
I'm getting main memory write of ~1700 and read of ~6100.
Storage card gets stuck at ~650 write and ~ 2600 read.
It's drama. Did anyone find a way to improve this, or must we start PM'ing tnyynt?
Click to expand...
Click to collapse
Can you verify that the registry entries from the cab have been indeed written to the registry?
If yes, use a tweaking program to verify File System Cache is enabled and set according to SD TuneUp.
Write operations should not be cached by default, so that result I seem fair but the SD read result I find low. What was your result on the previous ROM?
I checked and I think I found the issue. The settings are not applied indeed.
Funny thing is, I can't change them. I've tried with SOTI Pocket controller, as well as with SKtools' regeditor. The registry keys cannot be modified! Will try in another way, will post results.
EDIT: After some more thorough inspection, I found something is wrong.
The registry does show the correct HEX keys. In decimal however, it shows completely the wrong thing!
For instance the DWORD CardDetectControlMask:
In tnyynt SDtuneup.cab
Hexidecimal: fffff3ff
Decimal: -3073
In my registry:
Hexidecimal: fffff3ff
Decimal: 4294964223
How can this be explained? I've never seen HEX differ from decimal before..
Edit2
Third inspection shows me that the registry doesn't like a "-". In your CAB, - values are used. I can now modify positive values (took the SD card out), but can't enter minus.
Angelusz said:
EDIT: After some more thorough inspection, I found something is wrong.
In tnyynt SDtuneup.cab
Hexidecimal: fffff3ff
Decimal: -3073
In my registry:
Hexidecimal: fffff3ff
Decimal: 4294964223
How can this be explained? I've never seen HEX differ from decimal before..
Click to expand...
Click to collapse
i can explain this one. (i will use h for hexadecimal numbers and d for decimal numbers and b for binary numbers)
normally FFFFF3FFh =4294964223d in 32bits
but in binary you can not enter "-" in a cpu registry only 0 and 1
and you can only do addition. So to do 5d-2d they must do 5d+(-2d).
but (-2d ) can not be express in ordinary binary.
the example is only on 4bits
5d=0101b
2d=0010b
3d=0011b
the result must be 3d=011b
0101b
+xxxxb
_____
0011b
we find that xxxxb=1110b=(-2d) but 1110b also = 14d !!!
it works because of a registry overflow. on 4 bits you can only count up to 15 normally 0101b+1110b = 10011b -> 5 bits but only 4 bits can be stored so the one on the left is not in memory. so the result of the operation is 0011b.
the shortest way to find the representation of (-2d) is
take the biggest number on the number of bits you use. remove the absolute value of the negative number you are are looking for and add 1.
(computer can not do binary subtraction but human can )
on 4 bits
1111b - 0010b +0001b =
1101b +0001b=1110b
or 15d-2d+1d =14d
now on 32bits.
3073d=00000C01h
so
-3073d=FFFFFFFFh - 00000C01h +00000001h
-3073d=FFFFFFFFh- 00000C00h
-3073d= FFFFF3FFh !!!!!
all that to say that the value in the registry are the same....LOL
all depend if you consider it or not has a negative number.
normally we use the first bit on the left to know if its a positive or negative value.
Alright. So it actually is the same. Thanks for your elaborate explanation, it's never a bad time to learn something.
So it's all in the way it's displayed. I gues WinCE cab manager does allow showing -xxxx in registry entries, where the winmo registry does not.
This does mean that the values should indeed be applied correctly. Tnyynt?
After updating my firmware I've notice, faster boot up times, and TF3D is a lot smoother. A lot. Before the update TF3D would crash my phone. It hasn't crashed yet. I wondering why you guys are experiencing a sluggish update.
yogibear2009 said:
After updating my firmware I've notice, faster boot up times, and TF3D is a lot smoother. A lot. Before the update TF3D would crash my phone. It hasn't crashed yet. I wondering why you guys are experiencing a sluggish update.
Click to expand...
Click to collapse
This thread is not about it being sluggish, I'm pointing at the raw numbers. File transfer btw, is much slower.
Angelusz said:
This thread is not about it being sluggish, I'm pointing at the raw numbers. File transfer btw, is much slower.
Click to expand...
Click to collapse
My apologies. I didn't mean to highjack the thread.
tnyynt said:
What was your result on the previous ROM?
Click to expand...
Click to collapse
i got around 3000 on R2A
on R1A i use to have 12000 on my 16g sd card.
so it's significantly lower on R2A
Angelusz said:
Alright. So it actually is the same. Thanks for your elaborate explanation, it's never a bad time to learn something.
So it's all in the way it's displayed. I gues WinCE cab manager does allow showing -xxxx in registry entries, where the winmo registry does not.
This does mean that the values should indeed be applied correctly. Tnyynt?
Click to expand...
Click to collapse
it depends if Tnyynt have used decimal or hexadecimal to enter the values. registry are always imported in hexadecimal
if Tnyynt has entered the initial value in hexadecimal so the values are good but if Tnyynt entered the initial value in decimal there is a problem, but this one can be easily solved. it will just mean that R1A and R2A may not use the same code for numbers so in this case we will just have to recode the value to have the good numbers.
but i logicaly for a mask you use hexadecimal...
Has somebody tried to contact se about this problem?
Tylwith said:
i got around 3000 on R2A
on R1A i use to have 12000 on my 16g sd card.
so it's significantly lower on R2A
Click to expand...
Click to collapse
yeah same here. This is why I was wondering if it was worth staying on the R1A since most programs are installed onto the mem card, the R1A firmware should be quicker at loading programs correct?
Ok, why are you people so keen about the benchmarks? Copy a file on your SD and compare the result. This is a lot more realistic test and there you can see if there is any real difference for your programs. Everything else is just for bragging, sorry.
Dandie said:
Ok, why are you people so keen about the benchmarks? Copy a file on your SD and compare the result. This is a lot more realistic test and there you can see if there is any real difference for your programs. Everything else is just for bragging, sorry.
Click to expand...
Click to collapse
it's not that simple because of the file system and how machine handles access to them. depending of the size of file you are copying the result can be very different. Some fs are better with tiny files some other with bigger files. there is also the access speed of the file that you can not really tell even if it has a big importance. it's a bit like internet speed . you can have a fast non responsive internet connection(will take long time to access a server but will download very fast for example). Or a responsive but very slow internet connection(remember of the days people were playing counterstrike on rtc modem because the rtc modem gave them a better ping than adsl or cable)
benchmarks try to copy different kind of file size and try to make an average score they also test multiple simultaneous access and thing like that which is important for multitasking. Futhermore it's not easy to try launch a copy a several tiny files by hand.
if your system is faster reading bigger file it doesn't mean that program that use smaller files will be faster.
Very true. tnyynt, what does all this tell you?
Sorry to be so late, time is not on my side nowadays.
I find it really strange that the TuneUp would work on any device sporting a Card but on the Xperia with the latest firmware. I think we can easily rule out registry and import incompatibilities since it's the same operating system.
Nothing clever comes to my mind but this:
try exporting the regustry entries from my CAB with WinCE CAB Manager and apply them as a registry patch on your device. See how that goes.
Make your Glyph cache 4194304 ( With CAB )
If you want your youtube or video better
Install PPCAdvancedSet2: (( I find CAB file ))
PPCAdvancedSet2.cab
Note:
The glyph cache is the pipeline through which graphics render. Increasing the cache results in faster graphics. >> meschle
You don't need a cab to do this... Just go into the registry to HKLM\SYSTEM\GDI\GLYPHCACHE\limit and change it without any program to install !
Why should you change it to 4 MB ?
I recommend the value 131072 (DWORD decimal), this is 128 KByte or 65536 (64 KByte).
THERE IS NO PERFORMANCE IMPROVEMENT IF YOU MAKE IT BIGGER.
Test it for yourself! Use VSBenchmark2007 or TestOpenGL to benchmark your GPU.
Please post your Benchmark results!
I doubt it will improve the performance that is benchmark-able to milliseconds or KB/s units. But I do believe that for instance, if you had Opera running with multiple tabs opened and occupying lots of memory (check GWES.EXE RAM occupation), it still maintain their snappiness. That's what larger GLYPH cache should give.
Maybe Opera is not a good example... but close I hope...
I agree with "maesus".
WVGA screen have more perfomance improvements if you make GLYPHCACHE bigger. VSBenchmark2007 results is same because amount of bench data is always same.
hello everybody here in xda
I was wondering What is The Best File system cache size for different Pocket Pc's
and My question is
What is the Best File system cache size For all pocket pc's with wm6.5 Or wm6.1 ?
edit : the answer is in the next post I think
cheers
3 things:
1. Jeez, change the alignment on your post, it's annoying (edit: done, thanks, lol).
2. You have to set the caches in boot.rgu; it doesn't work changing them anywhere else. The caches are set in early boot, and making changes to the system registry does nothing.
3. The value 'cachesize' is obsolete; changing it does nothing. MSDN says this in its file system cache page.
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"FriendlyName"="FAT FileSystem"
"EnableCache"=dword:1
"CacheSize"=dword:0
The value you want to mess around with is mainly the datacachesize, and maybe the fatcachesize. In my experience, it doesn't make a hell of a lot of difference. You have more ram at boot with a lower datacache, though. If you make the datacache too large, the device won't boot. The stock setting is pretty big (8 MB). These are stock values in the raphael native kernel:
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS]
"DataCacheSize"=dword:00000800 ;2048 sectors(2048*2048=4MB)
"FatCacheSize"=dword:00000100 ;256 sectors(256*2048=512KB)
Farmer Ted said:
3 things:
1. Jeez, change the alignment on your post, it's annoying.
2. You have to set the caches in boot.rgu; it doesn't work changing them anywhere else. The caches are set in early boot, and making changes to the system registry does nothing.
3. The value 'cachesize' is obsolete; changing it does nothing. MSDN says this in its file system cache page.
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"FriendlyName"="FAT FileSystem"
"EnableCache"=dword:1
"CacheSize"=dword:0
The value you want to mess around with is mainly the datacachesize, and maybe the fatcachesize. In my experience, it doesn't make a hell of a lot of difference. You have more ram at boot with a lower datacache, though. If you make the datacache too large, the device won't boot. The stock setting is pretty big (8 MB). These are stock values in the raphael native kernel:
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS]
"DataCacheSize"=dword:00000800 ;2048 sectors(2048*2048=4MB)
"FatCacheSize"=dword:00000100 ;256 sectors(256*2048=512KB)
Click to expand...
Click to collapse
I have not the FLASHDRV key in HTC HD2.
NIKOSXRI said:
I have not the FLASHDRV key in HTC HD2.
Click to expand...
Click to collapse
Well, just look for datacachesize in the boot.rgu; the storage profile just has another name, I guess.
thanks for reply Farmer Ted
Farmer Ted said:
Well, just look for datacachesize in the boot.rgu; the storage profile just has another name, I guess.
Click to expand...
Click to collapse
Thanks, you got it, I have datacachesize dword hex400 and fatcachesize dword hex200 in my HTC HD2.
Which do you think is the best values for this phone?
..you know guys....
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"CacheSize"=dword:00000800
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS]
"CacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS]
"DataCacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"CacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"DataCacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]
"ReplStoreCacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\fsreplxfilt]
"ReplStoreCacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\Snd\Event]
"EventCache"=dword:00000100
and PP, of course.
filesys.exe vs file system cache
Hi Farmer Ted,
Thanks for the explanation.
Farmer Ted said:
2. You have to set the caches in boot.rgu;
3. The value 'cachesize' is obsolete; changing it does nothing. The value you want to mess around with is mainly the datacachesize, and maybe the fatcachesize. You have more ram at boot with a lower datacache, though. If you make the datacache too large, the device won't boot.
Click to expand...
Click to collapse
I'm facing a problem in my device with the filesys.exe.
There are certain processes (Manila contacts and PimBackup) which make the filesys.exe to use up to 95% of CPU making the device unusable. (details on the link on my signature).
I'm wondering if there is any relation between the filesystem cache and the behaviour of filesys.exe.
What will happen if the cache is set to 0?
Thanks in advance
I kind of doubt the cachesize is affecting the cpu load. I'm not sure what would cause that issue, especially with pimbackup. Adjusting the caches size affects how much RAM filesys.exe uses. If you profile the virtual memory of the device with virtualmemory.exe or with devhealth.exe, you'll see a larger or smaller virtual memory commitment for filesys.exe in slot 2 depending on the size of the caches.
If you set the caches to 0, then the system decides what cachesize to use at first boot. In my experience, it's usually around 2-3 MB total (including fat, data, and I guess the bitmapcache). It works pretty well, I've set it as 0 and used it quite a bit that way. If you want no caching, then you need to set 'enablecache' to 0.
Cache size vs battery life
Hi guys,
In your experience, does the different cache sizes/pagepool affects the battery life?
I don't think that either has much effect (if any) at all.