To Kill or Not to Kill? - Android Q&A, Help & Troubleshooting

Do you Kill Tasks on a regular basis?
and why or why not
which apps do you kill?
and what do you use to kill them, or what is your favorite task manager?
-

Can't stand having em' open(them all), once I'm done with an app, is killing time.

They say in Linux that unused RAM is wasted RAM
And they claim that, apparently, the fuller your memory the better off you are
and they say your programs "arent doing anything" in RAM
and that killing it increases your CPU and Battery usage, as it took much more resources to close the tasks and reload them into memory, as opposed to "sitting there doing nothing"
So, if they arent doing anything, Why do they need to sit there?
I think its alot of propaganda by people wanting their programs loaded into your memory 24/7
The problem, as I see it, is that many apps just throw themselves into memory like crazy, even if you only opened the program once ever
MANY programs we likely seldom use, once a month at most.. and alot of those same problems load themselves into your memory automatically
WHERE DID THEY COME FROM AND HOW DID THEY GET THERE?
you clear all your RAM, reboot your phone, and THEY CONSUME RESOURCES cheekily loading themselves into your RAM
as if my start up / boot up time doesnt count?
GET OUT OF MY RAM
thats all I have to say about it
and I've used alot of task killers and apps that claim to disable startup items, yet, they still load into ram
their solution is "uninstall apps you dont use all the time"
thats not a solution.. thats an excuse to keep things gratuitously loading themselves into my RAM
If I dont use the program, I DONT WANT IT IN MY RAM.. until I use it.. then, it can stay there until restart, or until I kill it.. and then it should never appear again in my ram until summoned forth by my own finger tap
Is there really no actual solution to this, and instead, we have to listen to devs tell us all why we need apps in our RAM at all times
because I dont buy it

"Unused RAM is Wasted RAM"
until you launch a game or apps you actually need..
then GOOGLE decides what should be deleted and the app you actually want to use next gets kicked out of memory
thanks eh
-

We should get a way to select which programs stay in memory and which are dumped from memory on close
any apps like that?
I have also used Avast Firewall to block certain apps access to the internet, and after a restart, several of the apps acted like it was their first time online, or like they deleted all the info and pretended not to work if they couldnt access the internet, and they were all programs that had no business accessing the internet. but also all programs that require this or that special privileged or control to your information.. leading me to the conclusion that they dont need that ability to access all your private data for the program to run, but so they can send it to themselves. Thus keeping their program in memory seems a high priority for many app developers
I have yet to find a task manager that allows me to truly control app behavior.. disable items, keep them from staying idle in memory, keep in memory if possible, etc..
I'm really hoping Piriform's CCleaner for Android will be the answer we're all looking for, when it comes out
-

Well, tried a thousand task managers, and I found only one that can help to give you full control of your RAM
its called "Android Task Manager" (ATM), by SmartWho
you can select which tasks get auto-killed after exit, which tasks stay in RAM, How long after you close the app it gets booted from RAM / How long it stays in RAM after you close it, and by far the most control & customizability of any Task Manager out there
most others are designed to "Kill Apps" but that doesnt solve the problem..
it is true that Unused RAM is Wasted RAM, but you also need to have control over what exactly is in the RAM, and what isnt, for it to be anything other than counter-productive and harmful to the performance of your Android System
I think this power should come standard in all Androids..
its a bit confusing to get all set up, but it does have Widgets in the "Android" section (of Yandex) and in ATM's settings you can specify an action for clicking the widget.
so now all my important apps are safe from ever quitting, such as swapps, floating keys, exernal2internal, etc..
and all the apps I bring up frequently (chat clients, etc) get to remain in RAM
and programs I often need to close in more of a minimize state (like Office, Notes, etc.) are now also safe from being kicked out RAM
and every single thing else gets booted out of my RAM, to be sure theres room for all the stuff I actually want in there
-

I always try to unload my phone APP, but always uninstall failed. :crying:

Lindsay02 said:
I always try to unload my phone APP, but always uninstall failed. :crying:
Click to expand...
Click to collapse
ya, i've ran into apps that wont uninstall..
which is why the other thing missing is a better way to control apps behavior, at the launch point
Of course you can try to boot into safe mode and try deleting apps, you can force quit them & clear the cache then try to uninstall, but some apps you want on your device because they're useful, you just dont want them to start up by themselves at strange times.. and alot of apps wont stop being intrusive even if they are taken off the Boot list
There's just too much crapware out there disguised as legitimate programs because of an excessive amount of bad /poor/weak/unethical coders
it makes a strong argument for a 100 dollar buy-in for Android devs, like Apple & WinPhone have
however, the largest party responsible for the troubles we face is the devs of the OS itself. the android phone team.. for making all this possible
and 2nd to that group are the many ROM devs, the Telecom Carriers as well as the Private ROM devs.. many ROMs are actually made with stuff you cant ever delete, even in Superuser mode.
-

Today I turned on my phone screen and SuperSU was just sitting there waiting for me, asking me to allow something called 10068 to have root permissions, I totally spaced out and hit the wrong thing with my thumb... 10086 is my Telecom Carrier company, i thought it was that.
it created a blank entry in SuperSU permissions that couldnt be deleted or forgotten, and every time I clicked "forget", SuperSU would crash
and there was literally nothing anywhere I could do to try and figure out what the problem was..
Avast didnt recognize anything either
and I have some blank space in my Apps folder too, like some invisible program or something
I looked through the running processes and couldnt find anything
It might be from Tencent, that would definitely be about par for the course for that company
I had to re-root my phone to reset permissions, but who knows what kind of malicious code was already executed by that point.
I swapped SuperSU for Vroot SuperUser, which gives me alot of control over boot apps, running processes, etc.. which I can use with Android Task Manager to manage most things..
anyway, its running pretty smooth at the moment.. hope it keeps up
but all this could have been avoided with a platform made for me, and not for malicious coders & Corporate coders

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sometimes, words are simply not needed.

Another thing about Android apps, is they are made for mobile phones, meaning they are made to be turned off, kicked out of memory, and start back up as fast as possible, with being auto-kicked out of memory or not having no impact on your phone or the app itself
Even my largest game boots up in a matter of seconds, after being auto-kicked out of memory
maybe when android first came out that was a different story, but older phones usually didnt even have enough RAM to keep many programs in them anyway
but phones today are pretty powerful & fast, CPUs are speedy Dual & Quad core, GPUs are fast & powerful, and RAM has increased, albeit very slowly.. and so has RAM speed
even if you kick your biggest programs out of RAM, the programs you think you need right away, they start right back up anyway, only difference is you might get a splash screen for a few seconds.
Maybe Android users have been trained to dread starting up a program from the single-core days, but those days are pretty much gone..
I dont see much performance difference between a program starting from out of RAM and a program starting in RAM
thus, RAM should be used for programs that contain actual data you are currently working on, and need to switch between
Android is lacking a basic "Switch Program" or "Minimize Program" function, and everything is just lumped in together with closed programs and programs you dont need in a "Recently Used" programs list which just sits and cycles random programs through RAM according to the time they were closed.
thats about as unspecific as you can even get.. at least they could give us the option to select how Programs are cycled through RAM, such as by Frequency of use, Duration of use, etc.. or let us assign programs an "Android RAM Rating Preference" of 1 to 5 stars, with the higher stars remaining in memory as Higher Priority Processes
and thats something Android could throw together if they really actually cared about the quality of their OS, rather than in its ways it can be used to promote & advertise.
You often hear that "Programs dont do anything in Android RAM but take up space", and thats literally exactly my whole point. So, cool you know, i'm totally stoked that I have 500 mb more RAM so I can store even more "Programs that dont do anything but take up space" in there, and actually have the same exact amount of free RAM you get on an older phone.
RAM is needed to run processes smoothly.. in fact... and that includes the OS, your Launcher & Home Screen, all your Widgets, Games, Reference Material, Office Programs, and whatever else.
it actually takes time, energy, & resources for Android to remove processes from memory in order to make room for new processes. Only difference is if you let Android control it, it happens while you're doing other important things that could cause performance issues
and your newly opened application may initially require 20 MB ram, which android will have to adjust for, then go up to 50 which android will have to slow down & adjust for, then go up to a hundred, which android will have to adjust for,.. and if it goes back down to 50, android will slow to allow more spammy crap back into RAM, and so on and so on
its actually reading & writing to RAM a whole lot more than if you just kicked the process out altogether
the only drawback I can see to that is companies not being able to keep their programs in RAM for covert sending of data without being noticeable by the user, cause it was just so fast cause it was sitting in RAM ready to go.
-

Archer said:
Sometimes, words are simpl
Click to expand...
Click to collapse
Glad you caught the show, here you go bud

Thanks for the pic - it makes what I'm about to do even harder
This is not a constructive or useful thread. It's just yet another in a long line of rants by you against Android and Google. This is a development site, and we're not focused on negativity here (especially when it's incoherent rambling). Please stop creating rant threads.
Thread closed.

Related

Running out of RAM

Okay, so I know that the xv6800 ain't generous on RAM, but I'm constantly running low. Usually well under 10 megs. I'm using memmaid to try and keep things in check, but I'd really like to get more freed up for use.
Any suggestions on utilities that might help? Are there specific files (like fonts?) that get read into RAM on boot up that I could look at trimming down to get more room?
Thanks,
Chris
You could post what ROM, Page pool size, apps, homescreen plugins, etc.. you are currently using. That could give us a base to help you with.
I use oxios memory to recover stale ram and the stock task manager to close apps and I bott at 32mb available. Obviously I am running nueROM3, so every rom is different.
I am running DCD 3.2.6 and after a night or two after charging, I'm down to about 8 megs and have to soft reset. MemMaid helps a tiny bit during day-to-day use.
I also found out that when I put my SD card in, it drops from about 25mb to 15mb instantly. I don't know if that's due to programs I have running on my SD card or some power setting. I yank it out....10MB magically re-appears.
I run iLauncher with some shortcuts to programs on my SD card, and have all of my TomTom maps on them as well. As far as that goes, nothing else I can think of as to why my RAM drains night after night and why I lose that 10MB.
You're not alone.......
Have you tried uninstalling programs and seeing where the big leak is? I only install programs like games to the memory card. Nothing that runs as a regular day-to-day process. Its something to try. Then maybe re-install to the main memory to see if that helps.
kdj67f said:
Have you tried uninstalling programs and seeing where the big leak is? I only install programs like games to the memory card. Nothing that runs as a regular day-to-day process. Its something to try. Then maybe re-install to the main memory to see if that helps.
Click to expand...
Click to collapse
Not yet. I just got an extra refurb 6800, so I plan on doing some testing with your suggestions (don't have the ability to go w/o my normal phone for too long for testing). I also only have games installed to my SD card, so I'm thinking it could be some of the power settings I tweaked with when I had my 6700 (as far as the losing-RAM-when-inserting-card issue).
After the end of charging, filesys.exe, device.exe and gwes.exe are all around the 6-8MB mark (I made it down to 4MB of available RAM two days ago). I don't know if it's a program leak, or again, maybe something I did with the power settings.
Time will tell......
kdj67f said:
You could post what ROM, Page pool size, apps, homescreen plugins, etc.. you are currently using. That could give us a base to help you with.
I use oxios memory to recover stale ram and the stock task manager to close apps and I bott at 32mb available. Obviously I am running nueROM3, so every rom is different.
Click to expand...
Click to collapse
Okay, I'm running build 20275.1.3.3 dcd ROM.
Not sure where to find my page pool size.
For apps, it depends, but my usuals are Mobile Shell, Media Player, SPB Online, eReader, and PIE. Mobile runs in the background of course, and I'm lucky to have two of the other programs open. If I try a third it usually slows WAY down and often hangs.
Today screen plugs ins = 0. I use Mobile Shell's NOW screen as my home screen. Which reminds me, I've got spbWatcher running somewhere in there too.
Have you tried dotFred Taskmanager to look at all your running apps?
joojoobee666 said:
Have you tried dotFred Taskmanager to look at all your running apps?
Click to expand...
Click to collapse
Good suggestion.
I have never ran it, but SPB mobile shell was thought to eat ram, much as manila does. I could be wrong though... Lots of weather and mail plugins constantly nibble at ram too over the course of a day..
signal34 said:
I am running DCD 3.2.6 and after a night or two after charging, I'm down to about 8 megs and have to soft reset. MemMaid helps a tiny bit during day-to-day use.
I also found out that when I put my SD card in, it drops from about 25mb to 15mb instantly. I don't know if that's due to programs I have running on my SD card or some power setting. I yank it out....10MB magically re-appears.
I run iLauncher with some shortcuts to programs on my SD card, and have all of my TomTom maps on them as well. As far as that goes, nothing else I can think of as to why my RAM drains night after night and why I lose that 10MB.
You're not alone.......
Click to expand...
Click to collapse
Signal34...
what version of MemMaid are you running? also it is possible you have too many programs running from ur SD card I only gain 4megs of ram when I remove my SD card...
on the latest version of MemMaid there is a system Tweak called "optimize" if you have this version you should try it...the lowest my memory ever gets is 11megs and then I go into the task manager close whatever is running and it gets back up to 15 or 16 megs and after a soft-reset I get anywhere between 18.4 and 20 megs free...
that is with:
SPB Mobile Shell
SPB Pocket Plus
HTC Homeplug
PhotoContacts Pro
and messaging...running at startup
pdub73 said:
Signal34...
what version of MemMaid are you running? also it is possible you have too many programs running from ur SD card I only gain 4megs of ram when I remove my SD card...
on the latest version of MemMaid there is a system Tweak called "optimize" if you have this version you should try it...the lowest my memory ever gets is 11megs and then I go into the task manager close whatever is running and it gets back up to 15 or 16 megs and after a soft-reset I get anywhere between 18.4 and 20 megs free...
that is with:
SPB Mobile Shell
SPB Pocket Plus
HTC Homeplug
PhotoContacts Pro
and messaging...running at startup
Click to expand...
Click to collapse
I'm running MemMaid v2.3 and just noticed that setting, so I'll give it a whirl (many thanks! ). I just found out that my SD card issue was due to previous FATFS settings I had ported over from my 6700 days (I have my own registry tweaks cab). After clearing those out, I no longer lose that 10MB RAM when I insert the card....only about 1MB.
On startup, I now get about 17MB RAM after everything loads. Besides all of the normal system files, on startup I see:
VoiceCommand
tmail
ActiveSync
connmgr (is this normal?)
AE Button Plus
Small Menu
Magic Button
poutlook
NK.EXE (????)
My Today screen runs:
TodayTime
PhoneAlarm
TodayAgenda
iLauncher
Weather Panel
I'm still trying to figure out the charging issue, though. I don't know why I lose all that RAM....though I wonder if it has to do with having it charge via USB rather than the wall?
Thanks for all of the suggestions pdub!!
I moved a bunch of dll to SD card as well, and that seems to help some. I also discovered that SprintDB has like four or five dlls... some of them quite big! I deleted that program and that seemed to free up a lot of memory. I also got rid of everything else that I'd tested at one point but decided not to get or keep. I had a lot of old dialers on there.
Last night I had PIE, Media Player, PocketInformant, Mobile Shell, and eMail all running and still had 8 megs free.
Feeling a lot better about the memory situation now. I'll still work at tweakin' as much out of it that I can, but I'm feeling better for sure.
signal34 said:
I'm running MemMaid v2.3 and just noticed that setting, so I'll give it a whirl (many thanks! ). I just found out that my SD card issue was due to previous FATFS settings I had ported over from my 6700 days (I have my own registry tweaks cab). After clearing those out, I no longer lose that 10MB RAM when I insert the card....only about 1MB.
On startup, I now get about 17MB RAM after everything loads. Besides all of the normal system files, on startup I see:
VoiceCommand
tmail
ActiveSync
connmgr (is this normal?)
AE Button Plus
Small Menu
Magic Button
poutlook
NK.EXE (????)
My Today screen runs:
TodayTime
PhoneAlarm
TodayAgenda
iLauncher
Weather Panel
I'm still trying to figure out the charging issue, though. I don't know why I lose all that RAM....though I wonder if it has to do with having it charge via USB rather than the wall?
Thanks for all of the suggestions pdub!!
Click to expand...
Click to collapse
No problem, until we can get our hands on a HTC Diamond we have to make the best of the RAM we're given...if I come up with any other MemMaid tweaks I'll let you know...I'm still trying to learn all its new functions..
Conmgr.exe seems to be a normal process, i have it as well
Willing to bet SPB Mobile Shell might be the problem
I have used mobile shell on a few different phones and I always found it to be a memory hog so I usualy end up installing it. Tried it orginaly on a Treo 700w (very bad idea) then a Samsung i760 good phone should have been plenty of memory but after a day I would be down to around 5 megs free I had already disabled the samsung today screen clock since that had a known memory leak. I have tried Mobile shell on my VX6800 with stock ROM, DCD 3.2.5, 3.2.6, and NueRom3. NueRom3 was the only one that left the device enough memory. Right now I have it uninstalled and am using Throtle Launcher seems to be a little easier on the memory.
Installing software and putting DLL's on the memory card won't free up RAM, it will free up ROM, but that makes very little if any difference on the performance of the phone.
On older PocketPC 2003 software and older, there wasn't a ROM, everything was in RAM, so it made sense to install software on to your storage cards. Since the Titan has seperate RAM and ROM, there is no need to install on to your storage card. Actually installing somethings on the storage card will slow the phone down, when the phone wakes up it has to reinitialize the card and this can take 1-2 seconds, which is one reason ring tones don't work well or will get delayed when played from the card. In my case I install all of my programs to my internal storage, copy over my ring tones, etc to my internal storage and only use my storage card as storage for backups, GPS software, and my cabs to reinstall after a hard reset.
To free up as much ram as possible, limit your number of today items, don't install MSVC, and have as few programs open as necessary. I use the HTC task manager and have it set to close all programs except ActiveSync and my phone runs on average around 20mb free at all times. I am using DCD 3.2.6. Programs like Manila and SPB Shell all are memory hogs, sure they look nice, but are they a required function for your phone, or are they just easier.... You have to be able to make the distinction in order to get more free ram on your phone. Since these programs have to be "running" to work, then they eat ram. I don't mind programs that are memory hogs, pending they aren't running 24/7. But those UI programs do eat a ton of memory.
BTC
I'm really debating dropping Mobile Shell, but I do enjoy it a lot.
There is no question it's a memory hog... usually between 2-4 megs depending on what theme I'm running.
But, it also gives me a lot of functionality. I really enjoy having the list of upcoming appointments and alarms along with a quick and easy way to adjust volume and brightness from the NOW screen.
And the menu launcher is perfect sized for fingers.
Plus I like the picture dialing rather than having to browse through my contacts. Again, nice sized for fingers.
I know there are other options out there that can do all these things, but my question is: Will they be an gentler on the memory??
I have the same dilemma. Really like all the SPB products especially Mobile Shell with the Diamond skin, but I just can't take the memory loss any more.
BillThyCat said:
Installing software and putting DLL's on the memory card won't free up RAM, it will free up ROM, but that makes very little if any difference on the performance of the phone.
Click to expand...
Click to collapse
I keep seeing where people move stored programs from internal ROM to external ROM to free up RAM. That doesn't work on WM5 & WM6.
I have a number of programs installed on my Today screen, and Voice Command. Voice Command alone eats up about 3 meg of ram. But those are things I need to remove to free up RAM.
Diary over Shell...and does MemMaid really work..?
Instead of Shell, you can actually try SPB Diary, which isn't as nice as the Shell..but I found it quite useful- especially since it allows mail and text message previews and even allows a contact plugin, where your entire contact list is on the today screen under a tab (this eliminates the need to actually open the contact program, which i found sucks up 1% of RAM..lol), furthermore you can choose to pin contacts on the top so you can put the contacts you call most in a more convenient place
About the calender and appointments..it also has a tab that shows upcoming appointments and if you hit the calender's tab twice, it brings up a mini version of a calender that lets you see when things are due..etc..etc
The SPB Diary can also integrate other plugins (I realize putting IM+'s plugin into the the tabs reduces the RAM usage by a lot)
It also has a Notes tab (allows you to quickly access Notes, Word docs and Excel docs) and a Task's tab (which shows all tasks)
Of course the SPB Diary isn't as finger friendly, but I found that my fingernail and a bit of tweaking allows it for finger usage..doesn't look as nice..but if its functionality you want, the SPB Diary works very very well
I gave MemMaid a shot..and set the Optimizer to Extreme Speed and transferred several DLL's into the memory card..but nothing seems to have improved..furthermore I used the "Reclaim Memory" function and it doesn't reclaim RAM at all! Oxios Hibernate works so much better, where you can actually see an increase in RAM through the HTC Task Manager's percentage..so..does MemMaid actually work for anyone? Since I bought it already..I figure I'll keep it..but..
One more thing..if you're using A_C's S2U2, it actually brings up the RAM usage..to probably 2-3 MBs..if you want a simple locking mechanism, use the device's lock program (ugly, but does the work well) and you can have it automatically activate by using Homescreen Plus..It took a very long time to get rid of S2U2, since I liked it so much..but in the end still did it for the RAM
Some SPB Diary Pics..
Thought I'd show what I meant when the Diary shows everything you might need:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know this has been beat like a dead horse, but if you like those RAM-intensive apps like SPB MS, M2D, HTC Home etc... Try No2chems 6152 pre3.
I have been messing with 3.2.6 and pre3 for the last few weeks trying to figure out a way to run these apps/plugins/launchers and make the best of all of it. I have a broken arm and am not able to work so i figured I would try to do something useful with my off time.
Now I just have to compile a list of all the files necessary to make pre 3 as solid as 3.2.6

Best task killer..

Can anyone suggesr me which is the best task killer available in the market..m using task killer from rhythm software..
Sent from my X10i using XDA App
gupta.anurag08 said:
Can anyone suggesr me which is the best task killer available in the market..m using task killer from rhythm software..
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm running on the Advanced Task Killer, I do not have any issues with them. What's your problem?
I tried 2 3 task killers and all were showing different 'available memory'
Sent from my X10i using XDA App
Yeah, ATK is the best task killer app I've been using
gupta.anurag08 said:
I tried 2 3 task killers and all were showing different 'available memory'
Sent from my X10i using XDA App
Click to expand...
Click to collapse
It is because different task killer have different security policy, which allow them to show the system apps or not. So, in the lower security policy, you can see more running apps and gain more memory after kill them
i do have a question. why are you using a task killer?
I'm not having a dig at people that use them, but more trying to educate people that they are not required
"free memory" is not indicative of a healthy system in linux based machines.
please remember the way in which linux based OS's (which Android is) handles memory. Basically, if you have a heap of free memory it is simply wasted, the OS is not running any more efficiently. It is actually slower.
Here is a quick overview. Written for the desktop computer perspective, but translates over to a mobile phone OS quite well.
"Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time."
Read more here - http://www.linuxhowtos.org/System/Linux Memory Management.htm
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
gupta.anurag08 said:
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Nope, that is the reason why i have to use task killer
For me, it help me save much of battery
Since I stopped using a task killer my battery is better.
Don't use a task killer for a week and watch the difference.
gupta.anurag08 said:
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
Click to expand...
Click to collapse
yes and yes!
if your phone requires the resources, it will kill tasks that are no longer required. its all automatic. let it do it itself and you will have a much happier phone
AND better battery life, because the android OS is not continually restarting processes that your task killer deems unnecessary. I would trust the actual OS over a 3rd party app. It is designed that way for a reason (see my previous post).
mrtim123 said:
i do have a question. why are you using a task killer?
I'm not having a dig at people that use them, but more trying to educate people that they are not required
"free memory" is not indicative of a healthy system in linux based machines.
please remember the way in which linux based OS's (which Android is) handles memory. Basically, if you have a heap of free memory it is simply wasted, the OS is not running any more efficiently. It is actually slower.
Here is a quick overview. Written for the desktop computer perspective, but translates over to a mobile phone OS quite well.
"Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time."
Read more here - http://www.linuxhowtos.org/System/Linux Memory Management.htm
Click to expand...
Click to collapse
The idea is absolutely right if memory is being used for apps you are likely to open frequently. ATK allows you to unselect the apps you want to keep running. That way you can unselect the ones you use the most and then use the widget to kill everything else.
I notice when I press the home screen many apps don't kill them selfs and after a while I have loads of apps running and the system starts to lag, specially when I try to run something else.
There are advantages in both approaches and I find a mixed combination (available with ATK) makes it best, although the user need to use some common sense to do it right. Killing everything means the system will be more responsive but regularly used apps will take longer to start up. Not killing means the apps you use a lot "startup" faster when you use them repeatedly (as in fact they never stop running) but after a bit the system will lag when using other apps and may need to use pagefile/swap to atone for the lack of free RAM. That causes page faults which make the system even slower.
The iphone developers aren't complete idiots for killing every app. They have a priority for system responsiveness and they did achieve it at the cost of background running apps. I like the possibility to choose what I want to keep running and kill the apps I'm not likely to use again and it's one of the reasons I picked android.
A little Offtopic to both ifanboys and ihaters:
I never owned any apple product as I think of them as over priced. That said I think the iphone has great merit and I doubt very much we would have Android if the iphone didn't pave the way. Besides I jailbreak my brother's 3G and made it multitask enabled. Now it runs apps in background and there is little diference between it and my android. Except for the extra 200€ it cost, the lower hardware specs and expensive service provider contract my brother pays for a mandatory 24 months, while my X10 cost ~65% initially and came free of any contract.
well said, PCO
pco.vaz said:
I notice when I press the home screen many apps don't kill them selfs and after a while I have loads of apps running and the system starts to lag, specially when I try to run something else.
Click to expand...
Click to collapse
Thats what I and others have found, which is why some people choose to use one, myself included. Someone posted a link to an article last week with similar information posted here about the OS handling itself, but the comments section of the article were full of comments similar to what pco and myself have said, so it's all down to personal preference whether or not you choose to use one.
I did use a task killer for a while, then stopped. Personally my phone is better without. I have nothing except weather that updates automatically, I do it manually when I need it.
It is one of those things, just like on a laptop, everyone has different configurations and usage patterns that results will vary.
Sent from my X10i using XDA App
Don't apps exit when you keep hitting the back button? And for games doesn't hitting exit shut down the app?
I thought its a feature that apps don't close when you hit the home button?
gavriel18 said:
Don't apps exit when you keep hitting the back button? And for games doesn't hitting exit shut down the app?
I thought its a feature that apps don't close when you hit the home button?
Click to expand...
Click to collapse
The browser for instance doesn't. Same with many other. I think it's up to each individual developer to program that behavior for his app.
I got Visual task switcher and I notice lots of apps just stay running forever.
Task killer caused probs for me. A daily switch off doesnt hurt, but have run mine for 7 days and been ok. Even a bberry cant do that!
Sent from my X10i using XDA App
Guys, don't use home button to exit apps.
Will just send them in background.
Use the back button... this won't exit (most of) the apps but will put them in a "sleep" state so, next time when you will use it, it will load faster.
So, again, home button will put the app in background, still running.
Test it with an audio player for ex.
Or a browser... send it in background with home button and the player will still play or the browser will still have that page loaded.
With back button, after all views are "closed" the app will close too (well, put in sleep state).
I use ATK only to kill the apps i use once in a while ... the rest of the stuff, is always in memory.
My X10 has usually about 25Mb free
Actually I used ATK to kill application that need to connect to internet, and in my case there is extra charge payment. But after i used ATK I don't notice that the battery live is longer. So I ever ask someone in my thread about after ATK kill applications and so forth....
And somebody told me to quit using ATK and now I realize that the battery last longer than before.
But one thing still bother me is:
Setting - Wireless control - mobile network - mms & data (no checklist)
means: I can not access internet and receive or send mms either.
Actually I only need MMS, not internet.
May be somebody can help me solve this problem.
Thanks.
But my conclusion:
NO NEED ADVANCE TASK KILLER.
After I uninstall ATK, my phone still running smooth and the battery last longer.
May be we just need best Cache cleaner. But I still trying some of that.
@pco.vaz
I don't want to be mean, but you are wrong.
Even those iOS versions that are not multitasking enabled keep apps in memory. Leaving an app on an iPhone resets its UI state and halts its processes, but parts of the app are left in the memory. You can see the difference in loading speed if you decide to reopen it.
There were apps that could show memory usage and clean it on the App Store, but Apple removed them. You can still get them through Cydia and see for yourself how memory management on iTouch devices actually works. Basically the iPhone goes as low as 3-4 megs of free memory and handles it in smiliar way as Android.
On both Android and iOS, apps that are in background are paused after a while and do not use processor cycles. Memory they keep occupying is overwritten if needed by another process.
I do not recommend using task killer to people who do not know what they are doing exactly. Killing even simple processes often causes phone instability and drains battery faster, as others have already said.
If you feel your phone is stalled, perform a simple reboot. There are apps that run in background (in most cases you are warned about this) or are poorly coded that could cause this behavior. Other than that, inbuilt application manager is able to force close apps pretty well, if you need to kill a single app causing problems

Ram optimizers???

Hey...not sure if this has been answered before or not but im trying to figure out battery draining issues and one of things ive always used is ram optimizers...I have Android Booster and Android Assisant ....and then i also use the built in task manager to clear memory...shouldbi be using these apps or are they draining the battery by running in the background? They seem to clean up a nice amount of memory....and keep my phone running fast....just dont know much about them...
Sent from my GT-I9100M using xda premium
I do not think that by cleaning your RAM, you can reduce power consumption by RAM.
Actually, you do increase it. Android itself closes unnecessary applications when needed to clear memory. But, when you clean memory, either by task manager, or some custom tools, you are basically forcing applications to close and restart unnecessarily. I would say, it is additional load on CPU, and thus on battery.
For most applications, exactly startup and finish times are most expensive in terms of CPU load and battery. And most well-designed applications will not drain your battery when paused.
Reminds me of RAM cleaner programs for Windows machines, that would simply trigger excessive page faults.
while i agree with most of what you posted, there are 2 major flaws in your logic:
1. you talk about closing apps that restart on their own, but not many apps actually do that. sure, widgets, services, your launcher, communication apps and syncing apps need to run in the background, but certainly there are other apps eating away the battery, that need to be fully closed, when not needed. kies air or wifi file explorer come to mind. some of those apps don't fully close through the back button and must be killed from a task manager to save battery.
2. you say apps are paused. that is not necessarily true. many apps are capable of fully running in the background, after all, we are talking android and not iOS. we have full multitasking and apps are not generally suspended. say, you want to play a game for the first time and it needs to download more data. you can do whatever you want with your phone, open a dozen other apps, browse and listen to music, that download will continue in the background. this might fill up the ram over time, if you never close an app or apps do not allow direct closing.
there is a reason why samsung supplied the phone with a built-in task manager.
some apps are not well made and don't quit properly and need to be killed that way and killing off unnecessary apps (that won't restart) makes sense.
and let's not forget apps that get stuck but don't force close. they need to be killed as well. what else are you gonna do? restart the phone? certainly that wastes way more power than a restart of a few services.
every time you have a look at the samsung task manager or the "running" panel of "manage applications" and you use 500 something MB of ram and kill all apps, it will go down to something like 200 something, then the services restart and you are back up to maybe close to 300 (all numbers vary on your rom and apps). given that situation permanently saving 40% of ram is certainly a good reason to kill apps before you put the phone in your pocket.
I guess, then, it is best practice to kill all apps from task manager, a few times a day, especially after using several different applications and closing them. Applications that are needed will be restarted automatically.
I am not sure about running so called "RAM optimizers" constantly, though. When you are using your phone, it simply introduces more lags. Otherwise, it does nothing, if you have cleared RAM after heavy usage.
mirbeksm said:
I guess, then, it is best practice to kill all apps from task manager, a few times a day, especially after using several different applications and closing them. Applications that are needed will be restarted automatically.
I am not sure about running so called "RAM optimizers" constantly, though. When you are using your phone, it simply introduces more lags. Otherwise, it does nothing, if you have cleared RAM after heavy usage.
Click to expand...
Click to collapse
killing itself is not necessary in the 1st part.
the more the memory android uses the better the apps behave, thats how android is desinged.
if you people still want to release some memory just use the samsung task manager ot clear memory or "fast reboot" from market.
Thx for the posts...i deleted the 2 android apps for now to see if theres a difference...i will trybusing just the built in task manager for a few days and see how that goes. But for example i mainly use my phone for words with friends...facebook...twitter and instagram....when i run the built in task manager it frees up mabye 200mb of ram....then i would run android booster which would clean up another 200mb and would close stuff like facebook...and tweetcaster and so on....the built in task manager doesnt seem to pick up on and close everything it should...which is why i downloaded the others...my phone has 800+ mb available and i usually find that ots using 500 of those 800 at all times...i wouldbfind myself constantly closing stuff with the optimizers...but like you said...they just open up in the background again anyway. Im rooted and have got rid of all the safe stuff to get rid of and the funny thing is i still dont see much of a difference in ram consumption...i think of ram as important cause it keeps things running smooth with no lag...not sure what to do i guess...ill try it like this without the optimizers and see how things go and download them again if i get bad lag...what i really need is a actual list of my phones internal software so i can get rid of the rest of the unneeded system files...ive found similar lists..but never a list of my actual phone...theres certain stuff running on my phone that isnt in the lists ive found so i left them with the worry that i may have to reinstall the rom if i delete the wrong thing...im also a android noob...only 2 months of using it so far so ive got tons more learning to do...thx for the opinions tho...keep em coming if you got em!
Sent from my GT-I9100M using xda premium

Why is it pointless to use a task killer

It 'just a habit of many displaying applications in the background to go on the Android Market and install a task killer for fear that some application in the background throughout the battery consumption and slow down the phone memory consuming.
First Step
Android is the son of Linux and not Windows, Windows programs make sense that clean and optimize your memory, not in linux and behaves the same way if you have 10 or 100MB of free memory.
How to manage Android applications
Android applications and processes have defined 3 stages:
1) Running
2) Break In
3) Stopped
Each application runs in its own process when Android starts the process need to be made and ends when no longer needed, it lives in its own world and its code running is isolated from the rest with a Virtual own machine, it is assigned an ID whose permissions are visible to the user and 'application.
If an application needs to share files with another application creates a unique ID to save memory with a single Virtual Machine she shared.
Services are active as long as they need as well as activities that require the data connection and every process of Android. To understand whether an application or any process needs to connect and see if there are updates that it is active so that makes this operation.
It is not good or terminate these operations because the process will start all over again immediately active or when we are going to open an application it will take longer to open.
All processes are terminated when there is no longer needed or when the memory required by other processes.
If a user leaves a task for a long time, the system deletes all activities except the root, and when the user returns to the task it is like you had left.
An application is running when in fact you're running and is the first system plan
When it is no longer at the center of the 'attention but can still be visible is paused and can be killata by the system in case of need for extreme lack of memory
Finally, the application is blocked, but retains all the information is no longer visible on the screen and is in the background, can be killata from Android for any other activity that requires memory.
Summing Android is designed to kill the tasks when
You need more memory
They finished their work
Are not used for a long time
Kill process "by hand" can lead to side effects such as non-receipt of messages, slowdowns, crashes, etc. widget
The majority of applications closes with the BACK button and in any case by pressing the HOME Android close the task after it has been in the background for a certain period of time.
The majority of services running in the background using very little memory when they are not doing something so all other processes (reporting, etc.)
Domada: But why do I open google maps, facebook etc. mail.
These programs are not actually "open" if you notice are all programs that need a network connection, when you turn on the phone they do nothing but check for updates and notifications and then close.
If these activities killiamo happens that most of them will re-open to start all over again or take longer to open when we need them, or worse, will not give us accurate and up to date or will not work properly as well as make a lot more processor.
stempox said:
It 'just a habit of many displaying applications in the background to go on the Android Market and install a task killer for fear that some application in the background throughout the battery consumption and slow down the phone memory consuming.
First Step
Android is the son of Linux and not Windows, Windows programs make sense that clean and optimize your memory, not in linux and behaves the same way if you have 10 or 100MB of free memory.
How to manage Android applications
Android applications and processes have defined 3 stages:
1) Running
2) Break In
3) Stoppati
Each application runs in its own process when Android starts the process need to be made and ends when no longer needed, it lives in its own world and its code running is isolated from the rest with a Virtual own machine, it is assigned an ID whose permissions are visible to the user and 'application.
If an application needs to share files with another application creates a unique ID to save memory with a single Virtual Machine she shared.
Services are active as long as they need as well as activities that require the data connection and every process of Android. To understand whether an application or any process needs to connect and see if there are updates that it is active so that makes this operation.
It is not good or terminate these operations because the process will start all over again immediately active or when we are going to open an application it will take longer to open.
All processes are terminated when there is no longer needed or when the memory required by other processes.
If a user leaves a task for a long time, the system deletes all activities except the root, and when the user returns to the task it is like you had left.
An application is running when in fact you're running and is the first system plan
When it is no longer at the center of the 'attention but can still be visible is paused and can be killata by the system in case of need for extreme lack of memory
Finally, the application is blocked, but retains all the information is no longer visible on the screen and is in the background, can be killata from Android for any other activity that requires memory.
Summing Android is designed to kill the tasks when
You need more memory
They finished their work
Are not used for a long time
Kill process "by hand" can lead to side effects such as non-receipt of messages, slowdowns, crashes, etc. widget
The majority of applications closes with the BACK button and in any case by pressing the HOME Android close the task after it has been in the background for a certain period of time.
The majority of services running in the background using very little memory when they are not doing something so all other processes (reporting, etc.)
Domada: But why do I open google maps, facebook etc. mail.
These programs are not actually "open" if you notice are all programs that need a network connection, when you turn on the phone they do nothing but check for updates and notifications and then close.
If these activities killiamo happens that most of them will re-open to start all over again or take longer to open when we need them, or worse, will not give us accurate and up to date or will not work properly as well as make a lot more processor.
Click to expand...
Click to collapse
I know I'm likely to get criticised by some for saying this but some of us have to use task killers.
My phone has an average of 140 mb free after it boots up. Add to that apps that stay in ram even when you close them and you can have as little as thirty or fourty mb free.
I've seen apps such as facebook and tapatalk, and even some games, taking up ram even though I don't want them used once I exit from them...and when my phone gets to around fifty mb free or less it can get slow and unresponsive.
A quick kill of un needed apps makes the os perform as it should again.
It's nice to say android clears up ram as needed, and it does, but try playing a decent hd game when your ram is low and, unless you kill some apps first, you're left with a black frozen screen while it tries clearing some ram. In some cases your phone can be unusable for a while, on mine when this happens the capacitive buttons stop responding to keypresses.
Now on ics with 1 gb ram this isn't an issue but for those of us with less ram and / or an older os it is.
Ideally we could configure non system apps so that if we don't want them in ram when finished with them then they cannot auto restart.
It is a simple fact that two identical phones will perform differently if one has lots of free ram and one has most ram in use, I use an on demand task killer so that apps that stay around on exit can be stopped from eating ram and slowing my phone down so for me a task killer is not pointless specifically because it frees up ram so that something memory intensive can be run without slowing my system while android tries to make room for it.
So while I agree with the theory, in practice task killers can be useful or at least on demand ones can.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
I agree with how Linux handles its applications. I switch between WinXP and Ubuntu and the overall way tasks are utilized are similar, but linux does a better job at handling running applications. On windows i have Chrome open and with 9 tabs open im hitting 1.5 gb ram used. Same situation on linux i find myself hitting around 500mb of ram used. Im sure this applies to android as well.
On a side note i find that people who "Kill Tasks" are just running them because they can and are usually fixated on seeing a large amount of ram free. It just adds another reason to stay on their device. Just my opinion.
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
gruntparty said:
On a side note i find that people who "Kill Tasks" are just running them because they can and are usually fixated on seeing a large amount of ram free. It just adds another reason to stay on their device. Just my opinion.
Click to expand...
Click to collapse
I use one to make sure my phones already low ram does not drop so low my phone becomes slow, which it does when you get to even just fifty mb free ram left. And to kill those applications which do not exit properly.
On an android phone that has 512 mb ram if ram gets eaten up the phone goes slow, and I know it is not just me because other users with similar setups have same issues. So I think it is too general an assumption to say we all use task killers for say a cosmetic rather than practical reason though I'm sure some do.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
Markuzy said:
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Unfortunately this only stops apps auto starting at boot and once you have used an app and exited it, a lot stay in ram.
Some restart when killed some don't but when your phone is on permanently as many are, having low ram can quickly be a problem.
I think part of that is the phone manufacturer as 512 mb ram, with just 140 mb free at boot, is rubbish on a dual core 3D phone but whatever the cause I find killing tasks helps make phone run better.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
I used to kill tasks when i was on Android 2.1 an 2.3, but since 4.0 i feel my phone gone strangely fast, and i don't need to use task killers anymore. Phone is LG GT540, so...
lewymaro said:
I used to kill tasks when i was on Android 2.1 an 2.3, but since 4.0 i feel my phone gone strangely fast, and i don't need to use task killers anymore. Phone is LG GT540, so...
Click to expand...
Click to collapse
I used to love my gt540. Didn't know you could run ics on it though, good phone for the price but didn't like the resistive screen though the phone itself can take some serious punishment and still keep working.
I love lg for their build quality, pretty hard to break them with dropping etc, but unfortunately they do bad with the software side.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
Good topic, I don't like the task killer!
Sent from my GT-I9100 using Tapatalk 2
In general, yes task killers are bad. But occasionally it IS necessary to kill an app. Sometimes an app will freeze. Then it needs to be killed to be able to use it again. But you can easily just go into Settings > Applications > Manage Applications, find the app and then Force Stop it. So there's no real need to have a task killer. Although I do like to have Watchdog on my phone, as it shows the amount of available CPU cycles being taken up by each app, so you can make sure background apps aren't using too much CPU. (It does also show RAM usage, but it sorts apps by CPU usage, by default at least).
Linux has nothing to do with the management of an application, the applications under Android are sandboxed in java and there is this dalvik machine that takes care of everything.
I don't get why people keep mentioning this kernel over and over, also for the biggest part of its history Android did not use a real linux kernel with vanilla flavour, only recently the Android kernel was merged with the linux kernel mainline.
This is one of the very first Google video about Android http://www.youtube.com/watch?v=Mm6Ju0xhUW8
edit: In this series of videos there are also references to memory management and app management.
Markuzy said:
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
You are right
I do the same thing
In cm9 you can enable auto close apps with long press back button
So I don't need a task killer
Sent from my LG-P500 using xda premium

How to have commonly used apps always preloaded into the memory

I was wondering if there is a way to always keep commonly used apps preloaded into memory for instant access. (sms, contacts, browser)
xemi1 said:
I was wondering if there is a way to always keep commonly used apps preloaded into memory for instant access. (sms, contacts, browser)
Click to expand...
Click to collapse
Start them once, and they will be remaining in memory until Android OS decides the memory is better needed elsewhere.
What you describes is not The Android Way. Primary memory is the most critical resource in Android, lacking virtual memory. Due to this fact, an app may be killed by the OS if more memory is needed for other needs. On the other hand, an app often used, is very likely to reside in memory, giving you this "instant access" you want. If you'd be able to lock an app and its memory, the phone would get out-of-memory not being able to release it when you try stating Angry Birds.
This said, some devices have "Don't keep activities", "Background limit: no processes" or so much bloatware installed, leaving an app gets it more or less instant killed, causing the next start of it to be considerably slower. In this case, the solution is to adjust those parameters, not forcing your apps active.
Read this thread. It might give you some light. Specially the " bulletproof " thing.
The only reason I'm needing this is because of the buggy dialer/contacts that comes with the stock sgs s3 ics 404, where if they go out of the memory they take like 1 sec to load, whereas different dialers and any other stuff is pretty much instant.
It's annoying to experience that delay whenever you need to make a call on a flagship smartphone.
And other market dialers are ugly and/or need the stock dialer to open for them to work.
I would like to avoid rooting g and losing my warranty as well.

Categories

Resources