Chris has personally written over 2,000 articles that have been read more than one billion times-and that's just here at How-To Geek. For example, a poorly coded app could start a service process that remains running in the background all the time, using up all your CPU time and dramatically decreasing your battery life.Ĭhris Hoffman is the former Editor-in-Chief of How-To Geek. ![]() Of course, Android provides apps with so much flexibility that they have room to misbehave. Android intelligently uses your device's RAM for caching apps and other data, because there's no point in leaving your RAM empty. In most cases, Android does this all without you needing to worry about it. If you need more memory - for example, if you're playing a particularly demanding game on a device without much RAM, Android will then start to kill service processes, so your streaming music and file downloads may stop. Android will start to kill empty and background processes to free up memory if you're running low. When Android needs more system resources, it will start killing the least important processes first. It may be kept around for caching purposes to speed up app launches later, or the system may kill it as necessary.Īndroid does a good job of automatically managing these processes, which is why you don't need a task killer on Android. Empty process: An empty process doesn't contain any app data anymore. They're kept in memory so you can quickly resume using them when you go back to them, but they aren't using valuable CPU time or other non-memory resources. You can think of these background processes as "paused" apps. At any given time, many background processes are currently running. They have no impact on the experience of using the phone. Background process: Background processes are not currently visible to the user. For example, if you start playing music and switch to another app, the music-playing is in the background is being handled by a service process. However, it's doing something in the background, such as playing music or downloading data in the background. Service process: A service process isn't tied to any app that's visible on your screen. ![]() For example, the foreground process may be a dialog that allows you to see an app behind it - the app visible in the background would be a visible process. Visible process: A visible process isn't in the foreground, but is still affecting what you see on your screen. There are only a few foreground processes at any given time. ![]() Other processes can also be considered foreground processes - for example, if they're interacting with the process that's currently in the foreground. Foreground process: The app you're using is considered the foreground process. A process on Android can be in one of five different states at any given time, from most important to least important:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |