Why I never close applications on Android

This article was inspired from a conversation with a friend. He asked me how many applications can be kept running in the background so the smartphone doesn’t discharge too quickly. Frankly, that question put me in a stupor. My friend was firmly convinced the filled multitasking menu leads to increased power consumption and wanted to find out at what point the smartphone begins to consume so many resources that it starts to become noticeable. If the same question gnaws at you, I will answer you a little more in depth than I answered him.

Closing applications on Android is not only pointless, but sometimes also completely unjustified from a functional point of view
Closing applications on Android is not only pointless, but sometimes also completely unjustified from a functional point of view

I have not closed applications on Android for a long time. I got this habit from when my only smartphone was the iPhone. It seemed then one of Apple’s representatives made a statement that closing background programs not only doesn’t save charging, but actually consumes it the battery even more. It sounds strange, but iOS is so energy-efficient that applications, once in the background, simply freeze and stop showing signs of life, giving the impression they’re not there.

Do I need to close Android applications?

iOS is not much different from Android in terms of resource allocation
iOS is not much different from Android in terms of resource allocation

When I almost completely switched to Android, I decided not to change my principles. It’s not that it was difficult for me to close running programs, but I’m so used to it I don’t need to do it, so I was just too lazy. Nevertheless, the fear my negligence could cost me a few minutes or maybe hours of battery life didn’t disappear and I decided to check out what was happening.

The experiment I conducted was quite simple. I just decided to compare how fast my smartphone charged if I closed applications and then if I didn’t. Perhaps my testing option won’t seem indicative, but since I use a smartphone the same way every time (messenger, Instagram and occasionally web surfing), it seemed to me this is a fairly objective way to figure out how to work with multitasking.


Do apps in the background consume battery power on Android?

As I expected, the results on battery life were almost identical. Closing the application didn’t have a particular load on the battery like on iOS, but their work in the background also didn’t consume charging, which is a plus. Nevertheless, I admit that different software may function differently and therefore, if you know for sure some of your programs are activated in the background and consume battery life, I have a great solution.

Applications in the background consume no more energy than closed ones
Applications in the background consume no more energy than closed ones

Most smartphones running Android have a kind of controller that monitors how applications work and prevents excessive energy consumption. On Huawei devices, it’s located in the “Launch Applications” section. Just find it in the “Settings” and turn on the automatic control function. It will block the automatic launch of applications in the background, preventing them from updating and consuming energy or Internet traffic.


How to reduce background power consumption on Android

I don’t unload applications from memory and they continue to stay in the background, without consuming or practically not consuming battery life. But not because the applications are so well-optimized or developers took care of my smartphone’s autonomy. It’s just that my device, or rather, its mechanisms, block them.

So, autonomy is sorted out. But lack of visible changes in operating time is not the only reason I don’t close applications. I don’t know what this is connected with, but sometimes Android can stop sending notifications from some applications. Changing the settings is useless – the system blocks notifications or pretends they’re not there at all.


What to do if Notifications on Android don’t appear

My personal experience has shown that push notifications don’t happen if the application is unloaded from memory. It’s worth opening it and leaving it to work in the background – albeit under the supervision of a controller – and it will continue to send you notifications again. Unfortunately, for some reason, I wasn’t able to find out why this is, but I’d keep applications in the background rather than suffer from lack of notifications.

My third reason is rationalism. In my life I try to follow a rational approach in everything: don’t pickle barbecue in mayonnaise, because mayonnaise is eggs, oil and vinegar; don’t buy a car if taxi rides are cheaper; and, of course, don’t close applications if this there is no point. Just think how many times in your life you have done these things.

If there is one button on your smartphone to close all programs at once we would us it, but many applications need to be closed manually, scrolling the screen dozens of times and erasing the data. Have you ever wondered why you do this? Most people mistakenly believe that closing the application in the background either saves battery life or allows the smartphone to work faster. But neither one is wrong.

You might also like
1 Comment
  1. Demi says

    A nice review, thanks!

Leave A Reply

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More