Quote:
Originally Posted by kronium
With dynamic ram, aren't you using your battery more when it's filled up? Capacitors have to keep refreshing right?
|
RAM behaves in exactly the same way whether it's filled or not. It doesn't affect your battery life empty or full.
Quote:
|
Also, if available ram isn't a good benchmark, why does my phone always slow down when it reaches the 20meg available mark? Granted it's obvious that the more apps running in the background, the more taxed your cpu becomes.
|
Well you answer your own question. On your phone, whatever you are running, starts taxing the CPU when you see about that much RAM in use. It is likely a single app causing the problem but as you point out in the next paragraph you don't want to bother figuring it out. My phone runs, without a task killer, for days. It runs until I forget to charge it.
Quote:
|
I feel that using a task killer is so much easier than going through the steps of curing a bogging phone. Not to mention being able to kill everything on bootup. A necessity for a speedy phone right off the bat. With no ill effects to date, and a constantly zippy phone, I just don't get your argument. I understand what Linux is trying to do in the background, but who's to say it's the right way? Especially when a battery comes into the equation...
|
Well you are affecting your battery whether you realize it or not. When you kill some of those apps they start back up automatically which uses CPU time to get them to their sleep point and CPU does affect your battery. If you don't think the Linux way of handling memory is right then switch to a WinMo phone where a task manager is a necessity. Your post essentially says you are too lazy to track down what's causing your phone to slow down so you use a task killer. Good for you. That's not the way your phone was designed to work which is why the task managers are third party. I have a zippy phone all the time and I don't have to worry about the task killer side of things. You can do things your way or the way the phone was designed to be used. One way is definitely right and the other is you way. Both will work but I know which one will work better long term.
As to my argument. I present no argument at all. I simply state the facts on how your phone is supposed to work. They aren't debatable points. The only debate is whether or not you want to find out what app is not acting like its supposed to act. You can use a task killer all you like but it's not the way your phone is supposed to perform and that's just the fact of the matter at hand. Developers are great most but all of us make mistakes and when we do things don't work like they are supposed to work. Your answer is to kill running processes, some of which will start back up and eat your CPU and thereby use battery life. My answer is to figure out which developer made a mistake and remove the mistake. I think it's obvious which is a better path.