does anyone have experience with this app on android? I've read a lot about the fact that the app has become almost unusable after the new Android versions
Greenify is useless from Android 10 with the Battery profil app-by-app.
Now you can choose Unrestricted (no optimization), Optimized (the standard), or Restricted (which restricts battery usage even when the app is running in the background).
So restricted is like Greenify process.
System apps dude, you can't restrict system apps...
Related
Ok, I have the task killer app, but not sure how to determine what apps are ok to have running in the background and not suck up juice...
Seems odd to me that all the apps, even some that have an 'exit' menu item still linger after closing.
I searched about this forum (and wiki), but did not see similar questions.
It's probably so obvious that it doesn't register...
Thx!
Don't kill things like Alarm Clock, Messages, Touch Input, etc. Background apps only suck juice and use data if the app's themselves connect to the internet or use background data, if you aren't using background data, then disable it (there are third-party apps to toggle it mobile data and GPS on and off through widgets).
Personally, I used a task-killer and thought it would extend my batter but your battery life doesn't go down any faster killing tasks. My phone runs faster and smoother with it uninstalled and my battery was mostly draining because I had mobile networking on. Turn that off when you aren't using it (including GPS) and your battery life will increase two-fold. Not as much to do with background apps as you think.
Ok, thanks!
I have to Rogers too, but in my readings, everyone has said use the task killer, so I thought that was standard operating procedure. Then surprised a stock system didn't have anything like that installed.
I had left wifi and gps enabled on my Pure (Topaz) and battery life wasn't that bad. Would turn off when not in use. Does this one just stay on all the time?
-P
It will stay on all the time unless you turn it off via Settings or a third-party widget installed through the marketplace. As said in a few topics, Android is a Linux based OS meaning it's meant to handle the loads of apps running at the same time, it's how Linux handles RAM that makes Android fast. Running background apps do not mean they are literally running in the background, like in windows when you open 18 different windows and minimize a few, the programs are still running full capacity. Linux saves the applications settings and puts the application on 'idle' or a 'sleep' mode that allows the application to run in the background without it affecting battery life much. (I believe that's how it works.)
Don't worry about the task managers and just get some third-party toggle widgets installed from the market place.
I should have been more clear in my original question, sorry.
I'm quite familiar with *IX, been using / running / admin since 86.
I was mostly concerned with misbehaving apps (apps in background that continue to chew cycles), or devices that do not go idle when not in use. Generally unusual stuff that will drain the battery, not necessarily the obvious.
My experience with Android prior to this phone with with Android 2.0 as a work in progress on the HTC Topaz (which I am selling), and I constantly used task killer. I'm using it as a bad reference, I know it was in early stages of devel, but it was hard to tell what was draining the battery (and it got very warm).
I just unlocked my Sapphire last night and so far am very happy with it.
One thing that I wondered: is the expectation that if it gets slow, or if memory/swap starts to run low/out, you should reboot it? I guess that is why there is no task killer initially installed?
Hello guys. I noticed in JB or android os, whenever we kill background or foreground apps using any task manager but these apps does not killed permanently as nokia OS does. On android, when we killed apps these apps runs again after short whiles. The point of killing back-foreground apps to recover ram for boost battery & device performance. But unable to be satisfy due to self run apps after killed. Is there any way or any app to killed background apps permanently until we does not start again as well can we scheduled or restrict particular apps as i can do on nokia belle & i had set program rules for running apps & these does not run again until i want or reboot device. Plz someone suggest me any way??? Thanx
New owner of a Nexus 7 2013 here. Had it for a month or so now.
So the device came shipped with 4.3, I updated the device to 4.4.2 OTA. Weird thing is, everytime I "Force Close" an app from Settings, the RAM usage decreases, then it INCREASES!
Google Play Store (44mb), current RAM usage: 444mb
Force close Play Store, current RAM Usage: 400mb
*a couple of seconds later after display refresh*
current RAM Usage:480mb
This keeps going. No matter how many apps I force close, the RAM usage keeps increasing until the point where it reaches ~660-~700mb!
Is this normal? Does this happen to anybody else? Is there something wrong with the garbage collector? Also my RAM usage is in the 400mb range on startup and a LOT of apps run on startup which I need to force close manually (is it normal they run on startup?).
Thanks!
So memory usage is supposed to increase when you force close apps, so I take it this is usual for Android? But is there any explanation as to why ram usage increases instead of decreasing like on iOS? Is the garbage collection on this thing significantly different to conventional Linux kernels or for that matter Windows' variant too?
Sounds like a very stupid idea tbh
greatnoob said:
So memory usage is supposed to increase when you force close apps, so I take it this is usual for Android? But is there any explanation as to why ram usage increases instead of decreasing like on iOS? Is the garbage collection on this thing significantly different to conventional Linux kernels or for that matter Windows' variant too?
Sounds like a very stupid idea tbh
Click to expand...
Click to collapse
OK wrong forum this one is for the n7 2012 but your question is more to do with how android runs rather than specifically the nexus.
First of all forget everything you think you know about ram. In android the more ram being used the better the device will run. This is not always true but largely the more apps being held in ram the smoother android will run them. When an app closes it moves from running services to cached and the system will then call on that if you reopen the app or clear space if it needs it thus saving itself valuable power. The other reason for not force closing apps it they no longer run in the background as they were designed to. This is one reason task killers are bad for your system. If you close the mail app you won't get emails, if you close the clock your alarm won't go off, if you close the play store your apps won't update ect. Android is as far removed from windows as iOS is although windows 7 does use a similar idea towards ram. It doest need you to clear ram its perfectly capable of doing it itself. The exception to this is when you get badly designed apps that don't clear up after themselves and stay in the running services.
Try looking in your cached services you will probably find that's where your ram increase is. By force closing apps you make more work for the system reopening them.
Look here for more information about this
http://forum.xda-developers.com/showthread.php?t=904023
Sent from my C5303 using xda app-developers app
Hi ,new user on xda
i have a nexus 4
running completely stock 5.0 LRX21T NO ROOT
i have noticed very high ram usage on 5.0 as compared to 4.4 after the update
normally had ~1gb Ram free but now only ~500mb remains free
on ruuning applications screen,it shows
system-~750mb
apps-~600 mb
why is system using so much Ram,wasnt the case in 4.4...
is it bcoz of ART ?
is this normal?
same problem..on my nexus 4 after 5.0 update
After reboot, system ram usage stays low (read 100 to 150mb) for 1 to 2 days.. But suddenly shoots up to more than 1gb.
Does anyone know the root cause.
I think i found the root cause to this..
In Settings -> Sound & Notifications
change the setting When Device is locked -- Don't show notifications at all
By doing this, the system ram usage never shot up above 200mb for the past 2 days for me.
previously I had to reboot my device every night before going to bed.
I will further observe if this is the root cause and revert back.
apv25 said:
Hi ,new user on xda
i have a nexus 4
running completely stock 5.0 LRX21T NO ROOT
i have noticed very high ram usage on 5.0 as compared to 4.4 after the update
normally had ~1gb Ram free but now only ~500mb remains free
on ruuning applications screen,it shows
system-~750mb
apps-~600 mb
why is system using so much Ram,wasnt the case in 4.4...
is it bcoz of ART ?
is this normal?
Click to expand...
Click to collapse
art by default use more ram than dalvic to run applications so this might be normal for you. on top of that there is some memory leak found in android l.
the important thing to now is how android manage ram. when you open an application it is loaded in the ram. whether you close the application or let it run on the backround android does not clean the memory occupied by the application until it has to. android LMK (low memory killer) clean the ram memory occupied by a program denpending on the priority id of the app. for example system apps (system ui) has lowest priority so LMK never kills that app. other apps have different priority. an application that runs in the backround (facebook messenger or whatsup) have lower priority than a game so when android need more ram it will empty the ram occupied by the game first and if there is more need for ram it will later empty the ram occupied by the backround app.
Long story short android will handle the ram as it sees fit. unlike windows, android will keep the memory full so apps can be launched faster. the problem is that android l has memory leak so you need to reboot your device every few days if you feel it starts to have some lags.
apps like task killers do more harm than good in terms of performance or lags. also facebook and facebook messenger are very badly written apps so they will consume a lot of memory. also antiviruses (especially cm security) are responsible for lags and memory leaks.
hope i helped you somehow understand android and find your problem (if there is one)
P.S. sorry for the long post!!
ttheodorou said:
art by default use more ram than dalvic to run applications so this might be normal for you. on top of that there is some memory leak found in android l.
the important thing to now is how android manage ram. when you open an application it is loaded in the ram. whether you close the application or let it run on the backround android does not clean the memory occupied by the application until it has to. android LMK (low memory killer) clean the ram memory occupied by a program denpending on the priority id of the app. for example system apps (system ui) has lowest priority so LMK never kills that app. other apps have different priority. an application that runs in the backround (facebook messenger or whatsup) have lower priority than a game so when android need more ram it will empty the ram occupied by the game first and if there is more need for ram it will later empty the ram occupied by the backround app.
Long story short android will handle the ram as it sees fit. unlike windows, android will keep the memory full so apps can be launched faster. the problem is that android l has memory leak so you need to reboot your device every few days if you feel it starts to have some lags.
apps like task killers do more harm than good in terms of performance or lags. also facebook and facebook messenger are very badly written apps so they will consume a lot of memory. also antiviruses (especially cm security) are responsible for lags and memory leaks.
hope i helped you somehow understand android and find your problem (if there is one)
P.S. sorry for the long post!!
Click to expand...
Click to collapse
thanks
ttheodorou said:
art by default use more ram than dalvic to run applications so this might be normal for you. on top of that there is some memory leak found in android l.
the important thing to now is how android manage ram. when you open an application it is loaded in the ram. whether you close the application or let it run on the backround android does not clean the memory occupied by the application until it has to. android LMK (low memory killer) clean the ram memory occupied by a program denpending on the priority id of the app. for example system apps (system ui) has lowest priority so LMK never kills that app. other apps have different priority. an application that runs in the backround (facebook messenger or whatsup) have lower priority than a game so when android need more ram it will empty the ram occupied by the game first and if there is more need for ram it will later empty the ram occupied by the backround app.
Long story short android will handle the ram as it sees fit. unlike windows, android will keep the memory full so apps can be launched faster. the problem is that android l has memory leak so you need to reboot your device every few days if you feel it starts to have some lags.
apps like task killers do more harm than good in terms of performance or lags. also facebook and facebook messenger are very badly written apps so they will consume a lot of memory. also antiviruses (especially cm security) are responsible for lags and memory leaks.
hope i helped you somehow understand android and find your problem (if there is one)
P.S. sorry for the long post!!
Click to expand...
Click to collapse
This is why Google needs to give us an extended power menu. I understand they say it shouldn't be necessary under normal circumstances, but I consider every single nexus update to be a beta, of sorts...and we all know how buggy betas can be from time to time. They're very unpredictable, and you never know if you'll need to reboot. Saying it's simply never necessary for something that is basically beta is just plain egotistical as hell.
hp420 said:
This is why Google needs to give us an extended power menu. I understand they say it shouldn't be necessary under normal circumstances, but I consider every single nexus update to be a beta, of sorts...and we all know how buggy betas can be from time to time. They're very unpredictable, and you never know if you'll need to reboot. Saying it's simply never necessary for something that is basically beta is just plain egotistical as hell.
Click to expand...
Click to collapse
my philosophy is that when you buy a nexus device, because it is a very simple os without the good stuff that lg/sammy or any other oem android manufacturer put on their phone(i am refereeing to the shortcuts power menu or toggles and other things that make your life easier and not the whole change of the os like touchwizz) you have to root so you can do your own small changes as you see fit (and fortunately for me i live in europe where there is a European law that states that you have the right to do whatever you want to the software of your device an be eligible to waranty).
So if you root your device you can do everything you want. for me on kit kat it was xposed and gravity box. on android l, yesterday i installed simple aosp.
In my opinion pure android with a twist is the way to go! and of course a custom kernel for better battery life and ad free for no ads!!
P.S. a quote by a fellow nexus user: A nexus without root is like an angel without wings
ttheodorou said:
my philosophy is that when you buy a nexus device, because it is a very simple os without the good stuff that lg/sammy or any other oem android manufacturer put on their phone(i am refereeing to the shortcuts power menu or toggles and other things that make your life easier and not the whole change of the os like touchwizz) you have to root so you can do your own small changes as you see fit (and fortunately for me i live in europe where there is a European law that states that you have the right to do whatever you want to the software of your device an be eligible to waranty).
So if you root your device you can do everything you want. for me on kit kat it was xposed and gravity box. on android l, yesterday i installed simple aosp.
In my opinion pure android with a twist is the way to go! and of course a custom kernel for better battery life and ad free for no ads!!
P.S. a quote by a fellow nexus user: A nexus without root is like an angel without wings
Click to expand...
Click to collapse
I do have root access and a custom kernel, but I prefer the nexus factory images, and the only system change I want is an extended power menu. Have you ever actually looked for an odexed version of an extended power menu flashable zip??? Don't waste your time. The last one I saw myself was for Nexus S. It can be done, but it never IS done. Stuff like that I could almost definitely do myself, but I just don't have the time anymore to sit down and read how to do it, actually do it, test it, etc. I haven't done any android dev at all in a few years and I'm rusty as hell, not to mention how much things have changed for android in the last two years.
1) Is there any trick or settings to prevent selected apps services from running in background, prevent autostart? It's just waste of battery and Ram. (Check attached)
2) what is the difference between running services & cached services?
It's Android's RAM management. Cached services means whatever services you have used till now are stored in the RAM at whatever capacity the OS thinks it's available.
Running services means the services that are actually being used by the OS/apps currently.
Best not to touch that as Android does a good job of RAM management and the more you clear your recent apps/these cached services, the more redraws are made by the system /OS; eg. To start an app again which you were using a few moments ago but, you cleared it from recent apps (smaller difference magnitude) and cached services (bigger difference magnitude).
The redraws also uses more battery and power, ofc slightly.
And there is this adage that goes - Free RAM is wasted RAM, which I agree only slightly.
You can't prevent autostart in the stock ROM unless you are rooted. Atleast if I recall correctly, i used to cringe looking at the apps autostarting and running in the BG with it's services (obviously there ways around this).
So the whole thing that I mentioned (1st and 2nd para) kind of becomes pointless? as there ****ty apps like Facebook, for eg which keep running in the background, autostart, have so many bloody cached services like cancer which hogs the system resources. I disable these apps immediately when I am done using them.