here's the story: my Tytn II was running fine for some months
one day I was travelling and need to use the GPS until there was just around 8% battery level
then everything started to get slow (GPS map couldn't even redraw)
ok, I though it was in some "slow-clock mode" to preserve battery
then I reseted it and, when I came synced it at home, ActiveSync said it couldn't sync (don't remember why) and it would have to send all the information again
but it was taking forever, so I stopped it and did it again later, when it said it was success
I then noticed my speed dial numbers had been lost, but that's not a big problem
the biggest problem here is that for the last 5 days my Tytn is slowing down very often (like 5 minutes after I reset it), even after I removed all startup programs!
What I'm noticing:
1) GPS maps doesn't redraw (I waited more than 2 minutes... it should take like 1 second)
2) Freecell cards are animating very slow after a completed level
3) touchscreen responsiveness is slow
4) I have TodayAgenda... after I change the date of a calendar item, it doesn't get displayed in the new day (just if I reboot)
5 and probably most important) mstli.exe is using 80 to 98% CPU
any hints?
Lem0nHead said:
here's the story: my Tytn II was running fine for some months
one day I was travelling and need to use the GPS until there was just around 8% battery level
then everything started to get slow (GPS map couldn't even redraw)
ok, I though it was in some "slow-clock mode" to preserve battery
then I reseted it and, when I came synced it at home, ActiveSync said it couldn't sync (don't remember why) and it would have to send all the information again
but it was taking forever, so I stopped it and did it again later, when it said it was success
I then noticed my speed dial numbers had been lost, but that's not a big problem
the biggest problem here is that for the last 5 days my Tytn is slowing down very often (like 5 minutes after I reset it), even after I removed all startup programs!
What I'm noticing:
1) GPS maps doesn't redraw (I waited more than 2 minutes... it should take like 1 second)
2) Freecell cards are animating very slow after a completed level
3) touchscreen responsiveness is slow
4) I have TodayAgenda... after I change the date of a calendar item, it doesn't get displayed in the new day (just if I reboot)
5 and probably most important) mstli.exe is using 80 to 98% CPU
any hints?
Click to expand...
Click to collapse
What rom are u using? Sometimes its good to make a hardreset.
Mikulec said:
What rom are u using? Sometimes its good to make a hardreset.
Click to expand...
Click to collapse
I'm using L26
Since I didn't change anything else, not installing/uninstalling programs and so on, I don't like the hardreset idea (there's a lot of work to set everything back again )
Lem0nHead said:
I'm using L26
Since I didn't change anything else, not installing/uninstalling programs and so on, I don't like the hardreset idea (there's a lot of work to set everything back again )
Click to expand...
Click to collapse
There's often alot more work in diagnosing exactly what the cause is. If you haven't installed anything else then a hard reset (not a reflash) isn't to much work and it gives you the opportunity to progressively reinstal and test any additional software you do use. When you find the app that when installed or configured/used causes the slowdown, then you've found the culprit. Major slowdowns don't just happen out of the blue without changes to the software unless it's due to hardware failure and a hard reset will quickly pick up that sort of issue.
By all means wait to see if others with the same setup have experienced the same issue and if so what they did to solve it but I suspect you'd have it fixed sooner, going down the hard reset route.
Flying Kiwi said:
There's often alot more work in diagnosing exactly what the cause is. If you haven't installed anything else then a hard reset (not a reflash) isn't to much work and it gives you the opportunity to progressively reinstal and test any additional software you do use. When you find the app that when installed or configured/used causes the slowdown, then you've found the culprit. Major slowdowns don't just happen out of the blue without changes to the software unless it's due to hardware failure and a hard reset will quickly pick up that sort of issue.
By all means wait to see if others with the same setup have experienced the same issue and if so what they did to solve it but I suspect you'd have it fixed sooner, going down the hard reset route.
Click to expand...
Click to collapse
I couldnt say it better. I flash and hardreset my phone very often, its a little bit painfull but u will get used to it.
Do not be afraid of the hardreset.
just letting you know I remembered in this same day I had the battery problem, I changed a setting on IP Dashboard (configuring it to keep max 500 KBs history)
I now removed IP Dashboard the problem stopped
will try some other program later, or the old config
thanks
Related
http://www.oliy.co.uk/download.asp?dir=\software\OmapScaler
it is working fine in my wizard but some ppl complain about causing soft resets or not working at all:
about resets: ver .11 have a "max clock step" option, try to reduce it, my wizard works fine with 50 but some ppl r using 25 or even 20...
about not working at all:
1- unpack
2- copy to windows folder in device
3- copy also omapclock.exe to windows folder in device
ftp://xda:[email protected]/Wizard/Misc/OmapClock_v0.2.zip
4- create an icon or run manually
5- set ur desired options and press save
6- copy the .lnk created to windows\startup so it stats with windows everytime (but test it carefully before doing so or u can end with a neverending soft-reset cycle)
my config (working)
- overclock marked and 240mhz (some ppl report soft resets over 220,
reduce this number also)
- above 70%
- underclock marked and 120mhz
- below 30%
- default speed 214mhz (this is the speed center, used if u dont mark
overclock or underclock)
- max clock step 50 (if u have soft resets reduce this number)(mine
work fine at 50 but resets over 70 as example)
- update period 2000 i guess this is the time between system
monitoring of speed in miliseconds, but please correct me if im wrong
- clock threshold 2 (i guess this is the step between clock changes,
but im not sure what is a period...maybe an internal clock tick?)
ok, i tested this one, if u increase it it takes more time between clock changes,
another thing to try to solve soft-resets, i tested 3 and 4...and takes more time
between changes...
some comment: it speeds up depending on the cpu usage but for some reason it dont get along fine with agile messenger in my setup...if agile is connecting it appear as if the device hang but in fact it resumes operation in 10 secs or so...so try to test it first without loaded applications...then load 1 by 1 and test...
lets talk about this and try to solve problems for the ones that have them...
btw...im using molskis rom and working flawlesly...
hi, there,
I followed your instruction fully.
however, when I clicked Omapscaler, I got an "error exception".
I wanted to show you the details..... but I couldn't "copy & paste" the message.
Noted that, I have been running smartskey + Omapclock at 252 stably for long time, and now with Risidoro 2.26 ROM.
hope to get it working.......
thanks,
ecchi
Cool, I'll give this a try ASAP and report back
Activesync quits
I installed the Omapscaler. It seems to work fine. I have it set fairly conservative - middle at 200, underclock at 170 and overclock at 230.
If I am connected to activesync, it quits after a few minutes of idle time. Have you noticed this?
-Kal.
Mine does the same, but in my case it puts a red cross over the green circle, it didnt sync anymore but i can explore the wizard files...and it does it also without the omapscaler, i guess that that have some relation maybe with the proccessor clock losing sync with the pc...dunno...but in my case is not related to omapscaler...but related with the overclock...
Yeah, I saw the same problem with ActiveSync and rom updates.
Just disable the omapscaler, run omapclock and set the speed to 200 or so, then try again.
Oliy, great program, thank you
Again...in my case i tested activesync just using omapclock (NO omapscaler) and does exactly the same...
Since I got the "error exception" with Omapscalar.witrh my current ROM (risidoro), I have started trying XCPUScalar. However, it is not any more stabler as some ppl had mentioned.
Bottom line:
Omap + smartskey ==> most stable, tried at 252, but about 1 day of battery only.
XCPUscalar ==> fixed at 232, stable. fixed at 247 reboot sometimes. Autoscaling b/t 117 and 247 reboot 50% of the time when you launch/close/activesync. I am testing now autoscaling between 117 and 232. Hope it will work.
soft resets with max clock step at 10
I had the max clock step at the default 50, and got a soft reset. Then, per the advice on this thread, I reduced it all the way down to 10. It still soft resets. I have top speed at 230, default at 200, and bottom at 170.
So, I am giving up on this program.
just a q. it stays at least some seconds or die instantly? omapclock alone works?
Yes, it stays up for a while. It seems like it stays up until it goes into standby mode, or I put it in standby manually. A bit after that, it soft resets.
I have not used Omapclock by itself. I have never felt the need for it. But, something that automatically scales up and down to suit the load seems very useful to me; so I tried it. I am willing to keep trying it, if there are bug fix versions.
-Kal.
Maybe ur problem is with the overclock per se, not omapscaler...try using the device with omapclock fixed...if ur device resets then omapscaler is not the faulty...also, what rom do u have? maybe we can pinpoint the problem to a specific rom or set of roms...
hmm... the problem cannot be overclocking, because it goes into the soft reset directly from standby mode. I would think it would be *underclocking* when it is on standby mode, no? Let me do some experimentation with both overclocking and underclocking using smarskey with omapclock, and see what I can figure out. But somehow I doubt that is the issue.
I have standard stock Cingular 2.25.11 rom.
-Kal.
I have been running Omapclock at 230MHz for a while now, with no problems. The Omapscaler would have definitely reset by now.
And what device exactly and with what rom do u have?
It's a Cingular 8125 device, ROM version 2.25.11.1 WWE (stock ROM that came with the device from Cingular).
Omapclock has been running for almost a day now, with no problems, so the problem must be with the scaler.
-Kal.
A theory...
In case the developer is monitoring this thread:
I saw in the other thread on this forum that someone reported that XCPUScaler has the same problem as I have with resetting when in standby mode on a Cingular 8125 with stock rom as well. It may be that these units have some kind of daemon processes that run even while the unit is standby (I know for instance that my unit retreives email when in standby mode), and that causes activity that pushes the scaler to try to scale up. And maybe the unit (or the rom os version) doesn't like the processer speed being mucked around when in standby mode. Or maybe, even that the API call to sense the CPU load craps out when in standby.
This is a conjecture of course, but it seems to me that there can't be very heavy activity during standby. So, could the developer please try to disable scaling when in standby mode? This may solve the problem. Or maybe, just make that an option that people with this kind of a problem can select.
Just a suggestion...
-Kal.
error exception log
I can run omapclock with smartskey @252 stable.
But when I reconfig my wizard to use omapscaler, I got the following exception on launch:
=============================================
OmapScaler.exe
Exception
CompareInfoRef::.ctor+0x35
CompareInfoCache::GetCompareInfoRef+0x9c
CompareInfo::GetCompareInfo+0xc
CultureInfo::get_CompareInfo+0x19
DataTable::RecomputeCompareInfo+0x11
DataTable::Reset+0x6
DataTable::.ctor+0x113
DataTable::.ctor+0x6
ConfigDB::setupConfigDB+0x32
ConfigDB::Load+0x2a
ConfigManager::setupConfigDB+0x14
ConfigManager::Get+0xc
ConfigManager::get_ocLoad+0x15
CpuClocker::readConfigSettings+0xb
CpuClocker::.ctor+0x56
MainForm::MainForm_Load+0xb
Form::OnLoad+0x15
Form::_SetVisibleNotify+0x1d
Control::set_Visible+0x1f
Application::Run+0x7
MainForm::Main+0xa
==========================================
I have a Molski Rom WWE (30MB) G3 Wiza, installed with CE Star (language tool), and some 7 today plug-ins.
any idea?
astromusic said:
In case the developer is monitoring this thread:
I saw in the other thread on this forum that someone reported that XCPUScaler has the same problem as I have with resetting when in standby mode on a Cingular 8125 with stock rom as well. It may be that these units have some kind of daemon processes that run even while the unit is standby (I know for instance that my unit retreives email when in standby mode), and that causes activity that pushes the scaler to try to scale up. And maybe the unit (or the rom os version) doesn't like the processer speed being mucked around when in standby mode. Or maybe, even that the API call to sense the CPU load craps out when in standby.
This is a conjecture of course, but it seems to me that there can't be very heavy activity during standby. So, could the developer please try to disable scaling when in standby mode? This may solve the problem. Or maybe, just make that an option that people with this kind of a problem can select.
Just a suggestion...
-Kal.
Click to expand...
Click to collapse
i have read around that there r several levels of standby, full, partial, etc...maybe he only need to modify it to work only on "full on"...
but maybe we r both wrong thinking about it a lil longer...maybe he already thought about that and omapscaler dont work when on any kind of partial standby, in any case the device is in standby, u r not going to notice if it takes 20 more seconds downloading the mail as example...
and btw, xcpuscalar didnt worked for me also, random softresets, but omapscaler worked like a charm (now im using batterystatus solution and also works fine)
Hi all,
First post here for me Got my TyTN II a few days ago and I'm loving it. It's such a nice phone and has a great build quality.
The only big thing that I find disappointing is the speed of the device. My previous phone was an HTC Wizard and my TyTN II is supposed to be literally double the speed of it, but there's no way it feels like that. In fact the Wizard, when overclocked with BatteryStatus to about 260Mhz) seems faster than this new beast (at times).
The things I particularly notice the slow speed with are...
- opening the keyboard (switching from portrait to landscape mode seems to take 2-3 times as long as with the Wizard)
- navigating (scrolling) through the list of Programs just seems sluggish compared to my [overclocked] Wizard
Another peculiar thing I've noticed is the speed of the "view finder" in the camera. It seems sluggish to the EXTREME, almost like a "night mode" is permanently on! I've noticed that sometimes putting the device in to standby and waking it back up gets the view finder running at "full speed" (what I would say looks like 25-30 fps).
Anyone got a clue what I'm talking about?
Dave
Did you add any applications (which may not be 100% compatible) after getting the machine? I had a Wizard too and am waiting for the TyTN II to come, but with the Wizard certain applications slowed the phone down much!
Regards,
Nika.
Well yeah, I've loaded it with a ton of rubbish now but in all honesty I noticed the slow down when I first took the machine out of the box.
The camera preview/view finder is particularly puzzling!
I've just put BatteryStatus on (a) to see if the CPU is constantly working and (b) with the hope to overclock it a little. I've just noticed that it doesn't support the TyTYN II processor tho so that's out of the window!
Once a new cooked and "polished" ROM comes out for your Kaiser, it will work faster. Almost every first official ROM is buggy and sluggish. it's not the hardware, it's the software.
One reason why I don't buy a device on it's first release.
About the camera preview/view finder slowness, it is due to not enough light in the room.
I was puzzled also. I tought I got faulty device.
Try to use it outdoor, it is very good when it has enough light.
Here is the discussion:
http://forum.xda-developers.com/showthread.php?t=328628
UncleJimbo said:
Well yeah, I've loaded it with a ton of rubbish now but in all honesty I noticed the slow down when I first took the machine out of the box.
The camera preview/view finder is particularly puzzling!
I've just put BatteryStatus on (a) to see if the CPU is constantly working and (b) with the hope to overclock it a little. I've just noticed that it doesn't support the TyTYN II processor tho so that's out of the window!
Click to expand...
Click to collapse
UncleJimbo said:
Hi all,
First post here for me Got my TyTN II a few days ago and I'm loving it. It's such a nice phone and has a great build quality.
The only big thing that I find disappointing is the speed of the device. My previous phone was an HTC Wizard and my TyTN II is supposed to be literally double the speed of it, but there's no way it feels like that. In fact the Wizard, when overclocked with BatteryStatus to about 260Mhz) seems faster than this new beast (at times).
The things I particularly notice the slow speed with are...
- opening the keyboard (switching from portrait to landscape mode seems to take 2-3 times as long as with the Wizard)
- navigating (scrolling) through the list of Programs just seems sluggish compared to my [overclocked] Wizard
Another peculiar thing I've noticed is the speed of the "view finder" in the camera. It seems sluggish to the EXTREME, almost like a "night mode" is permanently on! I've noticed that sometimes putting the device in to standby and waking it back up gets the view finder running at "full speed" (what I would say looks like 25-30 fps).
Anyone got a clue what I'm talking about?
Dave
Click to expand...
Click to collapse
Well, this surprises me. Mine is very fast and in particular for those things you mention!! Screen orientation for example is virtually instantaneous (maybe 1 to 2 seconds compared with TyTn that could take 5 to 20 seconds) and scrolling (with the exception of PIE) is smooth and fast. From standby by to on is less than a second. Compared with the TyTn the camera on 2mg is much faster as well.
Not sure where that leaves us then, if you say it was like that out of the box. That does not sound like it's something you have loaded, but might be worth re-checking that with a hard reset.
I notice a suggestion above that a new ROM might be faster. I really question that because as I say my ROM (presumably the same as yours) is very fast and the single most impressive thing about the device!
In your situation - I would seriously consider a hard reset to be sure it was a good installation. If problems persist, I would be tempted to look at a replacement as that slowness is not normal.
Mike
DaVince said:
Once a new cooked and "polished" ROM comes out for your Kaiser, it will work faster. Almost every first official ROM is buggy and sluggish. it's not the hardware, it's the software.
One reason why I don't buy a device on it's first release.
Click to expand...
Click to collapse
That was certainly true with the TyTn, but my Kaiser (unbranded) is superbly fast. Virtually instant switch on screen rotation scrolling (except PIE), so I'm not at all convinced this is the problem in this case.
Mike
Hi
Main reason for making a device slow is running apps from the memory card. Especially if they are there in the background. Make sure that everything on your today screen and everything that runs more often is on the main memory. Storage card is good for instlations of everything you use and then close (e.g. SatNav, Camera apps etc.)
Kaiser is running extremly faster than anything else.
RonenB said:
Hi
Main reason for making a device slow is running apps from the memory card. Especially if they are there in the background. Make sure that everything on your today screen and everything that runs more often is on the main memory. Storage card is good for instlations of everything you use and then close (e.g. SatNav, Camera apps etc.)
Kaiser is running extremly faster than anything else.
Click to expand...
Click to collapse
GOOD point! Not sure if the OP does this automatically as we all should, it's easy to overlook the obvious sometimes!
Mike
same experience
Hi - I too am having the same problems described above regarding the slowness. I'm using the default HTC installed rom (1.56.405.5).
Were you able to solve the slowness issue? If so, how?
Thanks.
I'm having an odd slowdown issue. Everything runs incredibly fast pretty much 90% of the time except when I'm syncing. Everything on the device slows to a crawl and it takes forever for activesync to finish its business. This occurs both when I'm syncing via the USB cable and when I'm doing it via bluetooth. Any ideas?
Bellfazar, the exact same thing happens to me too... I'm using Vista btw.
Plus i have a serious slowdown after softreset (so maybe it's software related, don't have time for hardreset), but after a minute or so, its fast again
darkilici said:
Bellfazar, the exact same thing happens to me too... I'm using Vista btw.
Plus i have a serious slowdown after softreset (so maybe it's software related, don't have time for hardreset), but after a minute or so, its fast again
Click to expand...
Click to collapse
After a soft reset, the phone has to load everything in memory for the first time.. So accessing the Programs window or the start menu the first time takes a while. Accessing it for the second time, everthing is already loaded into memory and fast again...
Is there not a powertool for WM6 which can help us disabling stuff?
You can use Startup Manager by Baniaczek to disable items that start at warm reboot. Or remove them manually from the WINDOWS\Startup folder
http://forum.xda-developers.com/showthread.php?t=262476
And use HTC Task Manager to kill running applications and/or close them when closing an app instead of minimising it...
http://forum.xda-developers.com/showthread.php?t=330498
sometimes since the new kaiser tweak version i can see (batterystatus) that my processor keeps running at 100%. everything slows down. even a soft reset does not help. when i soft reset without my storage card everything is fine but as soon as i insert the card 100%. man this sucks.
reihen said:
sometimes since the new kaiser tweak version i can see (batterystatus) that my processor keeps running at 100%. everything slows down. even a soft reset does not help. when i soft reset without my storage card everything is fine but as soon as i insert the card 100%. man this sucks.
Click to expand...
Click to collapse
Yeah, I can imagine! Especially when it seems you're the only one (or at least the first that complains). I don't mind trying to help you, but you'll have to answer some questions first:
1. What KaiserTweak.exe (time/date of file) and KaiserTweak.xml (time/date of file, or name of zip-file you downloaded) versions did you load?
2. What tweaks did you use after implementing the new version?
Regards,
Nika.
i never said it was the kaiser tweak nor do i think thats the problem. i restored to a backup from a week before and this still (sometimes happens). so you got me. When i figure this out i will let you know.
UncleJimbo said:
Hi all,
First post here for me Got my TyTN II a few days ago and I'm loving it. It's such a nice phone and has a great build quality.
The only big thing that I find disappointing is the speed of the device. My previous phone was an HTC Wizard and my TyTN II is supposed to be literally double the speed of it, but there's no way it feels like that. In fact the Wizard, when overclocked with BatteryStatus to about 260Mhz) seems faster than this new beast (at times).
The things I particularly notice the slow speed with are...
- opening the keyboard (switching from portrait to landscape mode seems to take 2-3 times as long as with the Wizard)
- navigating (scrolling) through the list of Programs just seems sluggish compared to my [overclocked] Wizard
Another peculiar thing I've noticed is the speed of the "view finder" in the camera. It seems sluggish to the EXTREME, almost like a "night mode" is permanently on! I've noticed that sometimes putting the device in to standby and waking it back up gets the view finder running at "full speed" (what I would say looks like 25-30 fps).
Anyone got a clue what I'm talking about?
Dave
Click to expand...
Click to collapse
Try Q-Mobile 1.11 it is the fastest ROM I have ever used.
After much searching I am lost...here's the deal...
I am running on Dutty's newest ROM and everything is working great except for one stupid little thing...
After I go into the backlight settings and set the timeout to 10 secs, It will return to 20 sec or 5 minutes at any given random interval. I check the setting menu say 2 hours later, and it says 30 sec or 5 min. Any ideas??? it's driving me nutso and killing my battery quicker.
Sounds like a poltergeist issue. Can you flash a Shaman?
Well....hmmm, that's not a viable solution unfortunately, leave it to me to find a bug that nobody else has...does anybody have any ideas...i've manually edited the registry and it still seems to change on its own...is there a 3rd party program that i might try to control it?
sorry boss im running the same rom and just performed a few tests for you but my device is acting normal.
This may not mean much but did you do a hard reset after the flash?
yeah i hard reset and it didn't go away and then I flashed duttys newest rom I believe the apr16 one, and it still does...i'm wondering if it's software related, maybe tomtom or something...i'm about ready to try with a clean rom install and no 3rd party software and add one program a day until I see if one is doing it...i'm lost at this point!!!
Right another thing ive noticed tonight...and i would have thought HTC would have solved this but seems like they couldnt care less.
Left my phone on charge at 6pm and went downstairs to watch some TV...anyways i came upstairs at about 12 and turned the phone on....it was in sleep mode like it normally does. Anyways looked at my screen and saw that the internet connection was still alive even though i specified that it should disconn after 1 min of idling. I also found the phone to be extremely sluggish....touchflow slowed right to a crawl. I opened up the the status and looked at the memory and it was down to 23mb!!!...no bloody wonder it wasnt snappy lol. Now this is where it gets interesting because really i had nothing running on the phone...always make sure all tasks are killed off. The only thing that was running was my gmail polling which takes place every hr or so...so dont know if that was causing a massive memory leak.
Im running it with the 1.37 uk stock rom as its a uk spec diamond...i looked through the task manager and couldnt see anything running.
So has anyone found this with the 1.37 rom??..i was going to flash to the new TLR 1.37 rom but just havent had time...has that rom fixed the memory loss.
Dont get me wrong, i still love the device...i restarted the phoen and all was well but over the past few hrs ive been watching the status of the memory and its slowly getting lower and lower. To be honest ive never come across a phone with such a bad case of memory leakage...ive owned most of the SE smartphones...P800, P900, P910i and P990c and i never found them to be as bad as the Diamond. But the good thing about those phones is that SE usually put out a new firmware to sort the memory leakage problems.
So i was just wondereing if anyone found their devices suffering from massive memory leakage....i know its WM thats causing it...
Just to give you an example....i re-started my phone about an hr ago and it was at 50 odd free mb...less than an hr later its at 40.85 mb free...and 72mb are being used...
Hi Spawn,
I've tried every ROM available and none of them fix the memory leak. After some time, a soft reset is necessary to get the TouchFLO 3D 'performance' back. My biggest gripe, is that when returning to the home screen, and watching the hour and minutes 'flop over' the hour part stutters a little bit. The only ROM I've had no stutter with is the Middle East ROM, and even then after some time the memory leak gets worse and it starts stuttering again. *Really* annoys me. Surely it cant be that hard to make that little animation look smooth and fluid.
HTC really need to get off their collective asses and fix this.
In the meantime, thank god for xda-developers.com!
You could try something: turn off Flow and see if you still get a leak.
I loved the look of the interface, but was forever actioning wrong items/ringing wrong people/whatever. I dropped it and went beck to SPB Mobile Shell (which I had been using on my 'good old' P3600i). I have never seen any leak.
I've noticed this too.
If I click on the little task manager icon in the top right corner as soon as the phone is rebooted it displays about 50% roughly. As the day goes on, its up at about 75% - and I have no programs running at all. The only thing I've used through the day is Texting and a bit of Opera.
It seems the phone needs rebooted every day or 2...
I'm also running the UK 1.37 ROM
Hi,
Does Hibernate help reclaim the lost RAM?
Regards
Hello,
You know, the memory leak problem exists since Windows Mobile 6.0. I had it with my previous Eten X500+. Unfortunately, it has not been fixed with WM 6.1. This is a microsoft problem, not HTC...
Philippe
salada2k said:
Hi Spawn,
I've tried every ROM available and none of them fix the memory leak. After some time, a soft reset is necessary to get the TouchFLO 3D 'performance' back. My biggest gripe, is that when returning to the home screen, and watching the hour and minutes 'flop over' the hour part stutters a little bit. The only ROM I've had no stutter with is the Middle East ROM, and even then after some time the memory leak gets worse and it starts stuttering again. *Really* annoys me. Surely it cant be that hard to make that little animation look smooth and fluid.
HTC really need to get off their collective asses and fix this.
In the meantime, thank god for xda-developers.com!
Click to expand...
Click to collapse
Yep thats what my diamond was doing...it was having a hard time with the clock.
Anyways seems like we are stuck with this memory leak till HTC release a rom which rectifies or wait for someone to cook up a rom which will rectify the memory leak. Only other gripe i have other than the memory leak is the battery but thats not too bad.
Guess ill just have to re-start the phone every so often. I disabled emailing polling as that seemed to cause it to hang a bit ie the connection stays on even though ive told it to disconn after a min of idling.
Hibernate as far as i know doesnt help the situation as my phone last night was in sleep mode.
I have this issue also, and I have to restart the phone once every two days to free up the memory. I think I know where this comes from : TouchFlo3D records every action you make to optimize the use the next time you boot
or not...
raphaelc said:
I have this issue also, and I have to restart the phone once every two days to free up the memory. I think I know where this comes from : TouchFlo3D records every action you make to optimize the use the next time you boot
or not...
Click to expand...
Click to collapse
Yeh after doing a few more tests, it seems like tfl3d is right resource hog...it just wants to take over everything. Im hoping future rom releases optimises the tfl3d but like you im resorting to restart the phone every other day or else it just becomes unuseable.
Its shocking how bad HTC are with their QC control...surely they could see this being a problem ie tfl3d eating up memory like a rabid wolverine.
Thank god for XDA though, at least ill be happy in the knowledge that someone here will be able to figure out this mem leakage and sort it out fingers crossed.
Spawn12 said:
Its shocking how bad HTC are with their QC control...
Click to expand...
Click to collapse
it must be the same dream team which Q-checked windows vista
raphaelc said:
it must the same dream team which Q-checked windows vista
Click to expand...
Click to collapse
LOL...well i run vista ultimate on my laptop and its not that bad...M$ and HTC really dont have a clue when it comes to mem leakage...even in WM6 and before it was apparent that memory leakage is a problem..they really need to address the memory leakage problem....i just wish they would do so rather than ignore the problem altogether.
I've changed the clock to the non-flipping one... it seems to make the TouchFlo a bit smoother as it has less 3D to cope with. You certainly notice it after a day when pressing the Home key - its much quicker!
alright it is with great pain that i am writing this, but i really need some help here. for months i've read the forums, searched for answers, asked little individual questions, IMed with people directly for help... and i'm still having trouble.
i rooted my T-Mobile G1 all the way back when cupcake first came out. everything was great. life was grand. everything ruled. i was a happy android fanboy, talking friends into switching to android, talking crap about iphones... the works... but slowly things started getting slower and slower and slower...
the obvious thing was to wipe and reflash. i was constantly just updating to newer cyanogen roms at that point without wiping. so i wiped to the newest cyanogen at the time (can't remember at this point, but just picture it was like a couple months after cupcake). so things were good again for a little bit, but then it started slowing down again, getting FC's, etc. so a friend recommended i switch to superD... i did, and again, everything was great for a while. i consistently upgraded superD roms (sometimes wiping in between sometimes not). eventually i got to the point where i was on the most recent superD release. it lasted about a day before things started slowing down. examples include when i hit home to exit an application and go to the home screen, the whole screen would either turn black or just show my wallpaper for a good 5 seconds before my home screen would appear, or opening the browser would take like 10 seconds. lots of slow down.
so with the help of a friend i decided to completely wipe and reformat/repartition my sd card. i bought titanium backup but i didn't even bother with it, i said to myself, look, you barely use any of the stuff you have right now, how about just start fresh and reinstall things as you need them manually. so i formatted, repartitioned (using amon Ra's recovery, using the menu option that helps you do it automatically). i made sure i had the most recent radio and spl (this was just a couple months ago), and reflashed the most recent superD (i think its 1.11 if i remember correctly)... again, maybe one day of good performance before everything slowed down. this was also about the time when my battery life started becoming an issue. i'm not exaggerating when i say i couldn't make it home without breaking under 20% battery by the end of the day... and i really don't use my phone THAT much. i'd say i'm a little above average on my usage. i'll get into my widgets and apps in a second, but i really don't use that much stuff...
SO... continuing my story (thanks for sticking with me if you're still reading...). when cyanogens 2.1 for the g1 rom came out (5.0.8d/s) i decided it was time for a change. i reformatted AGAIN, repartioned AGAIN, and flashed 5.0.8. basically, i've got the same story going on. slowdowns, poor battery life, etc.
so here i am with my cyanogen 5.0.8 flashed g1. let me tell you about apps and widgets and stuff. right now i have a regular wallpaper (not live), 14 icons between my 5 screens and just the google search and power management widgets. i used to have calwidget, the genie widget (both news and weather), and the setcpu widgets too, but i decided to take them off to see if it would help with performance. zero help. apps that i either know for sure are always running or i think may have some impact are twidroyd, newsrob, craigsnotif (craigslist notifier), and dealdroid. i don't think any other apps are running and/or do automatic updates for content and stuff like that.
i also use cachemate (purchased) regularly to clear my caches. apps2sd is enabled.
i'm not sure what other information you'd need to help me out, but just let me know and i'll try to give you more details.
right now, i've got slow down like almost all the time. things are constantly pausing, slowing down. i feel like i'm back on my t-mobile mda with winmo5 haha. and forget about it with the battery. i left the house with 90% battery this morning. i went to the gym. went home. picked up lunch. came to work. its been like 4 hours. i currently have 19% battery. all i've done is make 2 phone calls, about a dozen text messages and i've sent 2 tweets (about my battery problem haha). i also used google maps once to look up a number. my wifi and gps is off.
so there we go. really guys, please please please. help me out if you can. any help would be appreciated. i'm so sick of this. and i'm stuck in contract until july 2011. so i'm not getting a new phone any time soon. i gotta figure this thing out.
i really appreciate your help.
thanks.
Dave
OH... and PS... forgot to mention that I just got a new battery this week thinking maybe the battery was just getting old and bad. obviously, no such luck.
I had the same issues till I flashed a SuperD, then everything was fine. I just recently flashed the Froyo from Cyanogen and its like it fixed everything and I'm on a brand new device (knock on wood)!
How old is your G1? Do we know if there are issues with the first run out of the factory? Is that even an issue?
i got the g1 last july. so it was already out for a while at that point. it was new from a store though. i suppose there could be something actually wrong with the phone itself, but i don't know. i was thinking of trying the cyanogen froyo but because its not a stable release yet i figured it would be just this bad or worse...
I promise cm5.0.8 has wonderful battery life when no custom apps are installed and not on any network..
so the question is what is your phone doing, and ought it be doing what it is doing.
There are some nice built in tools for this
Applications->running services
And
Applications -> manage applications (check out the filter in the menu from that screen)
You may be surprised by the apps the think they need to constantly have a service running for some painful trivial job the android API has better interfaces for.. if in addition to that you don't need the app uninstall it.
Otherwise experiment with comp cache and lock launcher in memory.
another example, as i was reading this i was on the phone and i just finished the call and hung up, and i was previously in text messages, it took 12 seconds for my text messages to come up. thats just insane...
as for running services:
- GTalkService <--- I use GTalk all the time
- GenieRefresh Service (Restarting) <--- weird considering I disabled this widget, although I'd LIKE to have it back
- Maps FriendsAppWidgetUpdater (Restarting) <--- never used this in my life
- NewsRob UnreadWidgetProvidor (Restarting) <--- never used the widget before (as a matter of fact, you have to pay to use the widget and i have the free version... weird)
-Twidroyd Background Service <--- understandable, I use this constantly
- AKNotepad Snaptic Update (Restarting) <---- umm... I use this all the time but I don't know why a notepad program would need an updater service running... interesting...
- Swype <---- gotta have that
- CM Updater (Restarting) <--- Don't really think that needs to be on all the time. Can easily manually refresh that...
So that's it. I didn't realize this was included now. Very cool. On older roms I had to use task managers which don't seem to really work. I'm going to stop everything except twidroyd, gtalk and swype right now and see how that does... at the bottom it says Avail: 3.2MB+0.00B in 0 ... Other: 55MB in 4 ... While typing that the Maps FriendsAppWidget just popped back up... I'm gonna see if theres a setting...
In the meantime, does any of this give you any ideas? thank you so much for the advice. Also what does (Restarting) mean?
ezterry said:
Otherwise experiment with comp cache and lock launcher in memory.
Click to expand...
Click to collapse
oh and i have compcache not checked and launcher in memory IS checked... i just tried turning on the compcache option... lets see how that goes...
ok so...
now that i know about those things that were running, i stopped all the ones i don't need, and also went into the apps to see if there was any options for turning off automatic updates, background syncing, etc etc for those things... i'm gonna charge my phone while getting ready to go out and then we'll see how it goes throughout the evening. lets see if i make it home with more than 20% battery left (i'll be gone for like 5 hours). if so then we're on to something here still i find it weird that i can't have a few widgets loaded. but whatever, i'll take a smoothly running phone that lasts all day and i just have to click on icons to get to stuff any day... thanks for the help, i'll let you know how its going tomorrow.
the next day
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
so back to square one... any ideas guys?
thanks so much for any help you can give me. i really really appreciate it.
polarbearmc said:
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
Click to expand...
Click to collapse
Um... The compcache instability scares me a bit
Compcache has had issues (maybe still does) where the first time you enable it the phone crashes.. but then works fine with Compcache on reboot. Otherwise it really ought no make the phone unstable. (it may or may not speed things up depending on how memory is being used.. usually however it allows 12MB of memory that is rarely used to be compressed, allowing a little more active memory to be utilized) You may want to look into wiping dalvik-cache both on the internal memory and SD card:
Enter console and run (this will restart the phone)
Code:
rm -rf /data/dalvik-cache/*
rm -rf /cache/dalvik-cache/*
rm -rf /sd-ext/dalvik-cache/*
reboot
if you get an error about no files found thats not an issue; but other errors may indicate a problem.
This may help system stability (with or without compcache) .. but won't do anything about the battery life (nor speed unless something was seriously wrong)
-------------------
Unfortunately you will either need to erase all your apps and just run stock CM5 [maybe slowly restore your apps you really need] -- OR -- be very patient and debug whatever application(s) are causing issues on your phone (and maybe complain to the dev for failing to read/understand google's documentation on how to write android applications.. not that some of the google apps haven't quite figured that out until recently)
Thus again the main question is what is running on your phone.. The places I mentioned before allow you to see the services (most of which usually restart if you run the related application again) but not strictly all the details to look for.
Example 1 An widget service is likely holding onto memory starving timer services (those not listed) and swapping out other services (phone/launcher making everything feel slow) At the same time the widget is not very active usually and may not connect to the internet at all; thus may not reduce battery life.
Example 2 An IM client on the other hand may requires a service to keep TCP/IP connections alive, and if not coded properly may be very persistent and cause a slow continual stream of data from your phone requiring a large amount of power to keep the phone on 2G/Edge.
Example 3 A Task killer an kill tasks that re-spawn, or kill a task in use if it doesn't know better causing things to behave in strange ways.. so can killing services/applications from the setting screens btw.. but at least that is a one off by user decision not a automatic operation in the background. Tasks when re-spawned may require more data from the internet thus more power to 2G/Edge
User: Then the one that causes me the most problems: A user that keeps the phone in his/her pocket rather than surfing the web, checking XDA, or continuously checking the battery level is using the device less thus will have longer battery life. (careful to not fall into this trap)
Other Ideas:
SetCPU: set the sleep CPU low in profiles (sleep for me is 245/160)[/*]
Verify End action: Settings->End Button Behavior->Go to sleep[/*]
Set longer periods between polls in applications that poll the net (example twitter every 10 or 20mins.. not 5)[/*]
Larger net transfers on wifi if available (example tell newsrob to sync on wifi only) wifi drains the battery faster than idle, but is much cheaper if larger amounts of data are involved.[/*]
As you can see many things will impact the system. You will need to find the ones eating your battery
Another helpful screen for debugging this may be Settings->Spare Parts->Battery History and Settings->Spare Parts->Usage Statistics
I get between 4h and 12h batter life under semi-normal conditions. 4h = surfing 3g + tappatalk + games.. 12h check email/tweat if i get one.. otherwise stays in my pocket. I've seen my test phone hang out for days on a 2g network without data. (so you can always set your apn type to mms if you just need it to be a phone for many hours.. mms keeps mms support btw)
Ebuddy (and most other MSN/AIM/ect chat clients is frequently one of the biggest problems on my phone.. so if I need more battery those are the first to go.. and whomever it is can poke me on gtalk/txt/or wait
Good luck in your search.. Took me a while to make cm5 work as long as cm4.. most of it was mis-behaving apps that I either know to shut off when I need longer battery life.. or have found replacements for.. or avoid widget functionality if the widget was misconfigured. (