1) Is there any trick or settings to prevent selected apps services from running in background, prevent autostart? It's just waste of battery and Ram. (Check attached)
2) what is the difference between running services & cached services?
It's Android's RAM management. Cached services means whatever services you have used till now are stored in the RAM at whatever capacity the OS thinks it's available.
Running services means the services that are actually being used by the OS/apps currently.
Best not to touch that as Android does a good job of RAM management and the more you clear your recent apps/these cached services, the more redraws are made by the system /OS; eg. To start an app again which you were using a few moments ago but, you cleared it from recent apps (smaller difference magnitude) and cached services (bigger difference magnitude).
The redraws also uses more battery and power, ofc slightly.
And there is this adage that goes - Free RAM is wasted RAM, which I agree only slightly.
You can't prevent autostart in the stock ROM unless you are rooted. Atleast if I recall correctly, i used to cringe looking at the apps autostarting and running in the BG with it's services (obviously there ways around this).
So the whole thing that I mentioned (1st and 2nd para) kind of becomes pointless? as there ****ty apps like Facebook, for eg which keep running in the background, autostart, have so many bloody cached services like cancer which hogs the system resources. I disable these apps immediately when I am done using them.
Related
Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.
robnil said:
Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.
Click to expand...
Click to collapse
I haven't used it in a while, but "spare parts" in the marketplace tells you which apps are consuming your processor IIRC. This will obviously give you a temporary hit to your ability to load and run processes but will let you know more details about your phone that you don't already have and the battery use section of settings obviously only talks about what is using your battery but that isn't going to tell you the whole picture.
I am also someone who says you shouldn't use ATK, at least the way you do, but I have it installed and use it a bit differently. What I try to do is kill all tasks after I've used the marketplace or before I do anything intensive (gaming, GPS tracking) and I kill all apps including ATK. ATK will consume processor, battery and will free up memory which then Android uses to open more tasks you don't need (using processor and battery in the process -> repeat cycle). If you need to free up memory 1-5 times a day I think my way will save maybe 15-30% of your battery over a 24 hour period while costing you less than a minute of hassle (too much for some, sure). Again, I only kill after marketplace (because everything opens to check for updates, AFAIK) and before something that will use heavy memory and processor.
robnil said:
Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.
Click to expand...
Click to collapse
Forgot the first part of your question, forgive me. I believe, the reason for more apps causing more lag is at least 2 fold. There are more apps that can be opened when you have free memory (in the vicious cycle I described above). There is also something that might be a bit unique to our phone, and I've only recently read this, it's a bit of speculation so I'm not trying to pass it off as fact but I think it's likely to be knowledgeable on the issue, even if not completely correct. Samsung's internal storage method is an SD card, that allows extra apps to be written to the internal storage but comes with a trade off of lag due to a potential combination of:
slow random-access
bad partition
I think I'm missing an important reason, I'll try to look and edit.
When I initially got my SGS I loaded it with a heap of apps and suddenly noticed the lag and quick battery drain. Problem was I couldn't track down the culprit.
I recently reset my device and was a bit more organized with what I installed. One of the things I started doing was checking what services were being used in the process which you can find under the manage apps part of the system.
So while you can load apps and they may/may not be killed by android or a task killer, the services will always be running - taking up memory, sometimes cpu, network. Things like weather checking, news checking, even email sync are some examples. These services plus any apps you run are I think what starts the lag. You need to be aware of which apps are also run as services.
Yes, there are some bad apps (last Facebook version was found to be a heavy drain) but I think they tend to add up with all the other services running.
As for 'Aggressive' depends on the app killer but my understanding (with the one I use), is that there is a memory limit before the app is killed. Once the limit is reached on aggressive, it doesn't take much before memory is cleared.
One thing to install is SeePU as this gives an indication of CPU, memory and network on the top menu bar. This also helps when the system lags (usually CPU is high and memory is low) and helps to know when to clean (or what threshold to set).
Hope this helps.
Hi,
i just bought an Ideos x5 and it's great.
I've loaded most of the usuall stuff including task manager.
Now i found that on average my free memory when i'm not using so much apps is around 180(that's how much free RAM i have).
Is this normal..i mean...the thing says it has 512 mb of RAM.
Sorry for beeing a noob..
Van
its said 128MB go to the GPU, 32MB are used by android system, which leaves about 352MB (353MB as shown in Elixir) for application use..
and then those google apps (Maps, Search, Market, etc.) all take up RAM in the background, plus other background apps you have installed and widgets you have enabled..
on average i usually have around 80-120MB free RAM left.. and since android 2.2 is said to have a good task manager which frees up the RAM when needed, i dont think its a place to worry about..
As iamelton said, Android's in-built task managing system does a good job of managing what apps are using the processor, memory and battery. Task manager apps don't really do all that much useful, and can sometimes be counterproductive if you're trying to use them to save battery. Lifehacker has a really great article on this called Android Task Killers Explained: What They Do and Why You Shouldn’t Use Them (I can't link because I don't have enough posts, but the article's a search away and is really worth reading). It runs through why it's generally best to avoid task manager/killer apps, plus it also explains how Android uses RAM - in a similar way to Windows Vista/7 (basically to speed up launching or re-opening apps).
It's probably worth noting that Android already has a function to force stop apps. If you go to Settings > About phone > Battery use, you'll get a list of what's been using the battery since it was last unplugged. Some widgets like Switch Pro have shortcuts to Battery use. It's useful if you've got Maps or a launcher or a rogue app sucking up battery in the background. As a rough idea, you may have an issue if anything not a system process is using more than 10%.
If you do need to force close an app, Battery use is generally the best way to go about it.
thx to cyvros for ur mentioning of the good article..
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
its a good read indeed, and for this topics discussion, i think the following paragraph gives a very good view on androids ram usage:
The problem is that Android uses RAM differently than, say, Windows. On Android, having your RAM nearly full is a good thing. It means that when you relaunch an app you've previously opened, the app launches quickly and returns to its previous state. So while Android actually uses RAM efficiently, most users see that their RAM is full and assume that's what's slowing down their phone. In reality, your CPU—which is only used by apps that are actually active—is almost always the bottleneck.
Click to expand...
Click to collapse
Basically, I went into Settings>Apps>Running and realised I don't want Facebook in there ever unless I actually open the app. I opened the Facebook app Settings and disabled Notifications off. Also Messenger Location Services is off too. Each time I try and kill the process or reboot it comes back.
Things that load that I want to permanently disable unless I actually open the specific app:
Facebook
Maps
Google Play Store
I use Titanium to put a widget on my screen where I can freeze and unfreeze that app. I have done it with maps and some other programs that were aggressive in their communications. Unfreeze them, open and use, refreeze when done.
Thanks grubbster.
Any other options available to me?
Other than ignoring it, you can kill the app each time you close it. There's a developmental setting that shuts down the apps (not sure if it's in Cyanogenmod only or just stock) because it doesn't keep anything in the background. This would close ANY app that's not holding forground view however.
I'll just leave it as it is to be honest. Just thought there was a quick way of doing it similar to how the MSCONFIG utility operates in Windows.
MSCONFIG does that for startup, there are apps that block apps from starting up in android too but those apps need to be running as well which defeats the whole purpose of having plenty of RAM in the first place..
The whole point is Android manages the background apps just fine. Having 2GB of RAM but wanting 1.6GB to be free all the time (200MB used by GPU AFAIK so you are left with 1.8GB) is not the smartest way to manage apps. You want them snappy, in and out and done. Apps sitting in memory doesn't use more power because the RAM is active even as long as it's plugged into the the motherboard.
New owner of a Nexus 7 2013 here. Had it for a month or so now.
So the device came shipped with 4.3, I updated the device to 4.4.2 OTA. Weird thing is, everytime I "Force Close" an app from Settings, the RAM usage decreases, then it INCREASES!
Google Play Store (44mb), current RAM usage: 444mb
Force close Play Store, current RAM Usage: 400mb
*a couple of seconds later after display refresh*
current RAM Usage:480mb
This keeps going. No matter how many apps I force close, the RAM usage keeps increasing until the point where it reaches ~660-~700mb!
Is this normal? Does this happen to anybody else? Is there something wrong with the garbage collector? Also my RAM usage is in the 400mb range on startup and a LOT of apps run on startup which I need to force close manually (is it normal they run on startup?).
Thanks!
So memory usage is supposed to increase when you force close apps, so I take it this is usual for Android? But is there any explanation as to why ram usage increases instead of decreasing like on iOS? Is the garbage collection on this thing significantly different to conventional Linux kernels or for that matter Windows' variant too?
Sounds like a very stupid idea tbh
greatnoob said:
So memory usage is supposed to increase when you force close apps, so I take it this is usual for Android? But is there any explanation as to why ram usage increases instead of decreasing like on iOS? Is the garbage collection on this thing significantly different to conventional Linux kernels or for that matter Windows' variant too?
Sounds like a very stupid idea tbh
Click to expand...
Click to collapse
OK wrong forum this one is for the n7 2012 but your question is more to do with how android runs rather than specifically the nexus.
First of all forget everything you think you know about ram. In android the more ram being used the better the device will run. This is not always true but largely the more apps being held in ram the smoother android will run them. When an app closes it moves from running services to cached and the system will then call on that if you reopen the app or clear space if it needs it thus saving itself valuable power. The other reason for not force closing apps it they no longer run in the background as they were designed to. This is one reason task killers are bad for your system. If you close the mail app you won't get emails, if you close the clock your alarm won't go off, if you close the play store your apps won't update ect. Android is as far removed from windows as iOS is although windows 7 does use a similar idea towards ram. It doest need you to clear ram its perfectly capable of doing it itself. The exception to this is when you get badly designed apps that don't clear up after themselves and stay in the running services.
Try looking in your cached services you will probably find that's where your ram increase is. By force closing apps you make more work for the system reopening them.
Look here for more information about this
http://forum.xda-developers.com/showthread.php?t=904023
Sent from my C5303 using xda app-developers app
I'm finding the RAM management on the S8+ and probably therefore the S8 to be heavily throttled.
My device memory is split as:
4GB total:
System and apps: 2.8GB
Available: 600MB
Reserved: 639MB
The problem I am seeing is that I am never seeing memory consumption above 2.8GB so that the last 600MB is never touched whatever I open. This aggressive throttling is evident If switch between a mere 5 or 6 open apps, the first ones opened have been closed and have to completely re-open and re-load even though there is a is about a 600MB chunk of memory sitting around so this last 600MB is being totally wasted. This is validated when I go to the built in memory manager within Device maintenance and it only shows the last 3-4 apps opened as being active. Believe Samsung needs to adapt the memory management to be less aggressive here as it is impacting on multitasking quite severely.
Right now I have system and apps using 2.4gb., Available space 1gb, reserved 639mb.
I find that if you back out of an app by pressing back, it closes and you have to reload, such as facebook, messages, phone, gmail etc.
I find that if I use the home button to back out of apps they remain in memory. Apps like facebook have to resync when I go in but are still in memory.
What apps are you using to have them close on you?
Exynos or Snapdragon? Mine is UK Exynos maybe there is a difference.
I'm multitasking, so using the app switch button. I'm not backing out which closes apps. Processor is nothing to do with apps closing and I have Exynos. In my experiments I'm using the web browser, whatsapp, email, music player, maps and samsung health.
Hasn't it been like that for ages, Jonathan-H?
i can understand the op's point, especially if multitasking is needed, but the behavior described is actually a good thing for a phone. otherwise you can have too many apps eating up memory that you don't want. the phone doesn't know the user intends on multitasking back and forth. there was a time when there were pages of complaints about apps staying on after user moved on from it, so this is specifically something they would have designed for. there's no right answer here short of a full adaptable ai of some kind.
Unfortunately even Pixel is bad with RAM Management. Till now only Oneplus 3 and Xiaomi Mi5s Plus with 6 GB of RAM keep many apps in memory. I had an iPhone 7 Plus before S8 Plus and all the apps were in the same state like when I left them even after one day. So till now iOS is the fastest OS for me because it keeps apps in memory. Even Youtube stayed in Memory and on S8 Plus it reloads after one hour. I guess it's about keeping battery under control on S8 Plus and this is the reason. On the other hand, the first time launch of apps is faster on S8 Plus compared to iPhone. If somehow Android can keep apps in memory and also control the battery consumption, it can be perfect.
standard101 said:
i can understand the op's point, especially if multitasking is needed, but the behavior described is actually a good thing for a phone. otherwise you can have too many apps eating up memory that you don't want. the phone doesn't know the user intends on multitasking back and forth. there was a time when there were pages of complaints about apps staying on after user moved on from it, so this is specifically something they would have designed for. there's no right answer here short of a full adaptable ai of some kind.
Click to expand...
Click to collapse
If you never get to use the RAM you paid for then it is not a good thing. It's poor RAM management. We're not talking about it closing down apps once the RAM is even close to the limit, we're talking about it closing apps withing minutes and long before the last 20% of RAM is used up which is a sizeable chunk. And having RAM empty is old school thought which is now accepted to be bad practice and was just a benchmark used to see that your system was not being stressed. These days it's better to have as much in RAM as possible rather than waste it empty and have the system need to reload things.
standard101 said:
i can understand the op's point, especially if multitasking is needed, but the behavior described is actually a good thing for a phone. otherwise you can have too many apps eating up memory that you don't want. the phone doesn't know the user intends on multitasking back and forth. there was a time when there were pages of complaints about apps staying on after user moved on from it, so this is specifically something they would have designed for. there's no right answer here short of a full adaptable ai of some kind.
Click to expand...
Click to collapse
For serious multitaskers like me, it leads to the opposite problem: apps keep getting reloaded from scratch and that ruins battery life even more.
I'd like to add my voice into this. I am also a heavy multitasker. I have a set of standard 6-8 apps that constantly keep getting kicked out of memory and closed out of the carousel. It is not a RAM limitation issue as I am, like the OP, always below the limit. It just seems that Samsung made the memory management much too aggressive. I already set all possible options in the OS to control what is monitored and suspended and such, but this made no difference.
Same for me. At first reading this I though I posted this because of the exact numbers.
Jonathan-H said:
. Apps like facebook have to resync when I go in but are still in memory.
What apps are you using to have them close on you?
Exynos or Snapdragon? Mine is UK Exynos maybe there is a difference.
Click to expand...
Click to collapse
If it is 'forced' to refresh the displayed content it is not keeping it in memory.
You need to use a device where the issue is not exhibited to see how memory management should work.
Sadly my S8 Exynos can not keep more than half a dozen apps fully in the background without then forcing the content to reload/refresh when going back into those apps, from Facebook, YouTube, Photos, Gallery, newsstand, Play Music.
dhorgas said:
I'd like to add my voice into this. I am also a heavy multitasker. I have a set of standard 6-8 apps that constantly keep getting kicked out of memory and closed out of the carousel. It is not a RAM limitation issue as I am, like the OP, always below the limit. It just seems that Samsung made the memory management much too aggressive. I already set all possible options in the OS to control what is monitored and suspended and such, but this made no difference.
Click to expand...
Click to collapse
Exactly my issue and I have done likewise to no avail unfortunately.
Sent from my S8 using Tapatalk
The last update of the Gallery from Play Store made it start almost instantly. Maybe they need to put all the stock apps in Play Store so they start fast. About the difference between App refresh and App reload, it's totally different thing. We all agree with refresh and we don't like reload.
Android Doze
The problem is Android Doze, which freezes every app once it's in the background. Solution is simple: Settings -> Device Maintenance-> Battery -> Battery usage -> Optimize menu -> All apps. Untick the ones you need and, probably, they will remain in memory for while. So far, working for me.
so no solution to this thus far?? any root tweaks or build prop tweaks useful to solve this??? or we still have a dump phone