I've been getting quite a few messages as of late, after sharing battery results for a particular ROM or kernel, asking how I'm achieving such good battery results, so I've decided to update this aged thread that's become buried. Let me start by saying that those who complain that Xposed itself causes a heavy amount of drain are either naive with a particular module they're using causing the drain or are just part of an unlucky few who's phone doesn't like Xposed that runs fine for so many others. A second thing to note, if you spend a lot of time in an area that has pretty poor reception (especially orange/red under the battery details), it'll be hard for you to get exceptional battery life; poor reception simply drains the battery quite a bit. Lastly, watching a lot of YouTube videos or playing games often will never let you get amazing battery life, especially with the GPU this phone uses. While I will watch the occasional movie trailer on YouTube and watch a few Facebook videos, I don't watch TV episodes or play games much at all. I do, however, stream music quite often.
With that said, let's get started. The goal here is to limit how much your phone stays awake with the screen off, so that battery life is primarily being saved for the times you're actually using your phone.
The Basics
Wi-Fi:
» Make sure to have "Keep Wi-Fi on during sleep" set to Always (Settings > WiFi > 3dot menu > Advanced)
Display:
» Turn Adaptive brightness off (Settings > Display)
» Turn Ambient display off (a notification sound is enough for me, but can use this if you like your phone's screen to turn on)
Location:
» Most people will turn this off, and if you don't use location much you may as well. There's a misconception that it's a big battery hog while it's on, but that's only marginally true. It's a hog if you allow apps to use it in the background and not just when you want to use it with Maps, Chrome, Speed Test, etc. If you keep the apps in check, location is typically only used when you want it to be.
» Do turn Google Location History off at the bottom
» Turn Wi-Fi scanning and Bluetooth scanning off (3dot menu > Scanning)
Moto App:
» Under Actions, turn Approach for Moto Display off. While you may keep this on for convenience, it seemed that the phone's screen would turn on much more than I would ever intend it to. Given that apps would randomly be open after the phone has been in my pocket, it seems the screen may consistently turn on while in your pocket.
» All other Actions, options under Assist, and Voice listening are good to use with negligible battery consumption!
» NOTE: I personally keep Wi-Fi, Bluetooth, and location on at all times. Each of them consume negligible amounts of battery when not in use, and it's more convenient for me to just keep them on. I especially keep location and Bluetooth on for convenience when driving in the car. I do intend to find/write some Tasker scripts to control turning them on/off, though that'll come at a later time. If you rarely use Bluetooth, turn it off to same some juice.
Disable apps not needed
There's quite a few apps and language packs that could actually be disabled entirely. You can disable apps by going to Settings > Apps. Below is my list, so make sure to not disable something you use. Disabling the app(s) just means one less app to have to worry about misbehaving in the background. What's available will be dependent on if you're running stock or a custom ROM, as the ROM may already have some of these already removed.
» Android Live Wallpapers
» Android System WebView
» Audio Effects
» Bubbles
» Cloud Print
» Connect
» Docs
» Email (I use Gmail)
» Emergency Alerts
» Exchange Services
» Help
» Google Hindi Input
» Google Japanese Input
» Google Keyboard (I use Swiftkey)
» Google Korean Input
» Google Pinyin Input
» Google Play Movies & TV
» Messaging (if you have an alternative installed)
» MotoCare
» MotoCareInt
» Motorola Checkin
» Motorola Migrate
» Motorola Update Services
» Print Spooler
» Sheets
» Slides
» Tags
» Talkback
Now to the fun stuff..
Downloads
Better Battery Stats: HERE
Xposed: Installer and framework HERE (For MM use sdk23 arm64)
Amplify: HERE (You'll want to make a small donation to enable everything)
Greenify: HERE
Power Nap: Download from Xposed repository
*Note: Amplify, the best parts of Greenify, and Power Nap require the use of Xposed!
Have everything downloaded and installed? Good. Let's begin.
Amplify
Amplify is going to take care of how often wakelocks, alarms, and services can run on your phone. You'll want to make a small donation ($2) to the developer in order to unlock the full potential of the app. You'll want to search for each of the things below and limit them as specified in parentheses. A lot of credit for a majority of the list goes to THIS thread, with what actually applies to our phones, and the rest coming from my own testing.
Wakelocks:
» *net_scheduler* (7200)
» ConnectivityService (7200)
» GCoreFlp (7200)
» LocationManagerService (40000)
» NetworkStats (800)
» NfcService:mRoutingWakeLock (7200)
» NlpWakeLock (86400)
» NlpCollectorWakeLock (86400)
» RILJ (800)
» SyncLoopWakeLock (7200)
» ANYTHING you find with "facebook" it in, set it to 999999
Alarms:
» com.android.internal.telephony.data-stall (86400)
» com.android.providers.calendar.intent.CalendarProvider2 (43200)
» com.android.vending/com.google.android.finsky.services.ContentSyncService (7200)
» com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana.Mqtt_Wakeup (43200)
» com.facebook.orca.database.ACTION_ALARM (43200)
» com.facebook.push.mqtt.keepalive.KeepaliveManager. ACTION_INEXACT_ALARM.com.facebook.katana (43200)
» com.google.android.apps.gsa.sidekick.shared.a.a.UPDATE_CALENDAR_ACTION (7200)
» com.google.android.apps.sidekick.SCHEDULED_REFRESH (7200)
» com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS (999999)
» com.google.android.gms.gcm.ACTION_CHECK_QUEUE (43200)
» com.google.android.gms.gcm.HEARTBEAT_ALARM (7200)
» com.google.android.gms.icing.proxy.action.SMS_CHANGED (3600)
» com.google.android.gms/.checkin.EventLogService$Receiver (86400)
» com.google.android.intent.action.GCM_RECONNECT (43200)
» com.google.android.intent.action.SEND_IDLE (43200)
» com.motorola.slpc.ALARM_STOWED (7200)
» android.appwidget.action.APPWIDGET_UP-DATE (3600)
» android.content.syncmanager.SYNC_ALARM (43200)
Hit the notepad looking icon at the top left and apply the following:
» ALARM_WAKEUP[0-9]{4,}
Services (deny the following):
» Anything with "facebook" in it
» com.google.android.gms/.ads.jam.NegotiationService
» com.google.android.googlequicksearchbox/com.google.android.apps.gsa.sidekick.main.TrafficIntentService
» com.motorola.moto/com.motorola.checkin.AnalyticsService
Greenify
Most of you should already be accustomed to Greenify, which will hibernate apps from working a lot when you have your screen off and aren't using your phone. What makes Greenify really useful is its ability to push your phone into Doze mode quickly after you turn the screen off, also mostly disregarding the motion sensors, unlike stock MM. Some settings to use:
» Working Mode: Boost
» Shallow Hibernation: Enabled
» Aggressive Doze: Enabled
Go to Aggressive Doze > White list and enable the following apps (change the filter from Not optimized to All apps):
» Amplify
» Greenify
» Power Nap
Xposed-based Features to enable:
» Wakeup Timer Coalescing
» Block App State Abuse
Power Nap
Power Nap is essentially a lot like Greenify, except rather than having to create a list of apps to hibernate, you create a list of whitelisted apps that are ok to trigger wakelocks/alarms. While Greenify will allow apps to do their thing when you turn the screen on and then hibernate them when you turn the screen off, Power Nap keeps these apps from wasting cpu cycles in the background while using the phone. It pairs nicely with Amplify, because we can either block apps entirely by not whitelisting them, or we can whitelist them and allow Amplify to control how often the apps are allowed to collect data or push a notification. You'll want to make sure to whitelist any programs that you don't want to be blocked (i.e. Amplify, Greenify, your messaging app, etc.).
» Turn on Endurance Mode
Suggested apps to whitelist (tap the words "Endurance Mode")
» Amplify (do it!)
» Android System (required)
» BetterBatteryStats (if you have it)
» Google Play Services (required)
» Google Services Framework (required)
» Greenify
» JavaTcmdHelper
» Photos (if you use Google Photos)
» Spotify (or any music program you wish to still launch with Moto Drive Assist)
» Tasker (if you use Tasker)
» Textra (or whichever messaging app you use)
» Xposed Installer (do it!)
Better Battery Stats
BBS, if you don't already use it, provides a lot more information than Android's battery stats can ever give you. As a first gauge of how much battery your phone consumes when not in use, you should either charge your phone to 100% and unplug it before you go to sleep at night, or within the app you can set a custom reference point before you go to sleep. When you wake up, check what % was used per hour. With everything outlined above, I only lose .1%/hr. Anything between 0-.5% is acceptable, with there being a lot of factors involved (ROM, kernel, Wi-Fi and/or Bluetooth on, receiving texts, an alarm set, etc.). BBS will also help you determine what app(s) are often waking your phone up (check to see which fire a lot of alarms, as those apps have an obvious need of having some of its alarms put in check via Amplify).
While the tweaks above will have the biggest control over how your phone behaves with battery life, there are two other factors to consider.
ROMs
Odexed? Deodexed? AOSP? CM? Each ROM will have its own changes that could affect battery life. Play with each one with customization in mind first and battery second (with reason). Don't care for customization and want the smoothest experience? Go with the stock odexed. Want some customization with a minimal hit to smoothness? Go with a deodexed ROM. Care more for speed/fluid and features over battery life? Go with an AOSP or CM based ROM.
Kernels
A ROM may be great with its smoothness and list of features, but often the kernel can really be the culprit of how a ROM is with battery life. Kernels built for the stock ROM have often had the best battery life, while those on a AOSP/CM ROM experience less battery endurance due to the kernel alone.
My setup
ROM: TruPure
Kernel: Frankenclark
Kernel settings: See This post
Results: 7hr 7m SOT with 2d 2hr off the charger
Reserved
Great work! Thanx!
how is the battery draining during gaming?
Can you post powernap apk? Closed beta is not accepting anyone.
Sent from my XT1575 using Tapatalk
knince said:
how is the battery draining during gaming?
Click to expand...
Click to collapse
I don't really play games, but nothing here will affect gaming performance or battery life while doing so. This guide is primarily to make it so your phone is barely draining while not using the phone.
patt2k said:
Can you post powernap apk? Closed beta is not accepting anyone.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Really? That's weird considering how long it's been in a beta w/o issues. I'll look into doing so tonight after work.
Tonight I'll be adding some extra stuff in post 2. I'm also testing out the modified stock kernel available in the Android development forums. It's optimizations and added governors/schedulers should further help battery life.
I have a quick question, curious if anyone else had this problem. I used Power Nap for a while, then it kept freezing my Moto Display. I'm almost positive that I had Moto Display whitelisted. It would literally just freeze and not let me do anything, and I would have to restart the phone. I eventually turned off Power Nap, and never had the Moto Display freeze again. Do you think this was because I didn't properly whitelist it? Does anyone use Power Nap + Moto Display? If so, do you have any issues?
It didn't freeze it all the time, it was random and sporadic.
EDIT: Also, thank you so much OP for taking the time to do this post!! I Amplified a lot of things based on your thread, and I plan to try AppOps as that will hopefully help my device not be kept awake. I would love to keep my location on with minimal drain when it's not in use. Thanks again!
Excuse me OP do you think mobile radio fix can help too or doesn't matter
Sent from my XT1575
juancaperez2000 said:
Excuse me OP do you think mobile radio fix can help too or doesn't matter
Sent from my XT1575
Click to expand...
Click to collapse
I notice too that the radio take a lot a battery even with no wifi or data.. Do we have a fix or should we wait MM ?
chris23445 said:
I have a quick question, curious if anyone else had this problem. I used Power Nap for a while, then it kept freezing my Moto Display. I'm almost positive that I had Moto Display whitelisted. It would literally just freeze and not let me do anything, and I would have to restart the phone. I eventually turned off Power Nap, and never had the Moto Display freeze again. Do you think this was because I didn't properly whitelist it? Does anyone use Power Nap + Moto Display? If so, do you have any issues?
It didn't freeze it all the time, it was random and sporadic.
Click to expand...
Click to collapse
How often would you have issues with Power Nap and Moto Display? I ran days w/ using it along with Power Nap w/o issues, until I decided Moto Display wasn't worth it. Make sure all the Moto stuff in the OP are whitelisted in Power Nap (when I get time I'll be digging into what services pertain to what).
juancaperez2000 said:
Excuse me OP do you think mobile radio fix can help too or doesn't matter
Click to expand...
Click to collapse
The MobileActiveRadioFix module for Xposed actually just fixes the bug associated with how the numbers are reported. There's no actual bug (afaik) with the radio itself, just how things are reported. I kind of forgot about it until you mentioned it, but I do have it installed myself.
I have google play services battery drain issue: https://www.dropbox.com/s/wsa0ic6d8cs8c59/Screenshot_2015-11-17-13-49-14.png?dl=0 what to do?
rehpyc said:
How often would you have issues with Power Nap and Moto Display? I ran days w/ using it along with Power Nap w/o issues, until I decided Moto Display wasn't worth it. Make sure all the Moto stuff in the OP are whitelisted in Power Nap (when I get time I'll be digging into what services pertain to what.
Click to expand...
Click to collapse
It honestly seemed to happen every day or two. It was so often I couldn't stand it. But I restored Power Nap from Titanium Backup and I did have Moto and Moto Display and all that whitelisted. But I added some new stuff to the Whitelist. "Moto Display System Process", " Motorola Services" and "Motorola Services Main". I also added a few more. I basically added most Motorola apps just to be safe. I'll report back if I don't have the issue at all this week.
I wanted to let you know I followed your guide, I didn't block as much of Google Services in Amplify cause I'm actually a fan of Google showing my location map and all that. But my battery life is much much better already. Both on screen and off. Also, I found out through AppOps a ton of apps were using my location when it was on. I navigated for 30 minutes yesterday and barely lost 10% battery, maybe even less. Before, I would have easily lost at least 20%. Thanks again for everything!!
Fjjd
rehpyc said:
While many of you are probably happy with your battery life, there seems to be a large number of people who are shocked at how short of time their battery lasts through the day despite Motorola giving us a rather sizable one with our phones. A lot of the time, battery life is being lost when the phone is not even being used due to your installed apps constantly waking the device to perform some actions. The goal is to limit how much your phone stays awake, so that battery life is primarily being saved for the times you're actually using your phone. Below are some apps and settings that I and many others use to help maximize battery life. The spoiler link below are just some examples of what you can achieve with using these settings. For those that are also getting great battery life, please share any additional things you do that aren't listed here so that I may add them for others to try out.
1hr 40m of SOT over ~11hr with good signal (extrapolating to 100% battery use would be ~6.5hr of SOT over ~1d 20hr)
4hrs of SOT over 2d 5h 30m with pretty bad signal 20% of the time
The Basics
Wi-Fi:
» Under Advanced Wi-Fi make sure "Scanning always available" turned off
» Make sure to also have "Keep Wi-Fi during sleep" set to Always
Display:
» Turn Adaptive brightness off
» Turn off Attentive Display (I personally leave it on and have experienced only a small hit on battery life)
» Under Screen notifications use None (a notification sound is enough for me, but can use this if you like your phone's screen to turn on)
Location:
» Most people will turn this off, and if you don't use location much you may as well. I personally have it turned on and set to High Accuracy. There's a misconception that it's a big battery hog while it's on, but that's only half-true. It's a hog if you allow apps to use it in the background and not just when you want to use it with Maps, Chrome, Speed Test, etc. In sections below we'll be making sure to keep location use in check so that it can always stay on and barely consume any battery.
» Do turn Google Location History off at the bottom
Moto App:
» Under Actions, turn Approach for Moto Display off. While you may keep this on for convenience, it seemed that the phone's screen would turn on much more than I would ever intend it to. Given that apps would randomly be open after the phone has been in my pocket, it seems the screen may consistently turn on while in your pocket.
» All other Actions, options under Assist, and Voice listening are good to use with negligible battery consumption!
» NOTE: I personally keep Wi-Fi, Bluetooth, and Location on at all times. Each of them consume negligible amounts of battery when not in use, and it's more convenient for me to just keep them on (especially Bluetooth for the car). I do intend to find/write some Tasker scripts to control turning them on/off, though that'll come at a later time.
Disable apps not needed
There's quite a few apps and language packs that could actually be disabled entirely. You can disable apps by going to Settings > Apps and side scrolling to ALL. Below is my list, so make sure to not disable something you use.
» Android Live Wallpapers
» Android System WebView
» Bubbles
» Cloud Print
» Connect
» Docs
» Email (I use Gmail)
» Emergency Alerts
» Exchange Services
» Help
» Google Hindi Input
» Google Japanese Input
» Google Keyboard (I use Swiftkey)
» Google Korean Input
» Google Pinyin Input
» Google Play Movies & TV
» Messaging (make sure to have an alternative installed)
» MotoCare
» MotoCareInt
» Motorola Checkin
» Motorola Migrate
» Motorola Update Services
» Print Spooler
» Sheets
» Slides
» Tags
» Talkback
Now to the fun stuff..
Downloads
Xposed: Installer and framework HERE (For Lollipop use sdk22 arm64)
Amplify: HERE (You'll want to make a small donation to enable everything)
AppOpsXposed: HERE
Power Nap: HERE
Better Battery Stats: HERE
Have everything downloaded and installed? Good. Let's begin.
Amplify
Amplify is going to take care of how often wakelocks, alarms, and services can run on your phone. You'll want to make a small donation ($2) to the developer in order to unlock the full potential of the app. You'll want to search for each of the things below and limit them as specified in parentheses. A lot of credit for a majority of the list goes to THIS thread, with what actually applies to our phones, and the rest coming from my own testing.
Wakelocks:
» *job*/com.facebook.katana/com.facebook.analytics2.logger.LollipopUploadService (999999)
» ConnectivityService (7200)
» NetworkStats (800)
» NfcService:mRoutingWakeLock (7200)
» LocationManagerService (40000)
» RILJ (800)
» StartingDockService (7200)
» SyncLoopWakeLock (7200)
Alarms:
» ALARM_WAKEUP_ACTIVE _COLLECTOR (86400)
» ALARM_WAKEUP_ACTIVITY_DETECTION (86400)
» ALARM_WAKEUP_CACHE_UPDATER (40000)
» ALARM_WAKEUP_LOCATOR (86400)
» ALARM_WAKEUP_BURST_COLLECTION_TRIGGER (86400)
» android.app.backup.intent.RUN (86400)
» android.appwidget.action.APPWIDGET_UPDATE (3600)
» android.content.syncmaster.SYNC_ALARM (43200)
» android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED (7200)
» com.android.internal.telephony.data-stall (86400)
» com.android.providers.calendar.intent.CalendarProvider2 (43200)
» com.android.vending/com.google.android.finsky.services.ContentSyncService (7200)
» com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana.Mqtt_Wakeup (43200)
» com.facebook.push.mqtt.keepalive.KeepaliveManager. ACTION_INEXACT_ALARM.com.facebook.katana (43200)
» com.google.android.gms/.checkin.EventLogService$Receiver (86400)
» com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS (999999)
» com.google.android.gms.gcm.ACTION_CHECK_QUEUE (43200)
» com.google.android.intent.action.GCM_RECONNECT (43200)
» com.google.android.intent.action.MCS_HEARTBEAT (43200)
» com.google.android.intent.action.SEND_IDLE (43200)
Alarms (deny the following):
» com.facebook.katana/com.facebook.analytics2.logger.LollipopUploadService
» com.facebook.katana/com.facebook.analytics.service.AnalyticsService
» com.google.android.gms/.ads.jam.NegotiationService
» com.google.android.gms/.ads.social.GcmSchedulerWakeupService
» com.google.android.gms/.analytics.service.PlayLogMonitorIntervalService
» com.google.android.gms/.analytics.service.RefreshEnabledStateService
» com.motorola.moto/com.motorola.checkin.AnalyticsService
Power Nap
Power Nap is essentially a lot like Greenify, except rather than having to create a list of apps to hibernate, you create a list of whitelisted apps that are ok to trigger wakelocks/alarms. It pairs nicely with Amplify, because we can either block apps entirely by not whitelisting them, or we can whitelist them and allow Amplify to control how often the apps are allowed to collect data or push a notification. You'll want to make sure to whitelist any programs that you don't want to be blocked (i.e. Amplify, Greenify, your messaging app, etc.)
» Turn on Endurance Mode
Suggested apps to whitelist
» Amplify (do it!)
» Android System (required)
» BetterBatteryStats (if you have it)
» Google Play Services (required)
» Google Services Framework (required)
» Greenify
» JavaTcmdHelper
» Moto
» Moto Actions
» Moto Display
» Moto Display System Process
» Moto Voice
» Motorola Modality Services
» Motorola Modem Service
» Motorola Notification
» Motorola One Time Init
» Motorola Services
» Motorola Services Main
» Motorola Slpc System
» Photos (if you use Google Photos)
» Spotify (or any music program you wish to still launch with Moto Drive Assist)
» Tasker (if you use Tasker)
» Textra (or whichever messaging app you use)
» Wakelock Detector Free (if you have it)
» Xposed Installer (do it!)
AppOpsXposed
AppOpsXposed will let us control what permissions each install app has. Do you want many apps to have the ability to check your location, keep your phone awake, or read your contacts and texts? Didn't think so. While we want to limit their permissions for the sake of privacy, it'll also keep these apps from performing these duties in the background with the phone trying to sleep. The list below is what I have installed and how I limit those apps, so yours may be different. 2 main things to limit for apps would be location and keep awake. Not all apps will have this permission or show "Never used," so you needn't worry about those.
» In the settings, go to Hacks and check Fix OP_WAKE_LOCK
Location off:
» Amazon
» Connect
» ES File Explorer
» Facebook
» Fitbit
» Google Play Services (do it)
» Google Play Store (do it)
» Hangouts
» MotoCare
» Slickdeals
» Starbucks
» Textra (or check your messaging app)
Keep Awake off:
» Amazon
» Chrome
» Connect
» Emergency Alerts
» Facebook
» Fitbit
» Gmail
» Google App (do it)
» Google Play Services (do it)
» Google Services Framework (do it)
» Hangouts
» Motorola Checkin
» Motorola Update Services
» Snapchat
» Starbucks
» Textra (or your messaging app)
The results/screenshots found at the top of the post have been on Motorola's stock build and kernel. I'll be trying out custom kernels and/or ROMs to see if results are better on them. I'm sure a custom kernel alone could improve results.
Click to expand...
Click to collapse
What are your battery stats with this setup?
dlepp22 said:
What are your battery stats with this setup?
Click to expand...
Click to collapse
Click the button in his post, the "click to show content" button. It literally shows all of his battery stats.
Okay so I am having an issue after following this guide. Keep in mind I was actually already using amplify first before I read this based on the same threat you reference so I just essentially added powernap into the equation and apops exposed. Everything is great except smart lock location no longer functions and I can seem to figure what it is that's causing it. Smart lock on body detection and Bluetooth detection work fine so its specifically to do with location bit I cant seem to figure it out. Any idea?
timde9 said:
Okay so I am having an issue after following this guide. Keep in mind I was actually already using amplify first before I read this based on the same threat you reference so I just essentially added powernap into the equation and apops exposed. Everything is great except smart lock location no longer functions and I can seem to figure what it is that's causing it. Smart lock on body detection and Bluetooth detection work fine so its specifically to do with location bit I cant seem to figure it out. Any idea?
Click to expand...
Click to collapse
Sorry for the late response.. final holiday projects at work keeping me busy I'll try using smart lock myself and see if I have any issues.
For those that may not have received their invite to the Power Nap test group yet, it seems you may be waiting quite a while. I updated the info in the OP of how to still obtain the app.
If you aren't happy with the battery stats you're getting after these changes, I'll soon be adding stuff to post #2 to help assist you on your way in determining the app(s) sucking up your battery. I've also recently flashed AICP ROM, so I'll be able to do some testing of how things go on a non-stock build.
Is Greenify even necessary if you're already using Power Nap and Amplify?
As far as I can tell, any app that you would hibernate with Greenify is automatically blacklisted by Power Nap as long as you don't actively "whitelist" it. Is that accurate, or am I missing something?
how is the battery life after MM update?
Related
✭[GUIDE][26-07-2016]Extreme Battery Life Thread(Greenify+Amplify+Power Nap)✭
On the Portal News on 06-06-2015.
Battery life has been a prime concern for all users around the world.Each day people try different methods to improve upon their battery life.
Here I come up with a blended guide that includes the latest apps and Fixes' to help improve your android battery experience.
This is based on my experiments on attaining a better battery life.For any queries,reply within the thread.
Use BetterBatteryStats and Wakelock Detector to acquire stats.You can also use Ampere to measure the current and get notifications when the device gets fully charged.
Requirements
1.Root
2.Xposed Framework
3.Greenify
4.Amplify
5.AppOpsXposed
6.PowerNap
Index
1.Basic Settings-Post #2
2.Greenify-Post #3
3.Amplify-Post #4
4.Power Nap and AppOpsXposed-Post #5
5.Frequently Asked Questions and Known Issues-Post #6
Featured on @tkdsl TK's Youtube Channel
If anyone is interested in supporting my work and wants to buy me a beer,log in to your PayPal and use my donation mail to donate.Select the purpose as "Services" Any donation is appreciated
Lets Start with a few basic settings.
DisplayDisplay brightness is an important factor in battery life.The more brighter the screen is,the more juice it drains.So keep the brightness under control.Using automated brightness is not adviceable.Try manually adjusting the screen brightness.Using dark wallpapers(on AMOLED display) can help you save some bit of juice.
Cell NetworkThis is simple stuff,but results in noticeable improvement in battery life.Toggle LTE/3G to 2G while not in use.(While on WiFi).You can use Smart Network to switch between networks.
For devices that support Fast Dormancy(Read Here) can disable it to save some juice on 3G.(Link to disable Fast Dormancy for Xperia Devices)
WifiEven if your wifi is off,the phone searches for signal.To switch off this feature,go to Settings > Wifi > Options(Top right corner) > Advanced >Scanning always available(Off).
LocationAnother juice sucker in Android-Location Services.You can turn it off while not in use.That saves a lot off juice.You can also set the location to 'Device Only" in settings.
Navigate to Settings->Location->Menu->Scanning->Turn off "Wi-Fi Scanning" and "Bluetooth Scanning"
These are the basic stuffs one must look into before complaining about their battery.
Is your battery gauge lying to you?:Take a look at this link.This thread explains why you get sudden drain after waking up from sleep.Many people should've noticed that the battery drains faster after keeping the phone idle for some time.It is very informative and is worth a read.
Xposed FrameworkXposed Framework is essential as it is required fo proper working of Greenify,Amplify and PowerNap.If you're running android 4.0.3+ you'll be able to run Xposed Framework on your device.It has an initial Lollipop support.Xposed Installer is required for functioning of the apps mentioned in the guide.
Downloads:
Xposed Installer 4.0-4.4.x
Xposed Framework 5.0.x-6.0.x
Xposed 5.1.x-6.0.x(TouchWiz)
Find the support for the framework in Xposed for Lollipop and Xposed for MarshMallow threads.
GreenifyThanks to @oasisfeng for such an awesome app.The latest 2.9.2beta update brings the feature to disable the motion scanning in doze.
You can use Greenify to hibernate apps that are not in use.You can use Donation Package of Greenify which includes lots of features.Once you have a Donation Package with you,you need to activate the Greenify Xposed Module in Xposed.Once done,enable the Boost mode and Experimental Features.See attached screenshots.
Downloads:
Greenify
Donation Package
Greenify the apps that eatup battery by running in background(Refer BBS)
Below are some of the major drainers:
Browser
Facebook
Facebook Messenger
Google+
Hangouts
Hike
Instagram
Maps
UC Browser
Marshmallow Settings
@oasisfeng introduced a new feature in Greenify 2.9 beta 1 which disables the "Motion Sensing" of doze.This can be achieved by turning ON the "Aggressive Doze" in Greenify settings.Unlike the default behaviour of doze,the device won't be kicked out of doze when a motion is detected.This helps in complete utilization of "doze".All you have to do is to enable the "Aggressive Doze" option in Greenify settings.See the attached screenshots.
Apps to be whitelisted in doze are being tested.You can also contribute in testing
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Aggressive Doze
There's no need to hibernate all the apps.Do not Greenify Dialer or Messaging apps
AmplifyAmplify is a genius in handling wakelocks and alarms.It is also capable of blocking services.Amplify is the best battery saver I've come across.It is a must have app for all droids running Xposed.
You'll need a donation package to block wakelocks and alarms.
Downloads:
Amplify
Limit the following:
Alarms
Alarms(Allow every 600 seconds)
com.android.internal.telephony.data-stall
Alarms(Allow every 1800 seconds)
com.oasisfeng.greenify.CLEAN_NOW
Alarms(Allow every 3600 seconds)
android.appwidget.action.APPWIDGET_UPDATE
Alarms(Allow every 7200 seconds)
android.content.syncmanager.SYNC_ALARM(delays sync)
Alarms(Allow every 10800 seconds)
android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
com.facebook.common.executors.WakingExecutorService.ACTION.ALARM.com.facebook.katana
com.google.android.apps.hangouts.CLEANUP_DB
com.pushbullet.android/.gcm.GcmFixReceiver
com.android.server.action.NETWORK_STATS_POLL
com.diune.pictures.intent.action.MEDIA_CHECK
LocationManagerService
Alarms[LOCATION](Allow every 41400 seconds)
ALARM_WAKEUP_LOCATOR(com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR)
ALARM_WAKEUP_CACHE_UPDATER
ALARM_WAKEUP_BURST_COLLECTOR(com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLLECTOR)
com.google.android.gms.location.fused.GPS_ALARM_BALANCED_ACCURACY
ALARM_WAKEUP_ACTIVE_COLLECTOR
ALARM_WAKEUP_PASSIVE_COLLECTOR
ALARM_WAKEUP_BURST_COLLECTION_TRIGGER
com.google.android.intent.action.SEND_IDLE
ALARM_WAKEUP_ACTIVITY_DETECTION
com.google.android.location.reporting.ACTION_UPDATE_WORLD
Alarms(Allow every 93600 seconds)
android.app.backup.intent.RUN
com.google.android.gms/.checkin.EventLogService$Receiver
com.google.android.gms/.checkinCheckinService%Receiver
Wakelocks
Wakelocks(Allow every 800 seconds)
WakefulIntentService[GCoreUlr-LocationReportingService]
RILJ
NetworkStats
Wakelocks(Allow every 3600 seconds)
WeatherUpdateService
Wakelocks(Allow every 10800 seconds)
SyncLoopWakeLock(delays sync)
*net_scheduler*
GCoreFlp
Icing
Wakeful StateMachine: GeofencerStateMachine
NfcService:mRoutingWakeLock
wake:com.pushbullet.android/.gcm.GcmService
SyncService(Package: Push Bullet)
ai(Package: Push Bullet)
ae(Package: Push Bullet)
AsyncService
Wakelocks(Allow every 41400 seconds)
NlpWakeLock
NlpCollectorWakeLock
LocationManagerService
Config Service Fetch
Wakelocks(Allow every 9999999 seconds)
*job*/com.facebook.katana/com.facebook.analytics2.logger.LollipopUploadService
JobSchedulerHack-com.facebook.analytics2.logger.LollipopUploadService
UploadServiceLogic-com.facebook.analytics2.logger.LollipopUploadService
*job*/com.facebook.orca/com.facebook.bugreporter.scheduler.LollipopService (com.facebook.orca.Messenger)
*job*/com.facebook.katana/com.facebook.bugreporter.scheduler.LollipopService (com.facebook.katana.Facebook)
Services
Services(Block/Deny)
com.google.android.gms.analytics.AnalyticsService
com.google.android.gms/com.google.android.location.internal.GoogleLocationManagerService(Location Service)
com.android.gms.Feedback.FeedbackService(Breaks Play Games)
com.android.gms.ads.AdRequestBrokerService
com.google.android.gms/com.google.android.location.network.NetworkLocationService(Location Service)
com.google.android.location.geofencer.service.GeofencerProviderService(GPS Service)
com.google.android.gms/com.google.android.location.copresence.service.ProximitySettingInjectorService
com.facebook.katana/com.facebook.analytics.service.AnalyticsService
com.facebook.orca/com.facebook.analytics.service.AnalyticsService
com.android.cellbroadcastreceiver/.CellBroadcastAlertService
com.android.cellbroadcastreceiver/.CellBroadcastConfigService
NB:I don't use Location Service.That's why I've disabled the location Services.If your'e using Location service,do not disable the services with location and GPS tag)
Alarms(REGEX Blocking)
ALARM_WAKEUPxxxxx
CONTEXT_MANAGER_ALARM_WAKEUP_xxxxx
Procedure(Screens attached)
Open Amplify.
Select Alarms from the menu.
Tap the list icon on the top right corner
Tap + button on top.
Add the following code to 'Enter Regex to match'
Code:
ALARM_WAKEUP[0-9]+
Code:
CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{3,}
[*]Set the interval to 9999999 seconds.
Screenshots:
Regex Blocking
Power NapPower Nap for Xposed is the SONY's stamina mod for non-Sony devices.When your screen is off, Power Nap maximizes your device's deep sleep time by stopping services, alarms and wakelocks from waking the device when the screen is off.You can get notification from the apps you've whitelisted.
NOTE:In order to download the app you need to join the alpha testers community in Google+ here and opt to become a tester.Then you'll be able to download and run the module
NB:XDA Thread for PowerNap is closed down due to lack of activity from the developer.
Set the Endurance Mode to Always ON.
You can use Power Nap along with Greenify and Amplify for a better sleep time.You have whitelist both Greenify and Amplify for proper working of both the modules.
If you need certain apps to run in background while screen off(eg:Instant Messengers),you have to whitelist them in Power Nap.
List of apps to be whitelisted:
Amplify
AndroidSystem
BetterBatteryStats
Cyanogenmod System
GooglePlayServices
Google Services Framework
Google Account Manager
Greenify
Greenify Donation Package
Trebuchet
Xposed Installer
Screenshots:
AppOpsXposedAppOps is a permission manager in android.There are various versions of AppOps available in the PlayStore.I recommend the one linked with Xposed.(You can also use CyanogenMod Privacy Guard).
Downloads:
AppOpsXposed
You can use Privacy Guard to disable some permissions of Google Play Services and Google Services Framework
Navigate to Settings->Hacks->Check FIX OP_WAKE_LOCK
Disable the following Permissions of Google Play Services using AppOps
OP_ALARM_WAKEUP/Wake Up
Keep Awake
Disable the following permissons of Google Services Framework
Keep Awake
Use Auto Start Permission of AppOpsXposed to disable apps on Boot.Make sure you do not disable crucial System Apps.Disable unwanted user apps that trigger on Boot.
Frequently Asked QuestionsSearch before posting:If you are having any issues after following the GUIDE,use the "Search" function in the thread and see if someone had the issue and is already solved.This saves your time and mine too
1.Reporting Logs
I recommend using BetterBatteryStats to report logs and dumps.Here's how you should report dumps in this thread.I request to follow the exact method so that it is easy for me to debug issues.
Note:Update BBS to latest version from the XDA thread.
Charge your device to 100 and unplug the device from the charger.
Keep WiFi/Mobile Data ON.(Leave the sync settings as per your usage pattern)
Leave it idle for atleast 6 hours(Do not turn on the screen during these period).
Choose "Unplugged" as a start reference and "Screen On" OR "Current" as stop reference(Refer Screenshots)
Pull a TextDump File from BetterBatteryStats.(Refer Screenshots)
You'll find the dump in the root of your SDCard.Post the dump in the thread.
Use
hide[/ hide] tags while posting screenshots.This makes the thread look a bit more clean and easy to read.
Readme for BBS:
*Make sure you have disabled the Enable while Charging option in BBS->Settings->Advanced
Screenshots:
2.What if I don't find all the wakelocks/alarms in Amplify as listed in the OP?
It'll take a day or two for the alarms/wakelocks to populate in Amplify.So report back after a day or so.
As the apps and services running depends on each person's setup you may not find all the wakelocks/alarms listed in the thread.
Known Issues
Delayed PUSH Notifications:If you encounter any delayed Push Notification from any app after using this thread,try PushNotificationFixer(PNF).If the problem persists,do report in the thread
SystemUpdateService Wakelock:If you are affected by SystemUpdateService wakelock issue.Use my fix here
For more easy fix for the same issue.See here
MobileRadioActive Bug:If AndroidOS the top consumer during idle(as shown in the inbuilt battery stats) and the 'Mobile Radio Active' shows high numbers,you can use this Xposed Module to fix the issue.
Android Marshmallow only
WiFi battery drain reported:High WiFi drain,even while it is turned off in Settings.
Refer:https://code.google.com/p/android/issues/detail?id=189018
Workaround:
Go to Settings>Location>Scanning(top right)>Wifi Scanning ( disable it ) & Bluetooth Scanning (disable it as well)
Credits to @Primokorn for sharing.
---------------------
Credits
@chamonix for BetterBatteryStats
@rovo89 @romracer and @C3C076 for Xposed Framework
@oasisfeng for Greenify
@cryptyk for Amplify
@caspase for AppOpsXposed
@waylaidwanderer for Power Nap
@andQlimax for PNF
Thanks to my bud @airlessproject for helping me to debug issues.
Special thanks to @orville87 for assisting me in the thread.
Thanks to @tkdsl for his cover
Special Thanks For Donations
@Ramer
@Stupifier
@-m3ta-
@beeshyams
@gunawanrusli
@Culateralligator
@LiL_Assassin
@injectx
@bkkzak
@Robati
@Razertje
@koekoek91
ChangeLogs
28-01-2016
Update wakelock/alarms lists
i)7200seconds->10800seconds
ii)40000 seconds->41400 seconds
iii)84000 seconds->93600 seconds
Added Facebook bugreporter wakelocks in wakelock section.
3.Removed com.android.vending/com.google.android.finsky.services.ContentSyncService(Reported to delay Whatsapp notifications-Thanks to @orville87 for the report!
07-02-2016
Removed Naptime/Doze Editor
Implemented Greenify's Aggressive Doze
Few changes in Power Nap whitelist
Links Updated
26-07-2016
Added CONTEXT_MANAGER_ALARM_WAKEUP_xxxx regex
vaisakh7 said:
Wakelocks(Allow every 84000 seconds)
com.google.android.gms/.ads.social.GcmSchedulerWakeupService
com.google.android.gms/com.google.android.location.internal.AnalyticsSamp lerService
com.google.android.gms/com.google.android.location.internal.AnalyticsSamp lerService
com.google.android.gms/common.analytics.CoreAnalyticsIntentService
You can either use Amplify or Servicely to block these Services
Click to expand...
Click to collapse
I'm using Servicely - what app do these services belong to?
tangcla said:
I'm using Servicely - what app do these services belong to?
Click to expand...
Click to collapse
Google Play Services
Tapped from my furious Dogo
vaisakh7 said:
Google Play Services
Tapped from my furious Dogo
Click to expand...
Click to collapse
Testing soon will give results in the afternoon
Sent from my SM-G900T powered by Alliance Rom and ktoonsez kernel
vaisakh7 said:
Google Play Services
Tapped from my furious Dogo
Click to expand...
Click to collapse
I think stopping Google Play Services causes issues with Android Wear.
tangcla said:
I think stopping Google Play Services causes issues with Android Wear.
Click to expand...
Click to collapse
Only a few services of Google Play Services is blocked.Not the app itself.
Tapped from my furious Dogo
vaisakh7 said:
Only a few services of Google Play Services is blocked.Not the app itself.
Tapped from my furious Dogo
Click to expand...
Click to collapse
So you're recommending selecting individual services in Servicely - do you know which ones are safe to stop?
Or, in other words, which ones are the biggest causes of wakelocks - I've got a Samsung Lollipop device so I have no Xposed, and therefore no Amplify. I would love to be able to stop the NetworkLocationProvider services.
I'll update the OP later,with the Hit-List in Servicely.
Tapped from my furious Dogo
tangcla said:
So you're recommending selecting individual services in Servicely - do you know which ones are safe to stop?
Or, in other words, which ones are the biggest causes of wakelocks - I've got a Samsung Lollipop device so I have no Xposed, and therefore no Amplify. I would love to be able to stop the NetworkLocationProvider services.
Click to expand...
Click to collapse
I'll update the OP later today.
Tapped from my furious Dogo
OP updated with list of apps to be blocked in Servicely.Try and report battery stats or dumps here.
Tapped from my furious Dogo
Suscribed, thanks for the thread !
Theres really no need to run Greenify + Amplify + Servicely as well, why use 3 programs which all have parts that do what the other 2 do? To me thats madness, your actually adding cycles and memory use and raising the possibility of less battery time by doing so.
I run Amplify and Servicely, but i use AutoStarts to tweak things before i even touch Amplify or Servicely...if it doesnt run at startup or triggered by an intent, then theres no need to touch it with Amplify or Servicely. I only use Amplify and Servicely to handle the apps that i run manually or have to have their intents left alone for interactivity with other apps.
Just the way i do it. I got rid of Greenify weeks ago as it became obvious it was no longer necessary with Amplify & Servicely running.
stylemessiah said:
Theres really no need to run Greenify + Amplify + Servicely as well, why use 3 programs which all have parts that do what the other 2 do? To me thats madness, your actually adding cycles and memory use and raising the possibility of less battery time by doing so.
I run Amplify and Servicely, but i use AutoStarts to tweak things before i even touch Amplify or Servicely...if it doesnt run at startup or triggered by an intent, then theres no need to touch it with Amplify or Servicely. I only use Amplify and Servicely to handle the apps that i run manually or have to have their intents left alone for interactivity with other apps.
Just the way i do it. I got rid of Greenify weeks ago as it became obvious it was no longer necessary with Amplify & Servicely running.
Click to expand...
Click to collapse
In the case of Servicely,the GCM push is a hit or miss.Blocking the apps having GCM push may stop the push notifications.So can't rely completely on Servicely.With Servicely we can't block alarms or Wakelocks.Its required that we use Amplify for that.
I won't recommend to remove Greenify.I've asked in the thread to Greenify only the apps having GCM push.This keeps the Push Messaging alive.
The fact is that Servicely runs a small service in background.It doesn't even show up in battery stats.So no need to worry about battery loss.
And using Greenify+Servicely is because of the fact that Greenify doesn't actually stops the service.It hibernates the apps.That's why I've asked to Hit-List the apps that you don't want to run without starting it manually.
So that's my point.
Tapped from my furious Dogo
vaisakh7 said:
In the case of Servicely,the GCM push is a hit or miss.Blocking the apps having GCM push may stop the push notifications.So can't rely completely on Servicely.With Servicely we can't block alarms or Wakelocks.Its required that we use Amplify for that.
I won't recommend to remove Greenify.I've asked in the thread to Greenify only the apps having GCM push.This keeps the Push Messaging alive.
The fact is that Servicely runs a small service in background.It doesn't even show up in battery stats.So no need to worry about battery loss.
And using Greenify+Servicely is because of the fact that Greenify doesn't actually stops the service.It hibernates it.That's why I've asked to Hit-List the apps that you don't want to run without starting it manually.
So that's my point.
Tapped from my furious Dogo
Click to expand...
Click to collapse
I respect your views, we all do things a little differently!
Hello,
Is anyone on Honor 8 / EMUI 4.1 able to get chrome notifications?
I've been checking Chrome settings and found nothing wrong, expect for the fact I don't seem to be able to add chrome to the list of apps that can ignore battery optimization, since it is not listed. I'm not sure if this is the reason though.
Please share your ideas / suggestions.
RM
It's because Chrome is a system app already so it is by default protected. Except it doesn't even work correctly probably because of their ram management, which kind of make this phone useless for receiving notification for me.
I tried adding Google Clock and S-Health to protected apps and also lock it in the "recent apps" menu, they still get forced close and the alarm didn't ring or it stopped counting steps.
I haven't used EMUI5 yet to know if it's fixed.
Hello!
Solution found! The hint (system app) of the previous post made me try this:
1-Uninstall Chrome (using TiBu - root needed)
2-Reinstall Chrome from Play Store
3-Configure settings to allow notifications from wanted pages
4-Add Chrome to the list of apps that can ignore battery optimizations
So far it is working as expected...
About the other notification issues I've faced before (Google Keep, WhatsApp,...) I've solved it after enabling "keep mobile data on when sleeping", besides adding the app to the ignore battery optimization list, of course.
RM
I have found that same exempt setting as well, unfortunately Chrome isn't in the list so I guess that's why you have to root to remove it first and readd it as third party app for it to show up.
To much effort to just get notification working, a basic feature of all phones and risk losing warranty and Android Pay access.
To make it clear for others:
1. add the app to the Protected apps list (settings - advanced settings - battery manager - protected apps).
2. go to settings - apps - advanced - exempt from battery optimization - select the drop down list and and select "all apps" - find your app and set it to allow.
Huawei programmers must have pride themselves in putting settings inside convoluted maze that's impossible to find.
You might also want to add Settings - Advanced Settings - Battery Manger - Upper right gear - keep mobile data on during sleep.
I second you about this kind of maze that we must run to just have notifications, but, on the other hand I'm kind of OK with it, as soon I can find a way to solve matter!
RM
[APP][4.0+][ROOT optional] SystemPanel2: It does not "BOOST". It does not "CLEAN".
SystemPanel is a tool to help manage your device, improve battery life, and keep it running fast by monitoring application activity. SystemPanel v1 has been in development since 2009; this is v2, and is a complete re-imagining of the idea. V2 is beta, under development, and suggestions and bug reports are greatly appreciated!
SystemPanel does NOT "clean" or "boost" your phone. Well, maybe it does, but even having been a full-time independent Android app developer writing system utilities for nearly a decade, I still haven't figured out what those terms mean. It won't magically double your battery life, but SystemPanel gives you the ability to visualize what's consuming resources. It might show you that some game or app is running full-bore long after you think you've stopped playing and turned the screen off. Or it might show you that some tool running in the background to "boost" your phone is actually only boosting your battery gauge toward zero. Or you might find that your phone and its apps are working perfectly, but it can still offer insight into which activities drain your battery most quickly.
Download link: https://play.google.com/store/apps/details?id=nextapp.sp
Overview
.
The main "overview" screen shows a brief summary of device status. Items on this screen include an overview of the top apps/processes right now, CPU/network usage, and a short history of battery drain rate and resource usage.
Tap any section to see more detail. (The hamburger menu can also be used to switch between screens at any time.)
Live
.
The "Live" screen is divided into two sections, "Running" and "Status". The "Running" screen shows a list of active apps and processes. You can tap on any app to see details about its current activity, history, installation info, etc. Long-press for a quick-access menu.
The "Status" screen shows basic device status information. CPU/Network/Memory consumption data, Wi-Fi/Cellular signal, and device temperatures.
History
.
The "History" section lets you see a week-long history of device activity. You can visually observe app/display activity over time and compare it to battery performance. The plots can be scrolled and pinch-zoomed. Switch from the "Activity" tab to "Top Apps" to see a complete list of what was running during a particular time period. The top 3 apps/processes are always shown on the "Activity" tab as well.
Note: you'll need to let SystemPanel record some history for a day or so before you'll see any meaningful data from this feature.
Analysis
The "Analysis" section is a bit experimental at the moment, it's under heavy development. The idea is to show you a picture of the recent history (last two hours or so) of your device in order to alert you to any recent battery-draining applications. In the Analysis section, SystemPanel itself processes history data and calls attention to problem items. There's more to come here.
Apps
"Apps" shows you installed applications on your device. Root users can disable apps directly here.
You can also "archive" applications to user storage and reinstall older versions (it turns out not all updates are good). Currently this feature is limited to backing up the APK itself, but I hope to improve this.
The "Permissions" section of the apps page shows you apps listed by the permission groups they use. Root users can enable/disable permissions for Android 6+ apps.
App Details
.
.
Clicking on any app or process item (of any SystemPanel screen) takes you to the App details screen. Here you can see details of the app's installation and permissions, its current resource utilization, its resource use over the past week, and its current storage use.
A services tab lists all services provided by the app. Root users can disable individual services. This can be useful for blocking OTAs to customized devices or turning off other undesirable items.
Device
.
The "Device" panel shows system information about your device.
NOTES
Privacy: no information recorded by SystemPanel ever leaves your device. Everything recorded is for *YOUR USE* and is not sent to anyone else, ever.
Root Access: SystemPanel does not require root. On Android Nougat (7.0) and later, root is extremely beneficial as Nougat restricts all access to running process information. SystemPanel wll work on Nougat without root, but its capabilities are limited.
Ads: You can use the app in ad-supported mode for free, and there's a "Plus" key if you want to remove the ads. The ads are Google AdMob "Native" ads. They don't animate or annoy, and are designed to blend into the design of the app (all ad content is however specifically marked as ad content). When the Plus key is installed, the ad engine is not even initialized.
Permission Usage
Close other apps: Used for "end process" feature.
Google Services: Required by in-app-billing/AdMob. Not used elsewhere. App does not depend on Google Play Services.
Internet/Network Access: Required to monitor Wi-Fi state and to show network information in device tab. Also required for AdMob.
Location: used only in "Device" section to show GPS location per user request.
Package Usage Stats: Currently not used, but planned for future update to "Analysis" reporting to indicate whether a particular process was in foreground/background state.
Phone/Read Phone State/Identity: Required to retrieve cell signal data, also used to display telephony information in "Device" section. This is used only to display this information to you.
Prevent device from sleeping: Required for recording history data in the background. (Wakelocks are only taken momentarily).
Retrieve running apps: Used to retrieve some minor detail information about running apps on some devices. This permission has largely been inerted on newer Android devices.
Run at Startup: Required to start history recording service (when enabled).
Storage: Used for app archival and application storage usage analysis.
Root access is used/required for the following operations:
Retrieving any kind of information about running processes on Android 7 (Nougat) and later.
Retrieving information about system processes (i.e. processes which are not Android Apps) on Android 6 (Marshmallow) and later.
Enabling/Disabling packages (non-root users may use "control panel" option to use Android preference panel for this purpose, where permitted by the OS).
Enabling/Disabling services
Killing apps and system processes. Root is not required for normal "End Process" feature to request an Android application to stop. Root is only required to send UNIX TERM/KILL signal.
Download link: https://play.google.com/store/apps/details?id=nextapp.sp
[Reserved]
I'll try it
Hey, I remember using version 1 from way back. Definitely on the OG Droid. I never used it to kill apps, but over clocking was the thing to do back then so there were a lot of things I could keep an eye on with your app. Also, it had nice graphs. I'll give this a whirl.
Saw this app at Android Police before. Great feature set.
Great app! The first one which is able to measure CPU load on N. Would be great to a have a widget or a permanent notification with the most usefull data (cpu load, clock, temp and battery temp)
Wonderful to get this tool back for newer system version.
The original systempanel was one of the first (I think THE FIRST) Android app that I've ever purchased and I've been a user for many years.
Great to see v2 out! SystemPanel has always been a great app to help diagnose problem apps.
Thanks everyone!
BTW just discovered a "brown paper bag bug" that can happen the first time you grant SystemPanel root access. There's a case where SystemPanel will attempt to perform a root operation on the user interface drawing thread (a giant "n00b" mistake in Android development). This can cause the device to freeze for 5-10 seconds if it happens to be the first such operation and hasn't been granted root access before. Thankfully it only happens once and will be corrected in next version.
Tiz92 said:
Great app! The first one which is able to measure CPU load on N. Would be great to a have a widget or a permanent notification with the most usefull data (cpu load, clock, temp and battery temp)
Click to expand...
Click to collapse
Widget, notification, and a persistent-overlay are all on the table...I probably just want to implement all three.
SystemPanel 2.0.b3 (r2041) now available in the beta channel.
"Surprise Her with Improved Android Analytics"
(Moved to production)
Changelog:
Added support for monitoring the active foreground application using an Accessibility service. You'll have to grant SystemPanel's service permission to operate via your accessibility settings for this to work (even if you have root). SystemPanel's settings contain a convenient link to turn this on in the "General" section. It's entirely optional. Currently foreground-process data is used on the analysis and specific-app-history screens, but this will be expanded soon.
Fixed bug where it was difficult to scroll vertically on screens with lists of plots.
Fixed startup bug for root users where some devices would hang for a couple of seconds.
Updated chart legends.
More precision added to use percentages in History/Top-Apps.
App-Info screen now differentiates between supported and required features of apps.
App-Info screen now shows when app was last used (if usage access is enabled). More usage stats features will be added soon.
Fixed bug where disabled services hidden on App-Services screen under Nougat.
Added "Tools" screen to "Device" section. Currently provides shortcuts to accessibility and usage stats preferences (some devices don't have any way to access these). Also allows access to device "Testing" screen (some devices support).
I've resurrected the beta channel for those that want early access to new releases, you can opt-in here: https://play.google.com/apps/testing/nextapp.sp
The product itself is of course beta, but opting into the beta channel will get you new releases earlier. Product will move to the main stable channel shortly thereafter.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Look at the circled part.
The 100% is missing and you can only see the bottom part of the number (zoom it).
Sent from my MI 5s Plus using Tapatalk
Thanks, need to remove this... I think I want to leave the 100% indicator off (it's easily implied and would crowd section label).
SystemPanel 2.0.b4 now available in the beta channel.
This release adds a new major section, "Usage". Usage data shows a history of the apps you've used on your phone. This data can be viewed in aggregate form to see which apps you use most and how often you're using your device.
There's still a long way to go with "Usage". E.g. it needs to be more integrated with the history section, so you can quickly see the effect that usage had on the device (i.e., battery drain). There is currently no "overview" section that takes you to the usage screen, it's accessible from the slide-out panel.
Like history data, usage data is visible for 7 days and data older than 10 days is purged from the database. Like all recorded information, data is never sent from your phone to anyone/anywhere.
"Usage Statistics screen", showing app usage in the last 24 hours.
Usage log screens. The left screen shows a raw log of app usage (in this case with launcher/SystemUI stuff filtered out). The right screen shows apps which ran for more than 10 minutes.
.
The "CPU" indicator below the app title shows the average CPU usage while the app was active. The battery indicator shows the net battery drain (or charge) while the app was active. This battery use is simply the amount the device's battery changed while the app was in the foreground, it does not indicate that the app itself consumed that much battery. This will explained in more detail when a help section is added to this screen.
The usage section works just fine on Android 7 without root. It uses the accessibility service (which must be enabled) to work. Once it's more integrated with the history section, this feature may be useful to non-rooted Android 7 users to determine if an app running in the foreground kept running longer than it was being used.
Changelog:
Added Usage section.
Added workaround for bug when scrolling plots when viewing a specific app (unfixed bug in Android widget library itself).
Removed broken 100% axis marker in history section of overview screen.
Fixed min/max clock frequency data in device section.
This release has been initially uploaded to the beta channel. It will be placed in production soon assuming further testing proceeds well.
The beta channel for those that want early access to new releases, you can opt-in here: https://play.google.com/apps/testing/nextapp.sp
The product itself is of course beta, but opting into the beta channel will get you new releases earlier.
No cell signal data
Hello, I'm a big fan of your apps, I've been using FX since 2012 and I was fond of the original system panel. I think the new system panel is just beautiful.
One thing I notice is, I don't seem to be getting any record of cell signal. The LTE bar is always blank and there's nothing in cell signal history. This is on a Verizon Galaxy G7 with Marshmallow.
MKairys said:
Hello, I'm a big fan of your apps, I've been using FX since 2012 and I was fond of the original system panel. I think the new system panel is just beautiful.
One thing I notice is, I don't seem to be getting any record of cell signal. The LTE bar is always blank and there's nothing in cell signal history. This is on a Verizon Galaxy G7 with Marshmallow.
Click to expand...
Click to collapse
Thanks and thanks for reporting this...
OEMs have severely failed on implementing Android's APIs for retrieving cell signal data. Some return nothing and others return random nonsense. Samsung is one of the worst offenders. I have a few Samsung test devices (including as-of-yesterday an S7 Edge) and will be trying to correct this. At the absolute minimum, I need to not display the data if it's out of range (some of this is already in place, but doesn't always work). Would prefer to workaround on popular broken devices though (e.g. Samsung Galaxy S/Note stuff).
I'm very happy I picked this S7 up...gorgeous hardware but somewhat ridiculous software (though slowly improving and debloating). I rooted it before even turning wifi on, and noticed some shortcomings when using SystemPanel to help debloat it (e.g. the UI for disabling packages is too slow.) Next version will also be categorizing apps by whether they're user-facing (have a launcher icon) or not. I think this thing came with 330-something system apps,, I've disabled 50+ already. I'll be tempted to get an international S8 as my own phone if I can put Lineage on it.
New feature request
Two, actually
First and foremost, battery usage rate (e.g. %/hr). To me, this is the most useful battery metric, to see in history and correlate with CPU and signal and so on. I'm always squinting at the battery % graph trying to estimate the slope....
Second, how about some info on sensors? Nothing too fancy, a list with current values perhaps?
tliebeck said:
Thanks and thanks for reporting this...
OEMs have severely failed on implementing Android's APIs for retrieving cell signal data. Some return nothing and others return random nonsense. Samsung is one of the worst offenders. I have a few Samsung test devices (including as-of-yesterday an S7 Edge) and will be trying to correct this. At the absolute minimum, I need to not display the data if it's out of range (some of this is already in place, but doesn't always work). Would prefer to workaround on popular broken devices though (e.g. Samsung Galaxy S/Note stuff).
I'm very happy I picked this S7 up...gorgeous hardware but somewhat ridiculous software (though slowly improving and debloating). I rooted it before even turning wifi on, and noticed some shortcomings when using SystemPanel to help debloat it (e.g. the UI for disabling packages is too slow.) Next version will also be categorizing apps by whether they're user-facing (have a launcher icon) or not. I think this thing came with 330-something system apps,, I've disabled 50+ already. I'll be tempted to get an international S8 as my own phone if I can put Lineage on it.
Click to expand...
Click to collapse
Im with you on international as i have a T-Mobile s7e. I need and miss root. Exynos don't play well with cm based roms that's caf supported. But Samsung really improved
Sent from my hero2qltetmo using XDA Labs
MKairys said:
Two, actually
First and foremost, battery usage rate (e.g. %/hr). To me, this is the most useful battery metric, to see in history and correlate with CPU and signal and so on. I'm always squinting at the battery % graph trying to estimate the slope....
Second, how about some info on sensors? Nothing too fancy, a list with current values perhaps?
Click to expand...
Click to collapse
Need to get the battery rate graph in SP2 (it was in the original). I do want to do a sensor list, undecided if this will be under the "Device" tab or in its own (will have to see how it flushes out). If "Sensors" winds up being its own top-level section, then the "Device->Location" feature will move there as well. I actually am inclined to try to make this section a bit fancy though... should be easy to make it look pretty (and informative) with lots of plots.
milojoseph said:
Im with you on international as i have a T-Mobile s7e. I need and miss root. Exynos don't play well with cm based roms that's caf supported. But Samsung really improved
Sent from my hero2qltetmo using XDA Labs
Click to expand...
Click to collapse
I'm waiting patiently (on MM) for this to update for Nougat... https://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470/page31
I'd really hoped I was done with the locked bootloader thing after leaving Verizon.
Hey guys! Let's share our ROM + kernel + kernel settings setups over here!
Stable/Open Beta OOS or Omni, Smurf (stock balanced) or Flash kernel for me.
_MartyMan_ said:
Stable/Open Beta OOS or Omni, Smurf (stock balanced) or Flash kernel for me.
Click to expand...
Click to collapse
Nice! Any screenshots?
All Kernel customisation are just gimmicks. The main culprit for battery drain is Google Play Services and the background running apps that provide quick notifications as soon as you receive a new message/email. This action takes up too much battery. The top list include WhatsApp, Snapchat, Facebook/Messenger, and other social media apps. The definte solution is 1. Magisk Modules- "Universal GMS Dose" , "Enable Dose for GSM Magisk Module" , "Greenify4Magisk". 2. Install Greenify(add all apps for hibernation).
These two steps will ensure excellent standby time and surely a better battery life that you not only need but you deserve.
Veestaai said:
All Kernel customisation are just gimmicks. The main culprit for battery drain is Google Play Services and the background running apps that provide quick notifications as soon as you receive a new message/email. This action takes up too much battery. The top list include WhatsApp, Snapchat, Facebook/Messenger, and other social media apps. The definte solution is 1. Magisk Modules- "Universal GMS Dose" , "Enable Dose for GSM Magisk Module" , "Greenify4Magisk". 2. Install Greenify(add all apps for hibernation).
These two steps will ensure excellent standby time and surely a better battery life that you not only need but you deserve.
Click to expand...
Click to collapse
Cool. I've flashed all the above mentioned modules. Will now add apps to the Greenify Hibernation list.
I'm running stock rooted, and I get 8 hours of screen time on most days. No custom kernel, I do have location off.
Location on, I use blue mail, WhatsApp and Textra and my battery is great. 9-11 hours sot work ex kernel or stock kernel. The custom ex kernel is for adjusting vibration motor intensity, max sound increases and lowering the min frequency of the little cores from 576mhz to 300mhz, this increases battery life a bit. I also use ex kernel to disable certain wakelocks as well.
Kernels overall really don't offer a ton for battery life increases, maybe 5%
Stock locked bootloader, clean oos 9.0.2 gets me over 5hours of screen usage. And i am using location services and bluetooth always. Since i moves to total stock state this phone is a battery beast.
Eric214 said:
Location on, I use blue mail, WhatsApp and Textra and my battery is great. 9-11 hours sot work ex kernel or stock kernel. The custom ex kernel is for adjusting vibration motor intensity, max sound increases and lowering the min frequency of the little cores from 576mhz to 300mhz, this increases battery life a bit. I also use ex kernel to disable certain wakelocks as well.
Kernels overall really don't offer a ton for battery life increases, maybe 5%
Click to expand...
Click to collapse
Mate, what exactly wakelocks you're blocking via ex manager app? I mean which is safe to block?
There are a few already blocked with EX Kernel. the one I block all the time is IPA_WS, the others are preset to blocked. I recommend taking a look and see in the list that have high wake times and block one at a time and see how your phone acts for a day if no issues move on to another. This is of course based on if your phone isn't sleeping. If your phone has a high percentage deep sleep time (mine is always over 93% if im not streaming music with screen off) then you don't need to worry about your wake locks with higher times listed.
Eric214 said:
Location on, I use blue mail, WhatsApp and Textra and my battery is great. 9-11 hours sot work ex kernel or stock kernel. The custom ex kernel is for adjusting vibration motor intensity, max sound increases and lowering the min frequency of the little cores from 576mhz to 300mhz, this increases battery life a bit. I also use ex kernel to disable certain wakelocks as well.
Kernels overall really don't offer a ton for battery life increases, maybe 5%
Click to expand...
Click to collapse
Okay
Veestaai said:
All Kernel customisation are just gimmicks. The main culprit for battery drain is Google Play Services and the background running apps that provide quick notifications as soon as you receive a new message/email. This action takes up too much battery. The top list include WhatsApp, Snapchat, Facebook/Messenger, and other social media apps. The definte solution is 1. Magisk Modules- "Universal GMS Dose" , "Enable Dose for GSM Magisk Module" , "Greenify4Magisk". 2. Install Greenify(add all apps for hibernation).
These two steps will ensure excellent standby time and surely a better battery life that you not only need but you deserve.
Click to expand...
Click to collapse
Do all notifications still come on time with the modules + greenify?
Back in my G4 days I use to use greenify but thought it's not needed anymore due to the nature of android pie
Edit: forgot to contribute. My current setup includes xXx module + EX kernel. Power efficient workqueues enabled, followed the recommendation for stune, and no other mods or edits after that. Best I've gotten was on a weekend, wifi all day, 8 hours SoT on track for 9 hours. Hardly used snapchat that day which likely attributed to the good times.
On a day to day basis I get less than that since there's moment I use data and I use snap fairly often. I'd say anywhere from 4-6 hours SoT.
Nice! I still get notifications (WhatsApp and Telegram), even after enabling the above mentioned Magisk modules, and Greenifying some apps.
As for both idle battery life and screen on battery life, I'd have one main recommendation:
1) use good well-made apps. i.e. open source apps:
-no data leaks so no idle battery drain,
-Most of the time better quality, lighter (so better performance and take less battery when you use them)
-Design-wise : usually they follow well google guidelines
-better support often as well, developers are closer to the community
2) If the option 1 is not available, use your browser instead of bad apps! Like for your favorite websites (news, bank, forums, etc.), most of them have decent mobile versions available on your browser and so you won't multiply apps on your device, and they won't drain battery for nothing. I've never had issues with idle battery drains for years now simply because I don't use random apps. Only the ones I trust.
So go through your app lists, and think for each one of them, do you actually need it? Wouldn't it be fine to just use the website? Could I use a lighter alternative instead?
3) Here are a few suggestions of lightweight apps you could use instead of the "famous" ones, and that I personally recommend:
-Phonograph instead of Play Music, Spotify. The design is wonderful, it's only a few MB and it's fast as f***. Open source
-Use Kiwi browser instead of chrome: no google bloatware, built-in adblocker, bottom bar, well made dark mode, other useful features, optimized performance. Partially open source
-Delete the facebook app and use your browser instead
-Use QKSMS: just a nice design and open source.
-Adaway if you have magisk: open source adblocker
-Amaze file manager: lightweight, gorgeous design, open source
-Libretorrent if you download torrents, nice design, open source
-Barcode scanner, open source
-MatLog to take logs, nice design, open source
That's pretty much all, you don't need much more apps. Feel free to freeze the Google apps you don't use.
Then it's basic advice: turn off location, bluetooth, wifi when you don't need it, check permissions, turn off always on wifi, wifi to improve location, etc.
Use dark themes when they are available, very useful on our device.
Veestaai said:
All Kernel customisation are just gimmicks. The main culprit for battery drain is Google Play Services and the background running apps that provide quick notifications as soon as you receive a new message/email. This action takes up too much battery. The top list include WhatsApp, Snapchat, Facebook/Messenger, and other social media apps. The definte solution is 1. Magisk Modules- "Universal GMS Dose" , "Enable Dose for GSM Magisk Module" , "Greenify4Magisk". 2. Install Greenify(add all apps for hibernation).
These two steps will ensure excellent standby time and surely a better battery life that you not only need but you deserve.
Click to expand...
Click to collapse
Isn't it important for you to see the incoming message instantly?
Has anyone tried these kernels: CleanSlate and Smurf?
I wanted to know if they both differ in battery life..
This is the 2nd cycle with Smurf kernel.
ROM: Beta 6
Kernel: Smurf latest
sohailss111 said:
This is the 2nd cycle with Smurf kernel.
ROM: Beta 6
Kernel: Smurf latest
Click to expand...
Click to collapse
What are your settings on the kernel? Or did you just flash it?
Veestaai said:
All Kernel customisation are just gimmicks. The main culprit for battery drain is Google Play Services and the background running apps that provide quick notifications as soon as you receive a new message/email. This action takes up too much battery. The top list include WhatsApp, Snapchat, Facebook/Messenger, and other social media apps. The definte solution is 1. Magisk Modules- "Universal GMS Dose" , "Enable Dose for GSM Magisk Module" , "Greenify4Magisk". 2. Install Greenify(add all apps for hibernation).
These two steps will ensure excellent standby time and surely a better battery life that you not only need but you deserve.
Click to expand...
Click to collapse
I was under the impression that greenify wasn't needed as of oreo.
---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------
Eric214 said:
Location on, I use blue mail, WhatsApp and Textra and my battery is great. 9-11 hours sot work ex kernel or stock kernel. The custom ex kernel is for adjusting vibration motor intensity, max sound increases and lowering the min frequency of the little cores from 576mhz to 300mhz, this increases battery life a bit. I also use ex kernel to disable certain wakelocks as well.
Kernels overall really don't offer a ton for battery life increases, maybe 5%
Click to expand...
Click to collapse
Mind me asking which wakelocks you are blocking?
Veestaai said:
All Kernel customisation are just gimmicks. The main culprit for battery drain is Google Play Services and the background running apps that provide quick notifications as soon as you receive a new message/email. This action takes up too much battery. The top list include WhatsApp, Snapchat, Facebook/Messenger, and other social media apps. The definte solution is 1. Magisk Modules- "Universal GMS Dose" , "Enable Dose for GSM Magisk Module" , "Greenify4Magisk". 2. Install Greenify(add all apps for hibernation).
These two steps will ensure excellent standby time and surely a better battery life that you not only need but you deserve.
Click to expand...
Click to collapse
How many hours of SOT are you getting now?
In Samsung OneUI, the battery usage of an app can be controlled from 3 different Settings (which kind of overlap with their functions):
1. App Info page/ Battery
2. Device Care / Battery
3. Ignore Battery Optimization Setting
By default, the battery is set to 'Optimised' for all apps.
On the App Info page, if Battery is set to Unrestricted, the app will not appear in the list of apps under Never Sleeping Apps in Device Care. But, if an app is added to the Never Sleeping Apps list in Device Care, the battery setting remains at 'Optimised' in the App Info page.
It is not clear which option is better for apps that the user wants running all the time. For example, I use Netguard and want it to remain running without being killed. Although I have not seen Netguard getting killed with either option, I'm still not too clear on which is the better option between these two settings.
Likewise, if Battery is set to Restricted on the app info page, the app will not show up in the list of apps under Deep Sleeping Apps in Device Care. But, if an app is added to the Deep Sleeping Apps list in Device Care, the battery setting automatically changes to 'Restricted' in the App Info page.
The problem with adding apps to Deep Sleeping list is that they are delinked from Google Play Store (and probably blocked from setting alarms, accessing System Events, etc. too), and so would not receive any updates until the app is launched again. So Deep Sleeping Apps setting is likely the more aggressive setting to prevent apps from running in the background.
The other problem with Deep Sleeping list is that any app that is removed from it is automatically added to the Never Sleeping list. So one must remove the app from this list too to bring it back to the default setting.
Finally, we have the Ignore Battery Optimization Setting, where an app added to this list will automatically have it's battery setting changed to 'Unrestricted'.
If I have to list them in the order of most aggressive to most privileged, it would be like this:
1. Deep Sleeping Apps
2. Restricted Battery (without adding to Deep Sleeping list)
3. Never Sleeping Apps
4. Unrestricted Battery
5. Ignore Battery Optimization
Hopefully someone can clarify this.
One is Android thing and the other is Samsung way. If you select restrict you won't find it through Samsung own app usage.
You can choose one of them or both. Samsung is easier to manage.
*EDIT* What the, you have over 600 apps ?!?!
therock3181 said:
One is Android thing and the other is Samsung way. If you select restrict you won't find it through Samsung own app usage.
You can choose one of them or both. Samsung is easier to manage.
Click to expand...
Click to collapse
Do you agree with the conclusion in OP
therock3181 said:
*EDIT* What the, you have over 600 apps ?!?!
Click to expand...
Click to collapse
Actually over 1,000 if you count the System Apps. Even my Watch has over 300 apps and watchfaces.