Related
Apps starting on their own. Anyone have these issues? All the att stuff is gone but the video and music player are open randomly as well as quik office. I can see gmail opening and others tho check for updates
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes, this annoys the hell out of me. I wish I knew what to do to stop it. I've even downloaded an app that's supposed to stop things from auto-starting, and it doesn't even work.
Search for StartUp Auditor on the market, it may work for you.
Android Market description
Startup Auditor is one of the original task killer & task manager apps. It is a boot monitor and startup monitor tool which displays a list of applications you may disable.
Terminate processes automatically.
Enable/Disable apps& keep disabled. No root.
Full version eliminates ads and can disable unlimited!
Package: com.vesperaNovus.app.StartupAuditorFree
Click to expand...
Click to collapse
On the advice of this forum I uninstalled my app killer. From time to time I use Android System to see what's running and I notice a number of apps that start themselves. These include the stock music and video players along with Slacker Radio, AT$T Maps, eBay, GPS Status and a dozen others at various times. I don't mean they remain running after exiting, I mean they start without my having used them. What could be causing these apps to start when not called upon? The ones that use GPS put a significant drain on the battery without me knowing it. Any ideas what triggers these apps? I think I'm going back to using an app killer.
Miami_Son said:
On the advice of this forum I uninstalled my app killer. From time to time I use Android System to see what's running and I notice a number of apps that start themselves. These include the stock music and video players along with Slacker Radio, AT$T Maps, eBay, GPS Status and a dozen others at various times. I don't mean they remain running after exiting, I mean they start without my having used them. What could be causing these apps to start when not called upon? The ones that use GPS put a significant drain on the battery without me knowing it. Any ideas what triggers these apps? I think I'm going back to using an app killer.
Click to expand...
Click to collapse
Mine does the same thing. I have Advanced task killer on mine. I dont use it to kill apps, just to look and see how much ram is free and whats running. But all kinds of junk opens by itself.
so does anyone have a fix for this?
derek4484 said:
Mine does the same thing. I have Advanced task killer on mine. I dont use it to kill apps, just to look and see how much ram is free and whats running. But all kinds of junk opens by itself.
Click to expand...
Click to collapse
What use is free RAM when it is kept free all the time?
AJerman said:
Yes, this annoys the hell out of me. I wish I knew what to do to stop it. I've even downloaded an app that's supposed to stop things from auto-starting, and it doesn't even work.
Click to expand...
Click to collapse
Use "start up auditor". With personal experience, this only slowed down my system.
dieselstation said:
so does anyone have a fix for this?
Click to expand...
Click to collapse
This is now android works. The way I see this, this is very much similar to "pre-fetch" concept in windows 7.
I have a 6 GB RAM laptop. Base OS uses less than 1.5 GB of RAM. But like an hour or so when I see my RAM usage, its to the tune of 3-4 GB. What I have noticed is that my most frequently/recently used apps are loaded to RAM and kept there idle. Some amount of RAM is always kept free instead of using up all RAM. This way apps start faster. When I load a different memory heavy program, it pushes the existing one out and loads this.
More or less the same in android too. When u go to any task manager app n see the running apps, u'll notice that many of the apps loaded are the ones u use frequently.
These apps do NOT use any CPU. They are just loaded to memory and kept there for quick access.
When I boot up my phone I have like 190+ MB free RAM. Though left in standy mode, within an hour, I see my free RAM fall to 80-120 MB range. I never saw it go less than 80 MB. And the apps in memory are the ones I used the last time, and the ones I use all the time.
Even if u use a task killer to kill these "inactive" apps at intervals, they would be loaded again sooner or later. That's the principle of android. So by using task killers, though u feel u r freeing up memory, in fact, u r only draining ur battery. What's the use of memory if u r not using it effectively.
Don't worry abt free RAM amount. Let android manage it. Systems are intelligent enough these days.
Hope this helps.
All well and good, but when I look at what apps are using the most resources, the GPS-enabled apps are almost always near the top of the list even when I haven't been doing anything with them. That tells me that they are stealing processor time even when not being used and that can't be good for battery usage.
Miami_Son said:
All well and good, but when I look at what apps are using the most resources, the GPS-enabled apps are almost always near the top of the list even when I haven't been doing anything with them. That tells me that they are stealing processor time even when not being used and that can't be good for battery usage.
Click to expand...
Click to collapse
Install Spare Parts and see battery usage. Do u see any GPS time under CPU usage. Though my system has all these apps loaded up, they don't show up as using CPU time or any sensors unless I use the app.
Android Memory Management
Android Memory Management
Android is a Linux based OS with 2.6.x kernel, stripped down to handle most tasks pretty well. It uses native open source C libraries that have powered Linux machines for years. All the basic OS operations like I/O, memory management, and so on, are handled by the native stripped-down Linux kernel.
How to use memory for each application
Android’s process and memory management is a little unusual. Like Java and .NET, Android uses its own run time and virtual machine to manage application memory. Unlike either of these frameworks, the Android run time also manages the process lifetimes. Android ensures application responsiveness by stopping and killing processes as necessary to free resources for higher-priority applications.
Each Android application runs in a separate process within its own Dalvik instance, relinquishing all responsibility for memory and process management to the Android run time, which stops and kills processes as necessary to manage resources.
Dalvik and the Android run time sit on top of a Linux kernel that handles low-level hardware interaction including drivers and memory management, while a set of APIs provides access to all of the under- lying services, features, and hardware.
Dalvik Virtual Machine Dalvik is a register-based virtual machine that’s been optimized to ensure that a device can run multiple instances efficiently. It relies on the Linux kernel for threading and low-level memory management.
The Dalvik Virtual Machine
One of the key elements of Android is the Dalvik virtual machine. Rather than use a traditional Java virtual machine (VM) such as Java ME (Java Mobile Edition), Android uses its own custom VM designed to ensure that multiple instances run efficiently on a single device.
The Dalvik VM uses the device’s underlying Linux kernel to handle low-level functionality including security, threading, and process and memory management.
All Android hardware and system service access is managed using Dalvik as a middle tier. By using a VM to host application execution, developers have an abstraction layer that ensures they never have to worry about a particular hardware implementation.
The Dalvik VM executes Dalvik executable files, a format optimized to ensure minimal memory foot- print. The .dex executables are created by transforming Java language compiled classes using the tools supplied within the SDK.
Understanding Application Priority and Process States
The order in which processes are killed to reclaim resources is determined by the priority of the hosted applications. An application’s priority is equal to its highest-priority component.
Where two applications have the same priority, the process that has been at a lower priority longest will be killed first. Process priority is also affected by interprocess dependencies; if an application has a dependency on a Service or Content Provider supplied by a second application, the secondary application will have at least as high a priority as the application it supports.
All Android applications will remain running and in memory until the system needs its resources for other applications.
It’s important to structure your application correctly to ensure that its priority is appropriate for the work it’s doing. If you don’t, your application could be killed while it’s in the middle of something important.
The following list details each of the application states shown in Figure (see the attached image) explaining how the state is determined by the application components comprising it:
Active Processes Active (foreground) processes are those hosting applications with components currently interacting with the user. These are the processes Android is trying to keep responsive by reclaiming resources. There are generally very few of these processes, and they will be killed only as a last resort.
Active processes include:
* Activities in an “active” state; that is, they are in the foreground and responding to user events. You will explore Activity states in greater detail later in this chapter.
* Activities, Services, or Broadcast Receivers that are currently executing an onReceive event handler.
* Services that are executing an onStart, onCreate, or onDestroy event handler.
Visible Processes Visible, but inactive processes are those hosting “visible” Activities. As the name suggests, visible Activities are visible, but they aren’t in the foreground or responding to user events. This happens when an Activity is only partially obscured (by a non-full-screen or transparent Activity). There are generally very few visible processes, and they’ll only be killed in extreme circumstances to allow active processes to continue.
Started Service Processes Processes hosting Services that have been started. Services support ongoing processing that should continue without a visible interface. Because Services don’t interact directly with the user, they receive a slightly lower priority than visible Activities. They are still considered to be foreground processes and won’t be killed unless resources are needed for active or visible processes.
Background Processes Processes hosting Activities that aren’t visible and that don’t have any Services that have been started are considered background processes. There will generally be a large number of background processes that Android will kill using a last-seen-first-killed pat- tern to obtain resources for foreground processes.
Empty Processes To improve overall system performance, Android often retains applications in memory after they have reached the end of their lifetimes. Android maintains this cache to improve the start-up time of applications when they’re re-launched. These processes are rou- tinely killed as required.
How to use memory efficiently
Android manages opened applications which are running in the background, so officially you shouldn’t care about that. This means that it closes the applications when the system needs more memory. However, most android users are not very satisfied with how it does its things because sometimes it leaves too many processes running which causes sluggishness’ in everyday performance. We can use advanced task killer/task manager and it does its job very well.
Source:
Code:
http://mobworld.wordpress.com/2010/07/05/memory-management-in-android/
Still doesn't answer the question of why the OS is starting apps randomly and without need. For instance, I have Titanium Backup and SGS Tools installed, but can't use them because I am not yet rooted. So why do I keep finding both programs started in the process list? Is the app making the call to start? If so, what can I change to stop it? Whatever Android does to manage memory, it just seems stupid for it to load programs that are hardly used without my asking it to.
Miami_Son said:
Still doesn't answer the question of why the OS is starting apps randomly and without need. For instance, I have Titanium Backup and SGS Tools installed, but can't use them because I am not yet rooted. So why do I keep finding both programs started in the process list? Is the app making the call to start? If so, what can I change to stop it? Whatever Android does to manage memory, it just seems stupid for it to load programs that are hardly used without my asking it to.
Click to expand...
Click to collapse
This is how the systems work in most systems, not just in android.
Take the new cars for instance. Power is generally sent to brakes when in low gears, though u r not actively engaging them. Why? Since u r at low speeds, higher probability of applying brakes. And when u do apply, since there is already some power already being sent, its faster to brake.
On similar lines is this principle of loading apps into memory in android too. It won't load apps to fill up ur memory. Plus the apps loaded into memory in this way don't use any CPU time (this means no battery usage). This speeds up system.
On a side note, if u feel u really do not need an app, and dont' want android loading that app, get "startup auditor" from market. Select the apps u don't want to persist in memory and don't want to auto start. Beware of one thing here: if u make an app as 'do not persist' in memory, and that app is started manually or by any other app, it would be killed giving FC in the app that's using it.
Note: I coined the term 'do not persist'. I do not have the app anymore to check for the exact term.
Edit: In windows, this pre-fetching is done through a service. And one can disable that service, though not recommended. I am not sure if this is done through a service that is "stoppable" in android.
I open the thread in DEV because I haven't got convincing answer until now.
I found many junior ROM makers and users delete the system apps as many as possible to think it will bring a longer battery usage. I also listened someone got a faster battery drain after deleting some apps like DrmProvider.apk or others.
Could someone explain the real reason please?
Will the missed apps make the system try to read the 'file' again and again so the battery drain faster or some other reasons?
And as mentioned in the begining, deleting those apps that donot affect the system will really bring a batter battery performance?
Thanks!
defw said:
I open the thread in DEV because I haven't got convincing answer until now.
I found many junior ROM makers and users delete the system apps as many as possible to think it will bring a longer battery usage. I also listened someone got a faster battery drain after deleting some apps like DrmProvider.apk or others.
Could someone explain the real reason please?
Will the missed apps make the system try to read the 'file' again and again so the battery drain faster or some other reasons?
And as mentioned in the begining, deleting those apps that donot affect the system will really bring a batter battery performance?
Thanks!
Click to expand...
Click to collapse
I'm no dev myseld, but you might find interresting reading what I've recently posted here: http://forum.xda-developers.com/showpost.php?p=16662568&postcount=10102
Don't take my words for it, but you can always delete apks one by one and carefully watch the logcat verbose to see if the system posts any strange behavior after doing so.
*** I take no responsibilty for you doing so - and do it at your own risks! ***
For sure deleting an apk that is needed by the Android system could make the battery usage worst; DRMprovider is probably a good example of a mandatory app - unless someone never listens to any audio at all.. I don't know the specifics for every error and what kind of energy the system would put into solving a bug related to a missing app -is this really important anyway?
I've deleted 30 apks myself from the system/app directory from CM7 and I did not see any drawback in doing so. Most of them are apks installed by the gapps.zip so they are not part of my stock rom per say -hence: both the system and myself can live very well without them.
I don't care much about saving battery by deleting them as much as: 1- saving space; 2-preventing the system to ever have to read or generate thumbnail previews (or anyhing else really) for those apks and most importantly 3- seeing apks listed in my "running apks" that I've never wanted to start in the first place.
I'm sure that you've read the comment that states that task killers are not needed with Froyo because the system now manages the ram usage very well..but I still kill aps many times a day. Some might say they're just listed but not using resources; well fine! But how can they prove that? If an apk is loaded in memory, it might do an update (or what not) once an hour or once day; that takes battery - not much- but it does and if it is not needed then...
One other good example would be my xda apk: it is always listed under the running task even though I logged out and exited the program. Checking it out with an apk like Process Explorer clearly shows that it still constantly uses up to 3%of the cpu unless I kill it properly... So all this to say: removing apks might not save you so much battery but it might save you some task killing.
Bottom line is: if you're sure that the apk is not needed why have it on the phone?
Battery saving might very well be negligeable and no one can say it's the case for every specific apks. Again, I removed those apks because they're of no use to me and my system seems to live well without them. But it's your job to make sure that deleting stuff is not detrimental for the system and that is the dev part of it.
Personally I use a Startup Manager kill anything or most anything that's listed that starts by itself including my xda app. Never understood why on the Defy there's 15 to 25 apps up and running when they're not being used. And why they start themselves. I don't need my music apps starting by themselves.Or Documents to Go/Equalizer/GPS Tracker/Maps, etc., etc. I'll manage my own stuff, thank you. I would think all those apps running in the background would affect battery life. I have also deleted some of the crapware. Seems to me battery life has increased and when I run Advanced Task Manager I'm only killing 5-6 apps instead of 15-20.
btw wrong section to post...
MikeChannon
please move this thread.. in here..
http://forum.xda-developers.com/forumdisplay.php?f=853
I found an application named AutoKiller Memory Optimizer by which applying its tweaks It makes my phone more smoothly and saves my battery very well!
There are some reviews below links:
http://forum.xda-developers.com/showthread.php?t=622666
http://andrs.w3pla.net/autokiller
http://andrs.w3pla.net/autokiller/details
http://andrs.w3pla.net/autokiller/kernel
If anyone has installed this application plz give your opinion !
Task killers are pointless, just use Autostarts and Greenify.
That combo will be far more efficient
It's not a regular task killer! I suggest to try it!
Listy2021 said:
Task killers are pointless, just use Autostarts and Greenify.
That combo will be far more efficient
Click to expand...
Click to collapse
It's not a regular task killer! I suggest to try it!
ehsan453 said:
It's not a regular task killer! I suggest to try it!
Click to expand...
Click to collapse
Yes it is, it's just filled with other guff to make it look more advanced or whatever
Listy2021 said:
Yes it is, it's just filled with other guff to make it look more advanced or whatever
Click to expand...
Click to collapse
You have not test it yet, therefore you can't understand what i mean!
ehsan453 said:
You have not test it yet, therefore you can't understand what i mean!
Click to expand...
Click to collapse
How do you know I haven't tested it before?
The whole reason I can make a judgement on task killers (including this one) is that before using Autostarts & Greenify I tested other options, therefore my opinion is valid :good:
Listy2021 said:
How do you know I haven't tested it before?
The whole reason I can make a judgement on task killers (including this one) is that before using Autostarts & Greenify I tested other options, therefore my opinion is valid :good:
Click to expand...
Click to collapse
It's not a task killer. It's an app that modify your lmk and add some tweaks. But you can kill some apps from this app.
What is so special about this task killer? No, I am not gonna test it.
Vit5000 said:
What is so special about this task killer? No, I am not gonna test it.
Click to expand...
Click to collapse
First Plz read reviews in first post and also these two reviews:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Releasing RAM With Autokiller Memory Optimizer
Have you ever wished to speed up your Android, but now known how? Have you tried task killers, but found it hard to tell whether you made an improvement? In this post, we’ll look at Autokiller Memory Optimizer, an app that gives you more control over how Android releases its system resources.
“You shouldn’t be using a task killer with Android” clearly explains why the task killers are not a good solution to fasten up your system in the Android interface. Briefly, we might say that the reason that task killers are no good for Android is that the same system regulates itself for releasing RAM memory. Process are not killed when you close the app; instead the process stays open until the system itself realizes it needs more memory to run a new process. This way, you can actually gain some speed when you restart the app, as its resources may still be in memory.
Just like a computer, a smartphone uses Random Access Memory (RAM) for processing the functionality of softwares and apps. When you are running low on RAM, your phone will start to slow down, because it needs more memory than is available. As a solution to this problem, Android devices has an autokiller that automatically shuts apps down when the memory used is close to the limit. Obviously this limit depends on the capabilities and configuration of your phone.
If you root your phone (and I totally recommend you to do that) you can use apps for changing your system parameters like the RAM auto killing. One of this apps is Autokiller Memory Optimizer available on the Android Market.
As the developer says: “AutoKiller Memory Optimizer is designed to fine-tune Android system’s inner memory manager routines to keep your device fast and smooth. It also features a full-powered process manager which lets you control your whole system.”
Warning: Messing around with system configurations like this is potentially dangerous to your phone, and not for the faint-hearted! Check out our other How To articles for safer tips on improving performance.
Going for It
The system itself divides the process into six different types, and here’s where it gets technical. The six types are as follows.
FOREGROUND_APP: This is the process running the current foreground app. We’d really rather not kill it! Value set in system/rootdir/init.rc on startup.
VISIBLE_APP: This is a process only hosting activities that are visible to the user, so we’d prefer they don’t disappear. Value set in system/rootdir/init.rc on startup.
SECONDARY_SERVER: This is a process holding a secondary server — killing it will not have much of an impact as far as the user is concerned. Value set in system/rootdir/init.rc on startup.
HIDDEN_APP: This is a process only hosting activities that are not visible, so it can be killed without any disruption. Value set in system/rootdir/init.rc on startup.
CONTENT_PROVIDER: This is a process with a content provider that does not have any clients attached to it. If it did have any clients, its adjustment would be the one for the highest-priority of those processes.
EMPTY_APP: This is a process without anything currently running in it. Definitely the first to go! Value set in system/rootdir/init.rc on startup. This value is initialized in the constructor, careful when refering to this static variable externally.
For every type of app, the system has a limit of pages (1 page=4 kilobytes) predefined. Autokiller Memory Optimizer allows you to modify this.
For the changes you can make you have the freedom to set as you wish, but there is a lock on the three first types of apps (this can be removed in the Preferences tab) and there isalso a list of presets configuration as follows (the numbers corresponds to megabytes remaining before shutting apps in the last 3 types of apps): Moderate (30, 35, 40), Optimum (40, 50, 60), Strict (60, 70, 80), Aggressive (82, 90, 98), Extreme (150, 160, 170), Ultimate (200, 225, 250) and (a wink from the developer about the TV series) Lost (4, 8, 15, 16, 23, 42).
Autokiller presets
Within these presets, you should try different ones, because every phone has its own RAM capacity and it would not be a good idea to set a killing parameter that is very close to your RAM total capacity as your phone would be killing apps constantly and you wouldn’t be able to use it at all.
Processes list
The app also categorizes the running apps in the six types and you can kill them manually for RAM release in the tab processes and the same occurs with the services in the current tab.
Services list
This app has also a donate version with some more features like the Chuck Norris mode when you can configure the app to use aggressive killing to release memory. It also gives the ability to set a different preset when the screen of the phone is off (this is very useful because when the screen is off you do not need memory to run new apps, but it still consumes battery).
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Tweak your system thanks to AutoKiller Memory Optimizer
Summary
Relax, I’m not trying to fool you into thinking that a task killer is really a tweak. Don’t be fooled by the ‘AutoKiller’ part of the app’s name, focus on the other words instead, because AutoKiller Memory Optimizer will allow you to fiddle around and make a few adjustments. Read on and find out what kind of adjustments I’m talking about, and whether the app is worth your time.
Features & Use
AutoKiller Memory Optimizer is there to help you bring your system up to par by conducting a bit of fine tuning. The app comes with a task manager. Use the task manager to get rid of lagging processes, the logic behind this being that if you’ve got something running that’s not really doing anything useful, but does consume 98% of the CPU as well as a hefty chunk of memory you should really unload energy hoggers. Your system will thank you by running smoothly. The task manager also displays the oom_value for ever app—more details below.
The app allows you to regulate the settings for the OOM killer, the automatic killer integrated in every Android device whose role it is to create more memory space wherever possible. As you know, in the Android world applications are never halted or shut down, they are merely rendered inactive—until the memory pipes up and the Out Of Memory Killer rears its head. But when does memory shortage become critical? And who decides which apps should be banished, and when should this occur? If you want to make these types of decisions yourself take a look at AutoKiller Memory Optimizer.
Android divides running apps into six categories ranging from the app that you’re currently working with to ‘empty apps’ (i.e. apps that you left by hitting the back button at some point). Once RAM space becomes too low the OOM killer will start by banishing said empty apps, and, if need be, continue working its way up. AutoKiller Memory Optimizer lets you decide how much free RAM space is required for your device run smoothly. There are different presettings to pick from (‘moderate’, ‘aggressive’, etc) and you can check out the developer’s website to read up on user experiences.
Bottom line:
AutoKiller Memory Optimizer affords you easy access to essential systems settings, allowing your Android to perform as optimally as possible. How essential this kind of app is is contingent on lots of factors: which device you’re working with, how good the manufacturer’s presettings are and what can be done to adjust them.
Screen & Controls
AutoKiller Memory Optimizer is set up in a very logical way. While high skilled, expert knowledge of Android isn’t essential in order to get the best performance out of the controls, it doesn’t hurt to have some experience. You can find in depth information and details regarding the settings options on the developer’s website, which means that you really don’t need much background knowledge in order to get something out of this app.
If you have a bit of experience you will find that the app’s controls are intuitive; if you’ve never worked with tweaking before I recommend that you give this app a miss.
Speed & Stability
AutoKiller Memory Optimizer is fast, stabil and dependable. I’ve been using the app for just over a month and it hasn’t crashed once so far.
EDIT: repeated
This actually helps very much with memory management. I've been using it alongside Greenify and Autostarts for several months now.
Those individuals banging on about it being just another task manager clearly did not use this app as it is intended to be used.
Sent from ThePureHeart's I9300 Boss Edition
If i use the "ultimate" preset, will it drain my battery faster?
AzizWahid said:
If i use the "ultimate" preset, will it drain my battery faster?
Click to expand...
Click to collapse
Best preset is optimum
Its 2018 now. Is it still useful?
Hi!
I have tried various task managers from play store. They all show either nothing or just few app. Mostly they dont even display stuff that is running such as Firefox.
Sofar the only task manager that works for me is:
Code:
su -
top
But the problem is that it my phone has so many processes working that they dont all fit in one screen, and since top command is constantly updating, it scrolls back down. So I have to Ctrl - C to interrupt and then write kill -9 pid which is a bit annoying.
Is there any simple task manager out there that is graphical version of top command and that shows me absolutely everything, not only stuff that is currently active? To me it's important to see cpu usage next to pid.
sysctl said:
Hi!
I have tried various task managers from play store. They all show either nothing or just few app. Mostly they dont even display stuff that is running such as Firefox.
Sofar the only task manager that works for me is:
Code:
su -
top
But the problem is that it my phone has so many processes working that they dont all fit in one screen, and since top command is constantly updating, it scrolls back down. So I have to Ctrl - C to interrupt and then write kill -9 pid which is a bit annoying.
Is there any simple task manager out there that is graphical version of top command and that shows me absolutely everything, not only stuff that is currently active? To me it's important to see cpu usage next to pid.
Click to expand...
Click to collapse
No, task managers are crap, the native task killer that android has built in works fine. 3rd party task killers actually make the device work harder because they constantly reload the tasks that you kill.
Best option is root your device then uninstall unnecessary system apps, and use Greenify to freeze your other apps when they aren't in use.
All task managers, RAM savers, optimizers and battery savers are all junk, they actually do the opposite of what you think they do.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Dunno how with Android, but actually the 'top' command can be configurated to di what you want. Just read the top man page.
Sent from this galaxy
Clean Master is a good one. I got it mainly for it's ability to clear junk files, but the ram boosting ability is handy as well every now and then. It also has a mode that let's you launch games in "boosted" mode, which I think is just a clearing a ram when launching the game. Not sure if it maintains that or just just does a task kill at launch. Killed apps can often just restart soon after. Incidentally, I do that a lot for Iron Man 3.
ABSarah said:
Clean Master is a good one. I got it mainly for it's ability to clear junk files, but the ram boosting ability is handy as well every now and then. It also has a mode that let's you launch games in "boosted" mode, which I think is just a clearing a ram when launching the game. Not sure if it maintains that or just just does a task kill at launch. Killed apps can often just restart soon after. Incidentally, I do that a lot for Iron Man 3.
Click to expand...
Click to collapse
No, Cleanmaster is not a good one, none of the task killer/RAM optimizer apps are "good" they are actually counterproductive and make your device work harder in the long run.
Sent from my LGL84VL using Tapatalk
Instead of using a task manager that will probably not work, try Kernel Adiutor and try setting the Low Memory Killer to your wishes, following this guide.
Google Software Engineers have made improvements to the operating system over time to the point I believe the necessity and usefulness of these utilities is questionable especially if you are on Android 7 or later. Many people post their experiences with these apps without acknowledging their operating system version which could be significantly different than many other users.
This article "Android Apps You Should Remove Immediately" on Adroid Pit (you can Google it) recommends you get rid of these types of apps.
But there are lots of other articles, forum posts, article comments (mostly older) that swear by these apps.
Maybe out of the dozens of functions in these apps there's one or two useful ones on Android 7 (although my LG G6 already comes with a Smart Cleaner app)
Are the majority of Android 7 users using these apps basically blindly using them because they feel good to use and aren't actually getting the significant benefit they think they are getting? Could many of them, especially the ones that may "try to do too much" actually be hampering your Android 7+ phone more than helping it?
The only app I would recommend is ccleaner
https://play.google.com/store/apps/details?id=com.piriform.ccleaner&hl=en_GB
It does the following
clears all apps caches which could save alot of storage space - especially good if you have apps that store alot of cache files like twitter for loading images faster but since in most cases you only look at the image once you really dont need it cache it to load up quicker
It can also do the following if you ask it to
Deletes downloaded files/apks in one click
Deletes call logs
Deletes empty folders
Deletes browser history, clipboard content
And can also
Check the usage of your CPU
Keep track of your RAM and internal storage space
Check out your battery levels and temperature
Any other app which claims to "optimize" the phone probably does nothing unless it does the same job as ccleaner but in my opinion this is the easiest most trusted app to use