, ,

Android O features you’ll surely love: Background execution limits

Share This Story with FriendsShare on FacebookTweet about this on TwitterShare on Google+Share on StumbleUponShare on LinkedInPin on PinterestShare on TumblrShare on Reddit

Your Android phone will let you do many things at once, even though all of them might not be on your screen. Besides system processes that can do things like checking your location or seeing if you have any new email, applications can be opened and then be left to run in the background while we are doing something else.

A good example would be when you open your preferred music player and cue up a playlist to listen to while you check out Facebook or do a little web browsing. The music application is running in the particular background, doing its point while you’re looking in another thing.

But some programs can be sent totally to the background. Within our example of Android O’s Background execution limits, the particular music player is not really on the screen plus running as a history app, but it’s nevertheless getting together with us and actively playing music. Other programs that will we’ve opened and turned far from should be handled differently because we’re not really doing anything with all of them.

This can have an effect on the limited resources of your phone. Apps operating can use RAM and take processing time away from other programs that have to have a turn or even the software you’re currently using in the foreground (what you see on your screen. ) While Android has always had some restrictions on what a software can do while a possibility on your display, Android O brings smarter limitations to help preserve system resources and electric battery life by figuring out when a software is absolutely in the background and can be idle, then keeping it quiet but ready for when you want to put it to use again.

While this video is Android Nougat specific, it does a great job explaining just how background services can influence the software you’re positively using and methods to maintain things in check.

What’s new or changed in Android O?

  • Background Service Limitations. The system now does a few routine checks to see if an app can be considered as being in the background. It checks to see that the app or any of the activities (things an app can do or initiate) aren’t visible on the screen. It then checks to see if another app is connected to it or uses any information from it, and finally, it checks for a few high-priority services like being able to act as a keyboard or if it is actively listening for voice input.

When none of these items are true the iPhone app is considered as working in the background. Whenever a software is 1st considered to be in the background, it offers a short window where it’s allowed to do its thing in case it needs to start out something that would move it to a foreground software or service. Once that time is over the software is forced to be idle. Idle programs are also given short windows periodically in case they need to hook up or start services, but other than those times it sits and uses very little sources until we switch back to it.

  • Broadcast Limitations. Broadcasts are done by the system when specific events happen. When you switch your phone in and out of Airplane Mode, for example, a broadcast is sent to let apps know what happened. Developers can set up their apps to listen for specific broadcasts and write code so the apps do something when they happen. If an app is listening for broadcasts, every time one is sent the app uses system resources to see if any action is needed.

Apps built for Android O can no longer register to listen for broadcast messages that don’t directly target the application itself unless they are started and running (not in the background based on the rules above). These changes started with Android N, and changes in O are a little more strict. Because this could limit what a developer might want to do, new tools to schedule specific jobs using their own applications processes have been created. There are also the few broadcasts exempt through all of this, such as once the time zone adjustments or maybe the phone was connected into the charger. Every single iphone app can listen regarding those, and react appropriately.

By limiting how a good iphone app can listen plus what it can pay attention for, software who have already been designated as being within the background won’t wake up up to see when they have to do anything since often. “Sleeping” software make use of far fewer resources.

Why you’ll love it

We would like our phones to perform a lot of things. But no matter what we’re asking it to do, while we are looking at the screen we expect things to be smooth and responsive.

We’ve all felt the frustration that comes with keyboard lag once in a while, and it’s not a good experience. By keeping a tighter leash on the apps we’re not looking at, memory, processing power, and battery life is used more efficiently and we’ll see less of things like keyboard lag. The end user — that’s us! — doesn’t have to do anything here because these changes are part of the system. Even better, older apps that weren’t built with Android O in mind can be set to follow these rules from the apps setting page.

Changes like this get combined with the great hardware we see every year and mean your phone can do the things you ask of it even better!


SOURCE: androidcentral.com

Share This Story with FriendsShare on FacebookTweet about this on TwitterShare on Google+Share on StumbleUponShare on LinkedInPin on PinterestShare on TumblrShare on Reddit

What do you think?

0 points
Upvote Downvote

Total votes: 0

Upvotes: 0

Upvotes percentage: 0.000000%

Downvotes: 0

Downvotes percentage: 0.000000%

Leave a Reply

Your email address will not be published. Required fields are marked *