It might not be immediately obvious that a phone is in wakelock for long periods. By all appearances, the screen is off and it seems to be asleep like it should be. One clue that something is going wrong is excess heat generation. When the CPU is cranked up instead of in deep sleep, the device might be noticeably warmer than usual when you pick it up. You’ll need to do a little detective work, though, and that’s where the apps come in handy. You’ll have to dig a little deeper in order to sort out the exact cause of your shortened battery life. The best app for this is BetterBatteryStats. The developer posts free beta builds on the XDA forums, but it’s also for sale in Google Play. Rooted users see more information in the app, but you can still get some data on wakelocks with almost all devices.<\/p>\n One quick and easy way to watch for a phone that won’t sleep is to use an app like System Monitor to track CPU clock speed. This app breaks down CPU activity as a percentage. Unless you’ve been using the device almost constantly, \u201dDeep Sleep\u201d should be the largest part of the chart. If not, you’ve probably got a misbehaving app or system process.<\/p>\n More often than not, the root of your problem will be some app you installed. The easiest way to deal with the issue is to leave the offending app or game uninstalled, but maybe you actually want to use the app despite its battery sucking behavior. In that , you need a way to end the process safely. Android has a built-in way of hibernating processes, and you can easily trigger it with an app called Greenify.<\/p>\n Simply use Greenify to identify the problematic apps, and hit the hibernate button after you’re done using them. Greenify works best with root access\u2014it can handle all this in the background. For non-rooted devices, you can use the in-app button or a widget to manually trigger the hibernation routine.<\/p>\n Android has gotten much better at managing background processes in the last few years. Anyone who has used Google’s platform since the early days can tell you how bad things used to be when \u201ctask killers\u201d were a necessity. Even though Android as a whole isn’t subject to the same horrible Dell 312-0625 Battery<\/span><\/a> life issues, the wrong combination of apps can still break Android\u2019s elegant process management scheme.<\/p>\n Conventional wisdom used to be that you should open the multitasking interface and kill any application you\u2019re not using to save battery life, and unfortunately this superstition still persists. But Android knows how to manage background tasks, and swiping apps out of the multitasking interface only closes the foreground process. If an app is indeed causing issues, it’s usually the background<\/em> process that’s doing it. This sort of micromanagement will only waste time.<\/p>\n The stock Android battery use menu can be helpful, but it only tells part of the story. Most apps show up here because you’re actually using them a lot\u2014that’s to be expected. This menu merely shows you the system process and app packages that are using juice, but the ‘Awake’ and ‘Screen on’ lines are the most important. If you have a lot more awake time than screen on, something might be keeping your phone from sleeping. This is called a wakelock<\/em>, and it’s the number one enemy<\/em> of your battery life.<\/p>\n","protected":false},"excerpt":{"rendered":"![\"hp-537626-001-battery\"](\"http:\/\/www.aussiebatt.com\/blog\/wp-content\/uploads\/2014\/06\/hp-537626-001-battery.jpg\")
<\/a><\/p>\n![\"dell-312-0594-laptop-battery\"](\"http:\/\/www.aussiebatt.com\/blog\/wp-content\/uploads\/2014\/06\/dell-312-0594-laptop-battery.jpg\")
<\/a><\/strong><\/h2>\nWakelocks and misery<\/strong><\/h2>\n