Related
It seems that my phone will sometimes randomly start running out of battery really fast and memmaid shows that the process filesys.exe is taking up the processor at a 100% load. I know that this is part of how windows mobile accesses its storage systems, but I doubt that it's normal. Anyone else having the same problem?
All red items have been uninstalled to see if they were the cause.
I'm running:
Touch-IT full ROM
Battery Status beta 1.04
Default Company Picture Viewer
S2U2 0.5
PocketCM Contacts 0.15
ClearTemp
OP3 ShortCode
FlashVideoBundle
Picsel Browser (Which BTW since installing has made my free space significantly shrink...)
vTap
TRE (reg editor)
memmaid demo
PocketTweak
Pocket Notepad
tGetFile.dll
PocketWeather
HTC Home
Total Commander
psShutXP
Mobile Office
hmm... That list suddently feels a lot longer than it did before. lol
But nothing is running in the background with the exception of ActiveSync.
Thanks guys
Update: Here's a list of what modules filesys.exe has loaded according to Memmaid:
Threads: 24
encfilt.dll
coredll.dll.0409.MUI
ole32.dll
sqlcese30.sys.dll
MSASN1.dll
crypt32.dll
rsaenh.dll
discache.dll
LSFILTER.dll
fsreplxfilt.dll
cachefilt.dll
fatsd.dll
cecompr.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
trueFFS.dll
Fsdmgr.dll
certmod.dll
coredll.dll
Update: It seems that the two coredll's are taking the most resources, but I can't test this out as I don't have any software that can break it down for me, except for abctaskman or whatever it's called and that's only a demo so it won't show me which module is using what other than the other of their CPU usage.
UPDATE: I thought that maybe it was a similar issue to this, but that it was running the compaction on my memory card since I had set the volatile temp to run from that... but that hit a wall as well when I made it run on the main memory again.
UPDATE: I forgot to mention that I also have the Extended ROM enabled as well.
MODS, can we please move this to one of the general forums? I'm not sure which one would be best, though....
OK, so far I've found out that it's a problem not only with this ROM but with WM5 on other devices.
Here is a patch for another device and OS. What I'm trying to figure out is what exactly he patched so we can do the same to our file for our phones.
HI !
I run the German Touch-IT Rom with S2U2 and have the same Problems. Here is what i found out:
- Battery drains in 3-4 Hours IF mortplayer has been started. I usually use Mortplayer to wake me up in the morning. My Music is stored on the SD Card, but this has always been this way.
- I have problems with the batteriy since S2U2 was installed.
-> Maybe Su2u does not suspend our Herald, so that the SD-Card is not suspended, too. Maybe filesys.exe (and with this mortplayer and also HTC Home) randomly ask if the card is still available - Which consumes a lot of power.
...
What do you think ?
I will delete S2U2 when i don´t need the wakeup function this weekend
Hmm... It started around the same time that I added S2U2... I'll try to remove it and see what happens.
I temporarily disabled S2U2 but no change.
Updated with more info.
I hate to bump my own thread, but it seems that updating the thread doesn't bring it up any higher. I wonder if anyone else was having the same exact issue?
I'm determined to solve this problem, as it brings my battery life to a sad 6 hours if the EDGE is on, about 9 hours when it's not. And that's with me underclocking it half the time... and the screen brightness down... and with the phone in "hybernate" or whatever you call the screen being off most of the day...
S2U2 actually did dramatically decrease my battery life... Uninstalling fixed it. Just thought I'd say that; I don't know anything about your other issues, sorry.
I have the same problem too on a mda vario (wizard) with wm6 rom(Dutch version) more info about the rom: http://cleanimport.xda/index.php?threads/350255/
I have been searching around for a solution. But I could not find one.
Here is my list of the modules filesys.exe has loaded according to Memmaid:
Threads: 17
encfilt.dll
coredll.dll.0409.MUI
ole32.dll
sqlcese30.sys.dll
MSASN1.dll
crypt32.dll
rsaenh.dll
discache.dll
fsreplxfilt.dll
cachefilt.dll
fatsd.dll
cecompr.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
trueFFS.dll
Fsdmgr.dll
certmod.dll
coredll.dll
Does anyone have found a solution for this problem?
whixh general??
there is "development and hacking" or "modifying and upgrading" i´m also NOT sure
S2U2 has also caused a battery drain on my wing as well. As i am sure it is the #1 reason my wing will crash (lock up) then when i reboot the wing it freezez permently on the password screen. i have tried numberious soft resets. with and without the microsd in... eventually i have to hard reset!
all applications that is running on your homescreen is consuming battery, because its constantly loaded in memory.
If you want a battery that last long, you need to remove sd-card, htc home, cube, touchflo, point-ui or w/e you use to make your device look cool.
you can put it this way, the more stuff you have, the more cool stuf you have, the faster is your battery draining. Ofcourse you can run BS and set up your device with tweaks and w/e, but in the end it all comes to what you want, lasting battery or a "cool" looking device.
In my personal rom, I use htc home, I like it. I use actionscreen and random acces. I have BS to configure battery usage, I deleted EVERYTHING that I dont use in the rom, and yes, it last way longer then fully or moderate loaded roms, but im sure if I kept only basic os, i could prolong battery with a day or two, but I dont need that. I have a device that is compatible to run so many cool things, and I have it because of the many features.
If you can figure out what you want to use in a daily basis, and you can manage to stay away from the heavy eyecandy-stuff (wich you keep to impress your friends) then you can have a longer batterylife
hi guys,
i had the same problem with S2U2, but since i use the cpu-scaler in battery status it's ok.
My battery lifes 3-4 days.
My settings from cpu-scaler: 130 - 201 - 234 without boost.
so i hope this will help you to cause your problem.
mxstyles said:
hi guys,
i had the same problem with S2U2, but since i use the cpu-scaler in battery status it's ok.
My battery lifes 3-4 days.
My settings from cpu-scaler: 130 - 201 - 234 without boost.
so i hope this will help you to cause your problem.
Click to expand...
Click to collapse
3-4 days!? is that with no data usage, no talking, pretty much letting ur phone just sit on the table? because the ABSOLUTE most i can get is 1 1/2 days. That sounds a lil too extreme...
did someones try filesys patcher from aximsite?
i'm using gprs over bt always on, a2dp (3-4hours daily), ~50 sms, opera mini and mobilegadu (im) and after 20hours i still got ~40% on this battery and this unit. i had another herald earlier and it was not possible to have 12hours without charging...
and btw - ive got s2u2 running all time and after it is cooked into rom its not using so much energy..
but a2dp draining more battery than on other devices (wizard, universal...)
nKiwan said:
3-4 days!? is that with no data usage, no talking, pretty much letting ur phone just sit on the table? because the ABSOLUTE most i can get is 1 1/2 days. That sounds a lil too extreme...
Click to expand...
Click to collapse
no, i uses my phone every day for 20min calling, 30sms and 1 hour gprs internet.
I used to have O2 Neo as my device, and when I tried to install "some apps from HTC rom", I notice a warning about battery drain bug of HTC Camera from some mods and admins in another forum.
Now I owned a HTC P4350 and have HTC Camera as defaul camera app on ROM. My battery always drains above 100mA or even 300mA . Do you think that it's caused by the HTC Camera appplication ? any idea how to remove it from ROM ????
mxstyles said:
hi guys,
i had the same problem with S2U2, but since i use the cpu-scaler in battery status it's ok.
My battery lifes 3-4 days.
My settings from cpu-scaler: 130 - 201 - 234 without boost.
so i hope this will help you to cause your problem.
Click to expand...
Click to collapse
Hello
Here the same. After I uninstalled S2U2 the battery was longer full.
Regards, Tommy
I seem to also have a problem with S2U2 on the LGKS20. Its a pity because its not just eye candy - its the only app I ever found that prevents accidental answer etc.. I also had massive battery drain with SPB mobile shell. bummer
Overall very impressed so far, this is cetainly the best WM device I have owned - it is particularly nice to carry such a powerful package around without needing something with the form factor of a brick!!
Points to note:-
-Battery life imporves after several charges - I get 2 days out of mine comfortably
-I am on ROM 1.35 still and have no problems with lag EXCEPT....
-Memory leak (which happens even with TF3D off) can slow the device down after a few days without soft reset- this needs fixing.
-Opera seems to have an impact on speed once it has been run and then closed - deice actually freezes for about 5 seconds after closing opera (i.e screen is unresponsive to taps)
Anyone else see these issues?
I'm on ROM 1.35 too.
And i too have observed that the phone is generally fine.... until I run Opera. Could be it's not dealing with process clean up properly?
Opera: Yes, I'm experiencing the same thing...on every ROM. Opera seems to be "quitting" for about 5-7 seconds... Not sure why it needs sooo long and so much CPU cycles to terminate.
Does anyone with 1.37 have this opera problem?
adesonic said:
Does anyone with 1.37 have this opera problem?
Click to expand...
Click to collapse
Yep before i flashed to the TLR rom i had that problem...the device after closing opera would take a few secs to close so that the phone was useable. Even with the TLR rom its still the same...not really an issue for me tho.
just upgrade your rom.. the memory leak was improved in 1.37...
Ok, first of all I'm very pleased with and happy with the two LEO ROM variants I've used over the last few months (Thanks Itje and NRGZ28), but I noticed a strange thing happening.
After install, hard reset and adding cabs the ROM's run great, but over time their performance (in my opinion) begins to degrade, to a point where I hard reset, and all is well again for a while.
There's no critical error nothing that crashes the phone just a overall slowdown and creeping laggyness.
To me it smack's of something being cached, some finite resource (not RAM) that's not getting cleared?
Has anyone else noticed this, are there any documented suggested fixes for this? Or even a pointer on what / where to search as to date I've found no reason for this?
Richard
I completely agree with you, seems like if I actually use a ROM for a week or more it seems to get slower.
The joys of using Windows-based machines ^^
Even my desktop after a much longer period of time degrades until I reformat
Actually, I noticed this slowing down issue only with Leo ROMs. After 1-2 weeks, it begin to slow down and it actually use always more RAM than previous week...
7 days....great TV show
I noticed this phenomenon too. At first I thought is was due to a cab that I installed, but I dont think its that as now I install a small set of apps right after the initial install.
this is also why people say "wow this rom is as fast as hell much better than the last one" - its not, it simply feels fast because the old one has slowed down.
The big question is why does a soft reset not fix it? that suggests its not a caching thing or a memory leak?
After two years of ownership Ive got rid of my much loved TD1 and changed it for a TD2 running WM6.5. To my amazement it actually runs slower than my old TD1. It has problems where sometimes the screen hangs then kind of catchs up with itself, typical of WM devices but now much more pronounced on my TD2.
Ive used Advanced Config tool (by schapps) which is, I believe, primarily aimed at the TD1/WM6.1 but that doesnt help much. Ive searched through the forums many times (typically getting distracted by Android forum news for the device)
Im also getting a lot of memory bleed, with memory after reset about 50% and 8 hours later about 70%. Ive made sure that closing apps with the X actually really does close the app.
Is there any point in delaying the inevitable, ie, flashing a cooked rom, or can I salvage some form of WM6.5 dignity with the stock rom using some tweaking tools?
Spenner said:
After two years of ownership Ive got rid of my much loved TD1 and changed it for a TD2 running WM6.5. To my amazement it actually runs slower than my old TD1. It has problems where sometimes the screen hangs then kind of catchs up with itself, typical of WM devices but now much more pronounced on my TD2.
Ive used Advanced Config tool (by schapps) which is, I believe, primarily aimed at the TD1/WM6.1 but that doesnt help much. Ive searched through the forums many times (typically getting distracted by Android forum news for the device)
Im also getting a lot of memory bleed, with memory after reset about 50% and 8 hours later about 70%. Ive made sure that closing apps with the X actually really does close the app.
Is there any point in delaying the inevitable, ie, flashing a cooked rom, or can I salvage some form of WM6.5 dignity with the stock rom using some tweaking tools?
Click to expand...
Click to collapse
Well before you do so you might want to check out htcs website as they do still have a 6.1 ROM on there which you might want to try out before going down the cooked ROM line
I'm using the Topaz 2.53 Stock rom Sense 2.5 with 2.1 Messaging (OS 5.2.21887 Manila 2.5.20113030.0) for almost a year now.
For a long time every thing worked great, messaging worked fast, the hebrew worked perfectly, even the cookie home tab was moderately fast.
In the last two-three months, I noticed that my topaz got significantly slower than it usually was, and that even right after a soft reset (56% of the memory is in use).
I can't understand what had happened, since I haven't installed any new software in the last six months, and haven't changed any setting too.
Has any one else had the same experience ?
hard reset or new phone will cure it.
Some good news and some bad news..
I did do a hard reset, and the phone worked as expected - like new.
I recomend installing the NeoS2007_Driverpack_3, it made the effects look smoother.
After installing CHT (1.8.5 btw) it got a little slower, and after synchronizing with outlook it went back to the original "old" state.
I can say that I could isolate the problem to the home tab, all other tabs are fast.
More over, I can say that overclocking the phone did not solve the problem (or have any effect for that matter).
Can someone tell my if the newer versions of CHT work faster ?
Or is it possible to make the clock smaller and add the flight mode as quicklink without CHT ?
Thanks
Diviner said:
Some good news and some bad news..
I did do a hard reset, and the phone worked as expected - like new.
I recomend installing the NeoS2007_Driverpack_3, it made the effects look smoother.
After installing CHT (1.8.5 btw) it got a little slower, and after synchronizing with outlook it went back to the original "old" state.
I can say that I could isolate the problem to the home tab, all other tabs are fast.
More over, I can say that overclocking the phone did not solve the problem (or have any effect for that matter).
Can someone tell my if the newer versions of CHT work faster ?
Or is it possible to make the clock smaller and add the flight mode as quicklink without CHT ?
Thanks
Click to expand...
Click to collapse
hi, i got my Diamond2 in October 2009, so it is not even 2 years old now. the plastic body is not holding so tight anymore, I bought 3 more batteries hoping to last longer than 1 day of intensive (i used those batteries, which were significantly worse after 1-2 months of use and I am back to the original one again). I flashed the ROM several times, used tess for 1 day, duttythroy for 1 day, EnterpriseV for 1 day, and I sticked to EnergyROM with CHT 2.0.0.0 again. having 80mb of free ram after soft-reset is pretty ****ty, but what can I do? still better than using the stock ROM. the phone is slow since I started to use WM65. it was significantly faster on WM61, but the lack of WM65 features made me accept the slow-down.
necessary tweaks - use the advised amounts of cache (use Touch Tools to adjust it), disable animation, no clock flips... keep it to the "low detail game settings..."
tlsty
Happy end
I decided to give the new CHT (meaning 2.0) a try, and that made a big difference.
The home tab is not laggish any more, at least no more than all the other tabs.
Any way, my conclusion is to do a hard reset every once in a while, and more importantly, install every software in the right order.
Thanks guys
Why not performiung a Hard-SPL and get introduced to the awesome world of customRoms? You will be surprised how snappier TD2 feels on a 20922 build plus all the custom rom goodies
EDIT: Oops just read your last post, everything is fine now... but I would recommend you a custom rom based on a far newer build with Cookie HomeTab 2.0 cooked in. It makes a huge difference, believe me.
The problem with using new roms is the hebrew. I have now a rom that the hebrew language does not mess. I'm sure other hebrew speakers managed to overcome this problem even with the use of wm 6.5.x, but for me this rom good enough.
I might want to use the android (including the sense), once it could be made the native OS .