Can anyone explain the amount of RAM that this phone is suppose to have?
The specs for the phone lists 768 MB. However, the total memory that comes up is 617940 kB.
Thanks.
Bull Shot said:
Can anyone explain the amount of RAM that this phone is suppose to have?
The specs for the phone lists 768 MB. However, the total memory that comes up is 617940 kB.
Thanks.
Click to expand...
Click to collapse
where are you finding this number? i am at 758 MB. since i have a bunch of apps installed, that would seem about right.
How are you guys getting so much free ram? When I check on Task Killer, whenever I kill all the apps I'm not using it usually shows 358 mb ... and programs I'm not using automatically keep running (i.e Maps).
hmm maybe im not checking the right place? i'm getting my 758 mb number from settings--SD and phone storage. the internal phone storage tells me 758mb.
on an unrelated note though, you shouldn't use task killers. they are considered by most to be more of a drain on your battery life as android is already setup to manage closing unused apps on its own.
Many people use the term "memory" to mean system memory as well as storage. I try to avoid calling system storage as "memory" and tend to use "storage" instead, or refer to the type of storage.
Total ram is around 768mb. Part of it is reserved (not sure why, possibly for filesystem caching) so around 603mb is available. For this platform that is a healthy chunk of RAM to work with. Even with my hefty usage I have ~126mb free.
Internal storage is something like 2gb, with it partially consumed by the Android install as well as NAND configuration adjustments for reliability which cause some of the storage space to be consumed through hardware (there's an excellent explanation of this somewhere, don't have a link handy), resulting in about 1.1gb being available. I have 103 apps installed, 523.5mb of the internal storage used, with 638.8mb available.
There was an excellent tool posted on xda (http://forum.xda-developers.com/showthread.php?t=1066060) called Android Optimizer that gives a lot of good information about memory, storage, cpu usage, etc. I'd recommend checking it out. It's not available on the market and it is a little buggy so use it with a bit of caution if you choose to use any of the optimization functions.
cool. thanks for the explanation nimdae!
There have been so, so, so many posts on this topic that I will not rehash them all here. Instead, I will ask a simple question: For what do you use all that free RAM?
Ask yourself that question, and be serious about it. I think you will find yourself uninstalling your task managers and memory optimizers before long.
Edit: to avoid unnecessary discussion, Watchdog is in fact neither of those, and I would highly recommend it as the only memory app you will ever need.
Edit 2: the total RAM displayed is the RAM that is actually available to be used by anything the user may want to run. As a poster earlier said, the system reserves a certain amount of RAM for its own use to keep important processes moving along. The reserved RAM is not available, and so doesn't appear in total RAM. Unless you want to uninstall the OS. Then you could have access to all 768 MBs.
I would like to reiterate why you should not use automatic task killers.
As of, I believe, Android 2.0, the garbage collection and memory management was significantly improved. However, this was not a new system in Android, it always existed.
How it works:
If you haven't noticed with Android, when you leave an app, it doesn't close it unless the app specifically does something to end the process. This is by design. Android allows the app to remain in memory. Frequently used apps will load faster with this design. A "task" that is not killed and is in the background ONLY consumes memory, it does not "run" (in Linux terms, the process is actually in a "stopped" state so the task can't do anything anyway). Only a "service" can run in the background. Most apps that have long running services have lightweight services.
If an application loads that requires more memory than is available, Android will examine backgrounded tasks for candidates to be killed to free up memory. This makes it so as many tasks as possible can remain in memory for better performance. In understanding this, you should know that if you have a large amount of memory, and memory usage is high, this is a GOOD THING. With the amount of memory in the I2, there is a lot of breathing space for this.
There is one other case where a backgrounded task will be killed: if it has been in the background for a certain period of time without being brought forward. Killing a task to free up memory to load another task can actually be a little cpu expensive (but not THAT much) so this can make it slightly easier.
Please note that backgrounded tasks WILL NOT contribute to battery drain. Only tasks at the front and services will. Killing your backgrounded calculator will do nothing for you other than free that small amount of memory it uses. Used memory does not contribute to extra battery drain as DRAM refreshes happen on ALL cells anyway.
Background services can also be made candidates for being killed. If an app needs more memory than can be made available by killing backgrounded tasks, then services become targets to be killed as well.
Automatic task killers cause a couple of problems. A less major problem is you lose that one benefit you get by keeping tasks in the background: performance. I don't just mean how fast it loads. If it can bring a backgrounded task to the front from memory rather than load from storage, you remove extra processing to load the app, including storage access, that contribute to higher battery drain. The other problem is a poorly configured task killer can break things like notifications.
Managing your services is always a good idea. Having a lot of services running means background processes that are capable of contributing to battery drain. Additionally, there are apps with misbehaving services (services that consume resources or use features they shouldn't). While I'm against automatic task killers, using something to monitor and manage services is a good idea. Just always keep in mind the implications for killing a service: it may affect a feature to an app that you would rather not impact.
Excellent explanation nimdae! Task killers are the devil.
On another note, my posts are getting too long...
nimdae said:
On another note, my posts are getting too long...
Click to expand...
Click to collapse
Everything is longer in Texas.
xgunther said:
Everything is longer in Texas.
Click to expand...
Click to collapse
That's what s...no, that's too easy.
Move along, nothing to see.
Before I read this I was like a task Nazi. I killed my tasks often, but now I think I will just let them be. Nice write up BTW. Very informative.
Sent from my ADR6350 using XDA App
TB13 said:
Before I read this I was like a task Nazi. I killed my tasks often, but now I think I will just let them be. Nice write up BTW. Very informative.
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
Remember: I'm not saying don't manage things. Poorly behaving services are the #1 cause of high battery drain (at least on non-LTE devices), and this will be even more problematic when you overclock.
xgunther said:
Excellent explanation nimdae! Task killers are the devil.
Click to expand...
Click to collapse
I tried not using them and I get better battery life with them...I use it maybe 3 times a day after heavy multi tasking. It's to each their own..but I see results for it..like 5 extra hours.
Sent from my ADR6350 using XDA Premium App
knipp21 said:
I tried not using them and I get better battery life with them...I use it maybe 3 times a day after heavy multi tasking. It's to each their own..but I see results for it..like 5 extra hours.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
If you get that much extra, you have a misbehaving app. Better to get the app developer to fix it or find an alternative.
nimdae said:
If you get that much extra, you have a misbehaving app. Better to get the app developer to fix it or find an alternative.
Click to expand...
Click to collapse
True, I don't need to use it often though lol
Sent from my ADR6350 using XDA Premium App
I'm in Texas as well.
sent from a phone without root.
I use a task killer only to manually kill an app that freezes or something. Its easier than going to manage applications. I have the autokill disabled.
Sent from my ADR6350 using XDA Premium App
AngelsPunishment said:
I use a task killer only to manually kill an app that freezes or something. Its easier than going to manage applications. I have the autokill disabled.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
CyanogenMod (maybe other ROMs) have a feature to kill a frozen app by holding the back button (long press, whatever). However, this can also be an annoyance on systems where for unknown reasons it registers a long press on a tap (my eris did this a lot).
Related
I just got the Dinc and I have advance app killer on it and when I used to push it i would have around 210 mg available memery on it. Now a days I push it and it's like at around 60-100mg every time I push it? What uses the memery and how do I view it and clear some stuff out?
veritas21885 said:
I just got the Dinc and I have advance app killer on it and when I used to push it i would have around 210 mg available memery on it. Now a days I push it and it's like at around 60-100mg every time I push it? What uses the memery and how do I view it and clear some stuff out?
Click to expand...
Click to collapse
You don't need task killers for Android, it will free up memory on its own. If you are rooted though there are some apps that will let you tweak the parameters of Android's internal memory management. The Dinc has plenty of RAM so I am not sure I would even worry about it.
Sent from my ADR6300
but it seems that there are always 6-10 apps always running?
veritas21885 said:
but it seems that there are always 6-10 apps always running?
Click to expand...
Click to collapse
Unlike a Windows device, seeing an app loaded and it running are two different things. An app on a Linux based system wil not use resources unless it is actively doing something. Linux does a good job of handeling its memory, hence no app killer is required. You can actually make your system do worse because apps will launch again and again as they are killed. Just let the system do the memory management.
veritas21885 said:
but it seems that there are always 6-10 apps always running?
Click to expand...
Click to collapse
download Systempanel by Nextapp... it will show you the truth. if you buy the donate version you will get to monitor your phones history and you will see which apps are truly using your battery and cpu.
task killers are a waste.
ATK or not - what about sync?
Opinions vary on using a task killer.
That said, take a look at what and how often things are synching on your device.
Facebook, twitter, mail accounts, etc. etc.
If synching lots of things frequently, automatically, consider tweaking those that synch, as well as their frequency.
Also you need to understand about RAM on a computer and RAM on a phone are different. You want a higher number on a computer because that allows for more processes to happen, however on a mobile device a lower RAM is actually better, due to the phone having different programs running in the background. The RAM allows them to boot up faster and get you back to where they were the last time you had them active. Taskkillers are pointless, and this comes from someone who use to swear by them.
I think many of us are using some kind of task killer. BUT, I find task killer sometimes cause more problem than it solves. And sometimes it doesnt really increase free RAM.
What I did was create a simple app to force Android memory manager to free RAM (by unloading tasks based on its own logic). This way you eliminate 3rd party task killer wrongful termination of tasks such as those active ones required by widgets etc.
This app just basically starts and creates a huge heap (forcing Android to free RAM) and then closes.
(You may still see this task linger in memory after you run it, but it will be unloaded the next time you start other app. You will see your free RAM increased a lot)
====Edit
You May not see free RAM increase immediately after running. You will see RAM increase a lot a bit later after you have started other app (which forces BfreeMem to be unloaded from memory)
Tip: Just put a shortcut on desktop. Click it when your RAM is low (<50-60Mb) and it will do its job. Dont run it when your free RAM is above 90Mb.
I'm trying it
Sent from my GT-I9000 using XDA App
This app should be tested by more Samsung Galaxy S owners to see if is working as it should be or not.
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
cosmoboi said:
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
mib1800 already had got ur all private data, no more diffs.
cosmoboi said:
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You have to wait for BfreeMem to be unloaded. (If you are impatient use a Task killer to unload it and you see it frees up lots of RAM.
Basically BFreeMem is a very bloated. When it starts it force Android memory manager to unload other tasks to cater to its RAM requirement. After that if you start other app, Android mem mgr will unload Bfreemem thus freeing huge chunks.
I tweak it to works best if your free RAM is around 50-60Mb. When I run it and when BfreeMem is unloaded later, free RAM goes up to about 100Mb.
btw: this app requires no permission so your data is safe
AutoKiller is a much better alternative.
The concept sounds correct. Not entire sure if it will work in practice.
psychedelic'd said:
AutoKiller is a much better alternative.
Click to expand...
Click to collapse
My purpose is to have something that does not circumvent Android memory manager which keeps track of tasks and their stats. It knows better what tasks are best to kill based on their usage/last access/active state/priority. Furthermore, if Android memory manager kill a task due to low memory, it will save the state for that task so that the next time that task is used the saved state is restored.
3rd party task killers sometimes mess this up by killing tasks which are actively use (resulting in those tasks being restarted just after being killed leading to wasted power and more lag) or killing dependent tasks such as those used by widgets without saved state causing widgets to malfunction.
snapper.fishes said:
The concept sounds correct. Not entire sure if it will work in practice.
Click to expand...
Click to collapse
I am using it. It does free up RAM. Is it useful? Depends. If you have lots of active apps (widgets/service etc), those freed RAM is filled up soon as Android restore back those "killed" tasks. Not much gain here. On the other hand, if you have lots of zombie apps lingering in memory then yes. The extra RAM does give a boost to the next app you open
AutoKiller is less of a task killer and more of a memory manager. Sort of like what your app is trying to do, but much better. More information: http://andrs.w3pla.net/autokiller/details
Your concept is good, but having an app that continually increases ram usage will waste battery. Then having to kill that app manually in order to free up ram is tedious. Just my 2 cents.
The new task manager in Touchwiz has a function to manually clear ram any way, which works great.
psychedelic'd said:
AutoKiller is less of a task killer and more of a memory manager. Sort of like what your app is trying to do, but much better. More information: http://andrs.w3pla.net/autokiller/details
Your concept is good, but having an app that continually increases ram usage will waste battery. Then having to kill that app manually in order to free up ram is tedious. Just my 2 cents.
The new task manager in Touchwiz has a function to manually clear ram any way, which works great.
Click to expand...
Click to collapse
OK. AutoKiller is changing Linux configuration. Unfortunately, it needs root.
I have used the TouchWiz TaskMgr clean Ram at safe level - it still messed up my widgets (Beautiful widgets, weather & toggle)
Bfreemem app does not continually run or increase RAM usage. You just run it when the free RAM is low (or close to threshold). At this low RAM level it just knocks other tasks out of RAM. btw: You should NOT run it when you have huge amount of free RAM. You should run it when RAM is low like <50Mb.
You dont really have to kill Bfreemem task manually since it will be quickly unloaded by the Android memory manager when RAM is required since its state is finished.
JUst put a shortcut on the desktop and click it when you feel RAM level is low and it will do its job.
Can it be used with autokiller?
It could be also automated to check if memory is low, and automatically kill applications. Battery drain would be present in that case tho..
Never has the default task killer from samsung messed up my widgets including Beautiful weather, I tried using task killer and never saw the benefits of it since andriod automatically keeps 40MB of free ram...
EarlZ said:
Never has the default task killer from samsung messed up my widgets including Beautiful weather, I tried using task killer and never saw the benefits of it since andriod automatically keeps 40MB of free ram...
Click to expand...
Click to collapse
When I try the option Level 1 - Clear Memory (in Samsung task killer), my beautiful widget clock stop working.
Soniboy84 said:
Can it be used with autokiller?
It could be also automated to check if memory is low, and automatically kill applications. Battery drain would be present in that case tho..
Click to expand...
Click to collapse
Personally, I dont use task killer. Not sure whether Autokiller kills tasks physically or just adjust some running config. Just have a feeling task killers (those that kill tasks physically) cause RAM leak. For example when my phone reboot, I can see at least 12 tasks (in Advanced Task Killer) and free RAM is about 95Mb. If I physically kill those tasks, my RAM may temporarily goes up to 130Mb but sometime later free RAM drops to 50-60Mb and there were no more tasks to kill.
When I use Bfreemem, my free RAM fluctuates betw. 60-100 Mb and I can still see all/most of those tasks that were there just after boot-up.
If you have one of those scheduler/timer app, you can just use those to schedule Bfreemem to run regularly. (I can build another timer app to schedule)
Hey everyone I just got my Galaxy Nexus from Bell and it isn nothing short of amazing. Screen is amazing compared to my milestone which is basically the international version of the Droid. So far, I have experienced lag only after loading up approximately 10-15 apps which I never do on a daily basis, so lag isn't an issue with this phone. Now, I do have a few issues.
1.) The wifi keeps disconnecting while I try to download the files for shadowgun
2.) The speakers are REALLY quiet.
3.) When I use advanced task killer the ram available is always under 300mb even if i kill all apps (is it optimized for ICS?)
4.) The multi touch barely works?? (Download a multitouch tester app... when you have one finger on the left side, the bottom right side wont detect your other finger?? Noticable in shadowgun, if you are moving, you can't look around via the bottom left of the screen...
Sent from my Galaxy Nexus using XDA App
mohitrocks said:
Hey everyone I just got my Galaxy Nexus from Bell and it isn nothing short of amazing. Screen is amazing compared to my milestone which is basically the international version of the Droid. So far, I have experienced lag only after loading up approximately 10-15 apps which I never do on a daily basis, so lag isn't an issue with this phone. Now, I do have a few issues.
1.) The wifi keeps disconnecting while I try to download the files for shadowgun
2.) The speakers are REALLY quiet.
3.) When I use advanced task killer the ram available is always under 300mb even if i kill all apps (is it optimized for ICS?)
4.) The multi touch barely works?? (Download a multitouch tester app... when you have one finger on the left side, the bottom right side wont detect your other finger??
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
1) Samsung phones tend not to have as good wifi reception as others. See if you can move closer to the router.
2) You can use an app like Volume+ to boost it a bit.
3) The available RAM should be about 600+ MB. The app is probably not optimised for ICS. Anyway there really should be no reason to clear apps from RAM unless it is actively using CPU.
4) Multitouch is fine for me using "Multitouch Test" app from the market.
Sent from my Galaxy Nexus using XDA App
mohitrocks said:
3.) When I use advanced task killer the ram available is always under 300mb even if i kill all apps (is it optimized for ICS?)
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
People worry too much about free RAM. As a professional programmer (though not Android), power user, and hacker of almost any device or computer I use, I can tell you that free RAM is wasted RAM. Does the device work well for you? Unless you have a specific reason to believe that lack of available memory is affecting your experience, you shouldn't worry about it.
I expect any device I use (computer, phone, tablet, server, anything) to be making as much use of the RAM available to it as possible. The operating system should be caching as much as it can in memory to increase performance and enhance your user experience. Caching will normally show up as unavailable RAM, but any decent operating system (even Windows, haha) will dump cache and make it available for applications as needed.
Please don't take this the wrong way... I only ever comment on such things try to be informative. I honestly wouldn't worry about it, unless you're experiencing a problem directly related to available memory, such as an app (or worse, the OS!) leaking memory and causing lags or the inability to open new apps, etc.
There's also the whole thing about how you shouldn't even be using a task killer... but there are already enough threads on XDA about that topic, so I won't get into that here
And finally I will say... I'm jealous! I haven't pre-ordered, because I want to bargin with Bell a bit, but I'll be heading to Bell tomorrow and I hope they have a Galaxy Nexus in stock!
lol @ wanting to have free RAM
that was very informative!. I bought mine from virgin in Toronto Eaton Centre,with $50 off because I told him I don't want the case.(They give free case on the pre-launched date,don't know about tomorrow tho.)gl with your bargin!
BootsSiR said:
lol @ wanting to have free RAM
Click to expand...
Click to collapse
Haha seriously.
Uninstall that task killer. Jesus do people not learn?
From everything I have read it seems that task killers only really interfere with Androids OS. I've never used one and the system seems to run fine =]
mohitrocks said:
Hey everyone I just got my Galaxy Nexus from Bell and it isn nothing short of amazing. Screen is amazing compared to my milestone which is basically the international version of the Droid.
Click to expand...
Click to collapse
Glad to see I am not the only one coming from a Milestone, haha. Leaps and bounds are the words that come to mind.
martonikaj said:
Haha seriously.
Uninstall that task killer. Jesus do people not learn?
Click to expand...
Click to collapse
Maybe he wants to have free RAM to run something else that consumes a lot of RAM? Did you ever think of that?
It's like making fun of someone who is trying to make money and asking them "why do you want money? You can't eat it! LOL..."
Well, no duh. The point of making money is to exchange it for things you want...
Chirality said:
Maybe he wants to have free RAM to run something else that consumes a lot of RAM? Did you ever think of that?
It's like making fun of someone who is trying to make money and asking them "why do you want money? You can't eat it! LOL..."
Well, no duh. The point of making money is to exchange it for things you want...
Click to expand...
Click to collapse
You also don't understand then I suppose. If he wants free RAM to run something else, that foreground app will take the RAM away from anything else in the background that is unnecessary (obviously the foreground app is more important). But this isn't something he has to do (or think about doing). The process is not like: working with app X, then deallocating memory manually, then starting app Y. Rather, it's using app X, then starting app Y and if Y needs memory that X is using, X disappears automatically and Y continues to run with its necessary resources.
As stated above, free RAM is wasted RAM. His (and many other's) quest to have as much free RAM as possible is a terrible goal to have that overall hurts the user experience. Freeing RAM for the sake of looking at a screen that tells you a certain number (omg higher # is better!!!!) isn't the proper way to be managing your device.
Anyways, this isn't a task killer thread. Several other topics were raised by OP.
martonikaj said:
You also don't understand then I suppose. If he wants free RAM to run something else, that foreground app will take the RAM away from anything else in the background that is unnecessary (obviously the foreground app is more important). But this isn't something he has to do (or think about doing). The process is not like: working with app X, then deallocating memory manually, then starting app Y. Rather, it's using app X, then starting app Y and if Y needs memory that X is using, X disappears automatically and Y continues to run with its necessary resources.
As stated above, free RAM is wasted RAM. His (and many other's) quest to have as much free RAM as possible is a terrible goal to have that overall hurts the user experience. Freeing RAM for the sake of looking at a screen that tells you a certain number (omg higher # is better!!!!) isn't the proper way to be managing your device.
Anyways, this isn't a task killer thread. Several other topics were raised by OP.
Click to expand...
Click to collapse
Ugh...I guess I'll have to keep using the analogy to get through to you...
So you ask the guy why he wants to make money, because "extra money is wasted money" since you can't eat the money, right? He tells you "so I can use the money to buy other things I need." Then you ask him, "why do you need to make more money to buy other things you need? Your house is worth a lot of money, if you ever need other things, just sell your house!"
Do you understand it now? The house is some background process that's important to the user, which the user wants to keep resident in memory. The other things are other apps that the user might run. If the user keeps running other apps, eventually Android will need to reclaim memory. But the user doesn't want to lose his house (i.e. doesn't want that important background process closed)! How to make sure Android doesn't do that? Here's an idea: why not have some extra money to spend on things (i.e. free up memory by killing the non-important apps so the important one doesn't get killed)?
This...really isn't that difficult of a concept to understand. I don't get why you feel the need to bash everyone who wants to kill processes. Sure, a lot of people use task killers for stupid reasons. But you can't always assume the worst in people. How do you know that he's killing processes just to stare at the free memory graph? You don't know that. You are just assuming it. You can't rule out this legitimate use for manual process management.
Your analogy is completely flawed. The analogy of getting more money in terms of RAM is by opening the phone and putting another RAM chip in the phone, not by freeing RAM through a task killer. Freeing RAM with a killer is just shifting money around. You're not creating more RAM by killing apps, you're just moving it around.
He has a limited income in this case. He can't open his phone and put more RAM in it. If you're on a limited income and can't just "make more money" then if you want to buy a new car and don't have money, you have to sell something. The thing is, he's trying to do it manually. The phone will handle it automatically. It will choose what will be killed in order to free RAM for the front-facing process.
So you're getting the same amount of RAM either way. You have 1GB in the entire system to use. Whether you manage it manually or let the phone do it automatically, you still have 1GB of RAM. The difference is, when you do it manually, you are less efficient than letting the phone handle it. You kill things unnecessarily, kill things you shouldn't, and you spend extra time doing it.
martonikaj said:
Your analogy is completely flawed. The analogy of getting more money in terms of RAM is by opening the phone and putting another RAM chip in the phone, not by freeing RAM through a task killer. Freeing RAM with a killer is just shifting money around. You're not creating more RAM by killing apps, you're just moving it around.
He has a limited income in this case. He can't open his phone and put more RAM in it. If you're on a limited income and can't just "make more money" then if you want to buy a new car and don't have money, you have to sell something. The thing is, he's trying to do it manually. The phone will handle it automatically. It will choose what will be killed in order to free RAM for the front-facing process.
Click to expand...
Click to collapse
Yes, I know it's not a perfect analogy. But how about you point out the flaw in my use case, rather than the flaw in my analogy?
The problem is exactly that the phone "will choose what will be killed in order to free RAM". What if you want to choose what gets killed and what doesn't, and not let Android decide? What if you know exactly what you want to keep resident in memory and what's unimportant and can be killed?
Just out of curiosity, wanted to know how the OP got his bell GN so fast?
Preordered mine and waiting impatiently!
Sent from my Nexus S using Tapatalk
Basically he's saying that he's not gaining anything by rearranging his RAM. The system will free up RAM from background processes if need be. Him freeing up RAM and having available RAM doing nothing is not beneficial.
Chirality said:
How about you point out the flaw in my use case, rather than the flaw in my analogy?
Click to expand...
Click to collapse
You analogy is flawed because you have no idea what you're talking about. Your use case makes no sense. If the background app staying in RAM is more important than the foreground app, why are you using the foreground app? It should be in the background because its less important apparently.
Whether you manage things manually or not, if you are using the foreground app actively (ahem, its in the foreground) and it needs more RAM, then the other apps will be killed. Everything but the foreground app will be 100% wiped from RAM if it needs to. You can't tell it not to. If you want things to act differently, you'll have to write your own OS that never kills a background process sitting in RAM. And it'll suck.
What you want, and what a task killer offers, are 2 completely different things.
I'll go ahead and set this link right here just in case you want some more learnin'.
---------- Post added at 11:32 PM ---------- Previous post was at 11:27 PM ----------
gdap said:
Just out of curiosity, wanted to know how the OP got his bell GN so fast?
Preordered mine and waiting impatiently!
Click to expand...
Click to collapse
Are they not available in-store to pickup? Maybe he did that rather than order for delivery.
martonikaj said:
You analogy is flawed because you have no idea what you're talking about. Your use case makes no sense. If the background app staying in RAM is more important than the foreground app, why are you using the foreground app? It should be in the background because its less important apparently.
Whether you manage things manually or not, if you are using the foreground app actively (ahem, its in the foreground), then the other app will be killed. If you want things to act differently, you'll have to write your own OS that never kills a background process sitting in RAM.
What you want, and what a task killer offers, are 2 completely different things.
Click to expand...
Click to collapse
Oh for crying out loud, how is this not getting through to you.
I'm not talking about killing the foreground app to make room for the background app. I'm talking about how to choose amongst the different background apps which one to kill.
Let's say that in order to make room for a foreground, Android has to kill one of two background apps. Most of the time you probably don't care which one it kills. But what if in this case the user cares very much, and want one to be killed but the other to stay in memory? Why not use a task killer to kill the unimportant one so the important one stays in memory? Is this seriously a hard concept for you to grasp?
Let's not get into personal attacks about knowledge here. I can assure you, I know more about memory management than you do, since I've seen the stuff you post around here. I've written my own garbage collectors, my own implementation of malloc/free/realloc that beats the glibc implementation in both performance and utilization. I know the pros and cons of most of the major memory allocator implementations out there, I know which allocator data structures are better at utilizing TLB cache and which ones have better worst-case performance. I know when to use compacting GC and when to use simple generational mark and sweep GC. You want to tell me I don't know what I'm talking about?
Chirality said:
Oh for crying out loud, how is this not getting through to you.
I'm not talking about killing the foreground app to make room for the background app. I'm talking about how to choose amongst the different background apps which one to kill.
Click to expand...
Click to collapse
You realize that a task manager doesn't offer you this utility. Killing something manually means that it will simply re-open and be there right after you're done killing it. If it wants to run, it will run.
Let's say that in order to make room for a foreground, Android has to kill one of two background apps. Most of the time you probably don't care which one it kills. But what if in this case the user cares very much, and want one to be killed but the other to stay in memory? Why not use a task killer to kill the unimportant one so the important one stays in memory? Is this seriously a hard concept for you to grasp?
Click to expand...
Click to collapse
If its that important, you won't put it in the background. Again Task Killers don't offer you this functionality actively. Killing something then quickly opening your foreground app is the most inefficient way to operate this, and still doesn't accomplish what you want with frequency. As I said above, the app will simply re-open in the background and take up the RAM again if it is supposed to be running (we're always talking about well-performing and properly formed apps). If you never want it running in the background, you need to uninstall it.
Let's not get into personal attacks about knowledge here. I can assure you, I know more about memory management than you do, since I've seen the stuff you post around here. I've written my own garbage collectors, my own implementation of malloc/free/realloc that beats the glibc implementation in both performance and utilization. I know the pros and cons of most of the major memory allocator implementations out there, I know which allocator data structures are better at utilizing TLB cache and which ones have better worst-case performance. I know when to use compacting GC and when to use simple generational mark and sweep GC. You want to tell me I don't know what I'm talking about?
Click to expand...
Click to collapse
No, I'm sorry sir. Most respectfully as possible, you are wrong on this topic. Really. I'm not gonna argue with you on any of these things anymore. Anyone who runs Android or has written apps or mods or ROMs will agree with me.
Your crazy-ass examples of apps running in the background that you MUST have open is not the real-world case for what we're discussing, and should never be considered a reason for anyone to ever install a task killer. People are not using them for these reasons, and they're aimlessly installing them for the wrong reason. It is 100% ruining the experience of Android to install an Auto Task Killer.
martonikaj said:
You realize that a task manager doesn't offer you this utility. Killing something manually means that it will simply re-open and be there right after you're done killing it. If it wants to run, it will run.
Click to expand...
Click to collapse
Where the hell are you getting this nonsense? If it's just a normal app, how the hell is it going to run again after you kill it? Do you even understand how Android activities, intents, and services work?
martonikaj said:
If its that important, you won't put it in the background.
Click to expand...
Click to collapse
Do you really have no idea how Android works? Any app that is not currently visible on screen are in the background. How are you going to prevent apps from being put into the background? Is it really too much to ask in today's multitasking operating systems to have two things that you care about running at the same time, one in the foreground and one in the background?
martonikaj said:
No, I'm sorry sir. Most respectfully as possible, you are wrong on this topic. Really. I'm not gonna argue with you on any of these things anymore. Anyone who runs Android or has written apps or mods or ROMs will agree with me. Your crazy-ass examples of apps running in the background that you MUST have open is not the real-world case for what we're discussing, and should never be considered a reason for anyone to ever install a task killer.
Click to expand...
Click to collapse
And that, then, just shows you have no understanding of how memory management works at all. The use case I described is the one of the most usual case there is in any multiprocessing environment. You think somehow Android is special with its ability to automatically manage memory? No, it's not. It's not radically different from any modern operating system with virtual memory. The main difference is that instead of swapping memory to disk, it just kills processes. The use case I describe is a straightforward case of multitasking on a virtual memory system. It's so basic that frankly I'm amazed you don't understand it. When you are running multiple processes at once, you want to be able to choose which ones are resident in memory and which ones are swapped (or, in Android's case, killed). The best way to do it under a memory constraint is simply to kill processes you don't care about. Really, really basic stuff. And you are supposed to be a computer science student?
Maybe this is all to abstract for you. Let me describe a simple real world case. You are traveling and you rely on Google Maps to get around. You want to keep it resident in memory so that you can always instantly open up Maps. But you also run a lot of other apps during your journey. Looking up stuff on the Internet, reading restaurant reviews, checking news and weather, etc. The thing is, these apps aren't all that important. You might open them once and never need them again that day. But if you open a certain number of these apps, say, 5, then Maps will get killed since it was the least recently used. How to prevent this? Simple. Everytime you are done with one of these non-essential apps, you just kill it. It's not important to have this app be instantly accessible the next time. Or you kill them after opening 2 or 3 or them. Whatever. The point is, by manually closing these apps, you ensure Android never runs low enough on memory to kill Maps, so Maps will always be resident in memory and can be pulled up at a moment's notice, which is what you want.
Is this such a crazy-ass thing to ask for? Is this not something normal that we do on our computers all the time?
Chirality said:
You are traveling and you rely on Google Maps to get around. You want to keep it resident in memory so that you can always instantly open up Maps. But you also run a lot of other apps during your journey. Looking up stuff on the Internet, reading restaurant reviews, checking news and weather, etc. The thing is, these apps aren't all that important. You might open them once and never need them again that day. But if you open a certain number of these apps, say, 5, then Maps will get killed since it was the least recently used. How to prevent this? Simple. Everytime you are done with one of these non-essential apps, you just kill it. It's not important to have this app be instantly accessible the next time. Or you kill them after opening 2 or 3 or them. Whatever. The point is, by manually closing these apps, you ensure Android never runs low enough on memory to kill Maps, so Maps will always be resident in memory and can be pulled up at a moment's notice, which is what you want.
Click to expand...
Click to collapse
This is almost a non issue. Maps will save its state before it gets killed.
Also, if you're using maps throughout your journey multiple times, and these other apps are being used only once, the other apps will be killed first. But you do have a point in the case where if you open maps, use a bunch of apps, and fill up your ram to the point where android starts killing your oldest processes first(maps in this case). But as I mentioned before, maps, along with many other apps, will save their state so its not a big deal.
Overall, you are correct in saying a user might want control over which apps are never killed, which is why they would use a task manager, but there are probably many people who use task managers for the wrong reasons.
The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help
Search the market for startup cleaner
Sent from my A101IT using xda premium
yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.
Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium
rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.
It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on
...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk
I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.
Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium
I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium
yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-
PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.
So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-
Stop looking for excuses for poor multitasking in Sense 3+ roms
erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.
@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse
So i saw many posts on which people have asked as to which task killer should be used !
and then i stumble upon this site which provided me the details,
*I HAVE NOT WRITTEN THIS*
sources-by Chris Hoffman
http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/
Android Doesn’t Manage Processes Like Windows
Most Android users are familiar with Windows. On Windows, many programs running at one time – whether they’re windows on your desktop or applications in your system tray – can decrease your computer’s performance. Closing applications when you’re not using them can help speed up your Windows computer.
However, Android isn’t Windows and doesn’t manage processes like Windows does. Unlike on Windows, where there’s an obvious way to close applications, there’s no obvious way to “close” an Android application. This is by design and isn’t a problem. When you leave an Android app, going back to your home screen or switching to another app, the app stays “running” in the background. In most cases, the app will be paused in the background, taking up no CPU or network resources. Some apps will continue using CPU and network resources in the background, of course – for example, music players, file-downloading programs, or apps that sync in the background.
When you go back to an app you were recently using, Android “unpauses” that app and you resume where you left off. This is fast because the app is still stored in your RAM and ready to be used again.
Why Task Killers Are Bad
Proponents of task killers notice that Android is using a lot of RAM – in fact, Android stores a lot of apps in its memory, filling up the RAM! However, that isn’t a bad thing. Apps stored in your RAM can be quickly switched to without Android having to load them from its slower storage.
In summary, you shouldn’t use a task killer – if you have a misbehaving app wasting resources in the background, you should identify it and uninstall it. But don’t just remove apps from your phone or tablet’s RAM – that doesn’t help speed anything up.
Empty RAM is useless. Full RAM is RAM that is being put to good use for caching apps. If Android needs more memory, it will force-quit an app that you haven’t used in a while – this all happens automatically, without installing any task killers.
Task killers think they know better than Android. They run in the background, automatically quitting apps and removing them from Android’s memory. They may also allow you to force-quit apps on your own, but you shouldn’t have to do this.
Task killers aren’t just useless – they can reduce performance. If a task killer removes an app from your RAM and you open that app again, the app will be slower to load as Android is forced to load it from your device’s storage. This will also use more battery power than if you just left the app in your RAM in the first place. Some apps will automatically restart after the task killer quits them, using more CPU and battery resources.
Whether RAM is empty or full, it takes the same amount of battery power – decreasing the amount of apps stored in RAM won’t improve your battery power or offer more CPU cycles.
hope u understood!
words of wisdom by fellow-mates
go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
I understand this response, but I don't believe it. Task killers has always helped me in every matter. Even on a computer it helps greatly.
Conclusion: I noticed the same battery life using a Task Killer, than not using a task killer.
Sent from my HTC One V using Tapatalk 2
Curiousn00b said:
I understand this response, but I don't believe it. Task killers has always helped me in every matter. Even on a computer it helps greatly.
Conclusion: I noticed the same battery life using a Task Killer, than not using a task killer.
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
you don't have to believe it. those are real facts. go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
salve.
1ceb0x said:
you don't have to believe it. those are real facts. go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
salve.
Click to expand...
Click to collapse
I hope u don't mind if I take some of ur message and put it in the op
Sent from my One V using xda app-developers app
That's great.. I liked the article. I qm giving you a thanks for it
Sent from my One V using xda app-developers app
cybervibin said:
I hope u don't mind if I take some of ur message and put it in the op
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
sure. no problem mate
soham_sss said:
That's great.. I liked the article. I qm giving you a thanks for it
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Thank you
1ceb0x said:
sure. no problem mate
Click to expand...
Click to collapse
Sent from my One V using xda app-developers app
task killers were great before 1.6 but useless after that
Lloir said:
task killers were great before 1.6 but useless after that
Click to expand...
Click to collapse
+1 android has devloped a long way since!
cybervibin said:
Thank you
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
you're welcome!
I'm using task menager when is needed, and also I'm using custom system memory tweaks, it makes my phone running faster and smoother some apps knows to stuck and they keep the phone from entering deep sleep, and that drains the battery, so if you know what are you doing use task menager and customize when what apps the system should kill
Sent from my HTC One V
I have a task killer installed, but only use it manually, ie. if there's a stubborn app that's crashed/frozen/etc and just won't close and is eating the battery
donJim said:
I'm using task menager when is needed, and also I'm using custom system memory tweaks, it makes my phone running faster and smoother some apps knows to stuck and they keep the phone from entering deep sleep, and that drains the battery, so if you know what are you doing use task menager and customize when what apps the system should kill
Sent from my HTC One V
Click to expand...
Click to collapse
Use auto run manager the answer to most of ur problems
qzfive said:
I have a task killer installed, but only use it manually, ie. if there's a stubborn app that's crashed/frozen/etc and just won't close and is eating the battery
Click to expand...
Click to collapse
Sent from my One V using xda app-developers app
yayyy so task killer only kills my battery
you got that right!
Good to know. Thanks