Related
I notice the phone start lagging when there are less than 100Meg of available RAM on both 2.1 or 2.2 SGS.
Questions....
1. How do i make sure there will always be min 130 available when not in use?
I'm currently using Froyo Task Manager, ATK and SystemPanel together to make that happen manually. A better suggestion or use of them will be appreciated.
I also tried MemoryPlus and Taskkiller (The red android logo)
2. There are so many background service running some of them start with com.samsung.... (what are these?) do we need them?
3. Why some Apps always run without us telling them to run, or ask us to give them to permission to run on background at will?
ATK
In ATK in settings you have auto kill level, which is disabled on default.
jakaka said:
In ATK in settings you have auto kill level, which is disabled on default.
Click to expand...
Click to collapse
I'm using JPC, ATK autokill will not able to kill at a system level like SystemPanel, so after a day of active use, the memory will still continue to reduce as some of the background service start consuming more and more memory or run more background process. E.g. Touchwiz from 17 Meg to 25 Meg.
So at the start with ATK, i will have 130Meg, after a day of active use i left with 80Meg. With Apps killed.
I use autokiller set to aggressive. memory left 152mb
ivanchin99 said:
I use autokiller set to aggressive. memory left 152mb
Click to expand...
Click to collapse
Cool, does that remain for few days? How often do you restart your phone?
free memory is bad memory!
why don't let android do it's job?! this ist linux with a clever memory management, not windows 95!!! deinstall all auto task killer android is handling the memory very well. it uses all it can get and if it's not enough it kills old uses apps from it. why have free memory, there is absolutely no reson for that! ram is fast, let the often used apps be there not on slow sd or nand!
Mykron said:
free memory is bad memory!
why don't let android do it's job?! this ist linux with a clever memory management, not windows 95!!! deinstall all auto task killer android is handling the memory very well. it uses all it can get and if it's not enough it kills old uses apps from it. why have free memory, there is absolutely no reson for that! ram is fast, let the often used apps be there not on slow sd or nand!
Click to expand...
Click to collapse
QFT!
What is the point of having memory if it is constantly empty?
Think about it this way...If you had five friends at your house and you have five chairs, do you make 2 or 3 of your friends stand so there is always empty space or do you let everyone sit down and worry about something worthwhile?
Finguz said:
QFT!
What is the point of having memory if it is constantly empty?
Think about it this way...If you had five friends at your house and you have five chairs, do you make 2 or 3 of your friends stand so there is always empty space or do you let everyone sit down and worry about something worthwhile?
Click to expand...
Click to collapse
True, upto a certain point... I don't think you need to have at least 100 or 150 mb free but it DOES seem to help to not let it get down to like 30mb...
For me:
-JM7
-animations off
-voodoo lag fix
-minfree manager set to preset agressive.
minfree manager customizes the android memory management system.
I love it this way, No lags when starting the Phone (DIALER) or anything else. The dialer annoys me the must, this must be lag free, if i want to dial i want to dial right away.
Btw, I think you have made some wrong assumptions about the Android memory management system, as mentioned, unused ram is wasted ram.
dagrim1 said:
True, upto a certain point... I don't think you need to have at least 100 or 150 mb free but it DOES seem to help to not let it get down to like 30mb...
Click to expand...
Click to collapse
Agreed but I have never seen my Galaxy with free memory that low and I don't use a task killer. Of course I don't often have more than 3 or 4 apps running at the same time
This is not about letting ram do nothing.you surely don't wasn't your ram get used up by programs you don't want while you had no hand in this.All those services running I don't want.badly written programs that are hanging out in memory instead of closing.at least in symbian an app closed when you exited.
Why would you have 100MB free ? Do you have any application that needs 100MB to run ?! The android system already has enough memory to run so even if you could have 200MB of free memory you phone wouldn't run any faster you would just be able to lauch around 20 apps at the same time.
Read this:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Linux however isn’t generally affected by this. While I admit that I don’t know the architecture and reason for this… linux will run the same regardless of if you have 20mb free memory or 200mb.
Click to expand...
Click to collapse
Finguz said:
Agreed but I have never seen my Galaxy with free memory that low and I don't use a task killer. Of course I don't often have more than 3 or 4 apps running at the same time
Click to expand...
Click to collapse
Dunno, I just noticed that one time my phone was VERY sluggish and memory free was around 20mb or so. Cleaning it up did seem to help (unless one of the programs killed was causing the lag of course).
Ah well... Whatever people choose right?
You guys can argue all you want that free RAM is a waste of RAM....
But it is a fact that the SGS runs much slower when the free RAM is low. This is the experience of all the SGS'es I have tried and my own as well. At least this is the case when running 2.1. I have not tested anyone with 2.2 yet.
It s starts to lag when memory is below 40 mb. So when it s low and you start an application it starts to lag. I set it to 50-55-60 and got hardly any lag. No need to keep so much free ram
Sent from my GT-I9000 using XDA App
matty___ said:
It s starts to lag when memory is below 40 mb. So when it s low and you start an application it starts to lag. I set it to 50-55-60 and got hardly any lag. No need to keep so much free ram
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Which ROM are you using? as the low memory killer level for background apps is set at 40M which means you should have 40M free all the time or it will start killing background apps. This is also why task killers are useless, free ram is wasted ram for android.
I never had the experience that more free RAM is faster, perhaps with the stock rom but JC and upwards are all good by default. Animations off + Oneclick lagfix (or another) and the phone stays totally lag free.
Being an android user for 1,5 years now i'm very confident Taskkillers are useless except when an app is stuck. I've had periods where I used them allot but the phone only gets slower as the killed apps have to be loaded into the memory again.
Finguz said:
QFT!
What is the point of having memory if it is constantly empty?
Think about it this way...If you had five friends at your house and you have five chairs, do you make 2 or 3 of your friends stand so there is always empty space or do you let everyone sit down and worry about something worthwhile?
Click to expand...
Click to collapse
Provided you are not expecting anymore friends. The problem happens if all your 5 friends are happily seated and along comes 2 more friends a-visiting. So you have to now move 2 inactive (for want of a better word) friends out of the seats so that you can accommodate the 2 new ones. This takes time. So why not move these friends out as soon as they become inactive so that the space is readily available when someone comes calling?
Try to have a read about garbage collector before argueing about free memory.
The more you try to have a large amount of memory, the more you will need major GC (and during major GC all activity is frozen).
If you let the system manage memory, it does minor GC as needed when it reaches min memory waterline (seems to be 50Mo on SGS).
Let the system do its job.
Get rid of task killer.
Mykron said:
free memory is bad memory!
why don't let android do it's job?! this ist linux with a clever memory management, not windows 95!!! deinstall all auto task killer android is handling the memory very well. it uses all it can get and if it's not enough it kills old uses apps from it. why have free memory, there is absolutely no reason for that! ram is fast, let the often used apps be there not on slow sd or nand!
Click to expand...
Click to collapse
I completely disagree. OK, it is better to use memory, but the android memory management is extremely inefficient since it does not know which foreground and background processes are important to the user and which are not, even though it tries to figure that out. Since the Galaxy S does not allow the system to use the full 512MB of memory, this can be a critical factor. And the Galaxy S definitely lags massively when less then 70 or so MB of free RAM is available this is definitely a fact.
The biggest problem is that you cannot manually close apps and only have multitasking access to the last 6 apps used. If you use 7 apps simultaneously, the 1st app still consumes memory but you cannot even switch back to it. And there are so many useless background processes, starting up over and over again and consuming hundreds of MB memory if they are not killed in regular fashion.
Who needs gesture search, amazon mp3, layar, and all the samsung crap running in the background all the time. If you only have 10 such applications and each of them only consumes 15MB of ram, 150MB are wasted for nothing.
Every second market application registers itself as autostart on every boot, so to use a autostart manager is also mandatory.
Since everybody can easily develop for Android the application quality and resource efficiency is not always perfect. So in my opinion Android needs a task manager, this is why even Samsung integrates such a application.
Using a well configured ATK (set to ignore system applications, widgets and apps frequently used for multitasking and killing every else on screen off) and autokiller (strict setting) in addition to Autostart Manager (had to remove 40!!! useless apps from automatic startup) and lagfix, the SGS runs perfectly smooth.
Hi Arc Users,
Do you guys encounter low memory after long period of usage? It seems like the memory does not free up after using the phone for a long time. I mainly use the phone for FB, Camera and messaging.
When the phone hits like 50+MB ram or so it starts to slow down and if it goes lower than 40MB my home screen starts to lag and the app icons take a few secs to load every time i return to home screen. I'll usually reboot the phone but its quite a pain considering the boot timing for my phone is rather long, like close to 1 min.
What are the possible solutions? I've heard that advanced task killers are unnecessary for Gingerbread. If thats the case, how do I free up more memory or have better memory management for the Arc?
Am a first time android user, appreciate any advice from you guys
Thanks!
___________________
+1
Root is the solution. Delete apps and services which you do not use.
I haven't any problem either when free ram goes down to 30MB and i don't use a taskiller.
Just what are you doing when you run out of ram? Never did I run out of ram yet. Running ram hungry games will free up more what is needed as I experienced. When I return to homescreen, it takes a while (around 2 secs) because it will free up ram from the game, then load the homescreen launcher from start/scratch.
Same here but my Arc works fine, even with 30-40MB RAM, so it isn't a real problem.
But it would be nice from SE to make 400-450MB of the 512MB RAM available for the user.
Sent from my LT15i using XDA Premium App
Flo95 said:
But it would be nice from SE to make 400-450MB of the 512MB RAM available for the user.
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
What? That is a completely pointless excercise if you understand how ram is handled by the os.
You need to root and remove bloat, check ya settings etc to get better performance. I found letting things constantly access the network was a juice eater, I don't want fb to check every 4 seconds, I update it when I want to read it lol
I use a task manager, but only because I like to see what is running and using resources. I rarely actually kill any apps, just occasionally a few things I rarely use. Even then it fills the space with other stuff.
:edit: sorry flo95, that sounded a bit crappy, no bad attitude was intended.
Sent from my LT15i using XDA App
This is the solution...https://market.android.com/details?id=com.lim.android.automemman&feature=search_result
not a task killer... a memory manager that enhances googles memory management.
mariolouis said:
Just what are you doing when you run out of ram? Never did I run out of ram yet. Running ram hungry games will free up more what is needed as I experienced. When I return to homescreen, it takes a while (around 2 secs) because it will free up ram from the game, then load the homescreen launcher from start/scratch.
Click to expand...
Click to collapse
I do not play games with my Arc. I just used facebook, MSN, Camera and messaging occasionally throughout the day. Medium usage.
It runs smoothly for several days but maybe after a week or two, the RAM starts to get low.
im_iceman said:
This is the solution...
not a task killer... a memory manager that enhances googles memory management.
Click to expand...
Click to collapse
Thanks! Working so far... will monitor after a week or so.
Try a cache cleaner also will free up some space for ya
Sent from my LT15i using XDA Premium App
I use battery guard as a task killer. It comes with a widget where you can see the available amount of ram.
I'm happy about it. Though a lot of people say a task killer doesn't help I have no negative experience using this one... and I never go below 130 ram.
I still think it does help to close tasks that otherwise keep running in the background... But I'm new on android so I could be wrong.
Hey guys
Have you tried this script
http://forum.xda-developers.com/showthread.php?t=1111145
maybe this can help w/o having to install apps or task-killers. Should work on Xperia Arc but I don't guarantee it.
That script seems to do basically the same thing as auto memory manager.. (per my previous post..)..
PS.. I currently have mine set to aggressive.
Hi all!
I have a LG G3
Android 4.4.2
Baseband MPSS.DI.2.0.1
Kernel 3.4.0
Build KVT49L.A1412000029
SW V10l-EUR-XX
I have a question about the management of the RAM.
I have installed Task killer and Startup auditor (I have no root).
When I start my device in the morning, tapping the task killer widget icon, I can see free RAM of about 800 Mb, sometimes 900-1000 Mb. During the day, especially in the evening, this quantity of memory goes down to 450-500 Mb. My question is: why???
It seems that the device is not able to kill apps once opened. But I have to note also that I use same apps in the morning and in the evening.
In my opinion it is really strange and, even if my device works properly, I am curious to understand if there is the possibility to make more free RAM in order to get fast responses.
One more thing: I have tried to change the runtime from Dalvik to ART and I have noted no particular increment in performances but a significant reduction of the battery life, which is really odd considering that many persons say that ART make the battery stronger!
Thank you for your opinions.
Use clean master
or go, very efficient. http://forum.xda-developers.com/showthread.php?t=2809443
make sure to thank him
Or don't bother. This is the way Android/Linux works. Unused RAM is wasted RAM.
Tapatalking from my LG G3
Oops.
---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------
patro23 said:
Hi all!
When I start my device in the morning, tapping the task killer widget icon, I can see free RAM of about 800 Mb, sometimes 900-1000 Mb. During the day, especially in the evening, this quantity of memory goes down to 450-500 Mb. My question is: why???
It seems that the device is not able to kill apps once opened. But I have to note also that I use same apps in the morning and in the evening.
In my opinion it is really strange and, even if my device works properly, I am curious to understand if there is the possibility to make more free RAM in order to get fast responses.
Click to expand...
Click to collapse
Android isn't Windows. Empty RAM is wasted RAM. Your apps won't run faster with more free RAM. Android keeps recently used, or frequently used, apps in RAM, but not running, so that when you access those apps again they start up much more rapidly. If you kill them, and then go to use them again, Android needs to copy them from ROM to RAM and restart them, which takes more time and uses more battery. Lots of free RAM will slow your device down, not speed it up,
Google has lots of highly paid, very experienced OS engineers. They know what they're doing. Let the OS do what it's designed to do. Using a task killer doesn't gain you anything, and may make things worse.
I can live with the Nexus 5X' relative sluggishness when compared to the Nexus 5, but what really stops me from doing my work is the phone killing apps when I switch between them.
Example: I may be filling out a form on a website in Firefox for Android. I need to look up a word in the dictionary, so I switch over to the dictionary and look up the word. When I switch back to Firefox, the application has obviously been killed, as it reloads the page.
Example2: I'm listening to the Audio version of the Economist via the Economist app. The speaker mentions a certain placename and I open the Google Maps app in order too find where it is on the map. Suddenly the audio will stop playing - the app has been killed.
The above gets considerably worse when switching between more than two apps and is really hindering my work and productivity.
Now this almost never happened on the Nexus 5, which also only had 2 GB of RAM. So is it the power saving feature of the Nexus 5X kicking in? Is there a way to stop it from happening?
Marshmallow simply has very bad RAM management from what I've seen. I used to have the Nexus 5 too and as you said, multitasking was a very good experience on it (especially on Kitkat). Google's OS takes more of the phone's resources after each update (with no major new features or improvements). Marshmallow looks exactly the same as Lollipop, except for the tiny feature of apps permissions, and the Now on tap that I barely use (same for Android pay which I'm sure most of Nexus 5x owners won't even be able to use it outside the US). So I still don't understand why they had to jump so fast to a new version of Android while Lollipop still had a ****load of bugs that need fixing, they could've worked more on Lollipop to perfect it first then give us Marshmallow after 2 years maybe, we're not in a hurry.. I just hope they don't stop again at Marshmallow 6.1/6.2 or something and introduce Android N *sigh*
Sounds like you have more user installed apps with constantly running background services installed that the phone can comfortably handle with 2GB memory.
Check the memory stats in Settings - if the average over all the time options is 1.6GB or above used then your phone is going to struggle and cached apps are going to be getting cleared out when switching regularly. Look down the list particulary for apps running close to 100% of the time with a big RAM fingerprint. Also check running services in developer settings to get an idea of what is running a service all of the time.
Once you've identified the worst offenders make that difficult decision - is the apps utility worth it for the impact on performance. Consider reporting the memory use to the developer, particularly if it's much lower after a reboot and increases over time. Plenty of playstore apps ship with clear memory leak issues.
Other than that the other option is reasonably regular reboots to keep the system fresh and clear out any memory leaks.
thanks for the suggestion. Well here's the top 5:
Android operating system 524 MB
Wechat 156 MB
Firefox 117 MB
System UI 105 MB
Android system 99 MB
Clearly it's mostly the system using all resources. Firefox and Wechat, sure, I find them rather essential to my life, but together they don't even use as much as the OS.
Thing is, I can't remember this happening on the Nexus 5.
Sounds like you may have some apps using up a lot of your memory. I haven't been seeing any redraws with my apps, even 24+ hours of sitting in the background. The other day I was switching between gaming, streaming a live sporting even, and text messaging and the phone didn't drop a beat despite the game alone using 600MB of RAM.
Are those the average RAM or peak?
that's what shows up when I get the details of the RAM usage through settings
still this never happened on the Nexus 5, at least I can't remember
Yeah, I have a hard time believing it's the apps. I never had this issue come up in my Moto X 2013 (also 2 GB of RAM) using the same apps. We're seriously talking about one app open, switching to another app. No reason switching back to the first app should have everything reload.
Unless by "some apps," you mean that they have somehow not been optimized for Marshmallow in some way or other. But the apps simply running a process? A smartly-made OS (Lollipop, KitKat) will know "Hey, we have to kill something to free up RAM? Why don't we kill an app that hasn't been used in a while?" and a less-smartly-made OS (perhaps Marshmallow...?) will think "Hey, we have to kill something to free up RAM... why don't we kill the app the user just used?"
And there are two figures there - average and peak - which are those?
If there are the averages rather than peak then both Firefox and Wechat have got a problem.
---------- Post added at 06:42 AM ---------- Previous post was at 06:34 AM ----------
Marshmallow and Lollipop low RAM behaviour is pretty much identical and quite aggressive (the OS tries to preserve quite a chunk of free memory which is uses on the sly as a display buffer), KitKat was less aggressive.
I don't have any problem multitasking on my Nexus5x, but then again for the apps I've got when I check the memory tab I'm normally averaging 1.2-1.4GB used and 400-600MB average memory free so there is plenty of space for the OS to gracefully cache and uncache processes. If the phone is normally running at 1.5GB-1.6GB used and 200-300MB then the LMK is going to be kicking in frequently. It kicks in at around 250MB free on a Nexus5x.
It was the default setting, i.e. average. HM ok good to know. It's happening quite often when listening to the Economist too. Which is really bull****, it should treat it as audio playing. Why would Android kill your music.
I agree music players don't get the priority they should, although that particular 'bug' at least gives a clear symptom that lack of free RAM is an issue, if not the cause of the issue e.g. the OS, to many running services from user apps, or a particular user app with memory leak issues.
I came to the Nexus5x from a 1GB Moto G where it was almost impossible to keep background music running in combination with navigation after Lollipop without uninstalling pretty much everything else user installed and have got used to monitoring the RAM footprint and behaviour of apps as a result.
I've suffered the problem once since I've had the Nexus5x and that was due to the music player (Soundcloud) being a memory hog (120MB+) with it's background music player service coupled with a memory leak in the driving app I was testing at the time - Automate - it was peaking at 460MB use.
I'm not so precious about what is installed now but anything that wants to run a constant service either has to be tiny when running that service or absolutely fundamental to my use of the device.
I find this to be the worst problem .We want to kill our apps like we are use to.Switching between email and chrome is horrible especially when you have to start your application all-over again (submission request) Hopefully some XDA member will figure out how to solve this issue. For now I am testing DEVELOPER OPTIONS allow running
apps in background ? Anyone know what the default value is??
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
For me, Pie has actually been the smoothest compared to DP2 though DP5. There's a similar thread already here:
https://forum.xda-developers.com/pixel-2-xl/how-to/phone-sluggish-time-t3826729
harryfornasier said:
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
I've been getting stutters too. Occasionally it will just catch up and lag.
Haven't noticed any stuttering, just seems smooth for my usage...
harryfornasier said:
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
Click to expand...
Click to collapse
There's micro stutters here and there but they're insignificant, I wouldn't call them slowdowns. Google really needs to up their ram for the next phone, the 4gb is starting to show it's limitations. Compared to the iPhone , the pixel doesn't seem very smooth with it's animations.
Actually my test shows after couple hours usage, the free RAM of Android P will drop around 600MB.
At this stage, you will start getting stutter or even no response from apps due to system try to release free RAM.
Right after boot up, Andrpod P will have around 1300MB free RAM, however after couple hours use (depends on how heavy you use your phone), the free RAM will go down to around 500MB and you will notice stutter if you launch some App which requires RAM.
You can verify this by launch Google Map, Google Photo and Street View together... or you could launch Camera App then take some panorama after a day's use. When fresh out of reboot, Pixel 2 XL has no trouble running those App together or handling multiple Panoramas but will run into stutter or even kill your Launcher for free RAM after couple hours useage...
I checked the OOM setting on "empty app" and it's defaulted at 318MB. I suggest raise it to 512MB to get better, longer stutter free operation (YMMV). With default OOM setting when I launch camera app, sometimes Nova Launcher will be killed for free RAM. However after modifing the empty app OOM limit to 512MB I seldom got any kill rampage when launching camera app.
For me, Android P is smooth when free RAM is over 900MB and you will definitely get into stutter when free RAM under 600MB. And it's unavoidable to went to this low ram stage after some use...
If you don't have above issue then lucky you, or you just didn't use your phone heavy enough as Google think you should... I don't want to argue how good Android can manage RAM since for me, kill my Launcher to make RAM for Camera is not a solution... Which happened to me quite often. I use Greenify to block most background app and do check what runs behind the scene quite regularly and kill those unwanted... Still, Android P will go to 600MB free RAM unless I modify OOM... (It's now aound 800MB when Nova Launcher is foreground App)
You can use this app for monitoring your free RAM.
https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicatorPro
lssong99 said:
Actually my test shows after couple hours usage, the free RAM of Android P will drop around 600MB.
At this stage, you will start getting stutter or even no response from apps due to system try to release free RAM.
Right after boot up, Andrpod P will have around 1300MB free RAM, however after couple hours use (depends on how heavy you use your phone), the free RAM will go down to around 500MB and you will notice stutter if you launch some App which requires RAM.
You can verify this by launch Google Map, Google Photo and Street View together... or you could launch Camera App then take some panorama after a day's use. When fresh out of reboot, Pixel 2 XL has no trouble running those App together or handling multiple Panoramas but will run into stutter or even kill your Launcher for free RAM after couple hours useage...
I checked the OOM setting on "empty app" and it's defaulted at 318MB. I suggest raise it to 512MB to get better, longer stutter free operation (YMMV). With default OOM setting when I launch camera app, sometimes Nova Launcher will be killed for free RAM. However after modifing the empty app OOM limit to 512MB I seldom got any kill rampage when launching camera app.
For me, Android P is smooth when free RAM is over 900MB and you will definitely get into stutter when free RAM under 600MB. And it's unavoidable to went to this low ram stage after some use...
If you don't have above issue then lucky you, or you just didn't use your phone heavy enough as Google think you should... I don't want to argue how good Android can manage RAM since for me, kill my Launcher to make RAM for Camera is not a solution... Which happened to me quite often. I use Greenify to block most background app and do check what runs behind the scene quite regularly and kill those unwanted... Still, Android P will go to 600MB free RAM unless I modify OOM... (It's now aound 800MB when Nova Launcher is foreground App)
You can use this app for monitoring your free RAM.
https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicatorPro
Click to expand...
Click to collapse
This is only valid for people who buy the phones direct from Google and are able to root. For those from Verizon, you are out of luck, as there's no way to mess with memory settings.
This post is one reason in won't buy from Verizon.
Sent from my [device_name] using XDA-Developers Legacy app