Related
Ok, so there are task killer threads that lead me to believe that they a are a waste of time by and large, and that android automatically sorts things out. Those same posts also point out that task killers are an extra drain on the battery having to start applications over again uses more battery than leaving something dormant in the background. These posts are not the thoughts of one person but unanimous to those threads. All very well, but then there are the battery saving threads that say to close down all applications that aren't being used to save additional battery??? Again this is the view of everyone in those particular threads, so is there any chance of getting the two camps to FIGHT! And then I can decide which I shall choose to do!
For info I currently have task killer and use it all the time and get a full days use out of my battery which is good because I cane the hell out of it! But If I could improve it that would be good. I have however this afternoon decided to not use task killer for a few days and see how I get on. But an explanation would be good from both sides.
I never use a task killer and get 2 or 3 days use out of of my Desire. No point in a war just use your Desire for a week without a task killer and then a week with. I am pretty sure you will just find the task killer slows things down and doesn't improve battery life. You will not find any of the ROM chefs using a task killer either!
HI
I was reading one of those posts this morning and decided to uninstall task-killer.I have to say that after half day of heavy use my device started to be so laggy it took contacts or calendar 5 seconds to open!then I checked running processes and pretty much everything I was playing with was still running.memory dropped to 10MB and device became unusable.cannot say battery use has improved.I think it was the same.
But my task-killer is back up and running.
I must say that I am new to Android.I was using WM for long time.I can cook my own ROMs so I am not a noob but I know very little about Android.so if anyone knows what could be the reason of this huge slowdown I will be grateful for explanation.
And one more thing that needs to be said...
My device is rooted and I am using a2sd too.
polystirenman said:
HI
I was reading one of those posts this morning and decided to uninstall task-killer.I have to say that after half day of heavy use my device started to be so laggy it took contacts or calendar 5 seconds to open!then I checked running processes and pretty much everything I was playing with was still running.memory dropped to 10MB and device became unusable.cannot say battery use has improved.I think it was the same.
But my task-killer is back up and running.
I must say that I am new to Android.I was using WM for long time.I can cook my own ROMs so I am not a noob but I know very little about Android.so if anyone knows what could be the reason of this huge slowdown I will be grateful for explanation.
And one more thing that needs to be said...
My device is rooted and I am using a2sd too.
Click to expand...
Click to collapse
You may like to read this:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
dhiral.v said:
You may like to read this:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Click to expand...
Click to collapse
well.i did read that before.that is why i do not understand why my phone was so slow.they are claiming that android should close apps by itself to reclaim memory.but in my case that wasn't true.everything was running and nothing was getting closed by system.
Here's another good read:
Google and Cyanogen comments imply task killer/manager apps are pointless
Both Dianne Hackborn and Cyanogen say Task Killers are useless, even developers of these apps concur. You should listen to them, I guess they understand juuust a little bit more than we do what Android is about.
pascanu said:
Here's another good read:
Google and Cyanogen comments imply task killer/manager apps are pointless
Both Dianne Hackborn and Cyanogen say Task Killers are useless, even developers of these apps concur. You should listen to them, I guess they understand juuust a little bit more than we do what Android is about.
Click to expand...
Click to collapse
i would like to believe it.i was so excited when i saw a post saying that i should get rid of task-killer.but as i wrote before after half day of heavy use(my phone is new so i play with it a lot :-D ) without task killer my phone was soooooo slow i couldn't use it anymore.today i had task-killer back on the phone and all day no slowdown what so ever.i don't understand that.i am starting to think it is related to A2SD and memory being relocated to SD card.
I also agree that taskkiller (the way it works for WM) is not good for android, because android has a better memory management...
but there is another flavour of taskkiller in the market... which are based on this:
How to configure Android's *internal* taskkiller
Unfortunately, your phone needs to be rooted before you can use that method.
If you worry about memory remember that the worst kind of memory is...free memory ! Because it's not being used. Obviously ram gets reclaimed and freed when it's needed.
As said in a couple more redundant threads, there might be a rogue app which you are better off closing because it stays in the background wrongly eating cpu cycles, but this is very very rare. Otherwise I think it's just the usual placebo effect...
andycted said:
If you worry about memory remember that the worst kind of memory is...free memory ! Because it's not being used. Obviously ram gets reclaimed and freed when it's needed.
As said in a couple more redundant threads, there might be a rogue app which you are better off closing because it stays in the background wrongly eating cpu cycles, but this is very very rare. Otherwise I think it's just the usual placebo effect...
Click to expand...
Click to collapse
Have you read the link in my previous post?
ANOTHER thread about this... There must be plenty of threads on this now, but I'll just once more give my impression.
Personally I have had HTC widgets like NEWS or MAIL or CALENDER hang or crash on me and I could not restart them unless I restarted the phone. In this case an app killer was ESSENTIAL. I don't believe you need to leave the app killer running always and kill every single task when your done, but its essential to have one installed so if a widget hangs (as has happened quite a few times on the Desire) you can kill the hung app without having to try a 5 hour shut down(another desire issue) and battery removal.
Also... after 2 days use of many apps and camera use and internet and youtube app etc, your internal RAM will be about 50mb available to programs. yes, android is supposed to kill stuff as it needs, and Im sure it does, but 50mb free memory compared to 150mb the lag is VERY obvious. So I do tend to kill tasks like camera and youtube etc if I have not used them in a day and my phone seem slaggy. the phone definetly runs faster then. Thats just a fact. So the internal android task killer is not as efficent as you'd like to think. Android 2.2 runs 450% faster than 2.1 so maybe then no lag will EVER be noticable. I'll still keep a task killer installed though in case widgets crash or hang.
I found my battery most efficient with this setup:
- Installed Advanced Task killer (free)
- Security level: High (it doesn't show system apps)
- I have put all frequently using apps on ignore list: ATK, Messages, BatteryTimeLite, Internet, Weather, Clock, Calendar (so Android manage with those apps)
- Auto kill Level: Safe
- Auto kill Frequency: 2 hours
With that setup battery lasts almost half time longer than without TK or with killing all apps when screen goes off. Also I don't have any force closes / lag.
Never experienced lag at 100 or 20 mb free.
mcgon1979 said:
but 50mb free memory compared to 150mb the lag is VERY obvious.
Click to expand...
Click to collapse
The amount of free memory doesn't necessarily have anything to do with lag.
As Android does not use virtual memory (unless you've hacked in swapper, which is a bad idea anyway), it will attempt to make best use of available memory which may mean keeping recently used items in memory, and thus "consuming" free memory. However, if those items are not actively processing, they should not be consuming CPU cycles and therefore consuming little to no power.
As far as a running system is concerned, having lots of free memory just means that it is being underutilized.
I don't kill tasks and my phone never lags - that's just a fact too!
Regards,
Dave
boge said:
I also agree that taskkiller (the way it works for WM) is not good for android, because android has a better memory management...
but there is another flavour of taskkiller in the market... which are based on this:
How to configure Android's *internal* taskkiller
Unfortunately, your phone needs to be rooted before you can use that method.
Click to expand...
Click to collapse
Using this method it is possible to make the native task killer a bit more aggresive. I did some experiments with this on the HTC Hero and it just might have improved speed slightly but at the expense of stability.
"Normal" task killers are completely pointless but if people want to use them why not? It they want to sacrifice both battery life and performance by using one surely that is their choice. Whatever the experts says will not convince them.
I suppose you could use one to kill the very occasional hung app. i.e. Once every few days, but most people seem to use them constantly and totally indiscriminately.
1. About Cpu: get a task manager with cpu monitoring and verify for yourself, frozen applications in background don't do anything.
2. About memory: If an application needs 10 MB it just uses 10 MB and couldn't care less if there are 11, 100, 1000 MB free. The only moment you COULD see a tiny slowdown is the instant it needs 20 and there are only 10 available, but the system is quite good in managing that, and freeing resources (there are six levels of memory cleaning which progressively remove unused applications from the background)
3. If you stop monitoring memory usage, stop worrying about the system, you'll find out it manages itself perfectly and you enjoy the phone a lot more.
Interesting article about installed apps and a battery.
http://blog.gsmarena.com/android-handsets-batteries-should-last-for-more-than-a-day-google-says/
"...Page accused the installed apps of causing the problems and claimed that software running in the background exhausts the battery quickly...."
Interesting article about installed apps and a battery.
http://blog.gsmarena.com/android-handsets-batteries-should-last-for-more-than-a-day-google-says/
"...Page accused the installed apps of causing the problems and claimed that software running in the background exhausts the battery quickly...."
Click to expand...
Click to collapse
as said in the post above, get a cpu monitoring task manager and see for yourself if you have something wrong. Personally I don't have any.
Also watch battery history which tells you if the phone doesn't manage to go properly to sleep (partial wake)
regarding that article, iphone users get way less battery time and they don't even have multitasking...
-------------------------------------
Ipad's dont have "Spell Check" thery have "Replace" built into Safarii adn it wokrs just fineq!!!
I personally installed auto memory manager, an app that configures android's internal task killer. Its not a task manager by itself, uses android's task manager. You can set the limits in MB for all the app categories android has.
I was using it in my hero as well and found it really useful. Before having it installed, after some time my free memory was ~50mb, thus my phone was sometimes lagging. Now its always above 100mb and no lag at all
I am a noob when it comes to android phones so anything will help! I have been told and pretty sure I read something about task killers being bad for your android phone??? Is this true? I currently use Advanced Task Manager free. Is this a good task manager? If not does anyone know of one thats better. I tried to search the forumn but was unable to find anything on this subject...I'm probably just searching wrong. Any knowledge will help!
Try searching the Q&A forum
Don't use task killers is the bottom line.
Use Google search to find out about google and task killers.
avoid them like the plague
Not. It's stepping on Androids toes. If you really need a kill an app (froze or its just using a lot of battery), you can do it in Android itself in Applications.
i noticed i acctually get more battery life with out a task killer, android will close out programs as it needs the memory any way so have had better performance with out it. the Sprint rep actually installed mine on my phone when i bought it so was suprised to learn all this at first but has long sense proven true
Been using Advanced Task Manager since I had my G1 and have not noticed any negative effects. The browser alone takes up a considerable amount of interal memory and does not close on exit. Task managers are good as long as you know how to use them and exclude system applications or user apps that you want to stay running like widgets and such. They may not improve battery life that much, but they help free up internal memory. However, if you're running a Froyo rom, they're pretty much useless until the app devs update the way they work. Froyo doesnt allow them to kill the app, just background data.
Here's some pretty clear literature on why you absolutely do not need them.
While I agree that a task killer is not needed it is not bad. I mean using one wont cause damage to your phone or anything. Some people get better battery with one and some get better battery without. I just avoid task killers because I had a bad experience. I use my phone as an alarm and one day it did not go off because I had killed the clock app. Ofcourse you can use a task killer and not have this problem by setting apps to ignore but after several weeks of not using it I noticed my battery is not better or worse so to each his own.
BTW I also used advanced task manager and thats a perfectly good task manager if you do decide to keep using it.
Best thing you can do is install and use it for a couple days to see if you like it. I have used one since my Droid and would not consider uninstalling. I notice an immediate improvement in the smoothness of my phone while using, and a noticeable choppiness when not using. Your mileage may vary, but I would give it a shot for yourself vs. just listening to others opinions.
87Octane said:
While I agree that a task killer is not needed it is not bad. I mean using one wont cause damage to your phone or anything.
Click to expand...
Click to collapse
+1
If you kill a task and free up memory, Android just fills up that memory again with a program of its own choosing. If it needs the memory, it intelligently pulls programs out of memory on its own.
hi everyone, i'm no expert on phone, so don't kill me if i sound stupid
been using my galaxy S for about 4 months now. and yes it does lag compare to the iphone, or other HTC phones. so i been trying to find out, what's going on? why is my top end phone lagging? here's what i found:
1) when does it start to lag badly?
i installed system panel which gives me a nice list of active and inactive apps, and how much free ram i have left. the phone ALWAYS starts to lag like crazy when ram gets below 60mb. this is a problem - samsung is not giving us enough free ram to play with as once we run a few apps (market, internet especially), we're reaching the 60mb point already. when the phone gets to the 60mb mark it tries to manage the apps by closing some less important ones. but it lags BADLY while doing so.
what's gonna happen is the phone gonna get into this never ending cycle of closing apps and laggin as it's stuck in around the 50mb-60mb mark.
i can solve this by going to system panel and closing all inactive apps. then the ram is gonna go back to around 140mb. however after opening a few apps, once again it goes back to below 60mb and the lag starts again.
2) autokiller
guys been saying autokiller is great and they go with the aggressive settings. i tried it and it made the phone worse. why? because instead of killing apps at the 60mb mark it starts killing apps even sooner! that's wasting battery, wasting free ram, and making the phone even slower. we don't have enough free ram to begin with, so we should make max use of it. here's how i do it:
1) root the phone. install autokiller from the market.
2) instead of using high aggressive settings, use the LOWEST settings. i use advanced mode and then enter all values to 8mb only.
now it is awesome!! the phone never lags until you get it down to around the 20mb mark. you now have around 40mb of extra ram to use (of course autokiller does use some ram but no big deal). the lag starts much latter. u may not think 40mb is a lot but it is in practice!
if you dont believe me, you can try it. it may or may not work for u, but it's definitely working for me. of course, once the ram falls below 20mb, it may be a good idea to close some inactive apps yourself, LOL
but really, samsung should give us at least 100mb more free ram, i can't believe i even have to do this!
Well you point one issue that lag happens, but almost every custom kernel/Rom use memory tweak that Make you around 40MB more to start with.
And yes autokiller don't work good.
The program in the phone is the best to use.
The main lag issue is the filesystem.
Even these can be fixed with many different kernel/Rom.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram
i don't disagree with what you're saying. but a few things to add:
1) i have not applied lag fix myself but i have a friend who has. i dont feel his phone is much quicker than mine in reality. also, his phone crashed after a few weeks and he had to do a hard reset. what we REALLY need is more ram. if we have lots of ram, who cares about the file system? we don't even need any swap from the file system. just let everything stays in ram where it is the quickest.
2) i'm not using any custom roms. if custom roms give me extra 40mb, and then i adjust the auto killer setting to low, that gives me 80mb extra to play with. great.
autokiller DOES work good i feel if you're doing what i'm saying. maybe u have already tried what i'm doing, i don't know, but if you have not, then i highly recommend you to try it.
like i said i'm no expert on this, but autokiller is so easy to install and adjust, and that i feel anyone here can use it
maybe flashing custom firmware is easy to do, i haven't tried it, but it sounds complicated to do for me, and i don't want really big changes on my phone, i want it to be extremely stable and safe as i use it a lot for business. i don't really want to risk any data or risk reinstalling stuff.
so maybe i sound uneducated but like i said i suggest everyone to try this method if they're newbies and don't wanna do too much
I can confirm that setting autokiller to low settings makes the phone feel faster than on high settings, I tried that some time ago.
But lag will still be present.
As mentioned by the poster this is a low risk, low skill method of improving the phone and is easy to do for all.
For all others I recommend the JFS lagfix. It is by far the lagfreest experience out there!
i have a buddy with a moto milestone and his phone lags just the same as ours. his phone has even less free ram than ours and so his is constantly lagging. sometimes he can't even take a phone call while listening to music becoz his phone only has like 50mb of free ram after starting up. so, just a point of reference - our galaxy is crippled with just not enough free ram, i heard stories of nexus one having 200+ free ram after startup and that's why they dont lag like us, so at the end of the day we're fighting a losing batter becoz samsung didn't give us a good enough phone
Mycorrhiza said:
I can confirm that setting autokiller to low settings makes the phone feel faster than on high settings, I tried that some time ago.
But lag will still be present.
As mentioned by the poster this is a low risk, low skill method of improving the phone and is easy to do for all.
For all others I recommend the JFS lagfix. It is by far the lagfreest experience out there!
Click to expand...
Click to collapse
thank u and i may try the jfs fix, but i'm just worried about something happening to the phone becoz of what happened to my buddy who lost all his data (i can't remember which lag fix he used though), i always have this thinking that if the lag fix are 100% safe, then why aren't samsung doing it? samsung are paying tons of money to the programmers i'm sure and you would think they know how to do it too? but they choose not to, and there must be a good reason why.
You have a very good point supraman123! I realized it was the memory management that made the phone go crazy around the 60MB mark (you'll see the kswapd0 process go crazy), but never realized Autokiller could help us lower that mark. I hope this works, would be one of the best and easiest fixes for the SGS.
supraman123 said:
thank u and i may try the jfs fix, but i'm just worried about something happening to the phone becoz of what happened to my buddy who lost all his data (i can't remember which lag fix he used though), i always have this thinking that if the lag fix are 100% safe, then why aren't samsung doing it? samsung are paying tons of money to the programmers i'm sure and you would think they know how to do it too? but they choose not to, and there must be a good reason why.
Click to expand...
Click to collapse
If we know the amount of time and money Samsung spend on developing RFS...
So wait, the phone is faster if the minfree is set higher than default, and the phone is faster if the minfree is set lower than default... holy ****!
I applaud Samsung for figuring out the one setting that makes the phone suck and use that as default. Way to go, Sammy, way to go.
I know what u are talking about. I think it was an ext4 fix. All other lag fixes I know of don't share that problem.
Also with root there are many ways to secure your data prior to installing a lag fix.
Sent from my GT-I9000 using XDA App
Mycorrhiza said:
I know what u are talking about. I think it was an ext4 fix. All other lag fixes I know of don't share that problem.
Also with root there are many ways to secure your data prior to installing a lag fix.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
hi, thank u, can u tell me how to secure the data? or u have any good links to show me? thanks
jjwa said:
You have a very good point supraman123! I realized it was the memory management that made the phone go crazy around the 60MB mark (you'll see the kswapd0 process go crazy), but never realized Autokiller could help us lower that mark. I hope this works, would be one of the best and easiest fixes for the SGS.
Click to expand...
Click to collapse
i hope it will work good for u also
xmonkee said:
So wait, the phone is faster if the minfree is set higher than default, and the phone is faster if the minfree is set lower than default... holy ****!
I applaud Samsung for figuring out the one setting that makes the phone suck and use that as default. Way to go, Sammy, way to go.
Click to expand...
Click to collapse
i'm quite disappointed at the ram issue also. coming from a n97 mini which seriously lacks ram, i was hoping by going for a high end phone like the galaxy, i aint gonna have to worry about ram and closing apps manually all day, however in reality the Galaxy aint much better than the n97 at multi tasking. of course, it's far better than the n97 at everything else.
I totally agree with OP on this one!
But Autokiller is not the only app that can fix the lag.
One Click Lag Fix 2.0 can root your SGS (Eclair only), lagfix it (with EXT2) and it can even do some additional tweaks like minfree (same as the Autokiller app) and fix the Scheduler.
With minfree Samsung put these values in "/sys/module/lowmemorykiller/parameters/minfree":
"2048,4096,5120,5632,6144,7172"
But best is:
Aggressive: "1536,2048,4096,21000,23000,25000"
or
Strict: "1536,2048,4096,15360,17920,20480" - I prefer this one
btw when you've a lot of ram free the ram is mostly used to cache file system reads ^.^
this explains that a little
Im using the 341MB of free ram so that gives me an instant 40MB ontop of the stock kernel, never seen the phone had less than 60mb free with this kernel, with my usage it doesnt even go under 95mb free.
I am also running one of those kernels that gives extra RAM. And I have all my partitions Ext4 lagfixed. But my phone still seems quite slow at times. My RAM was above 80MB free at that time though, so probably not related to any minfree/Autokiller thing at all. Which means there are way more causes to get rid of I guess.
I don`t know how you guys have problems with the lag, I use the stock samsung JPO, not even deodexed with zankinz 23 kernel and NO-RFS all ext4 lagfix and the phone is running perfectly, no lag whatsoever, the RAM is somewhere near 220 mb free after reboot. After deodexing and optimizing the apk`s the phone should run even better. I was determined to change my SGS with a Desire HD, but now I`m really thinking of keeping it.
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).
So after installing viper one 2.1 on my m8, my phone is showing too much used ram. Even though there is no app running and also i force stopped them, my phone would still show 1.3 Gb consumed ram. Thanks
Well, that's just the viperone rom, you shouldn't be surprised. All the features included in this rom need ram.
Sent from HTC One m8, or maybe not anymore
mr.loverlover said:
Well, that's just the viperone rom, you shouldn't be surprised. All the features included in this rom need ram.
Sent from HTC One m8, or maybe not anymore
Click to expand...
Click to collapse
thats a bummer then. it looks really good, but no work then huh...
what are you "saving" the RAM for?
Its there to be used, and most developers will tell you that using as much ram as you have is a good thing, so no, its not a problem
wase4711 said:
what are you "saving" the RAM for?
Its there to be used, and most developers will tell you that using as much ram as you have is a good thing, so no, its not a problem
Click to expand...
Click to collapse
Problem starts when I run few apps at a time. Game, browsing etc., the phone slows down, lags and all. I ain't no expert but what good is 2 Gb ram if It can't run apps smoothly.
there are few, if any complaints anywhere on the internet about this phone ever lagging; close your game when you are done with it, and see if that makes things better.
wase4711 said:
there are few, if any complaints anywhere on the internet about this phone ever lagging; close your game when you are done with it, and see if that makes things better.
Click to expand...
Click to collapse
Of course it does get better.
So that means I have to run minimum apps
no just close your games when you aren't playing them..hardly means you have to run "minimum" apps..
I have about 9 programs running in the background, and I have over 400 mb of free ram on my phone..no lag at all
Use Greenify to hibernate a few high ram users. Especially games that don't close properly.
But as said already... Android/Linux is built to run with a lot of the ram used always. This makes task switching quick and normally doesn't create issue, quite the opposite... Usually makes things open quickly.
But large games that are kept in memory is probably not a great thing.
I Greenify all games and anything else that hurts performance or my battery. But that's a short list on my phone.
wase4711 said:
no just close your games when you aren't playing them..hardly means you have to run "minimum" apps..
I have about 9 programs running in the background, and I have over 400 mb of free ram on my phone..no lag at all
Click to expand...
Click to collapse
Wow. I ve just Internet Explorer running and I'm left with 320 mb
Browsers use more ram as their cache size increases. It's normal. Android will boot older cached apps out of memory when it needs more space.
Stop worrying and start enjoying your device. It's working as intended.
KJ said:
Use Greenify to hibernate a few high ram users. Especially games that don't close properly.
But as said already... Android/Linux is built to run with a lot of the ram used always. This makes task switching quick and normally doesn't create issue, quite the opposite... Usually makes things open quickly.
But large games that are kept in memory is probably not a great thing.
I Greenify all games and anything else that hurts performance or my battery. But that's a short list on my phone.
Click to expand...
Click to collapse
I'll give it a go. Thanks
KJ said:
Use Greenify to hibernate a few high ram users. Especially games that don't close properly.
But as said already... Android/Linux is built to run with a lot of the ram used always. This makes task switching quick and normally doesn't create issue, quite the opposite... Usually makes things open quickly.
But large games that are kept in memory is probably not a great thing.
I Greenify all games and anything else that hurts performance or my battery. But that's a short list on my phone.
Click to expand...
Click to collapse
My phone is much faster now. Thank you very much
KJ said:
Use Greenify to hibernate a few high ram users. Especially games that don't close properly.
But as said already... Android/Linux is built to run with a lot of the ram used always. This makes task switching quick and normally doesn't create issue, quite the opposite... Usually makes things open quickly.
But large games that are kept in memory is probably not a great thing.
I Greenify all games and anything else that hurts performance or my battery. But that's a short list on my phone.
Click to expand...
Click to collapse
My phone is much faster now. Thank you very much