Well as the title says
I first had a stock s2 and the memory usage would always be 700+
In the task manager and it would close 28 apps and go down but always after doing stuff its back to 700+
Now i rooted the phone and deleted all apps i did not use like google+ chaton and all the stock samsung stuff thinking it would improve but it wont
Does anyone have any clue either how to stop these 28 things from running or all the time or see wat they actually are
Any help or tips appreciated
Gr.
Boss
Sent from my GT-I9100 using xda premium
The short version re: Android & memory is - as Android is a Linux 'variant', and Linux variants don't like 'free memory', Android will reserve as much free memory as possible in order to make it immediately available when required (so there's no killing some processes in order to run other processes for example), it will also keep memory in reserve for apps you've recently closed/apps that are used a lot even after you close them in order to start them more quickly/get them up to speed when you do want to use them
Constantly manually 'freeing up' memory will actually make your phone less responsive.
In other words, let Android do its thing. People on here/elsewhere obsess about free memory because they're used to Windoze & even other phones/OS's.
This is the 'plain language' explanation, if you want the technicals, they're easily found online.
Edit - This is also a good explanation of how/why it works.
Thanks wasnt aware of the ram thing like this bit it sounds logic
But why are there 28things running ?
Makes nu sense to me
Sent from my GT-I9100 using xda premium
Depends what those 28 process are.
With all operating systems, there's a lot of system processes running at any given time, Android is no exception to this.
You should never need to 'free up memory', and the only time you should need to manually close an app (with a task killer or similar) is if it's badly coded & doesn't exit 'gracefully' (99% of apps do these days).
What is a program u can advice me to use to check what is running (free app) preffered
Thanks
Sent from my GT-I9100 using xda premium
Internal config option
KooolaNL said:
What is a program u can advice me to use to check what is running (free app) preffered
Thanks
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
You don't need any app to see what is running; go to Settings / Applications and choose "Running" tab. It will show you the processes and services that are currently in use. Depending on the version of your Android, you will have an additional option already visible at bottom or available via menu: "show cache processes"; these are the processes for which Android reserved some memory in order to quickly re-execute them (like MistahBungle explained above.
Regards.
Related
The apps should present the battery consumption of each application particularly those connected to the internet. After I kill apps which I choose from the list ( like skype, viber, fring, whether , mail and else , it's could not wake up anymore . Until I run it manually .
Sent from my Dell Streak using XDA App
I believe having a task killer on the device is a Bad Thing™ since memory management is conducted very efficiently by the Android OS itself. However, if you feel you absolutely MUST have a task killer, there are a lot of them in the market. Don't take my word on it though. Here's some reading material for you to peruse.
Android Forums - What Is The Best Task Manager?
Why You Shouldn't Be Using A Task Killer With Android
Back when I use to use them the best apps for what you ate looking for ate two that can work with each othet made by the same developer.... autorun manager and autokiller memory optimizer... and they have the setting you want, to not allow the app to restart... but be warned... you can terribly frag your system if you don't know what you're doing or if you get trigger happy with the settings
What about apps that present the memory usage of each running apps or process
Sent from my Dell Streak using XDA App
joelk said:
What about apps that present the memory usage of each running apps or process
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
AutoKiller Memory Optimizer will do what you want in that case
I have kinda nooby question... i am using a phone with stock gingerbread and i am using an advanced task killer. I know a lot of people say that I shouldn't do it, but it just makes my phone a lot faster and smoother. As a noob, i have one question: is task killer really harmful to my phone and is it better for me to not use it? If you say yes, please provide me some specific reason why. Thank you ask much guys!
Sent from my Nexus S using XDA App
its not that bad... but u should not kill background services!
keep settings on safe... don't use aggressive mode
applications u know u use often for example- browser or music player... u can add to excluded section... currently im using ZDBox and it works perfect... it also has additional features that you will need... hope this helps
I only use the ATK to kill an app that's not responding well.
For example, when I was using CM7, sometimes my Google Reader app would hang and display a loading symbol for a long time instead of displaying my articles, and the arrow that shows transmission over the network wasn't displaying so I knew it wasn't waiting on data, I would use ATK to kill ONLY Google Reader. Then I could go back into the app and it would load very quickly.
But since I switched to an ICS ROM, I haven't had that same issue and haven't had a need for ATK.
Also, do note that it does take processing power, and therefore battery power, when your phone decides to restart any of those apps you are killing, and it will restart apps.
For a great explanatory article, see here:
http://androidandme.com/2011/11/app...lers-still-dont-give-you-better-battery-life/
and also the links in the phrase "(see here, and here, and here)".
So in short, they are not exactly "harmful" but they don't provide any real benefit if you "kill everything, every time."
It is a common myth that more RAM = better performance, and this is a result of the market being dominated by Microsoft for so long. Android does not equal a desktop OS. Free RAM literally does nothing. In fact, it is wasteful to have bunch of free RAM. Android manages RAM very effectively and aggressively works to ensure that you have sufficient resources to do whatever it is you want to do. If you notice an increase in performance with a task killer, it is because you have a misbehaving app. Watchdog is the only task manager I would recommend, all it does is watch for apps that are using an abnormal amount of resources and alerts you. Part of the Android experience is the emulated multi-tasking, or having several apps saved to memory simultaneously to facilitate ease of switching between them. An app in the background will not affect the performance of your device, it is not using any resources. Aside from that, if you end a task, it will usually just start right up again, using more resources, because that is how Android is designed to work.
So, I would say finding the misbehaving app is a much better option than a task killer. They were important in eclair, maybe even FroYo. But anything above that they are unnecessary.
i dont really believe in android"s app managmentbut task killers make it only worst IMHO
I have to agree with member devator22.
Android is not Windows. Android is basically Linux and Linux is using a different memory management than Windows does. (Although Windows has got a lot of improvements during the last years)
RAM which isn't used, is wasted! That's a fact.
So, if you run a specific application, some of its data my be cached. Linux is reporting this as "buffered" (you can see the amount by running the 'top' command)
There might be a more or less big chance to hit this cache. If so, the data is loaded much faster ( definetly > 10 ) than if it had to be requested from the file system.
By killing your application by a task manger you are releasing this buffered resources (actually you are forcing the OS to release it). In the worst case you are wasting your advantage of loading already cached data from the RAM. In the best case you are gaining nothing because your device has to load it from the file system anyway.
(sorry for my english )
Get watchdog!
/end
*just because nobody understands you, doesn't make you an artist..
Thank you so much for these replies! I really appreciate it! I decided to keep my task killer but not use it aggressively. I probably will use it to end apps that i really find it pointless. And also to the people who said android dies it's own task managing, you're right but wrong at the same time. When i didn't use my task killer, android did killed some apps in in order to launch more apps, but it left only like 10mb of 300mb, which i found little odd and also it mainly killed launchers which was very annoying.
Sent from my Nexus S using XDA App
Task killer will speed up your phone if you know what you're doing. Only kill tasks that you are familiar with...e.g. apps that you know you have launched and won't be using anymore. Those apps running in the background can slow down your device.
If I'm on ICS, its better to use the bult-in task killer, or download one from the market?
Guys, he's not saying he does it for the memory. He says the phone's smoother. I don't know whether this is true, but if there are background tasks performing operations that he doesn't want them to do, it's *absolutely appropriate* to kill them.
The flip side of that is that the applications will eventually be automatically started again, and that startup takes extra CPU time. As long as the process startup and process killing happens when the screen is off, I would think this could improve the responsiveness.
But I think on most people's phones, the background processes really don't use a lot of CPU...
I know by default even Gbs memory management isn't the best. The app priorities are a bit weird aand the launcher gets killed to easily. Running the v6 supercharger scripts and making the launcher hard to kill and fixing the priorities and changing the oom settings makes any from wicked fast
Sent from my PG86100 using xda premium
I am not rooted, so I can't do anything that involves rooting.
Sent from my Nexus S using XDA App
Instead of killing an app over and over again install something like Gemini App Manager and disable the app's autostart permissions. For example, dropbox and dropbox sync are set to automatically start at boot or when there's a connectivity change. I understand why they're set to do that but for my purposes I only needed them to start when I actually used them.
Having said that, I no longer use Gemini and have never used an automatic task killer. I think android (ICS) does a good enough job managing it's memory that I don't need to be anal about micromanaging it myself. I think it also helps that I'm not an appaholic. I'm very picky about what I install and will only keep an app installed if I regularly use it.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Jinx Lumos Joke said:
If I'm on ICS, its better to use the bult-in task killer, or download one from the market?
Click to expand...
Click to collapse
Built-In is much better
im on ics on my captivate and it runs beyond smooth
like stated before having free RAM with not do anything
android has a good way of muti tasking
I am using Android 2.3.6 stock rom. My phone becomes very slow every 2-3 mins. When i open a task killer it shows 44mb-51mb ram. I have to clear all the apps and still it would show me 65mb-70nb ram. Phone gets ridiculously slow. Please help me with the solution.
Tusharkamath said:
I am using Android 2.3.6 stock rom. My phone becomes very slow every 2-3 mins. When i open a task killer it shows 44mb-51mb ram. I have to clear all the apps and still it would show me 65mb-70nb ram. Phone gets ridiculously slow. Please help me with the solution.
Click to expand...
Click to collapse
-go back to froyo
-or buy a new phone
Sent from my GT-S5830 using xda premium
Any better Solution?
Delete useless apps that use RAM unnecessarily...
Prawesome said:
Delete useless apps that use RAM unnecessarily...
Click to expand...
Click to collapse
Yea, like Samsung Apps, such a memory hog -.-
Sent from my GT-S5830 using Tapatalk
use another task killer, or stop some services from settings->applications->running apps->from there, stop some apps you think uses your phone's memory too much.
other thing, remove any apps that uses data transfer or any background services.
First stop DATA then u need to stop some APPS like Samsung APPs. The way ur telling invokes that ur in STOCk
try to install custom ROM.
or delete some useless app.
Delete bloatware apps.
Sent From My SGA via Xda Premium App
i have found a thread
http://forum.xda-developers.com/showthread.php?p=18561098
reflash n try a custom rom
Are you using the stock task manager, or some app from the market (play)? If you're using an app, then begin by deleting that app. They do nothing good for your phone, quite the opposite in fact. As long as there is free ram left, then the ram is not to blame. And android should free the ram on it's own, so basically you shouldn't even need to free the ram by yourself.
If that is not the reason, then it is some app you have installed, which keeps running on the background and needlessly uses resources. The ace runs fine, even on stock rom. And that means that, either you or some app, is doing something wrong...
Hi.
First: I haven't found a thread which is only meant for my problem.
So: As written above, I'm on XXDLIB, but this behaviour is there in earlier JB releases, too (all WanamLite).
When I minimize an app (means: press home button in an app) it won't stay there long. It will be closed after a (volatile) period of time.
Example: I'm navigating and want to read something in (stock) browser. I read and minimize this app too.
I'll go back to navigation.
Afterwards I want to read my opened page (which should be in browser) and waht happens: the browser reloads the page and hasn't been listed in task manager (hold home button, left side).
So it has been closed.
First i thought that this is a out of memory issue. So I removed many apps that I don't need from /system/app and observed the memory usage then.
Same scenario as mentioned above: Navigation (Navigon) is opened, I open the browser, finish my navigation... and .. the browser is closed again.
This is vice versa: when I minimize my navigon app and use the browser for.... let's say 3 to 4 minutes the app will be closed.
Then I got deeper into it. I opened FM radio, browser, WhatsApp and evernote and minimized them, before I slept. No app with that great memory usage I would say.
But at morning ALL apps are closed.
For short: I HATE it. When I want to have my browser opened, it should be opened until I want to close it.
Sometimes I minimize my navigon app and I only need audio orders... unusable now, because the app closes very fast...
Same for browser: It eats my monthly provided data, because it reloads the last viewed page (its not reloaded from cache; with flight mode enabled there is only an error page).
It's no memory issue I would say. After opening all these mentioned apps I have more than 230 MB of free ram.
I know that wanam adds a modified services.jar with some kind of 'memory optimization script/code' from XDA devs.
But as far as I understand it, it should not lead to any closed apps.
As far as I can see, this problem is 'new' since JB (AOS 4.1.1).
In 4.0.4 it hasn't been there.
Anyone with the same problem?
Stock or mod?
Any suggestions?
I'm missing my S2... never had this kind of problems there...
Greetings,
Mario
EDIT: I'm using the newest apex launcher (free). I don't know if this could be important.
The issues you describing are present big time in ICS also. That's what I hate this phone.
I don't even think this is a Galaxy S III issue. It seems to be more of an issue with Android itself. I've noticed things like this with the pure stock android Galaxy Nexus and even on the US Galaxy S III which has a total of 1.6gb of ram available.
Mine keeps it in memory and when I return to it is still there as I left not re-started. In fact I just opened xda app after not using all day today but using many other apps it was still on the last thread I was reading. I'm running stock but rooted.
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
I have also realised this problem as someone who comes from Samsung Galaxy S 2. Now I am on Omega Rom v27 and use hard swap, I should not be having this problem but no, I see that many apps are closed by system although I have huge ram available after some time. There must be a way to deal with it; I play with auto memory kill settings but have not seen a difference so far.
Regards
GT-I9300 cihazımdan Tapatalk 2 ile gönderildi
This is an Android issue even with GB, if the phone runs out of memory for the foreground process, it closes other processes in order to free up memory. However, what you're talking about (web browsing) if you're using Chrome I believe this is a chrome thing (does the page get greyed out?) Happens to me even if I leave the page on. For example:
Browsing, put phone aside, the phone automatically locks, as I unlock it does that. Doesn't bother me much though, as long as the page loads again normally. I haven't had any issue with the S3 concerning closing other applications for the foreground one.
d4fseeker said:
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
Click to expand...
Click to collapse
Thanks. I will have a look - but I would say, its now memory issue, because of the free ram that is left.
Heapsize is at 128 MB, heapgrowlimit too. I played around with these values. Nothing helped.
I'll give a report tomorrow.
EDIT: On stock the heapsize is 256m. Why should someone *lower* this value, like wanam?
Any idea? I'm no programmer...
Removing the bloat helped here a lot and that change in the build.prop from 256 to 128m.
Delete kiesexe from system/bin if you don't use kies. Freeze all the Samsung applications and services. Finally don't use Supercharger.
Swyped on I9300 - XXDLIB - Siyah kernel - JKay & Thunderbolt tweaks.
To me, it happens randomly. Sometimes the browser just show the same page without reload even after a few days! But sometimes it just reload after receiving a call!!!
Is not big problem on a daily usage but is very very big problem when I'm downloading something and have to worry about incoming call.
Sent from my GT-I9300 using xda app-developers app
hey guys, it makes me miss my little "Eclair" or "Froyo" phone...
a phone with this huge capabilities can't have this type of issue...
im getting this issue when im playing and need to change a track in song player...
then it always restart the game and it sucksssssssssssssss!!!!! ;/
So, thank you all.
I increased heapsize to 276. Now the apps are hold longer in memory.
I observed something strange: When I use flight mode, apps are closed too... but thats ok.
im playing Football Manager Handheld
and it closes everytime too...
cant handle this!!!!
i want a phone that does the things correctly.....so sad!!
Ya this is really sad!!
We keep on saying how Android does true multitasking and all, but at the end of the day it's not getting done what we want to.
I was downloading Shadowgun the other night, and after about 50%, I got a msg so I pressed home button to go to the Msg app and then:
1) Home Redraw ..grrrrrrrrrrrr.
2) I replied back to text and opened the Shadogun from Recent Apps and the downloading had stopped.
Had to start it again.
WTF??
Why does android not kill the other useless cached things which is taking upto 300-400 mb ram.
Why does it have to kill Launcher and the latest foreground operation??? The worst kind of management ever!!
Why doesn't it kill Maps instead of Launcher. I've not touched maps in two days and it takes about same ram as my Launcher does??
It has got the sorting all wrong...I hate it...
I don't know how it is in iOS, but it couldn't be worse
d4fseeker said:
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
Click to expand...
Click to collapse
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
To fix launcher redraws, change it's OOM value. Supercharger V6 can help with that. Also debloated ROMs help a lot
j0ep0 said:
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
To fix launcher redraws, change it's OOM value. Supercharger V6 can help with that. Also debloated ROMs help a lot
Click to expand...
Click to collapse
This is where Apple wins and Samsung fails.
So much just to make your phone smoothly, something Samsung should have done and not the user.
j0ep0 said:
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
this settings will solve the problem????
if so, how to set up?????
Click to expand...
Click to collapse
I recently installed a Rom and the ram is consistently at 700mb can anyone advise me on how to lower this say yo 500 - 600mb.
Also is there a app or task manager that will allow me to decide what apps I want to stay open and what ones close after a pre defined time. Dont know if im thinking ahead with this app
Sent from my GT-I9300 using xda app-developers app
V6 supercharge and greenify, Google these
Actually it doesn't really matter about RAM...
Sent from my GT-I9300 using xda premium
Thanks
I gave greenify a go looks pretty promising, once I actually get the hang of it
Sent from my GT-I9300 using xda app-developers app
Are you managing app auto starts? If not get LBE Security Master and set which apps you want to start up after booting. That will save you some RAM.
m0cha5hake said:
Are you managing app auto starts? If not get LBE Security Master and set which apps you want to start up after booting. That will save you some RAM.
Click to expand...
Click to collapse
actually i have been using LEB for a year or so, and only use it as bandwidth monitor ... that function about disable autostart seems is not very working well because my RAM always got over 700+ MB.
but anyway , consider the Android's RAM management which is quite different to Windows , so i am fine with that ...
just my music player get killed frequently which is very annoying !!!
jcurran.jc said:
I recently installed a Rom and the ram is consistently at 700mb can anyone advise me on how to lower this say yo 500 - 600mb.
Also is there a app or task manager that will allow me to decide what apps I want to stay open and what ones close after a pre defined time. Dont know if im thinking ahead with this app
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Freeze some things with titanium backup. Greenify apps you don't need running in the background. I normally always have around 180mb of ram free with widgets on the homescreen, messaging and exdialer in memory, whatsapp, headset manager, google services, quickpic, Facebook notifications etc. Personally not a fan of Swap/ZRam/Supercharger. My best experience has easily been running stock or WanamLite with no tweaks/build.prop edits other than Jkay Deluxe. Also, Perseus kernel has some ram modifications in the kernel so you get an extra 20mb or so of ram
Still do not understand why people want more free RAM; free RAM is doing nothing, while RAM that is being used is caching apps in memory so it can be loaded faster, making a more responsive system. Please research. With that being said, too much RAM usage is not good; about 5% (45mbs on our GS3) should always be left idle.
qtwrk said:
actually i have been using LEB for a year or so, and only use it as bandwidth monitor ... that function about disable autostart seems is not very working well because my RAM always got over 700+ MB.
but anyway , consider the Android's RAM management which is quite different to Windows , so i am fine with that ...
just my music player get killed frequently which is very annoying !!!
Click to expand...
Click to collapse
If you want more ram then you must setup which apps can launch in the background after startup. These are the apps that eat ram because they begin running by themselves and continue running even if you never use them. Of the 80+ plus apps that I have only 4 of them are allowed to startup on boot.