Related
I just installes arhd 2.1 rom and evrrything works fine.
I got most things installed.i need like twitter, fb, adv. task killer,
even auto startup killer, titanium, juice, setcpu and some more.
I disabled all notifications.
I prevent all startup apps i didnt want (all but 2,or 3)
I set sync to off. I checked all app settings twice.
Still there.are mostly like all apps running after i start my phone
And if i kill them it takes a while but they come back...
How to fix that ? Beside all my programms things like internet, mail, messages are also on.
My ram is down to like 210mb, when i kill its back to 480.
Thanks guys!
Android is nothing like windows.
Killing apps & processes to save memory is bad for your phone. Android handles its memory very well, and you killing apps interferes with that.
Apps are loaded into the RAM, for your convenience, if Android runs low on memory, it will decide what apps to kill.
I'm sure there is a guide that explains this.
andyharney said:
Android is nothing like windows.
Killing apps & processes to save memory is bad for your phone. Android handles its memory very well, and you killing apps interferes with that.
Apps are loaded into the RAM, for your convenience, if Android runs low on memory, it will decide what apps to kill.
I'm sure there is a guide that explains this.
Click to expand...
Click to collapse
So (Auto)-Taskkillers are Bull**** ?
Also Startup Prevention ? Everything like that ?
Or anything "good" ? I guess SetCpu is something useful which comes
into that area.
If someone has a guide, give me a "call"
Task killers should only be used to kill rogue apps, apps that are poorly coded. They shouldn't be used to manage your memory.
SetCPU is kinda different, all it does is allow you to alter the speed of your CPU.
mydanny said:
So (Auto)-Taskkillers are Bull**** ?
Also Startup Prevention ? Everything like that ?
Or anything "good" ? I guess SetCpu is something useful which comes
into that area.
If someone has a guide, give me a "call"
Click to expand...
Click to collapse
I find it very difficult to understand people who are using taskillers in their phone. The whole point, i guess, is to save some battery? But do you know that taskillers run constantly and consume even more battery? And you might end up messing up with your system and experiencing lags/problems.
The memory management of android system is different than what we are used to. You should let android manage the memory. If you still want to quit some of the apps which you think are using up your memory, you can do it manually via "manage applications" in applications.
I m also using ARHD. And i don't use any taskillers/ startup managers. I never experienced lags when playing gameloft games (i tell you they require lots of memory) or angry birds. I have my wifi-on, sync on all the time.
SetCpu is used to manage the cpu speed of your DHD. This can be used to create profiles (or comes already with some profiles like ondemand etc.) and the program itself understands the need for memory and adjusts your cpu speed according to that. It might give you some more bat. life.
Of course what kind of programs we want to use in our DHD is upto us. And people will have a divided opinion on whether to use taskillers or not. But if you ask me (and my almost 3 years of android experience), you are better off without any taskillers.
sphuyal said:
I find it very difficult to understand people who are using taskillers in their phone. The whole point, i guess, is to save some battery? But do you know that taskillers run constantly and consume even more battery? And you might end up messing up with your system and experiencing lags/problems.
The memory management of android system is different than what we are used to. You should let android manage the memory. If you still want to quit some of the apps which you think are using up your memory, you can do it manually via "manage applications" in applications.
I m also using ARHD. And i don't use any taskillers/ startup managers. I never experienced lags when playing gameloft games (i tell you they require lots of memory) or angry birds. I have my wifi-on, sync on all the time.
SetCpu is used to manage the cpu speed of your DHD. This can be used to create profiles (or comes already with some profiles like ondemand etc.) and the program itself understands the need for memory and adjusts your cpu speed according to that. It might give you some more bat. life.
Of course what kind of programs we want to use in our DHD is upto us. And people will have a divided opinion on whether to use taskillers or not. But if you ask me (and my almost 3 years of android experience), you are better off without any taskillers.
Click to expand...
Click to collapse
Word. Sounds convincing.
I will remove the **** from my phone - Task Killer and Startup Manager.
You also dislike Juice Defender ? I heard only positive things about battery.
Or is this 100% crap, too ?
mydanny said:
Word. Sounds convincing.
I will remove the **** from my phone - Task Killer and Startup Manager.
You also dislike Juice Defender ? I heard only positive things about battery.
Or is this 100% crap, too ?
Click to expand...
Click to collapse
I have never used Juice Defender but it is a OK app (it uses some bat. though). All i use i "currentwidget" to monitor what causes battery drain (if any). If i were you, i would see how the DHD goes along with/without juice defender for 48 hours. And then evaluate if i really need juice defender.
Killing apps is liking turning your car engine off on every street you go down. It's better to keep the engine running, it uses less petrol.
Same with memory management on Android, if you keep killing, it has to startup the app again each time you use it which actually uses more battery.
The only thing I use is setCPU on a smartass governor with a profile for when the screen goes off to reduce CPU usage to 450mhz. Mine idle's at 1-3ma.
What a bunch of rubbish. Task killers are an excellent easy to keep your phone running fast and smooth. They also save your battery by not letting tasks run in the background and eat battery unnecessarily.
I hope that wasn't too obvious a troll ...
Task killers suck. They are the Android equivalent of Windows registry cleaners. Sold to you to speed up your system but really they break it.
Sent from my super slick Android device.
dr.m0x said:
What a bunch of rubbish. Task killers are an excellent easy to keep your phone running fast and smooth. They also save your battery by not letting tasks run in the background and eat battery unnecessarily.
I hope that wasn't too obvious a troll ...
Task killers suck. They are the Android equivalent of Windows registry cleaners. Sold to you to speed up your system but really they break it.
Sent from my super slick Android device.
Click to expand...
Click to collapse
You had me for a minute there
The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help
Search the market for startup cleaner
Sent from my A101IT using xda premium
yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.
Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium
rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.
It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on
...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk
I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.
Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium
I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium
yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-
PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.
So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-
Stop looking for excuses for poor multitasking in Sense 3+ roms
erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.
@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse
I have heard somewhere that installing many apps can drain the battery more quickly
I just want to know wheter or not installing apps that are not running in the background drains the battery?.
Thanks.
Sent from my GT-N7100 using xda premium
Not if they are not running in the background
Some people have installed more than 300 apps (user apps)
scribbled from my note 2 (N7100)
It's no different than your computer. You can have 50000 apps installed, but only the ones running consume active (ram, battery, network) resources.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Be aware though that many do run in the background even if you haven't run them.
Sent from my GT-N7100 using XDA Premium HD app
In General Yes, but I'd say depends on the apps, if there are 200 quality apps, (however I don't know how many are there in Play Store), and you've not turned on the background data for them, then it might not drain much. But if you've even 5 crap apps installed then they'll be enough Culprit to hog the juice more than those 200 apps.
In short, DO NOT install crap apps, do not install whatever you see. Read user reviews, see ratings, then decide. I, for me, think 3 times before installing one, even if it comes from a Top Developer tag.
Yes it does take more battery. So install the apps which you are going to use.
AlanDS said:
Yes it does take more battery. So install the apps which you are going to use.
Click to expand...
Click to collapse
Can you please back this up? Used storage doesn't increase battery usage.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
It totally depends on applications you have installed
If you have hundreds of application and they don't autostarts or have no sync function and just occupying storage, it won't drain battery, in usual course i do have 150 user application installed but hardly it even drains recordable juice except some of it requires auto refreshing and sync
Sent from my GT-N7100 using xda premium
There are application that can disable the apps you've installed from auto starting or running in the background. Usually the biggest culprits are the free ad supported apps that tend to randomly call up even when the phone is in sleep mode. There are many ways to stop it from happening.. If you can pay for ad free app then go for it otherwise a lot of 3rd party apps will allow you to disable those features. I don't understand why someone would install 200-300apps in the first place when you only end up using less than a quarter of those. I guess its that "you never know when you're gonna need it" habits.
Sent from the Rabbit Hole
There are a number of apps which do run in the background, even when you don't manually run them first. Applications can register receivers to trigger at various events (such as boot-up complete, call ended, etc) and complete tasks in the background, or register themselves as services. You can check these with an autostart app, or I use ROM Toolbox (https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro&hl=en - there is a free version available too).
On top of that, apps can also run scheduled tasks which can wake the phone out of deep sleep in standby, which can cause additional battery drain, through either CPU or network usage.
Unlike iOS which kills most background apps after a couple of minutes, Android apps can run indefinitely in the background, unless of course they are killed by memory management first.
I wanna receive better battery stats since I'm only getting 1-2 ost ,and I read that greenify is recommended ,well is it useful ??
Sent from my Galaxy Nexus using xda app-developers app
It keeps apps from waking the device and running unnecessarily in the background. I use it for Maps so it isn't eating up resources and draining my battery. Technically you should see better battery life if you hibernate the right apps with Greenify.
t1.8matt said:
It keeps apps from waking the device and running unnecessarily in the background. I use it for Maps so it isn't eating up resources and draining my battery. Technically you should see better battery life if you hibernate the right apps with Greenify.
Click to expand...
Click to collapse
I know to hibernate maps/GPS but do you have any apps I should also hibernate
Sent from my Galaxy Nexus using xda app-developers app
t1.8matt said:
It keeps apps from waking the device and running unnecessarily in the background. I use it for Maps so it isn't eating up resources and draining my battery. Technically you should see better battery life if you hibernate the right apps with Greenify.
Click to expand...
Click to collapse
I toggle the location services in the settings when I am at a familiar place. Saves a LOT of battery.
Sent from my Galaxy Nexus GSM
used it but now choosing to use 2x battery
can't really say it's better or not but from my view 2x battery have better options like screen filters and such
but like all batteries (obviously) depends relatively on usage
powerkid39 said:
used it but now choosing to use 2x battery
can't really say it's better or not but from my view 2x battery have better options like screen filters and such
but like all batteries (obviously) depends relatively on usage
Click to expand...
Click to collapse
You're comparing apples to oranges there. Those two apps don't even remotely do the same thing. Greenify's sole function is to shut down those pesky apps that think they deserve to run services in memory when they really aren't needed. Many apps/games do this. It's gotten to the point of stupid and, imho, is the fatal flaw in Android. They need to implement something to end this behavior.
Say you install ten games and each one is coded to run a service in the background (either to collect data about you or just because they can). Now your phone is sluggish and runs like crap because you no longer have enough memory left over for your phone to cache previously opened apps. So now when you open an app, it has to load from scratch. And now when you open an app, android has to knock out one of those services to make enough room to load that app. But guess what, that service is coded to auto reload itself and to make room for itself, so it must knock out a different service to make room for itself. Now that service that just got knocked out wants to reload but has to knock out another one... and the cycle goes on and on. Services that aren't needed reloading and Android kicking the others out of memory in an endless battle for memory.
Now this scenario only happens in low memory situations, but it really doesn't take that many needless apps running services in the background to put the Galaxy Nexus in this situation.
This is why you see so many Android phones that just run like garbage even when they have a good processor and memory. And this is one of many reasons for crappy battery life.
Sent from my Galaxy Nexus using Tapatalk 2
Android experts all say task killers are unnecessary (except to kill a misbehaving app) because the android OS is designed to use all the available memory and it costs as much battery power to maintain a memory containing nothing as memory containing something. So emptying memory by killing an app just causes android to immediately load something else (or the same app) back into memory.
My question therefore has to do with apps like Greenify, which "hibernate" apps till they are actively called. Is hibernation just another name for removing apps from memory and therefore as counter productive as task killers? I can see the subtle differences but they seem minor compared to the similarities.
What do the experts who know android say? I don't know enough to really know.
Any studies to show an advantage (battery, etc.) in using an app like Greenify vs not?
Thank you.
Jeff
For me, I tried all of those battery saver app, none of them actually significant save battery, plus they use up some of your ram. I read somewhere says that android itself can handle battery save plus manage apps in it memory just fine.
Nam Huy Linux http://namhuy.net
Task Killers use extra CPU cycles and can lead to loss of battery life.
I'm not sure about hibernation but I think it just prevents apps from being started automatically when the device is powered on and therefore saves battery and CPU.
Sent from my Nexus 7 using xda premium
Anderson2 said:
Android experts all say task killers are unnecessary (except to kill a misbehaving app) because the android OS is designed to use all the available memory and it costs as much battery power to maintain a memory containing nothing as memory containing something. So emptying memory by killing an app just causes android to immediately load something else (or the same app) back into memory.
My question therefore has to do with apps like Greenify, which "hibernate" apps till they are actively called. Is hibernation just another name for removing apps from memory and therefore as counter productive as task killers? I can see the subtle differences but they seem minor compared to the similarities.
What do the experts who know android say? I don't know enough to really know.
Any studies to show an advantage (battery, etc.) in using an app like Greenify vs not?
Thank you.
Jeff
Click to expand...
Click to collapse
I have to agree with task killers not really being necessary, especially with newer devices, for the most part. I've had and used ATK for years now and use it on occasion but by no means do I use it regularly. The only app I use that ever misbehaves is Google Voice, while deleting a bunch of texts it will on occasion hang up and need to be killed. The two scenarios I use it regularly is before playing "some" games and usually before using VLC before watching a video. When using VLC I will often pause, skip, rewind, fast forward and on occasion use slow motion to further investigate any milk shake, if it's looks to be worth my time. In those two scenarios I believe it does make a difference. Other than that I don't use ATK and it's not needed.
As for Greenify, I've been using it since it was first released and I won't hesitate to admit to being a big fan. You don't want to use it for everything. Any widgets that need to update or apps you want to get notifications from I would not hibernate, even though it is supposed to work with some notifications I personally have never tried it. Having said that I have a ton of apps that I do hibernate with Greenify. System and user apps. And if I remember right I believe the auto-hibernate works at some point in time after your screen has shut off. If I'm wrong someone please correct me! I also have to say that using Greenify is part of the reason I routinely see 1-2% battery use during 9-10 hrs of standby and I have Never had a problem with wakelocks. I think it is unrealistic to attribute good battery life to any one specific configuration setting or app, it's going to be a combination of multiple things. And I think Greenify is part of the puzzle along with wifi use, wifi configuration, LTE use, display brightness, sync frequency, location settings and so on. My N7 is not a good example because it gets used very hard almost everyday and I still typically see 5-7+ hrs of screen on time and as high as 9 but rarely. My N5 also typically between 5-7 hrs sot, often as high as 9 and once saw 11 hrs of screen on time. And... I actually have screenshots. I would say give Greenify a try, used properly you will see a benefit. For what it's not worth, just my two cents!
Thank you. I've also used Greenify for a long time but don't know enough to really evaluate its effectiveness. I have not however dared to use it for system apps because of the warnings.
Which system apps have you hibernated without problem?
Anderson2 said:
Thank you. I've also used Greenify for a long time but don't know enough to really evaluate its effectiveness. I have not however dared to use it for system apps because of the warnings.
Which system apps have you hibernated without problem?
Click to expand...
Click to collapse
Google search, chrome, keep, news and weather (don't really use), youtube. Google play books, games, movies, music, Google+ and Hangouts I have disabled because I use other apps but those could very well be hibernated except for Google+ and Hangouts (notifications).
I missed currents, email, korean keyboard, google pinyin, iWinnIME, google play magazines which I have disabled also but any of those could be hibernated.
Thank you.
Anderson2 said:
Thank you.
Click to expand...
Click to collapse
No problem. I just realized I show google search in my list of apps I hibernate but I should mention that I don't use google now. If you do you probably want to leave google search alone if you want google now notifications.
That's fine. I don't use Google search, google plus, Hangouts, etc. Etc. Either but was afraid to disable them because of potential problems when the next system update comes. How do you disable them? Titanium b/U or something else?
(I'm rooted).