I have read that taskkiller is not necessary on Android as the OS will kill off running apps when it needs memory - what are people's thoughts on this?
Hmmm...I read somewhere (maybe on here) heard if the App is coded properly that when not in use it will be background so not take up memory.
Not too knowledgable, but in that case would imagine they are acting like a windows service so will be taking up memory somewhere....so perhaps what I read was nonsense
Well, I have stopped killing tasks and guess what - I notice no difference at all! Hero is just as speedy (or slow depending on how you wanna look at it!).
Interesting!
Killing truly idle applications wont have significant effect. There are however many applications which appear idle, but still drains resources. An example is Peep, the twitter client, which starts automatically even if there's no twitter account configured. It has some frequent checks that put load on the CPU and thus helps drain power. Killing it adds many hours of standby time.
i'm not using any task manager/killer, did try them for a couple of days, can't really tell the difference, except i was wasting time constantly killing apps :/
suisen said:
i'm not using any task manager/killer, did try them for a couple of days, can't really tell the difference, except i was wasting time constantly killing apps :/
Click to expand...
Click to collapse
Ditto... surely there is no need as the OS will kill a unused app if it needs the memory ??? I don't have any problem running any apps one after the other... they just load.
The only lag I get is while the handset starts a widget update, once they are started everything runs slickly.
I found it a little slicker without taskiller. Especially in the use of big apps like copilot or documents2go. It seems to be managing itself pretty well.
Yep. I can report that the phone is working very well without Taskkiller. I have uninstalled it now.
If you are reading this, give it a try for a few days and tell us what you think. You may be pleasantly surprised...
Ditto - I've removed taskiller so I don't get tempted. Surprise surprise, no problems, no lag, etc. Now mostly this is due to removing the clock and people widget, but memory management seems fine after playing many different games and browsing the internet.
I think a benefit to doing this is that you aren't going to get and bizarre problems caused by killing system processes by accident - ie you won't miss alarms or stop receiving email alerts.
Hey there all, this is 2 Bunny again. As many of you know, back in October I had to make an emergency switch from Windows Mobile to Android. As you've all read in my posts, it has been a very "mixed" experience with both some impressive and downright pathetic discoveries, but one of the worst things about it (beside the complete inability to sync) is the way that Android closes your programs whenever it feels like it instead of letting you close them. Sometimes I'll be browsing the internet in Opera Mobile and I'll switch over to the email program briefly to check something, when I hold down the "home" key and pick OM from the list of recently used programs, it starts it all over again, and I know for a fact I didn't choose "exit".
Sometimes I'm glad Android "cleans up" (like if I back out of a program that has no "exit" option) because it saves me the trip to the task manager later, but is there any way I can prevent it from closing stuff I'm actually still using?
Thanks.
- 2 Bunny
kainppc6700 said:
Hey there all, this is 2 Bunny again. As many of you know, back in October I had to make an emergency switch from Windows Mobile to Android. As you've all read in my posts, it has been a very "mixed" experience with both some impressive and downright pathetic discoveries, but one of the worst things about it (beside the complete inability to sync) is the way that Android closes your programs whenever it feels like it instead of letting you close them. Sometimes I'll be browsing the internet in Opera Mobile and I'll switch over to the email program briefly to check something, when I hold down the "home" key and pick OM from the list of recently used programs, it starts it all over again, and I know for a fact I didn't choose "exit".
Sometimes I'm glad Android "cleans up" (like if I back out of a program that has no "exit" option) because it saves me the trip to the task manager later, but is there any way I can prevent it from closing stuff I'm actually still using?
Thanks.
- 2 Bunny
Click to expand...
Click to collapse
Try ZDBox application.....maybe you'll find a solution to that problem!!
jimsiv said:
Try ZDBox application.....maybe you'll find a solution to that problem!!
Click to expand...
Click to collapse
Interesting. So that can prevent it from closing certain programs?
- 2B
kainppc6700 said:
Interesting. So that can prevent it from closing certain programs?
- 2B
Click to expand...
Click to collapse
Yup. I've been using it for a long time. As far as I know you can set certain apps to Protect so they're not closed.
ZaIINN said:
Yup. I've been using it for a long time. As far as I know you can set certain apps to Protect so they're not closed.
Click to expand...
Click to collapse
Great, I'll give that a try and letcha'all know if it works.
- 2B
Update - well it seemed promising, but it didn't work unfortunately. ZDbox said it was "protected", but that didn't stop Android's hammer of making people's lives miserable.
Any ideas if I might be doing something wrong in ZDBox (I did turn off the notification thing) or if there is other software I might be able to try?
Thanks.
- 2 Bunny
If rooted try V6 supercharger script. Just do a search on XDA. It rewrites your phones memory management to increase multitasking capabilities by reconfiguring your ram. If not rooted, your choices are severely limited by existing software to hardware configurations preset by the android operating system and the device manufacturer. Go through all of your programs and clear out all of your allocated cache memory. Freeing up ram memory may help your multitasking needs.
Sent from CDMA V6 SC GNexus w/Liquid & Franco.kernel
As mentioned by others, the most likely culprit is high memory utilization. However, there are a few other reasons that may contribute to the application closing down. Android "ranks" applications from 1 to 5 (where 5 means it is the first to get killed) based on certain criteria. Because xda won't let me link to it (I'm a new user), I have posted them at the bottom of my message.
Chances are, you are seeing the behavior in numbers 4 and 5. The fact that Android keeps applications in a least-recently-used list means that if you have applications which you just accessed but appear to have closed when you come back to them, then, once again, it is likely you are using a lot of memory that the phone is aggressively trying to keep cleaned up.
Although, it is possible that a small number of your problems are based on poorly implemented applications since the developer website states "If an activity implements its lifecycle methods correctly, and saves its current state, killing its process will not have a visible effect on the user experience..."
1. Foreground process
A process that is required for what the user is currently doing. A process is considered to be in the foreground if any of the following conditions are true:
It hosts an Activity that the user is interacting with (the Activity's onResume() method has been called).
It hosts a Service that's bound to the activity that the user is interacting with.
It hosts a Service that's running "in the foreground"—the service has called startForeground().
It hosts a Service that's executing one of its lifecycle callbacks (onCreate(), onStart(), or onDestroy()).
It hosts a BroadcastReceiver that's executing its onReceive() method.
Generally, only a few foreground processes exist at any given time. They are killed only as a last resort—if memory is so low that they cannot all continue to run. Generally, at that point, the device has reached a memory paging state, so killing some foreground processes is required to keep the user interface responsive.
2. Visible process
A process that doesn't have any foreground components, but still can affect what the user sees on screen. A process is considered to be visible if either of the following conditions are true:
It hosts an Activity that is not in the foreground, but is still visible to the user (its onPause() method has been called). This might occur, for example, if the foreground activity started a dialog, which allows the previous activity to be seen behind it.
It hosts a Service that's bound to a visible (or foreground) activity.
A visible process is considered extremely important and will not be killed unless doing so is required to keep all foreground processes running.
3. Service process
A process that is running a service that has been started with the startService() method and does not fall into either of the two higher categories. Although service processes are not directly tied to anything the user sees, they are generally doing things that the user cares about (such as playing music in the background or downloading data on the network), so the system keeps them running unless there's not enough memory to retain them along with all foreground and visible processes.
4. Background process
A process holding an activity that's not currently visible to the user (the activity's onStop() method has been called). These processes have no direct impact on the user experience, and the system can kill them at any time to reclaim memory for a foreground, visible, or service process. Usually there are many background processes running, so they are kept in an LRU (least recently used) list to ensure that the process with the activity that was most recently seen by the user is the last to be killed. If an activity implements its lifecycle methods correctly, and saves its current state, killing its process will not have a visible effect on the user experience, because when the user navigates back to the activity, the activity restores all of its visible state. See the Activities document for information about saving and restoring state.
5. Empty process
A process that doesn't hold any active application components. The only reason to keep this kind of process alive is for caching purposes, to improve startup time the next time a component needs to run in it. The system often kills these processes in order to balance overall system resources between process caches and the underlying kernel caches.
PAIN IN THE REAR TO DO THE INSTALLATION Reply
That sounds promising. I'll give it a try and letcha'all know if it works or not.
Just FYI, the installation is a HUGE pain. I messed around with it for a solid hour and a half, maybe two hours to get it up and running, so it better work or I'm out the time I put in and I'd have anotherwise useless something running/taking up space.
Thanks.
- 2B
Looks like I wasted my time. Not only did that not have any effect, it seems to have permanently brought back the useless update nagscreen - a million thumbs down to "supercharger" for being the most useless waste of an hour and a half of my life.
Not to be mean here, but did anyone try the suggestions before posting them?
Guess I'm off to the recovery menu again to try and get rid of the nagscreen, that is if I'm not booted out first.
- 2B
SAVE THE PROGRAMS Reply
Any updates on this?
Thanks.
- 2B
Any updates on this?
Thanks.
- 2 Bunny
FORCE CLOSE Reply
Any updates on this?
- 2B
STILL FORCED CLOSED Reply
Any updates on this?
- 2B
Yes.
Install V6 Supercharger and bulletproof Opera Mobile/Mini.
Are you sure you had it installed and it was running actually?
Your kernel needs to support init.d scripts.
If not, prior to installing V6 create init.d folder in /system/etc/ and grant it all the permissions. Download Script Manager app and set V6 scripts from init.d folder to run at boot.
I hope it works.
Simple Workaround:
Download MinFreeManager app and tweak your min free settings according to your RAM. More RAM = More Agressive Settings. Google android minfree and you'll find how to.
Boy124 said:
Yes.
Install V6 Supercharger and bulletproof Opera Mobile/Mini.
Are you sure you had it installed and it was running actually?
Your kernel needs to support init.d scripts.
If not, prior to installing V6 create init.d folder in /system/etc/ and grant it all the permissions. Download Script Manager app and set V6 scripts from init.d folder to run at boot.
I hope it works.
Simple Workaround:
Download MinFreeManager app and tweak your min free settings according to your RAM. More RAM = More Agressive Settings. Google android minfree and you'll find how to.
Click to expand...
Click to collapse
I'll tell you what, I screwed around with that "supercharger" for so long, I really don't want to look at it again (I think my ROM might actually have it included). All I know is that it did install because when I restarted the device, I got the stupid update nagscreen back.
I am going to try that "MinFree" program though and report back what I figure out. So far it seems to be working, so this could be promising, but I'll keep ya'all posted.
- 2B
BULLET Reply
kainppc6700 said:
I'll tell you what, I screwed around with that "supercharger" for so long, I really don't want to look at it again (I think my ROM might actually have it included). All I know is that it did install because when I restarted the device, I got the stupid update nagscreen back.
I am going to try that "MinFree" program though and report back what I figure out. So far it seems to be working, so this could be promising, but I'll keep ya'all posted.
- 2B
Click to expand...
Click to collapse
Update. Looks like "MinFreeManager" isn't doing its job either.
Any other ideas? Anyone? I'll even try the "BulletProof" thing.
- 2B
I use the browser and check email while browsing without any problem returning to the browser. In your first post you said you use the home button. Doing that will close the browser. Use the back button to return to the browser.
Sent from my LG-P500 using XDA
fdaconta said:
I use the browser and check email while browsing without any problem returning to the browser. In your first post you said you use the home button. Doing that will close the browser. Use the back button to return to the browser.
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Actually, the home key leaves it running. I usually check right away, and at first it continues running; it's when you're not watching that it takes it right out from under you. It might just be this build of Android.
Is anyone else running Gingerbread and having this problem?
Does anyone know of any kind of solution?
Thanks.
- 2 Bunny
PROGRAMS CLOSING BY THEMSELVES Reply
Any updates on this?
Thanks.
- 2 Bunny
This post is about getting great battery life for the average, every-day user. It is not inclusive or exhaustive, so it will reference other posts. What is talked about is what I did, the user-level stuff, explained in a more user-friendly fashion than some of the more diagnostic-focused posts out there (still invaluable reading, though).
Note: I originally wrote this for the Hyperdrive ROM on GS4 thread, but I've had many requests to break it out into a separate [GUIDE] post and update it here for ease of subscribing and discussing. Also note, that therefore, this should be considered sort of Android 4.2 specific and may not apply to all versions of Android. So, here it is. I'll link the old post to here shortly.
Preface
Okay, I'm writing this because I believe that @sbreen94 @eschelon @iceandfire @Imoseyon @TrevE and @ktoonsez all have done awesome, awesome dev work from which I have benefited. There are SO many other devs, as well. These are some from whom I directly benefit, regularly, daily, or did at one time. If you want a name added to the list, I'll update my post. This post, though, is sort of Hyperdrive specific since @sbreen94 has added a few tweaks that make it SO EASY to address some major offenders of ... sucking the life out of your battery.
Why do I mention this? Because does anyone truly think that a ROM dev or Kernel dev, compiles code, puts it on their device, runs it for days/weeks, validates it with experienced, community testers, and then releases it, all the time thinking, "well, the battery life sucks, but I'm gonna push this out anyways."??? NO! So, then, WHY does every ROM/Kernel thread have post after post, of people saying “Hey, I loaded this ROM and my battery life sucks now.” Do you REALLY think it's the ROM/Kernel?
We also have those that think they have no apps loaded, or “only 3, 4, 5, or whatever number” - so it can't POSSIBLY be an app! If you think that, then do this, Wipe your Dalvic Cache, reboot your phone, and tell me the number of apps it says Android is now optimizing. That is the number of apps you have on your phone, not the number you personally loaded. That means each one of those is a potential culprit for causing battery drain.
BTW – at one time or another, I've probably been guilty of every of the above mindsets. So, I'm not calling YOU out, if YOU are reading this and think that I am. I'm just saying, it's not the ROM, and it's not the Kernel.
Background Reading
The below two threads had everything I needed to know to get started increasing my battery life. I, probably like many reading this, had for a long time followed along, envious of screenshots of people getting those 3, 4, 5+ hours of screen time, and day+ or days of battery. After reading these threads, doing the analysis, and basically just changing some app settings, I can now get the 4-5 hours of screen and full day of battery out of my GS4. Kernel doesn't have much effect, ROM doesn't have much effect, most all of them do what they're designed to do, and do it well. Sweet.
In the next section, Real World Battery Saving, I'll explain what I did, so if you want to skip the background stuff, you can.
These two threads contain basically everything you need to know about improving battery life. They have great details about diagnostics, what's what, etc. What many threads/posts like these sometimes lack, is, the straight-forward answer of “This is what you should do after analyzing x, y, z.” That's what's in the Real World Battery Saving section of this post.
[APP][2.1+][09 Sept. - V1.14] BetterBatteryStats
[GUIDE] Wakelocks Definition and how to prevent them
Read those threads, and do some analysis, and the majority of what I've posted below you'll figure out on your own. If you just wanna jump into fixing things without the above understanding, then just go to the next section. Provided there aren't any seriously misbehaving apps on your phone, you should be able to get great results without becoming a Wakelocks, Alarms, Deep Sleep, etc., expert.
Real World Battery Saving
For those of you that don't want to read too much more about the analysis of apps, etc., to get to better battery life, here's the summary of what's in the section below:
Minimize screen brightness
Disable all Push
Disable all system sounds (Dialing keypad tone, Touch sounds, Screen lock sound, Haptic feedback)
Install Xposed Framework and use:
Greenify Donation (Experimental features)
NLPUnbounce
Greenify any app that you don’t need to notify you of things - Note: If you pay for Greenify Donation and use Xposed, you can still get alerts from any GCM-enabled app (look for the blue GCM icon next to apps in Greenify)
Greenify every Google app (except Voice and Hangouts, both of these may significantly delay or prevent proper message notification, despite being GCM-tagged in Greenify, and they seem to behave okay on their own)
Uninstall GMail (use any other client with IMAP)
Disable all GPS (enable as necessary upon use) Note: I really don't do this anymore. With apps under control with Greenify, I just leave my GPS on and let apps use it when necessary. I have noticed that GPS will stay active during Airplane mode, though, so as not to have my phone dead upon landing, I generally always turn off GPS when in the air.
Disable the autostart of almost everything, at almost any time, on an app-by-app basis. AutoStart Check delivers in spades for this function, at no charge, though, I recommend donating (as I do for all apps here, I have either donated or bought them all, Lux, Greenify, etc.). Note: With Greenify, I no longer worry as much about stopping apps/services from auto-starting. I do still use Xposed plugin BootManager to prevent certain apps from starting, mostly just to increase boot speed (or so I feel like it might). I don't use AutoStart Check at all anymore.
Continuing on with details...
Note: Required app functionality. You don't have to use these if you know another way to do it. But, to accomplish what I recommend, there are 3 key apps you absolutely must have. I'm not going to explain them all in great detail, as there are plenty of other places that go into great depth on all of them. The 3 essential apps that I use to increase battery by more than 50% are:
Lux (Pro - I'll explain why below)
Greenify
Xposed Framework
In general:
You want your phone to sleep when not in use.
You want apps to not be doing anything when you're not using them.
You want your screen to only ever be as bright as it needs to be, no brighter (including, off when you're not looking at it).
Display Brightness
Lux – Get it here Lux Auto Brightness
Thread here: [APP][2.3+] Lux Auto Brightness 1.51
Update: After posting this, and getting a lot of questions/comments that Lux doesn't really rock like I think it does, I checked it out on a phone without using the Pro version. Okay, I agree, the free version really doesn't deliver. It doesn't poll right, and you can't really set your custom lighting scenarios and lock them in correctly without using Lux Pro. Basically, if you want to save tons of battery life without a lot of constant manual intervention, you're going to have to purchase Lux.
Screen uses more battery than anything. You can do all kinds of things to address this, for me, Lux has been a (battery) life saver. It's easy, it reads the ambient light in your environment. Open its dashboard, slide the slider to the brightness that works for you at that lumen level, hold down the link button in the middle, and there you have it, locked in for those conditions. You only have to do this a few times and you now have custom lighting profiles that fit your eyes' needs under all conditions. Note, sometimes, when waking the phone in the sun, you'll have to wait a few second for Lux to activate and bring the screen up bright enough. This means that Lux is behaving extremely well and not constantly running in the background (Wakelocks) sucking up battery.
Applications
For applications, firstly, if you have an app that has Push available, disable it. Nothing keeps your phone from deep sleep like a Push-enabled application. If you can't wait 5/10/15 minutes for updates, then you can't achieve maximum battery life. Sorry, I don't make the rules of Android app-physics, I'm just sharing them with you.
In my mind, I think of applications in categories. I guess, I have 4 now.. I started with 2. Point being, there are different apps that behave differently so you treat them differently with different solutions for extending your battery life.
Category 1 Apps I want running and want notifications from them. When configured properly, they generally do not misbehave and eat my phone's battery
Category 2 Apps that I cannot seem to control, regardless of their settings, but I still want to be able to use, but getting regular or instant updates from them is not that important to me
Category 3 Apps behave without any special settings and without any Greenification. Just load them, run them, use them, don't worry about them. I haven't seen them cause any sort of bad battery drain.
Category 4 Apps are apps you DO think are vital/desirable (to you) but cannot control their battery consumption with mere settings. For those, only the developer can help you, or you have to accept the battery loss that app's notifications bring with it.
Category 1 apps, well-behaved when configured properly, along with the settings I used to make them behave well and still deliver their updates to me.
Corporate E-mail: Built-in e-mail, TW or AOSP. Disable Push for any account, use Priority settings for 15 minute interval on work days. Non-prioirty times set to 1 hour.
Maildroid: For every account, you must do this separately, under Preferences / Advanced – Connection Management, select first account, the rule (usually 1. Default), Connection Management, Wi-Fi: Close connection when I exit mailbox, GPRS, 3G: Close connection when I exit mailbox, Interval to check mail: 10 (or to your liking), Check Mail Periodically. Go back, go back in (confirm settings were kept, I've seen it not keep them and have to do this a few times, per account). Alternatively, select Let device sleep, and it will only check when you wake it up. Go back to Accounts and select your next account, do this again. You must do this for all accounts listed.
Note about all mail client: If you have more than 2 or 3 e-mail accounts, Maildroid and all other IMAP clients I have tried get moved to Category 2. Basically, they start to keep enough Wakelocks that they keep the phone from going into Deep Sleep as much as I'd like. This is a difference of 1-3% per hour at idle, but if you're looking for 4+ hours screen time, then you need to Greenify them and just check e-mail manually.
Viber: Just make sure your Wi-Fi sleep policy is set to device and not constantly on, and Viber seems to behave pretty well as far as messaging apps go, but it's probably going to make the Category 4 list, as well.
WhatsApp: This one appears to work well (better than Viber from a wakeup perspective) and not have any sort of unnecessary battery drain. I generally don't use it any more since I feel they bait-and-switched me from free to fee, but I dethawed it to check it out. If anyone sees problems with it, let me know.
Category 2 Apps. These apps were keeping my phone awake at night with nightmares, and no amount of settings changes seemed to fix the problem altogether. If you have a solution of app settings that would move these to Category 1, please let me know. When I say solution, I mean, you've done the Wakelock and Alarm analysis and they're eliminated or minimized. For these, I Greenify them all. None of these apps' updates are so important to me that I can't just check up on them when I have a moment.
Facebook: I didn't play too much with settings here, but it seems that if FB is running, it's keeping your phone awake. I Greenify it and check it manually. I'd be interested in hearing if someone knows settings that will get it to not wakelock / alarm constantly.
FB Messenger: I love the chat heads and ease of use, but it's a big-time battery offender. I keep it installed and Greenified. If I get messages, I'll see them when I open the FB app, and when I reply, FB Messenger takes over and I use it normally until the conversation is done. At some point, Greenify takes over, and FB Messenger's battery damage is contained.
Google Maps: You can't fix this thing. No amount of settings will stop it from going after your phone. I love its functionality, though, so, unlike many guides that say uninstall it, I say Greenify it.
Google Goggles: A fun one to have around sometimes, but it will also chew up battery. Just Greenify it.
Google Play Store: There are plenty of apps and Android wakeups for the Play Store. I'm not worried about missing an update notification, or whatever else it might be sending my way. Greenifying it seems to have fixed the Google Play Services Alarms issue.
Almost everything else: If it's an app that doesn't need to provide you updates, just Greenify it. Why not? One of the first things I do after loading a new ROM and getting most of the configuration stuff done, is I go into Greenify, and I add every mundane app on my phone, for example: Vonage, Adobe Reader, Airbnb, Angry Birds, APN Manager Pro, Google Authenticator, Barcode Scanner, Citibank, Craigslist, Google Drive, DroidVPN, ES Task Manager, Fast Charge, FasterGPS, Flashlight, GasBuddy, GNotes, GooManager, GPS Status, Hyatt, Lucky Patcher, Office Document Viewer, Office Suite, OpenTable, Opera Classic, PayByPhone, SoundHound, Squeezebox, Street View, etc. My list goes on... You aren't going to lose their functionality, they don't suddenly stop when in use, and you don't have to worry about them ever causing problems you weren't thinking you had to look for.
Category 3 Apps that behave, no special settings, no Greenification
Alarm Clock Xtreme: I don't use the built-in Alarm Clock. I like all the features of Xtreme, it's never failed me, and it doesn't show up in Wakelock/Alarm offenders lists in my analyses.
Google Voice: Of all the Google offenders, this isn't one of them in my experience, and I love its features.
Lux: Nuff said.
WhosCall: A caller-ID type app. I don't love it, but haven't gone looking for something better, that said, it hasn't popped up on my battery draining radar, so that's a plus.
Hangouts: While I don't care for the new Google Talk, it sure doesn't seem to be a battery offender, and I use it to chat regularly.
Category 4 Apps are anything that would have gone into Category 2, but you want them as active as possible.
Line: In Settings, Chats and Voice Calls, I turn off Receive Voice Calls. This made Line tolerable (as in, way better), but it's still a Category 4 until (if ever) its devs reduce its number of wake-up Alarms
Exchange Services: Despite Corporate E-mail being a Category 1 now, Exchange Services is still keeping my phone awake more than I'd like. Nothing I can do here, though, so I live with it.
Viber: As stated, it's not a terrible offender, but it's still on the radar for keeping my phone awake. We'll see what their “any day now” major update brings. (someone remind me to update this post if I haven't post-Viber release)
Have Your Google and Your Battery
The Xposed module NLPUnbounce is awesome. I've given it a nice test, and it seems to perform excellent. NLPUnbounce allows you to use Google services as usual, including Android Device Manager features, like Remote Locate and Remote Wipe, but not do the crazy, crippling and disabling of Google Play Services like many guides have you do. It changes the polling rate of NLP (Network Location Provider) to something VERY reasonable. I haven't modified any of its settings, and it's reduced average idle consumption from ~4-5% to ~2-3%. I tested locating my phone and ringing it, all working.
Automatically Launching Applications
Not so much needed anymore. Just make sure you Greenify. For the "big things", use Xposed BootManager module.
AutoStart Check - Get it here https://play.google.com/store/apps/details?id=ro.rbrtoanna.autostartcheck&hl=en
Fire up AutoStart Check (or any other autostart configuration app), set your view to Group by App, and expand every one of them and look at just how many different places some of these apps are set to start. Your Gallery starts with your Camera? ES File Explorer starts when you mount media or remove bad media? Facebook fires itself up just because you plugged in your phone. Google Goggles sees fit to start with every picture you take - and of course, it will then either drain your battery trying to get a GPS signal while your GPS is off, or drain your battery by getting one – fail. If you use S Health, it starts when your time zone changes – that's important. YouTube, seriously, YouTube – change accounts, mount media, connect power, every boot – you obviously need YouTube to fire up. Yeah.
A note here, read some guides on these before turning off too many system services. For example, don't disable messaging, bad idea, bad things happen. But most of this stuff, turn it off. You aren't killing your ability to use it, you're just making sure it isn't turning on all the time. If you've also Greenified well, after using any of these, they'll hibernate in the background without you having to worry.
Disable all system sounds (Dialing keypad tone, Touch sounds, Screen lock sound, Haptic feedback)
This is explained in some of the other threads, but, if you don't want to do the research, basically, the background services in Android that manage these things keep your phone awake. Turn them all off, battery life goes up.
Media Scanner
@sbreen94 included in the Hyperdrive Tweaks tools a one-button solution to turning it off. If it's drainging your battery, or you just want to make sure it doesn't, go click the button. This thing is better than the Staples button!
I'm sure there's probably a more generic way of stopping/managing Media Scanner. Someone please let me know and I'll update this section!
Battery Save Apps
I used to be madly in love with 2x Battery. Others swear by JuiceDefender. I guess if you don't/won't want to take the time to optimize apps and Greenify, they might be beneficial. You know what I found, though, when I started down this path? Some of the biggest offenders of Wakelocks and keeping my phone from sleeping when it should, are these battery saving apps!!! I now get BETTER battery life WITHOUT 2x Battery!
Short thoughts on this and example concepts of what's going on...
It may sound counterinterintuitive, but it seems most of the apps are so vigilant they keep your phone awake when it could be sleeping. And the vigilance isn't so necessary when you've properly configure things to not need this sort of overactive management of things. I'd love to see 2x Battery properly manage my data connection for me, without Wakelocks, but what's to say that the app trying to sync when the data is off won't now stay awake with new Wakelocks trying to get out to the internet? There's a cascading effect of whatever approach you might choose, so try to think about that, and keep it in mind when you look at your Wakelocks and your Alarms and you do your analysis.
The End
Okay, so I think that's aobut it. I may have forgotten some things, and I know this is a long post. But, this leaves very little excuse for people to blame ROMs/Kernels, while at the same time giving you the straight-forward, real world answer to battery savings 101. Yes, there are apps and details I left out. If anyone thinks of some obvoius ones, just let me know and I'll happily update this post.
You don't have to analyze any statistics or logs to do this. The principles are sound, and you'll see a dramatic improvement in battery if you don't already get a day of usage and 3.5 to 4.5 hours of screen time on your GS4. You just make some of these relatively straight-foward, user-level, common-sense changes.
If these changes don't give you the results you'd like, then do the analysis work in the threads linked above and find out what's the real culprit. Profit, enjoy, be happy. And remember... It's not the ROM.
Thanks for the thread, Bill. Here are a few of my questions/comments:
Regarding Lux, I used it for a few days, but could never seem to get a setting that worked for me. Whether using periodic updating or any of the other modes, the brightness level always seemed to adjust either too frequently or too slowly. Then I started experimenting with night mode and it got even worse. Do you have any suggestions to a quick and simple setup that won't drive me insane?
In terms of greenifying different apps, I always make sure that my SMS app and alarm clock are not greenified, and I don't use any widgets on my homescreen, but what about apps like Better Battery Stats, Boot Manager (for Xposed) and Automagic (flow chart based automation app) that are monitoring events and automating my phone? Will Battery Stats stop recording data is I set it to hibernate? Will Automagic miss a trigger I've set if it's hibernating? I would like to greenify EVERYTHING that I know won't cause any issues, but notifications aren't the only thing happening in the background that I want to allow.
Then, expanding on the autostarts, I mentioned that I use the Xposed module Boot Manager. This doesn't seem able to handle all of the situations that you described, like apps being launched based on SD card state, network state, etc. Am I missing something in this app or will I need to go another route to get all the options you've descibed?
Regarding the SD media scanning, my current ROM is a very debloated lean and mean stock Touchwiz ROM that doesn't have a native way to disable media scanner like the AOSP ROMs I used to run. Is there an app that does ONLY this, as I prefer to use dedicated apps rather than giant monsters which can control tons of things I don't need.
Anyway, I already do a lot of the practices you're advocating here, but I'm always looking for ways to do things in a more efficient or streamlined way. Using Greenify, keeping the stock clock speeds, and making sure that nothing is syncing (I keep backgruond sync disabled, but use an Automagic flow to enable it periodically throughout the day and then turn it back off again), keeps my battery life pretty solid. Add to that Deep Sleep Battery Saver which automatically turns off my connections when the screen is off, but will periodically turn them back based on my preferences, keeps my battery level pretty much steady wheen the phone is idle.