Root phantom process(s)

[traajik]

I dont know what the deal is, maybe the individual bit's are getting stuck. Here's the break down.

When you first turn on the phone, you can call/text and clear the ram (on my phone) for the first 2 hours or so will be at about 200mb freed up memory, if i dont clear it up and let it keep running it will be at about 170ish according to my go launcher task manager widgit that's updated every 5 seconds. But as soon as either the first couple hours are up, or after you browse the internet for any amount of time you go and clear the memory up, and you get stuck at 160-170, now i'm unsure if it's due to the time period since it's been turned on. or if it's directly involved with using the internet. either way after a couple hours i can go into super manager or what ever i want and manually end all processes and still only get about 160, which imo is no where near the 190 i want, because when it gets stuck at 160 like that if i dont clean the processes it'll drop down to 130-140, as apposed to 160-170(with out clearing ram) i would be getting if it had just been on for an hour or so and used for phone calls/texting.

So any suggestions? Are the individual bits actually getting stuck? Is the browser/wifi locking the bits for some purpose? Frankly i think i'm too concerned about it but if i could get my full 190-200mb free'd up memory back with out having to reboot everytime i use the internet i'd be incredibly pleased.

thank you.

p.s posted in root section because i'd assume you would have to be root to end the processes i'm talking about (if they're even there), even though i'm n root and still cannot see the processes. And btw i understand it's not that huge of a deal but wtf is eating up that 30mb it concerns me.

 

[tiede]

That's not a problem, that's a design feature of android.
Android's memory management scheme is different than other more popular OSes, and even a little different to desktop linux.
Processes seldom close/die in android, and rather are kept in the background for when the application is again needed. It is up to the scheduler and memory cleaner to make sure you do have a few megabytes of free memory for the eventual launching of a new app, but it won't actually kill any app until it really is necessary. (That's incidently why you don't have a close button on your android applications).

The following link might help you understand better if you are interested:Memory Management in Android Welcome to Mobile World !!!

But yeah, it's fine. Leave it alone. You don't need the free RAM
And yes, Task Killers are pointless (most of the time)...

 

[softtech]

But yeah, it's fine. Leave it alone. You don't need the free RAM
And yes, Task Killers are pointless (most of the time)...

And dangerous. Google recommends against their use. The OS knows what it's doing. Leave it alone and stay out of it's way. You should have a really good reason to use a task killer under Android.

You almost never do.

I discovered the converse problem awhile ago working on some Android software. Your natural inclination in creating a service that you want to run in the background is to try to stop the OS from killing your service. That strategy leads to failure. This is a very tight memory framework and the OS *WILL* be killing your tasks from time to time.

What you need to do, instead, is to learn how to cope with being killed and restarted. Once you've learned that lesson you can create such successful services. It's an important lesson to learn - work with the framework, not against it.

 

[tiede]

Well said.