• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help How often should all app cached data be cleared

shawnnote4

shawnnote4

Newbie
On the Note 4, if you go to settings/storage. You will find "Cached data" underneath it lists how many MB is being used, mine is at 241MB. When I depress " Cached data" I am presented with a prompt, which reads "Clear cached data? This will clear cached data for all app." The question here is how often should I clear cache data for all apps? Should I wait until it reaches 500MB or a 1Gb? Any information on this would be extremely helpful. Oh, as of this morning I am running Lollipop 5.0.1 just in case you needed this information.
Thank you,
Shawn
 
Cache files are there for a reason. Cache files rebuild anyway when the associated apps are used, so it's usually a waste of CPU cycles and power to clear caches.

But, like I said if an app is struggling it might help. Or another exception is after a major system update like Lollipop if the device is acting funky clearing all caches so they can rebuild sometimes straightens it out.

Otherwise, if it ain't broke don't fix it.
 
Let me ask you another question since you seem to be knowledgeable on the subject matter. I recently updated/upgraded to lollipop version 5.0.1, under app manger/show services in use I have anywhere from 1.2 to 1.5GB available if just a few apps are running, however, under the banner of "show cached processes" I only have 400mb to 600mb free. This is the reason I posted my original question. can I trouble you to check what you have available under "services used and cached used"?
Thank you in advance.
Shawn.
 
So, what are "cached background processes"?

Since you are asking for a technical interpretation of something listed in a device UI, the definition may vary by device, if device manufacturers elected to tinker with the Settings app.

That being said, "cached background processes" usually refers to processes that do not have a foreground activity and do not have a running service. These processes are kept in memory simply because we have enough memory to do so, and therefore, as you note, the user can switch back to these processes quickly. As Android starts to need more system RAM for yet other processes, the "cached background processes" tend to be the processes that get terminated to free up system RAM.

The pre-eminent example of a "cached background process" would be one where the user launched the app, poked around it briefly, then pressed HOME to return to the home screen. If the process does not have a running service, I would expect to find it listed as a "cached background process".​
They are still in memory, rather than switched to "disk" (as desktops/laptops do), right?

Correct. Android devices do not use swap space.​

from http://stackoverflow.com/questions/...etween-running-processes-and-cached-backgroun

Therefore it seems that the former is how much RAM you are actively using in apps, the latter is how much RAM is physically in use. There is still no reason to clear this cache, because if you needed that space, Android would just take it back. The page linked above has a much more thorough explanation on memory clearing/prioritization if you are curious.
 
Last edited:
jvook said:
So, what are "cached background processes"?

Since you are asking for a technical interpretation of something listed in a device UI, the definition may vary by device, if device manufacturers elected to tinker with the Settings app.

That being said, "cached background processes" usually refers to processes that do not have a foreground activity and do not have a running service. These processes are kept in memory simply because we have enough memory to do so, and therefore, as you note, the user can switch back to these processes quickly. As Android starts to need more system RAM for yet other processes, the "cached background processes" tend to be the processes that get terminated to free up system RAM.

The pre-eminent example of a "cached background process" would be one where the user launched the app, poked around it briefly, then pressed HOME to return to the home screen. If the process does not have a running service, I would expect to find it listed as a "cached background process".​
They are still in memory, rather than switched to "disk" (as desktops/laptops do), right?

Correct. Android devices do not use swap space.​

from http://stackoverflow.com/questions/...etween-running-processes-and-cached-backgroun

Therefore it seems that the former is how much RAM you are actively using in apps, the latter is how much RAM is physically in use. There is still no reason to clear this cache, because if you needed that space, Android would just take it back. The page linked above has a much more thorough explanation on memory clearing/prioritization if you are curious.
Click to expand...
Thank you for the detailed information. The expansive knowledge you possess is admirable. I now have a much better understanding, for that I thank you.
 
You must log in or register to reply here.
Back
Top Bottom