So i've noticed it a few times now - whenever I finish up a long call (say longer than an hour or so), my Dream becomes extremely sluggish. I've tried killing everything reasonable with Advanced Task Manager but nothing seems to help. I'm usually forced to reboot.
Does anyone know what the problem could be, or a way i could fix it? Is there a better task manager i could be using?
blyn100 said:
So i've noticed it a few times now - whenever I finish up a long call (say longer than an hour or so), my Dream becomes extremely sluggish. I've tried killing everything reasonable with Advanced Task Manager but nothing seems to help. I'm usually forced to reboot.
Does anyone know what the problem could be, or a way i could fix it? Is there a better task manager i could be using?
Click to expand...
Click to collapse
I'm reasonable sure that taskmanager doesn't kill the phone service (I think it runs in the background, check under processes) try killing it manually from there and see if that helps at all.
h.nocturna said:
I'm reasonable sure that taskmanager doesn't kill the phone service (I think it runs in the background, check under processes) try killing it manually from there and see if that helps at all.
Click to expand...
Click to collapse
Be warned though it might cause the phone to hang if its a needed process. So don't go "damn you hnocturna!"
xsnipuhx said:
Be warned though it might cause the phone to hang if its a needed process. So don't go "damn you hnocturna!"
Click to expand...
Click to collapse
let's cross our fingers... *crosses fingers and toes*
Yeah i tried killing both dialer and dialer storage. Didn't seem to help...
Try increasing the CPU frequency.
Cpu is already locked at 528 with setCPU...
Is it possible that this is a hardware issue?
I don't think so, if its still a problem, try reflashing the ROM but with a wipe and clean a2sd. Start fresh!
Related
From what I've read in other posts here I see that the average memory use is about 30-40%. Well mine is at 77%, with only Gyrator2 running in the background, and without 70%. I have the newest Aztor ROM, but even before, with the original ROM the memory use was the same as now.
Is there something wrong with my hardware and is there something I could do to lower the memory use?
try nataly rom. try kitchen tree too. around 70mb free!
Percentage memory use will depend on which ROM you have installed. Also some ROMs have a bigger page pool and so have less RAM available. These sytems will then show higher percentage used, even with the same number of MB free.
How much?
JesperO said:
From what I've read in other posts here I see that the average memory use is about 30-40%. Well mine is at 77%, with only Gyrator2 running in the background, and without 70%. I have the newest Aztor ROM, but even before, with the original ROM the memory use was the same as now.
Is there something wrong with my hardware and is there something I could do to lower the memory use?
Click to expand...
Click to collapse
Where did you get this figure from? (30-40% memory usage!) - I've tried pretty much every ROM in this forum (and few stock ROM's too), and I've never had mine below 60% after soft-reset. You may be thinking about Touch Pro, which has twice as much RAM! If anyone can show me how to have 30-40% RAM usage, please spill the beans! (Not that I've ever needed anymore RAM. I leave alsorts running constantly on my device and I've never had a 'low memory' warning.
grahamkdt said:
Where did you get this figure from? (30-40% memory usage!) - I've tried pretty much every ROM in this forum (and few stock ROM's too), and I've never had mine below 60% after soft-reset.
Click to expand...
Click to collapse
As above - load (just for test) Nataly Rom, and after start, with tf3d you'll have 47-49% EASY...
My memory use at startup is normally below 50% but I'm not using a ROM with TF3D... I'm running SPB Pocket Plus and TouchPal (which uses about 3MB but well worth it.)
Use can drop below 40% if I disable the HTC dialer and use the standard WM one instead.
So I guess as long as no warnings pop up, I don't have to worry?
My memory shows 52% after soft reset regardless of what I have installed onto it. After using RSS, Internet and Email it hits over 75% and becomes very slow. I can kill these apps and get down to about 60-65% so I generally just soft reset after this and I'm back to 52%. This is with stock Orange UK 1.93 ROM.
Just did a soft reset on my Diamond with the stock Sprint ROM and TF3D running. Only active task in the pull-down is Activesync and I'm at 31%
After a soft reset my memory is 47%.
I have a clean boot though but it runs various system programs like Touch Response, probably not much of a difference but I guess I could get that percentage lower.
I also deleted every shortcut in the startup folder in windows, it doesn't give any noticeable problems (yet).
The startup programs were:
AutoShortcut.ink
HTC StartUp.ink
poutlook.ink
After some usage the memory usage climbs to 50~60%. I don't use the Internet browser at all.
Something strange though, some games like Flux Challenge wont run smoothly (when using touch control of your race ship) after a soft reset. Even when my memory is at 50~52% it wont run too smooth anymore...
Does anybody knows what these startup programs do anyway???
Just did a soft reset and my memory is at 62% with WLAN turned off, not much difference when I have Gyrator2 on in the background. Though as soon as I start a application like the album, it jumps up to 80-88%.
When i startup i have about 45-50%. When doing alot of things, i never come higher than 75% or something....
Do you use the newest ROM?
VerusAmos said:
After a soft reset my memory is 47%....
I also deleted every shortcut in the startup folder in windows, it doesn't give any noticeable problems (yet).
The startup programs were:
AutoShortcut.ink
HTC StartUp.ink
poutlook.ink
Click to expand...
Click to collapse
Kevlah said:
My memory shows 52% after soft reset regardless of what I have installed onto it....
Click to expand...
Click to collapse
After removing my Startup items I am still at 51% after soft reset so it hasn't made much difference (AnswerKeysDisabler, AsyncKiller, AutoShortcut, batti, HTCStartUp, poutlook). After this I disabled TF3D and soft reset gave me 44%. I find TF3D and some of those startup items are too useful to disable and if I did disable TF3D I would need to add today items which would probably bump it back up to about 48-50% anyway.
EDIT: Just found this option in Opera to clear disk cache on exit and it has helped a bit: http://forum.xda-developers.com/showthread.php?p=3009554 or you can redirect the cache which may be better: http://forum.xda-developers.com/showthread.php?p=2791743
I've got arround 47 - 49 %. Sometimes around 55% but when i wait i few secs, it drops to 47 -49 % again. I used the Diamond Tweak to disable the Diamond Phone Pad. So right i have the default windows phonepad.
I also have Memmaid installed. And tweaked the system with this tool.
Also i configured memmaid to kill every unusable processes at 12:00 h.
So all day long i have a fast system.
I use the latest HTC NLD rom (2.03)
Sleehond said:
When i startup i have about 45-50%. When doing alot of things, i never come higher than 75% or something....
Do you use the newest ROM?
Click to expand...
Click to collapse
I use AlphaZeros' a.z.t.o.r newest version. Will install NisseDILLIGAFs rom when it's done and see if there is any difference.
is there a good program to clean the temp files?
sgerinckx said:
is there a good program to clean the temp files?
Click to expand...
Click to collapse
I heard about ClearTemp and was about to use it until I saw a thread on here saying it had cleared all files off the device including internal storage and the only recovery option was a backup (if one had been done before this happened) or a hard reset. I decided not to take the risk and try to find out where the files were located and delete them manually. (I have only looked for Opera so far but when I get time I'll search for the rest).
Kevlah said:
I heard about ClearTemp and was about to use it until I saw a thread on here saying it had cleared all files off the device including internal storage and the only recovery option was a backup (if one had been done before this happened) or a hard reset. I decided not to take the risk and try to find out where the files were located and delete them manually. (I have only looked for Opera so far but when I get time I'll search for the rest).
Click to expand...
Click to collapse
hehe ok, thanks
filesys.exe remains at 16.4mb.. and wondering if this is normal or how to reduce it to normal? Or any fix to this?
royalbloodvi said:
filesys.exe remains at 16.4mb.. and wondering if this is normal or how to reduce it to normal? Or any fix to this?
Click to expand...
Click to collapse
I think its normal, it uses 16.3mb in my xperia...
Huh?? Not for me. It takes 2129kb.
Cool eh?
That's defniately not taking up 95% of its ram though, considering it has like 200.48 MB of program memory. Check your programs running, make sure you dont have alot of stuff running, and restart your phone. If it starts up and stays at 95%, youve got a problem. Either alot of apps are opening at the start for some strange reason, or youve got a very screwed up ROM.
im using gttrab's barebone r3.6. very stable.
one thing i noticed was: when i take out storage card, filesys.exe: 7mb.
doesnt ANYBODY have this problem too?
im just running normal stuff, spb shell, voice command, s2u2. thats it....
my nexus one is charging on a regular basis around 106-7 F. I know there is another thread about this issue but the question was not resolved. So does anyone have experience with this issue. Is it a defect or dangerous? I have OSmonitor installed, this si where I am reading my temps. I also notice the CPU usage is pegged around 98-99%..is this normal?
I heard using setCPU with a charging profile can solve this problem if you have root?
No, it is not normal for the cpu to be maxed out while charging. Are you using the car dock or a wall charger?
nexous one
mine does the same thing all the time its not going to damage your phone at all
my phone has got about 120 F on car doc
my phone is perfect just set your set cpu for fail safe and your all good
You probably could use SetCPU to solve this problem, but the fact that your CPU usage is so high in the first place means there is something going wrong - my guess would be a rogue app.
Try downloading a task killer from the Market. Kill each app running one at a time then check your CPU usage. You'll soon find the culprit.
sn95chico said:
my phone has got about 120 F on car doc
Click to expand...
Click to collapse
Yeah I'm starting to see the problem with the phone having a metal casing. Not good when it's summer and you have to place it under direct sunlight for extended amounts of time, while using navigation AND charging
That thing can get burning hot alright.
Are you using froyo 2.2?
I have had the same problem; I also have random periods of high cpu use when not charging as well. This issue is not caused by problem apps either. I must reboot to fix the issue, sometimes I must reboot several times until the cpu load is back to normal.
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
I will also try to reapply the 2.2 update.
Marine6680 said:
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
Click to expand...
Click to collapse
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
frandavid100 said:
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
Click to expand...
Click to collapse
I bet your heat issues are related to cpu loads or staying at high frequencies like mine. Sometimes the phone does not feel like it is really running as hard as the system monitors say, though it may still get hot.
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
I am re-flashing the leaked 2.2 update to make sure there was no issue with the original install. I am also using the copy my GF downloaded when I sent her the instructions on the off chance that my download was corrupted in some small way; unlikely but hey. I do think that the original flash may have gone wrong, as mine hung and never rebooted after the flash was complete; I had to manually reboot. Lets hope this fixes it.
This issue may be more widespread than we realize, as many people do not actively monitor their cpu or notice/worry about the heat after charging. I do believe that these leaked ROMs send debug data to google, I remember reading something along those lines; these are internal test ROMs after all. Maybe this is a reason that 2.2 is not out yet, this and other bugs found during real world use.
Marine6680 said:
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
Click to expand...
Click to collapse
What I did was follow this guide up to the point where you have a stock eclair rom, then not upgrade to Froyo. Keep using that for some time, see whether the phone gets hot or not, THEN (if you want) move back to Froyo.
I am using the wall charger hat came with the nexus one. I am also running Froyo 2.2... can I set a CPU fail safe without my phone being rooted? Also what is a quick to check if my phone is rooted? I just bought this Nexus One from someone. I know on my G1 it was rooted bc I had Superuser permissions.
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
The fastest way I can think would be installing Lamppu, then trying to use it to light up the camera flash. If it works your phone is flashed, if it doesn't it's not.
As for your other questions... sorry, i don't know. I hope someone else can help you.
foethalove said:
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
Click to expand...
Click to collapse
Thats a system process so you can not kill it.
Going to test my GFs nexus and see if she has these issues as well.
I restored my N1 to the factory image, the updated back through each update to 2.2; so far so good. My GF's N1 has been running fine since I really started watching it, so I figured it would hurt to try to restore and redo the update.
No 100% cpu load during charging any more!
i am using the Motorola charger and my phone is not getting hot at all. with the charger that comes in the box for the N1 it seems to heat up.
Still had the CPU load get stuck at 100% today; though charging is not forcing 100% loads any more.
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
frandavid100 said:
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
Click to expand...
Click to collapse
System monitor apps, some will even put a little icon in the notification tray that shows current cpu load.
i was doing my 5k run with my recently updated hero and about a mile into the run pandora radio started skipping and then stopped. when i looked at my phone it was rebooting. i have task manager and killed all the apps before i started and unchecked jogtracker and pandora so i could use them. it didnt last long. the phones screen froze and dimmed then crashed until it finally restarted. is there a reason for the crash. seems to me like a memory problem. i have a two gig card with one pt. five left on it. and the internal memory is at 91mb. it always worked before i rooted and installed cm6. the phone in general is way faster and more responsive since i put cm6 on it but for some reason the two apps running together arent working. thanks for any help
Try removing the task manger reboot into recovery and wipe Dev/ cache and try it then might work good luck
Root-Hack-Mod-Always™
I've tried running with and without various task managers and always wind up uninstalling and reminding myself that I should know better.
I seriously don't think Froyo and these mods need a task killer. If anything, they seem to cludge things up. My phone was running beautifully for two weeks and earlier today I thought I'd try out a different task killer. Mistake. I uninstalled it after 1/2 hour because it just made the phone feel funky.
Try running without for a couple weeks....
jwhistler said:
I've tried running with and without various task managers and always wind up uninstalling and reminding myself that I should know better.
I seriously don't think Froyo and these mods need a task killer. If anything, they seem to cludge things up. My phone was running beautifully for two weeks and earlier today I thought I'd try out a different task killer. Mistake. I uninstalled it after 1/2 hour because it just made the phone feel funky.
Try running without for a couple weeks....
Click to expand...
Click to collapse
+1, CM6 does not need a task killer/manager. The best method is to download AutoKiller (which lets you alter Android's internal memory manager, much more effective than task killers) and change the settings to Strict or Aggressive. Also, two of the biggest problems that create soft reboots that you describe is (a) the VM heap size being too small and (b) CPU speeds being too high. So, steps to take:
1) Uninstall task killer
2) Install AutoKiller and change settings to Aggressive
3) Change SetCPU/Overclock Widget settings to 691 max/595 min with screen on, 480 max/245 min screen off
4) Change VM Heap size (in Cyanogenmod Settings) to 24 MB and reboot
The only other possibility I can think of would be kernel instability. If you flash Decand3nce's #14 Stable kernel found here it is far more stable than the stock kernel and (IMHO) has much better performance than the stock kernel.
These steps should rectify any memory and/or CPU overconsumption problems you are having that could cause the reboots (as well as make your phone much faster, smoother, and more stable). If these steps don't fix it, it most likely is a problem with one of the apps themselves.
Good luck!
thanks for the help.
also on the restart i got this message Sorry the applicating spring updater (process com.sprint.ce.updater) has stopped unexpectedly. please try again. force close. this is probably the cause of all the problems thanks
the changes u pointed out seemed to have fixed the phone so far. thanks so much for the great instructions. u da man.
i noticed a couple times a day the phone reboots. should i back off of some of the settings.
kevinr12345 said:
i noticed a couple times a day the phone reboots. should i back off of some of the settings.
Click to expand...
Click to collapse
Yup, lower the max cpu.
Froyo Hero to the rescue
what is the VM Heap size for what does it change. mine is at 16 right now.
clutch_08 said:
what is the VM Heap size for what does it change. mine is at 16 right now.
Click to expand...
Click to collapse
Its the amount of memory each application can take up maximum. You tend to get smoother running stops with higher vms; I set mine to 24.
Froyo Hero to the rescue
I did a mass app update in the Play Store last night (c.18 apps but crucially, I don't remember which ones!) and am now stuck in the following loop:
1. Boot handset (S3 LTE)
2. Watch responsiveness get progressively worse over period of a few minutes while available RAM shrinks progressively to zero
3. Phone shuts down or soft reboots when it runs out of available RAM.
I can't see any obvious culprit but then am no real expert in what I'm looking for. Desperate to avoid factory reset, particularly as I can't even get the phone to stay on long enough to sort out my backups.
Any thoughts?
Install this then run it as soon as you have booted up, it will stop the apps and free up your ram.
https://play.google.com/store/apps/...GwsMSwyLDEsImNvbS5jbGVhbm1hc3Rlci5tZ3VhcmQiXQ..
Raistlin1158 said:
Install this then run it as soon as you have booted up, it will stop the apps and free up your ram.
https://play.google.com/store/apps/...GwsMSwyLDEsImNvbS5jbGVhbm1hc3Rlci5tZ3VhcmQiXQ..
Click to expand...
Click to collapse
Thanks for the suggestion but the task killer shows no tasks running (and therefore nothing to kill), which fits with what the native task manager is saying. I don't know whether it's some background process but whatever it is, it seems quite hard to identify!
Very confused. From what (admittedly little) I understand, it should be impossible for Android to "run out of" RAM, which is exactly what's happening to me. Which begs the question, why isn't the system doing what it is supposed to? Which in turn makes me think this may not actually be app-related.
Sorry, bit stream of consciousness but if anyone else has any ideas they'd be gratefully received.
maybe some apps don't play well togheter and triger this issue, is your phone rooted?
maranello69 said:
maybe some apps don't play well togheter and triger this issue, is your phone rooted?
Click to expand...
Click to collapse
Possibly, I guess the question is which apps? Yes, I am rooted.
Starting to wonder whether this is related to the problems with SuperSU that seem to have arisen in the last update.
dave_uk said:
Possibly, I guess the question is which apps? Yes, I am rooted.
Starting to wonder whether this is related to the problems with SuperSU that seem to have arisen in the last update.
Click to expand...
Click to collapse
In case this is of use to anyone else, having now unrooted and removed SuperSU, problem seems to have disappeared! Chainfire is working on a fix.