Related
Not sure if you all are familiar with this app, I haven't seen anyone speak upon it on XDA yet, so just thought I'd share my experience with it.
http://www.androlib.com/android.application.com-lim-android-automemman-wBjq.aspx
IMO, this app is pretty cool. Very simple and easy to use, although it doesn't come with detailed instructions on how to use, so I felt the need to explain a little bit about it:
Tired of lags to and from Dialer/Contacts/Call Log?
Have you ever pressed the call button to dial a number/contact and nothing happens for 10 to 15 seconds then finally the call goes through and starts to ring?
Ever went back to home screen after fooling around with an app, or web surfing the browser only to find that a widget or two is missing or is not loading/refreshing properly?
Gmail not syncing daily as it usually does?
Market taking forever to load up the downloads page or lagging connection with G-talk to promptly start the download/updates you started?
Well these are the memory/background/content provider situations that need to stay snappy if nothing else does, agree?
Then this app may or may not be the answer to all of your problems.
For me it was. First and foremost, it is a FREE app, yay! (at least to my current knowledge, unless developer has changed it)
*FYI* This app does require root permissions, so if you are not rooted this will be of no use to you.
After installing, when first opening the app, super permissions should pop up, just check the always box and press allow for root access. Close the app, then re-open.
Now, there are 4 options you may choose, DEFAULT< CUSTOM< MILD< AGGRESSIVE
Default settings will be what you see on first use, those are the default Android memory settings for your G1
Custom- self explanatory, you move the bars of each memory category according to how you prefer- *Note* the amount shown is not exact memory, it is a threshold, basically a set amount not to exceed, Your phone will automatically choose how much to use according to how much it needs, but its limitations will be set by the threshold you choose. Go ahead and make your adjustments, then click the custom button, this will save these settings. So the next time you want to re-enter those settings, just hit the custom button, and it will restore.
Mild- Simply a preset application setting
Aggressive- Another preset app setting
You choose what works best for you, I would suggest playing around with different settings until you have achieved a memory usage that gives you the most improvement, *Note* Do note mistake this as a speed app, it only controls memory, so don't expect some super fast change, but if you set it up properly, and memory is being managed to the best case scenario of your usage, speed will increase, believe me.
Start with the presets, see how they work throughout the day, if you notice no difference, or worst than it already was, change it to something else.
Personally, my best experience has been with the Aggressive preset. Its been the most effective for my phone, however; this won't be the case for everyone. Aggressive basically raises the threshold for background data(widgets,home, cache, etc.) And content provider (google apps, settings, G-talk and stuff) And Empty application- this means, IMO, the amount of free memory sitting around available, for soon to come data or apps that you might open later, I.E.- multi-tasking, Call screen, new mms or sms
It also lowers the threshold of the foreground and running apps, so that they don't suck up so much memory the phone lags before it can open other things in memory. Get it? But as I stated, different people will have different preferences.
If you haven't already, try it out! If you don't like it, or don't need it...maybe results won't change things enough for you to have any use for it, you can always uninstall, and it won't harm any memory or data on your phone.
Also, regardless of threshold settings, if you open or use more memory than threshold limits, it will not break or crash you phone causing reboots or anything like that. So don't worry. The app does not prevent you from doing anything on your phone, it simply manages it according to your use.
I hope this comes in handy for someone, as it has been more than useful for me on a daily basis. You can find more information via market or the link above.
Don't take offence to this, but any "speedup" you think you are getting from it is entirely a function of the placebo effect.
There is no advantage to forcing memory to remain "free", and in fact, doing something like this will actually make the phone SLOWER than it would otherwise be.
Android has a VERY well thought out memory management system. It keeps a record of processes running and their priorities. In the event that more memory is required for a higher priority application, it will automatically select some other application to kill off in order to get that.
What this does is it ensures that you ALWAYS have the memory FULLY utilized, which means optimal performance under every circumstance.
An unfortunate trap that you are falling into is the traditional view of memory -- for example on a DESKTOP system, you don't have anything killing off unused processes, which means that every program you open will use up more memory, so the more FREE memory you have, the more new programs you can open before it starts swapping, and therefore you aim to always have a big chunk of free memory because more free memory means more applications can be open.
Android doesn't work like this!!!
What you are doing is forcing a memory utilization threshold on the thing. This has the same effect as simply reducing the total memory available on the device. That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
I could be wrong, but I believe the intent of this is to allow the Android internal memory manager to be tweaked so that certain applications/processes have a higher priority and remain in memory and those that you deem as "less important" are removed first.
Here is a thread on the Hero forum about it:
http://forum.xda-developers.com/showthread.php?t=622666
Also, here is another App that does the same thing... only it will allow the settings to persist through a reboot...
http://www.androlib.com/android.application.com-rs-autokiller-wEwp.aspx
With this App, I do not notice an increase in free (meaning useless) memory... I do notice that key processes that I deem important are still running on CM 4.2.14.1... Even after running many of the ~160 apps I have, including games...
Individual results may vary... Nobody runs the same exact configuration and apps on their G1...
L8r
@Ibcoder
That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
Click to expand...
Click to collapse
But it doesn't do that, the threshold simply states a measurable amount of reserve...but not a limitation. Theres a difference. Limits and thresholds are not the same, So what you are saying is not how the app works. All apps open in memory remain in memory, of course you still have to use kill switches and task managers to control unwanted memory hogs, but the app basically controls the memory in use, thats all Im saying, so if that memory is being divided properly, responsive times will increase, I know android had its own setting of doing this, hence the word *DEFAULT*...that is what the app is for, if you don't want to let Android control your memory usage, the app gives you the option to customize it
Also, here is another App that does the same thing... only it will allow the settings to persist through a reboot...
http://www.androlib.com/android.application.com-rs-autokiller-wEwp.aspx
Click to expand...
Click to collapse
Cool app! Thanks for the link, never seen this one.
But wouldn't auto kill be the same as all the other task managers and explorer apps? Its made to kill off unwanted apps, processes, and background services to free memory right? Well, I have plenty of those, and they all work quite fine.
The app I am discussing above is not a killer, its only a manager, it just gives the proper amount of memory to the category you specify to be more important memory users, thus for saving wasted memory. It doesn't specifically kill off or make memory, just manages it.
thanx though, I will try that out.
I recently saw this new app in the Market, but was unsure what advantage it will have on performance, if any. I'll pay attention to this thread to see where the discussion leads on it's usefulness (or potential lack thereof).
TeeJay3800 said:
I recently saw this new app in the Market, but was unsure what advantage it will have on performance, if any. I'll pay attention to this thread to see where the discussion leads on it's usefulness (or potential lack thereof).
Click to expand...
Click to collapse
Ok, and I don't blame ya, that's how I test everything on xda, roms,apps, hacks, you name it....but only after I review enough good responses (preferably 3)
But on the contrary, there have been times that something was reviewed poorly, but after my own experience turned out to be great! You'll see that a lot in the android market as well, great apps with two star/3 star ratings all because some asshole didn't know how to use it, LoL
Try it dude, you got nothing to lose...won't break ya phone, but if ya want to play safe nandroid your current stuff first.
Klyentel said:
Cool app! Thanks for the link, never seen this one.
But wouldn't auto kill be the same as all the other task managers and explorer apps? Its made to kill off unwanted apps, processes, and background services to free memory right? Well, I have plenty of those, and they all work quite fine.
The app I am discussing above is not a killer, its only a manager, it just gives the proper amount of memory to the category you specify to be more important memory users, thus for saving wasted memory. It doesn't specifically kill off or make memory, just manages it.
thanx though, I will try that out.
Click to expand...
Click to collapse
As far as I know, they are pretty much the same... The XDA thread I mentioned above has both the Dev of the App you posted and the Dev of the App I posted... They both created one at around the same time... One with sliders and one with fields... The only difference I think is that AutoKiller uses a service to write the settings on a reboot...
Still playing with this to see if it makes any real difference... I know if I set the values too aggressive, then the browser reloads every time I come back to it...
I know if I set the values too aggressive, then the browser reloads every time I come back to it
Click to expand...
Click to collapse
yeah that has happened to me too.
The linux kernel keeps a buffer cache of recently used files in RAM. So whenever an application wants to access something on the flash, instead of going to the flash file system, it can just get it from the file buffer cache in RAM, a significant speed increase.
If the RAM is currently being taken up by unused android apps, then that leaves less room for the buffer cache, so in theory, by killing off unused android apps more quickly, that will allow the linux kernel to allocate more space for the buffer cache and thus speeding up the system.
Am I way off here?
Dave
lbcoder said:
Don't take offence to this, but any "speedup" you think you are getting from it is entirely a function of the placebo effect.
There is no advantage to forcing memory to remain "free", and in fact, doing something like this will actually make the phone SLOWER than it would otherwise be.
Android has a VERY well thought out memory management system. It keeps a record of processes running and their priorities. In the event that more memory is required for a higher priority application, it will automatically select some other application to kill off in order to get that.
What this does is it ensures that you ALWAYS have the memory FULLY utilized, which means optimal performance under every circumstance.
An unfortunate trap that you are falling into is the traditional view of memory -- for example on a DESKTOP system, you don't have anything killing off unused processes, which means that every program you open will use up more memory, so the more FREE memory you have, the more new programs you can open before it starts swapping, and therefore you aim to always have a big chunk of free memory because more free memory means more applications can be open.
Android doesn't work like this!!!
What you are doing is forcing a memory utilization threshold on the thing. This has the same effect as simply reducing the total memory available on the device. That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
Click to expand...
Click to collapse
@dwang-agreed, as I stated @lbcoder, what he is saying is that the app holds everything in memory which slows down system, but it does not do that, and he implied that I stated it limited use of apps, which is incorrect, it does not operate as a limiter, or a kill switch, only a manager. Sort of like, organizing processes by priority based upon setting of threshold tolerance. Of course killing off unwanted apps and processes have to be done manually, via kill widgets or file explorers, When I first posted about this app I assumed that concept to be in mind of the reader....sadly I was wrong. I guess everything around here has to be put in perspective as if the reader knows nothing...sort of like an "101 handbook for Dummies" type thing.
What you are suggesting is incorrect, contrary to the product description, and quite frankly, impossible.
And you can't read.
There is no "I" in lbcoder.
Klyentel said:
@Ibcoder
But it doesn't do that, the threshold simply states a measurable amount of reserve...but not a limitation. Theres a difference. Limits and thresholds are not the same, So what you are saying is not how the app works. All apps open in memory remain in memory, of course you still have to use kill switches and task managers to control unwanted memory hogs, but the app basically controls the memory in use, thats all Im saying, so if that memory is being divided properly, responsive times will increase, I know android had its own setting of doing this, hence the word *DEFAULT*...that is what the app is for, if you don't want to let Android control your memory usage, the app gives you the option to customize it
Click to expand...
Click to collapse
lbcoder said:
What you are suggesting is incorrect, contrary to the product description, and quite frankly, impossible.
And you can't read.
There is no "I" in lbcoder.
Click to expand...
Click to collapse
First and foremost buddy, I quite frankly don't give a dam how you spell your name with an "I" or an "L"
Secondly, what I am stating is not incorrect, and is possible, because I have the app, use it everyday, and does exactly what I said it does via OP. Thank you very much. If you disagree, then don't download the app. Simple as that.
or heres a better idea create one of your own. I will be more than happy to try it if you feel you can do better, but don't downsize the quality of this one, straying other users away from trying it, as it may be as useful to them as it is me. Got it?
Now get ya DREAM on...(with android that is )
and leave me alone.
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
It would be nice to have, say, long press back key to kill the current app.
Big_O said:
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You obviously didn't search for this:
http://forum.xda-developers.com/showthread.php?t=678205
You DON'T need to intervene with N1 memory management, since you don't know how it works. You assume wrong. And most bad gossips are created by people wrongly assuming something, thinking they know something while they actually don't.
My N1 runs equally well with 40MB and 250MB free. The only reason I use a task killer is to kill apps that I want to return to their "initial" state for some reason, or to kill apps that I suspect of wrongdoing.
Exactly, the nexus has no memory management issues. It is just your misunderstanding of how Android works. Leave your tasks alone.
If you have one or two particular apps that are bad citizens and should be shutting down in the background but don't... you can use "1Kill" from the market to create a home screen shortcut that kills that specific app when you press it.
Fring used to be a bad citizen - it would lock my wifi on even when I didn't want to be using it, and had no exit feature. So I'd always have to kill it after finishing up with it. Now it does have a proper exit, thankfully.
Jack_R1 said:
My N1 runs equally well with 40MB and 250MB free. The only reason I use a task killer is to kill apps that I want to return to their "initial" state for some reason, or to kill apps that I suspect of wrongdoing.
Click to expand...
Click to collapse
Ditto!
1 app running or 50 apps running they all still run the same.
I find it even funnier how iOS4 users in Apple-land are suddenly freaking out that so many applications appear to be open "in the background" and complaining that they have to spend so much time "killing" apps.
Big_O said:
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I think you have the memory management issues.
Before anyone gets tarred and feathered, that explains why many users on unrooted stock roms ha e frequent touchscreen lockups, hesitation and freezes. Guess theres a reason why the market has so many task killers. Maybe the devs should read this thread also lol. Instead of flaming, positive feedback is appreciated. I did search, but its a bit time consuming sifting through 5000 posts. Maybe you guys o rooted phones have no lockups, but google shows an azzload of people with similar issues.
Sent from my Nexus One using XDA App
1) You've been given some answers in the thread, if you cared to look.
2) App that loses focus goes to background. That's the way OS is built. If you want apps to be killed on losing focus, get iOS 3 to run on your device. Seriously, what kind of answer would you expect, if you want to turn multitasking OS into non-multitasking?
3) The market has task killers because they can be written for multitasking OS, and because they help dealing with bad apps. Not for any other reason.
4) The OS loads some of your most used tasks when it runs, even if you don't know about it. Just loads in the memory, and allocates no CPU time. If you leave your phone unattended, your free memory goes down by itself. Why? Because free memory is wasted memory. You can check the "EMPTY" processes in Astro, for example.
5) The best task killer is careful selection of your apps. You see hangups? Find out the app that's doing it and remove it, or kill it specifically after running if it's necessary.
6) Task killers are a good source of lockups and freezes too, did you know? I guess you didn't read that thread...
All this meant to say: instead of looking for a way to cripple your OS, learn to select your apps, and don't solve issues that you don't have.
cmstlist said:
I find it even funnier how iOS4 users in Apple-land are suddenly freaking out that so many applications appear to be open "in the background" and complaining that they have to spend so much time "killing" apps.
Click to expand...
Click to collapse
Yeah, I think Apple needs to tweak their multi-tasking still. I've played with my gf's iPhone a bit this week, and it's a little annoying how now you have to explicitly quit every app. For example, with the Settings app if I go to change a preference quickly then return to home Settings app is still in the running apps list. I think little utilities like that should be able to quit themselves automatically.
I know the app isn't wasting memory or CPU down there, but I just don't see why you would want it cluttering up your app switcher forever.
Oh well, it's progress though. At least now you don't have to quit everything else you're doing to listen to Pandora
well android does the same thing. if you go into the settings menu, then hit home button, the settings is still running in the background. of course andoird will kill it later when it needs to.
You don’t need to change your ROM to get the best from your 2x, just a rooted stock ROM and a couple of apps that will change things dramatically. One thing I’ve noticed on the 2x is its memory management is too lenient and gets consumed quickly by background tasks etc. In no time I was down to 40-30Mb free memory and then my phone would run like a dog resulting in a reboot as the only solution.
Installing task and app killers are not the way, as they’ll only give you a short respite before the apps and background tasks you killed relaunch.
However, there is a solution.
1)Root your phone using SuperOneClick (piece of cake, instruction already on this forum)
2)Install “AutoKiller Memory Optimizer” by AndRS Studio free from the market
Optional
3) Install “Watchdog Task Manager” by Zolmut LLC (There’s a free or Paid version) I paid!
4) Install “Root App Remover” by Best of Best Android app
AutoKiller is not a task killer/manager it reconfigures Androids inbuilt memory manager to kill or suppress memory usage by applications and tasks. I now always have about 140-170MB free RAM at all times regardless of what I’m doing (but I do close my apps with the back button rather than click home)
AutoKiller Memory Optimizer Settings
I’ve used the ‘Extreme’ settings to ensure I have around 150MB free, and this makes a huge difference in everything I do with the phone.
----------Optional things you may want to consider-----------
Watchdog
Yeah, I know this is a task killer but Watchdog is different from other task mangers as it monitors CPU usage rather than free RAM, 3D Gallery for example is a CPU hog on my 2X, so I configured it to be killed if it consumes more than 30% CPU whilst running in the background, you’d be surprised what saps your battery!
Root App Remover
Uninstall the tosh supplied on the ROM, I removed the following, AndroidBackup (I use Titanium Backup), CarHome, F-Secure_Mobile_Security, SNS (If you’re not using the built in Facebook and Twitter app).
I also use LauncherPro with Beautiful Widgets to give my phone an almost HTC Sense look and feel and uninstalled LG Home using Root App Remover afterwards.
Hope it makes a difference for you, it did for me, vote if you like
What do you think having 140-170MB RAM free at all times actually does?
Guess what? Nothing.
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
We want to see some bench marks.
Thanks for sharing! My phone does become much more responsive
Sent from my LG-P990 using XDA App
I tried the app too and i can say that it works, I also did some of the advanced tweaks.
phone seems more responsive now.
Yes, me too. It's more responsive now. Also when I open app manager, the app list is a lot faster.I know it's more related to file read/write but still it's nice to finally able to browse with less waiting time.
Sent from my LG-P990 using XDA App
thx
good one and simple, thx
cann someone please post some benchmarks?
Here are some screenshots, tested with AnTuTu Benchmark
The first one is v10c stock, some apps like f-secure, carapp etc frozen, second one is with using autokiller memory with preset extreme, third one is to compare, this was while using cm7.1 rc
now we'll see if autokiller works stable ^^
edit: realized that with cm7 something seemed to be wrong with the sd-card, so don't forget to compare the single-scores
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'm sure Rusty knows what he is talking about. Thing is, this talk about "the more free ram the better" has been repeated so many times, and at the end of the day, it seems to be more about user preference.
The default LG ROM seems to allow tasks to run in the background until it reaches around 50MB free RAM, then it starts to close tasks one by one. For multi-taskers like me, this is fine, I love how I can switch between facebook, tweetdeck, miren browser, google+, gmail, and messaging without seeing the apps reload.
For some, they'd want to open a task, close it, and move on to another without looking back. I guess that is where the 100MB of RAM is good for.
If you guys will be looking at benchmarks, I can guarantee that you will have higher scores with RAM optimizers. As benchmarks do not test multitasking, they simply check the performance of your phone at that point in time. (Which is also why some modders pump up their CPU freq to insane values before doing their bench then posting it.)
I have nothing against AKMO, and I find it very effective for Froyo builds. But I would recommend that each user try it out themselves. It's not a "1 fix for all" thing.
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
kiljacken said:
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
Click to expand...
Click to collapse
Does O2X already support swap space in EXT? (Or are your referring to VM heap?)
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
akyp said:
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
Click to expand...
Click to collapse
Yeah, FR19 is one of the more stable ROMs out there. Try full wipe then reflash maybe.
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
no one is using any app. to stop unnecessary start up of tasks
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Ditto on Autostarts. Also, Autokiller Memory Optimzer works really well, it doesn't kill tasks itself, it tweaks the Android function thar does it to work better.
auto killer mem optimizer workd well for me.but now i simply don use any of those batt saving app,mem apps etc i jus kill apps in inbuilt task killer...iam using my phone to the peek cause at the end ill b getting a 2ghz dual core by selling sgs.......cant stick to old things lol........cheeerz
tarunagg said:
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
Click to expand...
Click to collapse
... what?
Do any of you even understand how Android works?
so mind sharing ur exp wiv us on how it works???
manosv said:
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
+1 Autostarts. It amazes me what runs on the phone after start-up, after you switch states or update apps. The perfect cure for batt draining nonsense
rocky23 said:
so mind sharing ur exp wiv us on how it works???
Click to expand...
Click to collapse
Google it. Android is Linux based. Its memory management is not the same as Windows. I'd explain further, but you're the 4,753,857,195 person to ask.
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Shanakin said:
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Click to expand...
Click to collapse
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
webwude said:
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
Click to expand...
Click to collapse
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
upichie said:
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
Click to expand...
Click to collapse
Well actually I don't see the point that an app, that I hardly use once per month should be loaded everytime I start the phone or change my internet connection. Also more apps at startup increase the time when the phone is available...
But on the other hand, you are certainly right, after a while, only the latest apps are still in background / memory. What I have recognized nevertheless: if you use a lot of apps with push functionality and load on startup, the phone runs out of memory...
Kind regards,
ww
Good day!
Im new to xda-developers forum, just found a link in youtube while watching some stuff about galaxy note.
I have not discovered my galaxy note thoroughly yet coz its still new to me. Just wondering, the usage of memory without running any apps will go about 60%-70% percent. My temporary solution for this is to run task application and kill all exciting apps. Just wanna ask what kind of problem this may be?
No need to get alarmed by that. That's the way Android runs: it keeps apps in cache, so you can access them faster. When there's too much of them cached, the system kills off some apps.
chasmodo said:
No need to get alarmed by that. That's the way Android runs: it keeps apps in cache, so you can access them faster. When there's too much of them cached, the system kills off some apps.
Click to expand...
Click to collapse
thank you for your reply.
in this case, i cannot access on other apps that i'll run. just manually kill all the apps every-now-and-then.
Just remember: free memory is wasted memory. This is true for almost every piece of computing machinery out there.
inkanyamba said:
Just remember: free memory is wasted memory. This is true for almost every piece of computing machinery out there.
Click to expand...
Click to collapse
Thank you.
the only thing is, when i access on other apps like games. loading on the apps takes longer or even it crashes. maybe its because of the memory allocation of the apps or just there is no enough memory space to allocate the app.
JoshuaTumanda said:
Thank you.
the only thing is, when i access on other apps like games. loading on the apps takes longer or even it crashes. maybe its because of the memory allocation of the apps or just there is no enough memory space to allocate the app.
Click to expand...
Click to collapse
While what the other member said is true, unused memory is wasted memory, but the issue is exactly that. Android ends apps that you may be running to be able to open more apps, which I find bad.
While it is normal to find the amount of ram you have said already loaded and being used, I still don't like it.
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
But still, I hope ICS fixes this issue. I don't need 200 of the 1 gig of ram in use, what I would like is to have 300 or so free to be able to multitask normally.
zkyevolved said:
While what the other member said is true, unused memory is wasted memory, but the issue is exactly that. Android ends apps that you may be running to be able to open more apps, which I find bad.
While it is normal to find the amount of ram you have said already loaded and being used, I still don't like it.
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
But still, I hope ICS fixes this issue. I don't need 200 of the 1 gig of ram in use, what I would like is to have 300 or so free to be able to multitask normally.
Click to expand...
Click to collapse
Thats exactly my point. Thank you!
zkyevolved said:
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
Click to expand...
Click to collapse
can you please elaborate on the workarounds so that Android doesn't kill the background apps especially opera mobile