Develop Bugs

[Q] Could someone clarify?

Okay, so I hear in FroYo that you're not suppose to kill and end tasks? Does that means services as well? And if I wasn't suppose to kill them, then wouldn't that make my battery life worse because of all the things running in the background?
TIA
Sent from my Epic 4G

You shouldn't use a task killer in any version of android from Froyo on, froyo handles its memory management extremely well when left alone, using a task killer could result in apps constantly opening and closing in the back ground, which would use a lot of battery .
Texted while driving

Alright. I got rid of my task killers. Is ending services fine though? And what about the task manager that the phone provides? (I'm guessing the second one is a no?)
And what other precautions should I take for battery (other than having low brightness, of course)
Sent from my Epic 4G

Only use the one built into the touchwiz framework if you have an app running out of control hogging resources.
If you're looking to improve battery, I strongly suggest Juicedefender with ultimatejuice, I have almost tripled my battery since I started using them.
Texted while driving

063_XOBX said:
Only use the one built into the touchwiz framework if you have an app running out of control hogging resources.
If you're looking to improve battery, I strongly suggest Juicedefender with ultimatejuice, I have almost tripled my battery since I started using them.
Texted while driving
Click to expand...
Click to collapse
Thanks. Just got both. What do you reccomend I put the aggressiveness on?
Sent from my Epic 4G

I keep it on custom and 15 minutes every 2 hours.
Texted while driving

063_XOBX said:
I keep it on custom and 15 minutes every 2 hours.
Texted while driving
Click to expand...
Click to collapse
Wait, I'm a bit confused. What do you mean 15 min every 2 hours? Like I can only put my frequency to 15 min OR 2 hours? Sorry if I seem stupid lol
Sent from my Epic 4G

Data on for 15 minutes every 2 hours.
Texted while driving

063_XOBX said:
Data on for 15 minutes every 2 hours.
Texted while driving
Click to expand...
Click to collapse
I figured it out
Thanks for everything.
Sent from my Epic 4G

I use the Advanced Task Killer for Froyo. Several apps I have like the Weather Channel and stock browser lower my available memory to a minute amount of what it was at boot up and do not reload if killed.
BONSAI 4 and loving it!

kennyglass123 said:
I use the Advanced Task Killer for Froyo. Several apps I have like the Weather Channel and stock browser lower my available memory to a minute amount of what it was at boot up and do not reload if killed.
BONSAI 4 and loving it!
Click to expand...
Click to collapse
The amount of memory available on your phone is supposed to become low. Apps are stored in memory when not being used. This does not take battery and allows the program to start in a faster fashion then otherwise.
Sent from my Incredible using Tapatalk

I'm sorry guys, but the information given in response here is really dangerous. Yes Froyo, and all versions of Android have built in memory management. HOWEVER, it is the job of the application developer to use the proper calls and closes to make sure the application isn't holding onto resources when in a background state. This is NOT always the case, and is constantly overlooked on all OS platforms, especially with how fast application development is happening on mobile platforms.
YMMV, when and if you should be using task killers.

linuxmotion said:
The amount of memory available on your phone is supposed to become low. Apps are stored in memory when not being used. This does not take battery and allows the program to start in a faster fashion then otherwise.
Sent from my Incredible using Tapatalk
Click to expand...
Click to collapse
No it's not. There is only 337MB of RAM available of which about 150 is used by system. If I keep loading apps that stay in memory when not being used I will have no resources or memory available for additional web pages or other apps. Why should the Weather Channel app load 50 MB of memory and stay there if I use it twice a week? When an app is closed I want it out of RAM. I can wait the 50 milliseconds to reload if I want to use it again.
BONSAI 4 and loving it!

Here we go again another argument of task manager for android
For me i use advanced task manager to kill some apps to speed up my phone a little and also use it to switch between programs that are already open where as if you try reopening some programs the restart,
I also ignore apps that i need to open and stay open like beuatiful widgets, word games to get more reliable notifications and widget locker.
I freeze with titanium some services such as drm and sns...

Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them

mattallica76 said:
Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
Click to expand...
Click to collapse
I like to save some for a rainy day

mattallica76 said:
Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
Click to expand...
Click to collapse
What that article hints at but doesn't exactly explain is that due to how the Dalvik JIT works, killing those apps that aren't actively consuming CPU will cause worse performance over the long run. The JIT has to spin up everytime the app is loaded - if it is already in memory then it's already optomized.
At least that's my understanding! I could be totally talking out my arse
EDIT:
Here is its straight from the Dalvik lead dev.

Well don't know about performance but yesterday killing apps with ATK Froyo especially the browser, I came home with 62% battery left. Today had about the same use but disabled ATK and never used it and came home with 31% battery left. ATK is doing something for my battery and will give up apps loading quickly for battery life any day.

How do I stop apps auto opening

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

task killers / managers

hi guys...is it true that task killers/managers would decrease battery life or even slow down the system? i'm using advance task manager pro...i simply dun like to hv those apps running in the background (facebook,line,etc) so i kill them all the time...will this effect my phone's battery life and performance?

Close them and they will reopen, so you are using your CPU to reopen the apps. Just uninstall Facebook already, use the web version, they look the same. Better still, socialize with real people.
Pressed from my Maguro

Mach3.2 said:
Close them and they will reopen, so you are using your CPU to reopen the apps. Just uninstall Facebook already, use the web version, they look the same. Better still, socialize with real people.
Pressed from my Maguro
Click to expand...
Click to collapse
but the facebook app loads a bit faster...haha...so basically the task manager is not needed？

No. Uninstall it because it will actually make your system unstable. Android already is very efficient in it's memory usage so don't worry. It will kill it by itself if need be. I used to believe in then a lot until I learned the real truth and experienced the benefits myself. You'll be amazed how little it does.
Sent from my Galaxy Nexus

Ever since android evolved from running on phones with sub 128MB of ram, task killers have been unneeded, the LMK (low memory killer) has also got smarter about what it kills.
Unused ram is wasted ram (as afaik the phone cant turn of individual sections of ram, it's all on or off, and even then, the power required to refresh it to keep the data around is minimal compared to how much it costs to hit the flash and pull the apk into ram again).
The facebook app is junk, use a 3rd party one or turn sync off and live with the drainage.

nexicon said:
No. Uninstall it because it will actually make your system unstable. Android already is very efficient in it's memory usage so don't worry. It will kill it by itself if need be. I used to believe in then a lot until I learned the real truth and experienced the benefits myself. You'll be amazed how little it does.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
task killer will make the system unstable?didnt know tat...looks like i’ll uninstall my task manager...

veyka said:
Ever since android evolved from running on phones with sub 128MB of ram, task killers have been unneeded, the LMK (low memory killer) has also got smarter about what it kills.
Unused ram is wasted ram (as afaik the phone cant turn of individual sections of ram, it's all on or off, and even then, the power required to refresh it to keep the data around is minimal compared to how much it costs to hit the flash and pull the apk into ram again).
The facebook app is junk, use a 3rd party one or turn sync off and live with the drainage.
Click to expand...
Click to collapse
actually my facebook app doesnt drain tat much battery compared to my chrome and temple run...haha

ace-user said:
actually my facebook app doesnt drain tat much battery compared to my chrome and temple run...haha
Click to expand...
Click to collapse
Make sure to turn off "Enable tilt scrolling" in chrome's developer tools settings, at least until they fix the wakelock bug it causes
As far as temple run, well its a game!11!1

veyka said:
Make sure to turn off "Enable tilt scrolling" in chrome's developer tools settings, at least until they fix the wakelock bug it causes
As far as temple run, well its a game!11!1
Click to expand...
Click to collapse
u mean enabling that setting will cause wakelock?

ace-user said:
actually my facebook app doesnt drain tat much battery compared to my chrome and temple run...haha
Click to expand...
Click to collapse
More than you realize.
I use Friendcaster with notifications off.
Sent from my AOSP Android 4.1.1 Galaxy Nexus

Zeinzu said:
More than you realize.
I use Friendcaster with notifications off.
Sent from my AOSP Android 4.1.1 Galaxy Nexus
Click to expand...
Click to collapse
seriously?i see from my battery stats tat it only drains about 6% , tats not much right?or is it?=/

ace-user said:
u mean enabling that setting will cause wakelock?
Click to expand...
Click to collapse
If enable tilt scrolling is turned on, chrome tends to hold a wake lock on the orientation sensor, causing wake locks.
And its turned on by default.
Sent from my Galaxy Nexus using Tapatalk 2

I use memory usage app from twistbyte, any app running with priority 300 is running as a service in the background. Check the apps running in 300 and decide if you really need them....
Sent from my Nexus 7 using Tapatalk 2

task killer is really pointless. Facebook app does take a lot of battery, so recommend using scope beta or friendcaster instead
Sent from my Galaxy Nexus using xda app-developers app

[INFO] Why You Shouldn’t Use a Task Killer On Android

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

Low memory!

How much FREE memory do you guys have when in normal usage (with browser, Facebook, whatsapp, tapatalk open..)??
Here I usually get 200 free, so I constantly have to free memory (it goes from 200 to 450, but few minutes later, it will be the same thing).
Help, anyone??

I usually have 1.1 gb free with kakao, whatsapp and basic apps running in the background. I close Facebook as I leave it, Facebook is a big memory hog.

I have about 900-1.1 gb used
Sent from my LG-E986 using xda app-developers app

Damn, 4-5 times my free memory!
I think I will reset the phone and reinstall everything again..
Any other hints??

artssa said:
Damn, 4-5 times my free memory!
I think I will reset the phone and reinstall everything again..
Any other hints??
Click to expand...
Click to collapse
Look at what is running. It sound like something is running in the background that is sucking up the memory. If you do a reset and re-install of everything, before you find out what is causing the memory problem you may be right back to square one.

TheMighyLoki said:
Look at what is running. It sound like something is running in the background that is sucking up the memory. If you do a reset and re-install of everything, before you find out what is causing the memory problem you may be right back to square one.
Click to expand...
Click to collapse
I agree with this, when your talking free "ram" as shown in the task manager , it is what is running at the time, not what is installed?
In my system i have not seen the "ram" ammount drop below about 350m ever.

Usually ranging between 200-400 free. Usually if I close the browser and clear my task manager, I can get higher. The thing is, why would you want all that unused? If your battery isn't being drained and your phone isn't lagging, you should be good to go.
Sent from my LG-E980 using xda app-developers app

Hmm!!!!!
only 200 MB free??
I have 500-700 free everytime!!
well, even if it is only 10 MB free, you should not worry about it(its a smartphone), until it affects performance of battery life!
to check whats eating up your RAM, go to settings>>general tab>>apps>>running tab!
you can also go to battery settings to check the most power hungry apps!
or you can install DU Battery Saver!

PsykoGeek said:
I agree with this, when your talking free "ram" as shown in the task manager , it is what is running at the time, not what is installed?
In my system i have not seen the "ram" ammount drop below about 350m ever.
Click to expand...
Click to collapse
PsykoGeek ram or memory is what I was talking about but that also includes the apps or software that is installed on the phone also If the underline problem is not found first, anyone can do a factory reset and re-install the app and there is a very high percentage that it will come back.
I would look at the app that I have downloaded and start to turn them off one by one and see which one could be the culprit. After you found one or two, see if you can live with out them.

High RAM usage is actually a good thing on Android unless you use a lot of emulators like I do. On PC, low RAM is good, but on here the more RAM that's used the better it is. Makes opening apps much faster. What would be killing the battery is an app keeping your device awake even when the screen is off.
Sent from my 4.4 Sphinx LG-E980

??????
Neroga said:
High RAM usage is actually a good thing on Android unless you use a lot of emulators like I do. On PC, low RAM is good, but on here the more RAM that's used the better it is. Makes opening apps much faster. What would be killing the battery is an app keeping your device awake even when the screen is off.
Sent from my 4.4 Sphinx LG-E980
Click to expand...
Click to collapse
Let me first say my Ram is usually around 350. But now I have a question, how is low ram a good thing and I am not trying to start anything I just like to learn more about the Andriod OS. I have use Wndows OS for year and it was always, like you said, bad to have low ram. So what has Adroid done to reverse that?
Again just trying to understand.

With 7 apps open.
Sent from my LG-E980 using XDA Premium 4 mobile app