My phone was running like crap so I ran the task killer and it only got back 35 megs of free memory. I checked for running services and it was no where near the amount of missing memory. I restarted the phone and I have 150 megs again...
I wouldn't have thought a memory leak would be possible in an os where everything is run in java. Has anyone else seen this behaviour?
Sent from my AWESOME Galaxy S
This has nothing to do with memory leaks, but is how Android memory management works. Using task killers usually mess up the automatic memory management.
The default settings for memory management on the Galaxy S aren't optimal unfortunately. Using Autokiller from the market, you can modify these settings (requires root) and avoid the device bogging down because of low memory.
Related
I have had my X10 for about 2 weeks now and im finding that, even though i havent got many apps on the phone, advanced task killer is reporting only 30-40mb of memory available. Does anyone know why this is happening? When i first got the phone it was reporting 100+mb memory for about a week.
Android = Linux
Linux = http://www.linuxhowtos.org/System/Linux%20Memory%20Management.htm
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk.
Click to expand...
Click to collapse
Do you use the advanced view of advanced task killer?
Maybe there are several system tasks running, that eat lots of memory.
i've found that since changing to RIFA016, I have slightly less available memory. (around 30MB if I remember right)
@VMaxxor: I get that i uses some of the RAM for disk caching but i had the same number of apps one week ago and i had 110ish MB of available memory. i dont how it could have cached more things.
@McKebapp: I did just enable the advanced view. the system process seem to be taking up about 100mb of memory but i hav no idea where the other 70ish mb is going.
@Niceties: What is RIFA0106?
R1FA016 is the latest build version available at the moment (correct me if I'm wrong here!)
You might have to debrand your phone to get it! (theres a thread on how to do this in this forum)
As mentioned earlier, Linux is very good at memory management and works on the principle that if memory is there and not being used for anything then it might as well fill it up with something. When you start a new app the Linux kernel organises the memory chunk it needs.
I don't use task killers, they don't really offer any benefits in a Linux based system, unlike Windows which has always been abysmal in doing this.
(BTW - The HTC keyboard rocks !!! I typed all of this fast and with the minimum of errors and corrections)
Sent from my X10i using the XDA mobile application powered by Tapatalk
savjanivv said:
@McKebapp: I did just enable the advanced view. the system process seem to be taking up about 100mb of memory but i hav no idea where the other 70ish mb is going.
Click to expand...
Click to collapse
I've also realized something strange.
After restarting the Phone, I've got around 154MBs of free Memory.
I use the Pro Version of the Advanced Task Killer, that flushs the phone Memory when one locks the screen.
4-5 Days later with normal use, the Phone begins to slow down.
Then, I've just 40MBs of free Memory but no task is open.
I guess this happenes by the Linux Memory Management cashaw mentioned earlyer.
But the Phone is slow as hell.
After restarting it again --> Voilá >150MBs and the Phone is back at normal speed...
problem
this same thing happens to me....turn the phone off and it shoots right back up to 150mb or similar but after awhile it returns to 40 with no apps running and is leaving the phone really slow.
McKebapp said:
I've also realized something strange.
After restarting the Phone, I've got around 154MBs of free Memory.
I use the Pro Version of the Advanced Task Killer, that flushs the phone Memory when one locks the screen.
4-5 Days later with normal use, the Phone begins to slow down.
Then, I've just 40MBs of free Memory but no task is open.
I guess this happenes by the Linux Memory Management cashaw mentioned earlyer.
But the Phone is slow as hell.
After restarting it again --> Voilá >150MBs and the Phone is back at normal speed...
Click to expand...
Click to collapse
i once saw 201 mb free memory....
but soon it reduces to 130-140.
it stays there for me for as long as 2-3 days..
i just set my app killer to be slightly more aggressive and it seems to have done the trick.... sticks around 190 available now!
Is the phone's internal memory shared for both app-storage AND running processes? I had assumed they were separate memory pools.
I monitor my Running Services pretty closely and I can see the memory mgmt only trying to maintain about 18 MB free. The phone starts to lag if there's less than that so I would like to see more available, e.g. 30 MB! Would implementing A2SD achieve this? Again, I was under the impression that it would not. Other threads have specifically stated that A2SD has nothing at all to do with performance and instead is intended to make it easier to switch ROMs by maintaining all your installed apps on the SD card (apart from the memory you need to flash when changing ROMs)
Thank you for any clarification!
Internal memory has nothing to do with RAM, which is what running processes use.
You want auto killer. Can set your minimum memory free and forget it, and let android maintain it.
Sent from my HERO200 using XDA App
I have been using advanced task killer free for a few days and have not noticed any difference in battery life. Shall i keep or uninstall?
same here, but its not bad, and its kill some appz and spece memory - so way not ?
google states that Android Users do not need to use task killers. Programs are left in memory for latter use, the system will even load programd you haven't used yet if the system thinks you might use it. These programs stored in memory use very little power and might actually use more because the program has to reload every time its used. I used task killers for a little. But now i don't.
Sent from Conical .07
Android doesn't need task killers really, if memory gets low then Android will close apps to free up memory, I find that if an app is using to much memory though...like a bad app the task killer is useful ..
To find out if an app is leaking memory you can donwload Watchtower for free to take a look whats going on..
I wouldn't uninstall it, just no need to use it so often..Android usually looks after itself..most of the time.
Task killers are actually a very bad idea. Many apps are making use of a background services, killing them as well (what most blind killers do) will result in a totally unpredictable behavior.
As a developer I really hate them. I have one app which totally depends on a background service. I get sometimes really weird error reports... questioning a little further always reveils that taskkillers have blown away the back-end of this app.
Task killers are stupid. Android has a linux base. The linux way is to cache a bunch of data into memory to allow apps to start and run faster.
How much free memory you are showing is actually meaningless because should an app require more memory the kernel will reallocate memory to the active task, automatically stripping it from idle tasks.
If you are trying to save power what its relevant is which apps are using cpu cycles. As fat as I know the only task killer type app which monitors cpu usage instead of memory usage is Watchdog.
Sent from my Desire HD using Tapatalk
Need some expert advice...I have vbn reloaded 2 as winmo Rom and mdeejay rEVOlution 2.0 as everyday build. Data img 512 mb. I power off, pull battery and load Android immediately using EBL. on first start "free memory" is 256mb. Bunch of apps start, i kill them all using ATK. after 2 days avail mem is only 158 mb. After a week, it does down to 108 mb. At this point I power down, pull battery and start all over again and I am back to 256 mb, then the process repeats all over again.
Is the build leaking mem? Anyone else observe this? Anything I am doing wrong?
Thx
Z
Sent from my HTC HD2 using XDA App
Stop worrying about memory unless you are actually running in to trouble. Android will actively make use of the memory your phone has by leaving apps running and caching things. This is a feature not a bug, there is no need to have memory sitting there empty, it won't improve performance or power use or whatever.
If you're worried by it get Autokiller from the market and set it to keep as much memory free as will make you happy when you see the number. Autokiller just lets you set the limits for the inbuilt memory management system.
Any useful tweaks or settings which I could use? There is many appn on the market and they allow to tweak internal memory management but I have no idea what settings to use.
No matter which I try, my phone always seem to stick to ~100MB RAM Free. Why so much? I'd prefer ~50MB RAM Free and more apps running without closing.
schriss said:
Any useful tweaks or settings which I could use? There is many appn on the market and they allow to tweak internal memory management but I have no idea what settings to use.
No matter which I try, my phone always seem to stick to ~100MB RAM Free. Why so much? I'd prefer ~50MB RAM Free and more apps running without closing.
Click to expand...
Click to collapse
you mean you want 100mb ram free but only have 50mb? you can check out a ram cleaner script. the link is in my signature called mods for virtuous unity. just download the zip file, back up your phone and superwipe, then flash your rom then ram cleaning script then reboot and your done
Actually it was the other way around, I always had 100 MB free and my apps have been closed often. I played with one of the tools to tweak internal memory manager and now my free RAM goes down to 60 and apps stay in memory, this is what I wanted. FireFox Nightly takes a lot on its own...
Will play with settings some more before posting them here.
Only app and root needed, no scripts or Rom flashing.
I'm runing CoreDroid port, I love its theme.
My opinion is if what you perceive as a lack of available memory is not degrading the performance of your phone, including the apps which run on the phone, then it's a non-issue as the latest versions of Android have a much better handle on memory management than the older versions.
I agree but in my case system had 100MB RAM free but when I launched another app it would close other app and system would still have 100 MB RAM Free. So imagine me opening media player and listening to mp3 and then I launch Firefox and music stops, yet there is still 100 MB RAM Free.
I have changed settings and it's better now, Free RAM drops down to 60MB so I can have more apps running.
Previously, Firefox would close whenever I switched out of it, annoying.