| X50 / X51 Forums Talk about anything related to the X50 / X51 series. |
|
03-17-07, 01:46 PM
|
#226 (permalink)
|
|
Aximsite Minor League
Join Date: Dec 2004
Location: California
Posts: 190
Thanked 2 Times in 2 Posts
|
Someone please post the output of pps -t on an X50V running A02. I might be able to update v10 to handle it.
You can download the 'pps' utility from http://www.xs4all.nl/~itsme/projects/xda/tools.html. This runs on your PC while you are docked and can list out the current CPU usage by process or by thread.
|
|
|
|
|
03-17-07, 02:10 PM
|
#227 (permalink)
|
|
Aximsite Prospect
Join Date: Dec 2005
Location: Milton, Florida (Emerald Coast)
Posts: 12
Device: Slivr
Carrier: Cingular
Thanked 0 Times in 0 Posts
|
It would be great if you could.. I too have X50 with A02 and filesys sucks it up.
Thanks,
Steve
__________________
:approve:
See ya.. Take Care!
I'd Rather Be Flying!
|
|
|
|
|
|
03-18-07, 01:01 AM
|
#228 (permalink)
|
|
Guest
|
Originally Posted by shsmith
|
Someone please post the output of pps -t on an X50V running A02. I might be able to update v10 to handle it.
You can download the 'pps' utility from http://www.xs4all.nl/~itsme/projects/xda/tools.html. This runs on your PC while you are docked and can list out the current CPU usage by process or by thread.
|
shsmith, I captured the requested output, however its >13000 characters. I sent a PM asking for your email, however I had a better idea... see your PM.
Thanks for the help shsmith!!!
|
|
|
|
|
|
03-21-07, 02:05 AM
|
#229 (permalink)
|
|
Guest
|
Just wanted to drop a quick note.
shsmith requested addl info from the pps -t command from the A02 rom. I have provided it to him, so we should have a fix soon! Thanks again shsmith!
|
|
|
|
|
|
03-22-07, 05:30 PM
|
#230 (permalink)
|
|
Aximsite Minor League
Join Date: Dec 2004
Location: California
Posts: 190
Thanked 2 Times in 2 Posts
|
|
Originally Posted by phdeez
|
Just wanted to drop a quick note.
shsmith requested addl info from the pps -t command from the A02 rom. I have provided it to him, so we should have a fix soon! Thanks again shsmith!
|
Thank you for sending me the pps output. I made a new build of the patch based on version 6. I have no way of testing this, but with a bit of luck it will work. Let me know.
Also, is this an x50v or x50mid? I will probably need a different patch for each model.
__________________
Freedom is a heavy load, a great and strange burden for the spirit to undertake. It is not easy. It is not a gift given, but a choice made, and the choice may be a hard one. -- Ursula K. LeGuin
|
|
|
|
|
|
03-23-07, 10:53 AM
|
#231 (permalink)
|
|
Aximsite Prospect
Join Date: Sep 2005
Posts: 6
Thanked 0 Times in 0 Posts
|
Thank you so much, we are all grateful ! I just installed it, seems to work. I'll let you know how it goes.
Thanks again !
|
|
|
|
|
|
03-23-07, 01:42 PM
|
#232 (permalink)
|
|
Guest
|
You Friggin Rock
|
Originally Posted by shsmith
|
Thank you for sending me the pps output. I made a new build of the patch based on version 6. I have no way of testing this, but with a bit of luck it will work. Let me know.
Also, is this an x50v or x50mid? I will probably need a different patch for each model.
|
shsmith- you are an absolute GENIUS! The pps output I gave you was from an x50v on A02.
Needless to say, I saw filesys.exe exceeding 90% @ 624mhz prior to executing your patch, and immediately after it was <40% @ 204mhz. Device is MUCH more responsive now. I really can't THANK YOU enough.... I feared I was going to have to go back to WM2003se- AFTER paying for WM5!
Again- THANK YOU THANK YOU THANK YOU
|
|
|
|
|
|
03-26-07, 11:12 AM
|
#233 (permalink)
|
|
Aximsite Prospect
Join Date: Feb 2007
Posts: 2
Thanked 0 Times in 0 Posts
|
Not working on my X50 mid. What can I do ?
Daniel.
|
|
|
|
|
|
03-26-07, 05:12 PM
|
#234 (permalink)
|
|
Aximsite Minor League
Join Date: Dec 2004
Location: California
Posts: 190
Thanked 2 Times in 2 Posts
|
|
Originally Posted by ic3d3m0n
|
Not working on my X50 mid. What can I do ?
Daniel.
|
Daniel,
I need the output of the 'pps -t' command on your version of the X50 rom.
You can download the 'pps' utility from http://www.xs4all.nl/~itsme/projects/xda/tools.html. This runs on your PC while you are docked and can list out the current CPU usage by process or by thread.
Please do something that triggers the high cpu usage (such as copying files in and out of flash) and then run pps -t. What I need is the output "filesys" line that shows a high CPU usage (80-90%).
Thanks,
__________________
Freedom is a heavy load, a great and strange burden for the spirit to undertake. It is not easy. It is not a gift given, but a choice made, and the choice may be a hard one. -- Ursula K. LeGuin
|
|
|
|
|
|
04-01-07, 06:45 AM
|
#235 (permalink)
|
|
Aximsite Rookie
Join Date: Feb 2006
Location: Moscow, Russia
Posts: 26
Thanked 0 Times in 0 Posts
|
After use of this patch on my A02 ROM my Dell is the slow. More slower it was not be any time.
that to do?
and THAT file to copy to Start Up???
Last edited by The Zip; 04-01-07 at 06:52 AM.
|
|
|
|
|
|
04-01-07, 09:12 AM
|
#236 (permalink)
|
|
Aximsite Major League
Join Date: Dec 2004
Location: Paris, France
Posts: 493
Thanked 17 Times in 4 Posts
|
I have tested the patch, if filesys raised to 90% and you apply the patch the filesys.exe will go down on 30 % of CPU. However if the patch is running the filesys.exe will remain running at 30% CPU. Finally if the patch is running the x50v will have worse performance. WIthout the patch the filesys.exe will raise to 90% for a certain period but will go down to 0% after, with the patch it'll stay minimum at 30% and will never go down to 0%.
|
|
|
|
|
|
04-23-07, 11:56 PM
|
#237 (permalink)
|
|
Aximsite Prospect
Join Date: Apr 2007
Posts: 2
Thanked 0 Times in 0 Posts
|
[QUOTE=shsmith;1328790]Quote:
Originally Posted by ic3d3m0n
Not working on my X50 mid. What can I do ?
Daniel.
Daniel,
I need the output of the 'pps -t' command on your version of the X50 rom.
You can download the 'pps' utility from http://www.xs4all.nl/~itsme/projects/xda/tools.html. This runs on your PC while you are docked and can list out the current CPU usage by process or by thread.
Please do something that triggers the high cpu usage (such as copying files in and out of flash) and then run pps -t. What I need is the output "filesys" line that shows a high CPU usage (80-90%).
Thanks,
QUOTE]
Dear Daniel,
My PDA is Dell X50 520MHz. And I attach the info you required. Basically, neither patch_filesys_v11 nor patch_filesys_v6.3 can run on my Dell X50 520MHz. Please help me out. Thanks a lot.
|
|
|
|
|
|
04-24-07, 09:06 PM
|
#238 (permalink)
|
|
Aximsite Prospect
Join Date: Apr 2007
Posts: 2
Thanked 0 Times in 0 Posts
|
Dear Daniel,
I have got the pps output for my Dell X50 MID 520MHz PDA. How can I forward the output to you?
H:\temp\1>pps -t
0eee1e9e 00011ce4 fb fb 0.0 0.0 6ef4c49a: rapiclnt -drndis_p
eer
0ef8aaca 0002cc14 fb fb 0.0 0.0 ef6da99a: repllog.exe AppRun
AfterRndisFnDetected
0f1a0822 00017aac fb fb 0.0 0.7 0f117356: MBUTTON.EXE
0f1b1b5a 034f62d0 fb fb 0.0 0.0 cspnet.dll 8f3c3fd6: connmgr.exe 70
0f3f73b6 02eb3970 fb fb 0.0 0.0 softkb.dll afa0b302: device.exe 20
0f643426 015e2604 fb fb 0.0 0.0 afa0b302: device.exe 20
0f98ad72 01666ff0 fb fb 0.0 0.0 afa0b302: device.exe 20
0f98dd72 01666fd8 fb fb 0.0 0.0 afa0b302: device.exe 20
0f98dfd6 01666fe8 fb fb 0.0 0.0 afa0b302: device.exe 20
0f99ce6e 01666fc8 fb fb 0.0 0.0 afa0b302: device.exe 20
0f99cf82 01666fd0 fb fb 0.0 0.0 afa0b302: device.exe 20
0ff6ad72 03dc9e68 ff ff 0.0 85.7 msflash.dll effa5752: filesys.exe
0ff7f2d2 03f38a04 fb fb 0.0 0.0 fsdmgr.dll effa5752: filesys.exe
0ff8d0ba 0004274c fb fb 0.0 0.0 effa5752: filesys.exe
0ffb4266 801a1280 ff ff 0.0 0.0 0ffb4002: NK.EXE
2eddb8c6 01cbb420 fb fb 0.0 0.0 ef3b3aca: services.exe 60
2ef8a916 000212c8 fb fb 0.0 0.0 ef6da99a: repllog.exe AppRun
AfterRndisFnDetected
2f04bda6 02ed5638 fb fb 0.0 0.0 wapdrv.dll afa0b302: device.exe 20
2f11730e 036396ec fb fb 0.0 0.0 redir.dll afa0b302: device.exe 20
2f14346e 00018fbc fb fb 0.0 0.0 ef14332e: BTTrayCE.exe
2f15f2c6 02e26d58 fb fb 0.0 0.0 ossvcs.dll ef6da99a: repllog.exe AppRun
AfterRndisFnDetected
2f1f70da 0004ae50 ff ff 0.0 0.0 2f3b3a82: shell32.exe 50
2f33b6ca 02e91650 fb fb 0.0 0.0 lassd.dll ef3b3aca: services.exe 60
2f36d8ba 02e26d58 fb fb 0.0 0.0 ossvcs.dll 2f3b3a82: shell32.exe 50
2f3871e2 0312127c fb fb 0.0 0.0 dtpt_srv.dll ef3b3aca: services.exe 60
2f3a573a 00017b60 fb fb 0.0 0.1 2f3b3a82: shell32.exe 50
2f3dc466 0223de40 fb fb 0.0 0.0 wsp.dll 4f3dc442: srvtrust.exe 80
2f3ddfca 01521ef4 fb fb 0.0 0.0 6f629402: gwes.exe 30
2f415fde 0002b954 f9 f9 0.0 0.0 6f629402: gwes.exe 30
2f616fd2 030f3330 f9 f9 0.0 0.0 dwxfer.dll afa0b302: device.exe 20
2f70ef2e 039f6af4 fb fb 0.0 0.0 wzcsvc.dll afa0b302: device.exe 20
2f7cf772 01521ef4 fb fb 0.0 0.0 afa0b302: device.exe 20
2f7e4fda 03507184 96 96 0.0 0.0 waveapi.dll afa0b302: device.exe 20
2f80eaba 03059fe0 fb fb 0.0 0.0 pptp.dll afa0b302: device.exe 20
2f86ed52 016ecde4 fb fb 0.0 0.0 afa0b302: device.exe 20
2f86efd6 016ed440 fb fb 0.0 0.0 afa0b302: device.exe 20
2f974c82 018a554c f9 f9 0.0 0.0 afa0b302: device.exe 20
2f9a1fb2 02d3b458 78 78 0.0 0.0 ndis.dll afa0b302: device.exe 20
2ff0ffb2 03f2201c ff ff 0.0 0.0 diskcache.dll effa5752: filesys.exe
4eef3dee 02e26d58 fb fb 0.0 0.0 ossvcs.dll 4ef15c82: tmail.exe -RunInBK
G
4ef15d12 00015c60 fb fb 0.0 0.0 4ef15c82: tmail.exe -RunInBK
G
4ef4c3c2 00013ff8 fb fb 0.0 0.0 4ef15c82: tmail.exe -RunInBK
G
4f13b5ea 0001c170 fb fb 0.0 0.0 ef14332e: BTTrayCE.exe
4f15f962 00031834 fb fb 0.0 0.0 ef6da99a: repllog.exe AppRun
AfterRndisFnDetected
4f15fa52 0002fe98 fb fb 0.0 0.0 ef6da99a: repllog.exe AppRun
AfterRndisFnDetected
4f1c7f16 033575c8 fb fb 0.0 0.0 connplan.dll 8f3c3fd6: connmgr.exe 70
4f1cf25e 03356944 fb fb 0.0 0.0 connplan.dll 8f3c3fd6: connmgr.exe 70
4f1f7b7e 00011068 fb fb 0.0 0.0 4f3dc442: srvtrust.exe 80
4f352bb6 030a662c fb fb 0.0 0.0 notify.dll ef3b3aca: services.exe 60
4f3d040a 033c2f1c fb fb 0.0 0.0 cspwwan.dll 8f3c3fd6: connmgr.exe 70
4f43194e 01652394 fb fb 0.0 0.0 6f629402: gwes.exe 30
4f431fb2 01653e30 91 91 0.0 0.0 6f629402: gwes.exe 30
4f606dda 00044d0c f9 f9 0.0 0.0 6f629402: gwes.exe 30
4f786c36 03311644 f8 f8 0.0 0.0 mmtimer.dll 4f3dc442: srvtrust.exe 80
4f98af2e 01664e10 69 69 0.0 0.0 afa0b302: device.exe 20
4fabb4d2 0004274c fb fb 0.0 0.0 effa5752: filesys.exe
6ef4cb22 00012fc0 fb fb 0.0 0.0 6ef4c49a: rapiclnt -drndis_p
eer
6ef65692 03452c24 fb fb 0.0 0.0 syncmgr.dll ef6da99a: repllog.exe AppRun
AfterRndisFnDetected
6f03c732 00011a00 fb fb 0.0 0.0 6ef4c49a: rapiclnt -drndis_p
eer
6f0bf0aa 00011508 fb fb 0.0 0.0 6f3d05ea: WirelessIcon.exe
6f1205ea 00011a40 fb fb 0.0 0.0 6f3d05ea: WirelessIcon.exe
6f33b796 0001142c fb fb 0.0 0.0 6f3d05ea: WirelessIcon.exe
6f379116 000145b4 fb fb 0.0 0.0 ef3b3aca: services.exe 60
6f42591e 01865464 fb fb 0.0 0.0 6f629402: gwes.exe 30
6f425d42 018641a8 fb fb 0.0 0.0 6f629402: gwes.exe 30
6f425fa6 01861c84 f9 f9 0.0 0.0 6f629402: gwes.exe 30
6f6408d2 014b1924 65 65 0.0 0.0 afa0b302: device.exe 20
6f66dbee 033946bc dc dc 0.0 0.0 audevman.dll afa0b302: device.exe 20
6f67cf22 014c3ef4 8a 8a 0.0 0.0 afa0b302: device.exe 20
6f68145e 014c378c 8a 8a 0.0 0.0 afa0b302: device.exe 20
6f79ceee 036ab7d8 fb fb 0.0 0.0 tcpip6.dll afa0b302: device.exe 20
6f9249ae 0188483c fb fb 0.0 0.0 afa0b302: device.exe 20
6f93e96e 0145a2c0 fb fb 0.0 0.0 afa0b302: device.exe 20
6f9a17da 03fb1c00 fb fb 0.0 0.0 coredll.dll afa0b302: device.exe 20
6f9a9d72 03b91918 84 84 0.0 0.0 cxport.dll afa0b302: device.exe 20
6fa14c96 02fe1b60 fb fb 0.0 0.0 afd.dll afa0b302: device.exe 20
6fa14d02 00016ff4 fb fb 0.0 0.0 6f629402: gwes.exe 30
8ef4c3e6 00011ce4 fb fb 0.0 2.0 6ef4c49a: rapiclnt -drndis_p
eer
8f0a7152 00049bcc fb fb 0.0 0.0 2f3b3a82: shell32.exe 50
8f0b6f72 02e26d58 fb fb 0.0 0.0 ossvcs.dll ef14332e: BTTrayCE.exe
8f1b19ca 02240124 fb fb 0.0 0.0 wsp.dll 4f3dc442: srvtrust.exe 80
8f213db6 02e1ab50 fb fb 0.0 0.0 ossvcs.dll 2f3b3a82: shell32.exe 50
8f254866 02e26d58 fb fb 0.0 0.0 ossvcs.dll ef3b3aca: services.exe 60
8f3870ce 00011aa8 fb fb 0.0 0.0 8f3c3fd6: connmgr.exe 70
8f415e56 0186455c 65 65 0.0 0.0 6f629402: gwes.exe 30
8f42e982 0007243c fb fb 0.0 0.0 6f629402: gwes.exe 30
8f61d2a2 016a34b4 fb fb 0.0 0.5 afa0b302: device.exe 20
8f61d6c6 016a40e8 8b 8b 0.0 0.6 afa0b302: device.exe 20
8f640f62 0187c270 1e 1e 0.0 0.0 afa0b302: device.exe 20
8f640fd6 01878fb0 64 64 0.0 4.5 afa0b302: device.exe 20
8f643b8a 014b35dc 64 64 0.0 0.0 afa0b302: device.exe 20
8f7cffce 01586f74 fb fb 0.0 0.0 afa0b302: device.exe 20
8f7e42c6 033934c4 fb fb 0.0 0.0 audevman.dll afa0b302: device.exe 20
8f7fbfd6 02d267c8 fb fb 0.0 0.0 ndis.dll afa0b302: device.exe 20
8f80cab6 0305a2f8 fb fb 0.0 0.0 pptp.dll afa0b302: device.exe 20
8f86ee1e 02d3be58 74 74 0.0 0.0 ndis.dll afa0b302: device.exe 20
8f9468a6 016b2770 fb fb 0.0 0.0 afa0b302: device.exe 20
8f953c82 01586e90 fb fb 0.0 0.0 afa0b302: device.exe 20
8f953f7e 01584878 fb fb 0.0 0.0 afa0b302: device.exe 20
8f9877fa 018a2664 00 00 0.0 0.0 afa0b302: device.exe 20
8f987eea 018a34d8 fb fb 0.0 0.0 afa0b302: device.exe 20
8f9dfb46 03b91b8c 84 84 0.0 0.0 cxport.dll afa0b302: device.exe 20
8ff7ffc6 03dc9e68 fb fb 0.0 0.0 msflash.dll effa5752: filesys.exe
aeee186a 01336c34 fb fb 0.0 0.0 ef3b3aca: services.exe 60
af1a90f2 034f2ec0 fb fb 0.0 0.0 cspnet.dll 8f3c3fd6: connmgr.exe 70
af32798a 031c1bbc fb fb 0.0 0.0 ethman.dll afa0b302: device.exe 20
af352bda 030a5e18 fb fb 0.0 0.0 notify.dll ef3b3aca: services.exe 60
af379c56 000156f8 fb fb 0.0 0.0 ef3b3aca: services.exe 60
af61db1a 016a1a54 6d 6d 0.0 0.3 afa0b302: device.exe 20
af6833d2 03012cb0 84 84 0.0 0.0 dhcpv6l.dll afa0b302: device.exe 20
af6a4fda 0301216c fb fb 0.0 0.0 dhcpv6l.dll afa0b302: device.exe 20
af6ea8ea 03c81ee8 fb fb 0.0 0.0 dhcp.dll afa0b302: device.exe 20
af6f4f86 03836068 fb fb 0.0 0.0 netbios.dll afa0b302: device.exe 20
af6f9a36 0183211c fb fb 0.0 0.0 afa0b302: device.exe 20
af78019a 017b1884 fb fb 0.0 0.0 afa0b302: device.exe 20
af7e0fca 015f2cc4 65 65 0.0 0.0 afa0b302: device.exe 20
af933a32 033a1a38 fb fb 0.0 0.0 tapi.dll afa0b302: device.exe 20
af9a1792 02d3bc4c 76 76 0.0 0.0 ndis.dll afa0b302: device.exe 20
afa03f56 03ef6458 f8 f8 0.0 0.0 pm.dll afa0b302: device.exe 20
afa37d42 00011048 fb fb 0.0 0.0 afa0b302: device.exe 20
afebffde 03f2201c ff ff 0.0 0.0 diskcache.dll effa5752: filesys.exe
cee2a206 01336a94 fb fb 0.0 0.0 ef3b3aca: services.exe 60
cf3227fa 02bd70d0 fb fb 0.0 0.0 sqlcese30.sys.dll effa5752: filesys.exe
cf322c56 03811bc8 fb fb 0.0 0.0 ipv6hlp.dll afa0b302: device.exe 20
cf65c0ce 01608140 64 64 0.0 0.0 afa0b302: device.exe 20
cf93e94a 01458630 fb fb 0.0 0.0 afa0b302: device.exe 20
cf99ee22 02d296e8 7e 7e 0.0 0.0 ndis.dll afa0b302: device.exe 20
cfa42f2e 03f53020 fb fb 0.0 3.2 certmod.dll effa5752: filesys.exe
ef12060e 00037410 fb fb 0.0 0.0 ef14332e: BTTrayCE.exe
ef12069e 000138a0 fb fb 0.0 0.4 ef6da99a: repllog.exe AppRun
AfterRndisFnDetected
ef1824ca 02ed5638 fb fb 0.0 0.0 wapdrv.dll afa0b302: device.exe 20
ef182a26 02ed5638 fb fb 0.0 0.0 wapdrv.dll afa0b302: device.exe 20
ef1ad8ca 02e26d58 fb fb 0.0 0.0 ossvcs.dll 8f3c3fd6: connmgr.exe 70
ef2441a6 00017318 fb fb 0.0 0.0 2f3b3a82: shell32.exe 50
ef3a5f6e 00011814 fb fb 0.0 0.0 ef3b3aca: services.exe 60
ef410f9a 0003fd48 f9 f9 0.0 0.0 6f629402: gwes.exe 30
ef6296ae 0312127c fb fb 0.0 0.0 dtpt_srv.dll ef3b3aca: services.exe 60
ef62ca8a 000171c0 fb fb 0.0 0.0 2f3b3a82: shell32.exe 50
ef65cfc2 01608140 65 65 0.0 0.0 afa0b302: device.exe 20
ef7cb70e 036e3200 fb fb 0.0 0.0 tcpstk.dll afa0b302: device.exe 20
ef7d4fda 033946bc dc dc 0.0 0.0 audevman.dll afa0b302: device.exe 20
ef93acde 018916f4 fb fb 0.0 0.0 afa0b302: device.exe 20
ef93afc6 01891640 fb fb 0.0 0.0 afa0b302: device.exe 20
efa034aa 03ef6d24 f9 f9 0.0 0.0 pm.dll afa0b302: device.exe 20
efa038ce 03ef4564 63 63 0.0 0.0 pm.dll afa0b302: device.exe 20
efa03f32 03ef68dc f9 f9 0.0 0.0 pm.dll afa0b302: device.exe 20
efa04fc2 03ef2a80 fb fb 0.0 0.0 pm.dll afa0b302: device.exe 20
efa0b3ea 03e061cc fb fb 0.0 0.0 devmgr.dll afa0b302: device.exe 20
eff5cf5a 03db24d0 fc fc 0.0 0.0 aximfsdspy.dll effa5752: filesys.exe
eff5cfce 03db23b4 fc fc 0.0 0.0 aximfsdspy.dll effa5752: filesys.exe
effa572e 000137d4 fb fb 0.0 0.0 effa5752: filesys.exe
effb1fde 8019f058 01 01 0.0 0.0 0ffb4002: NK.EXE
Last edited by doublelee; 04-25-07 at 04:55 AM.
|
|
|
|
|
|
04-29-07, 12:08 AM
|
#239 (permalink)
|
|
Aximsite Rookie
Join Date: Mar 2007
Posts: 25
Thanked 0 Times in 0 Posts
|
having exactly the same problem with my x30 :-( .. (wm2003se) its so horrible that my h1945 with 266mhz processor feels alot faster than my 624mhz x30.. even when its over 700mhz it feels alot slower then h1945.. this is my second x30 i had no problems like this with my first x30 high. i hard reseted the device and i will check the cpu times for the processes for a while with nothing but a task manager installed.. even tho both axim and hp had same stuff installed on them for a reason some program thats accessing the filesystem process slows it down horribly .. probably a program that needs constant access to the today page or something that needs constant access to activesync (or windows mobile device center) i'll post what i can fix ..
__________________
Palm m125, m130 Tungsten T, T|2, T|3, T|5, E
Axim X30h, Toshiba e740, HP 6315, HP h1945
still use T|5, X30h, h1945, HTC 2125
|
|
|
|
|
|
04-29-07, 09:37 PM
|
#240 (permalink)
|
|
Aximsite Rookie
Join Date: Mar 2007
Posts: 25
Thanked 0 Times in 0 Posts
|
hi, shsmith- even tho i have x30 high it seems like i am having exactly the same problem :-( i had 2 x30's before this and they both had a05 roms and they were running beautifuly with no issues but this last x30 i got has a06 rom and its horrible when i check the tasks i see filesys.exe always using almost all the cpu :-( making the pda super non-responsive and if i am listening to mp3's even taping start menu makes the device to stop cutting out the sound for about 20-30 seconds ... and while it does this of course filesys.exe is using all my cpu time ..  do you thing if there is anything that can be done for x30's ??? (checked the same thing with my h1945 and filesys.exe is most of the time at 0% and when it goes up it only goes to 1-2%) ( i tried to downgrade rom to a05 but it doesnt continue saying i already have a newer rom it doesnt even install the same rom saying i already have the same version) i would really appreciate any kinda help .. :(
__________________
Palm m125, m130 Tungsten T, T|2, T|3, T|5, E
Axim X30h, Toshiba e740, HP 6315, HP h1945
still use T|5, X30h, h1945, HTC 2125
|
|
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is On
|
|
|
All times are GMT -5. The time now is 10:47 PM.
Powered by vBulletin® Version 3.8.2 Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.0
Copyright © 2003-10 LeckMedia, LLC
|
| |
Follow Us
RSS Feed
Follow on Twitter
Facebook
YouTube
