Database Users

[Guide] How to Keep Android System Drain Minimal - Battery Life Boost

Good Day all,
I have benefitted greatly from Google and XDA. So I thought I would provide a consolidated way of saving our battery's grace from Android System demonic drain.
I am running Euphoria with Furnace, and I had loads of Gapps installed.
I tried multiple attempts over a 3 days period and did many researches back and forth. And it came down to these few main culprits:
1. Android Location Services
2. Google Play Services
3. Qualcomm Location Services
4. Google Now Launcher
5. Unwanted Sync
Tools I have used to assist in this matter.
1. Disable Service - here
2. Greenify
3. Privacy Guard (should be in built in most custom roms)
4. Titanium Backup
Basically the highest causing drain came from Google Play Services and Qualcomm Location Services. These items persistently wakes the phone up and runs on the background. Using greenify on there further cause issues as greenify tries to hibernate these services over and over again, making this a self-made draining routine.
I followed this thread on Google Play Services drain fix and used the Privacy Guard to perform those tricks. I ran through ALL Google Related Apps and as long as "Keep Awake", "Wake up" or "Auto Start" is enabled, I disabled them. I also look through apps I suspect were waking phone up by looking at the last activation of those events (Keep Awake, Wake Up, Auto Start).
Next I followed this thread on Guide to disable google play internal services using Disable Service app. I also took the opportunity to look at both 3rd party apps and system apps to see if there are services that could be disabled. I disabled Apex Notifier as I realize I didn't needed its service.
Then the next sneaky culprit was the Qualcomm Location Services. Even though I froze them with Titanium Backup, they persist in the system. So making a backup of them, I uninstalled them completely. Hasn't caused me any issue with GPS or Maps. They are namely, com.qualcomm.location and com.qualcomm.services.location. Both appeared as LocationServices 1.0 on Titanium Backup.
I went ahead to Greenify many Google Apps, namely Google App, Google Play Store, Google Services Framework, Google+. I also Greenify many apps that Greenify suggested would slow system down or appear to run in the background which I have no use for.
Lastly I uninstalled Google Now Launcher as it was persistently coming up as alternative home launcher even though I froze it. And I also went through settings of apps to make sure sync were turn off. I only kept Calender and Contacts and Gmail Sync on.
Now I have reduced Android System from 34% to 2% and increased my SOT from 2++ hours to 4++ hours at least. Not an out of earth SOT, but I believe that's decent.
Hope I helped and I wish you all the best in your endeavour to reduce Android System Drain. Cheers.

Thanks bro
Will try and give feedback asap

Suscribed, Rated, and Thanked.
I didn't had time to do any research on this, and this thread appeared on the right time.
Thanks

Paradoxxx said:
Suscribed, Rated, and Thanked.
I didn't had time to do any research on this, and this thread appeared on the right time.
Thanks
Click to expand...
Click to collapse
metuncc said:
Will try and give feedback asap
Click to expand...
Click to collapse
Your feedbacks will be appreciated. It works for me and I hope it works for you. And hopefully help many others that face our problem. Cheers

I can't seem to find App Ops anywhere..
Edit: found it by the name "Access lock" but there is no google play services in there..

bestest609 said:
I can't seem to find App Ops anywhere..
Edit: found it by the name "Access lock" but there is no google play services in there..
Click to expand...
Click to collapse
It should be found in settings page, "Privacy".

I know that this guide is meant for CM based ROMs but I said to myself "ehh, what the hell" and I tried it on my Cloudy 2.2 and the results were horrible. Had to fully charge my device twice in order to go through 22 hours and a total of 2h of screen on time which consisted mostly of browsing and messaging. Wakelock Detector told me that the device was mostly asleep and everything was normal in the Batter Usage menu. Usually I get around 18-20h on a full charge with 2,5-3h SoT. Maybe the locations tweeks were not liked by my Tasker app and caused a huge battery drain, although it didn't appear that much as a wakelock trigger.
I am wondering if the problem was caused by Tasker or the stock ROM itself, but badly I do not have the time now to tweak around and I am reverting back to my previous configuration.

steelclaw said:
I know that this guide is meant for CM based ROMs but I said to myself "ehh, what the hell" and I tried it on my Cloudy 2.2 and the results were horrible. Had to fully charge my device twice in order to go through 22 hours and a total of 2h of screen on time which consisted mostly of browsing and messaging. Wakelock Detector told me that the device was mostly asleep and everything was normal in the Batter Usage menu. Usually I get around 18-20h on a full charge with 2,5-3h SoT. Maybe the locations tweeks were not liked by my Tasker app and caused a huge battery drain, although it didn't appear that much as a wakelock trigger.
I am wondering if the problem was caused by Tasker or the stock ROM itself, but badly I do not have the time now to tweak around and I am reverting back to my previous configuration.
Click to expand...
Click to collapse
Try using GSam battery monitor to find out the real culprit. I used that to boil down to the final two irritants - Qualcomm LocationServices.

Really enjoying the app.
Here are the screenshots:
https://www.dropbox.com/sc/fvzvyvdsfqr1e89/AABeH-BwUHKOjpqnXaFcATbaa

steelclaw said:
Really enjoying the app.
Here are the screenshots:
https://www.dropbox.com/sc/fvzvyvdsfqr1e89/AABeH-BwUHKOjpqnXaFcATbaa
Click to expand...
Click to collapse
Kernel OS issue I am not too sure what issues are they. The issues I had was high Android OS drain.

@JokerAce my friend ...nice to see you posting useful advice ....gonna grab it ...especially qualcomm service....thanks mate
/LG-G3/d-855/16Gb/Titanium Black/

m1trand1r said:
@JokerAce my friend ...nice to see you posting useful advice ....gonna grab it ...especially qualcomm service....thanks mate
/LG-G3/d-855/16Gb/Titanium Black/
Click to expand...
Click to collapse
Thanks mate )

Up to 12 hours of continual use on stock ROM!

Note... the info below is old hat... I have made a breakthrough to breaking the 10 hr barrier of continual usage. Right now it is still in testing phase, will the latest Google Services and Play Store. Will post my final addition next week or so. Stay tuned!
Yes, I just figured out what is needed to get the most out of stock 4.4.2 with the latest google services as of Jan 15th.
The key is blocking a select set of services within play store and play services.
As of recent, Google has disclosed that more integration and services will be added to the upcoming update. So i aso included disabling auto system updates.
So my list of blocked services will include everything needed to keep your device from creating more battery drain and issues later.
Posted an attached file for a disable service. The config file is to restore, and use to auto block your Google Services. Since it covers a lot of apps, it will take some time depending on how many apps you have that are in the list.
Yes, I included within the configuration file, is disabled un needed services in popular apps. They do not break or create errors. Only a few apps may loose sync or notification functionality, but can be undone within disable service by opening the apps services list and selecting the disabled service to enable it.

Known issues with apps.
Peel smart remote for S5, and for Tab, both have update info pushed to notifications. They no longer do the push through notification, which many users complain about.
Google Geofence service is disabled... no longer are you able to setup a parameter around you to set actions when leaving and entering. Also Maps and other apps that require geofence will not be able to search around your location for active people around you. Though location works just fine, so maps works pretty much like the old way of placing you where you are at, and populating the map with POI Info.
Google Network Location is disabled. Both Google Geofence and Network Location eat up bits of bandwidth and 2% of battery power per hour, no matter if they are used or not. No longer network location will assist in tracking you. Google will rely on GPS only.
Widgets on Google and stock apps, most may not function. I personally dislike widgets as they eat resources, and I can do most anything I need without widgets, and most of the time just as fast.
Google Fileapkintentoperation service, reporting, and measurement service all have been disabled. Don't report any usage back to Google. Does not break paid apps, or play store usage.
Google Sync, on every thing but Calender. Though it does not disable the ability to manually sync google apps. Just because you turn off sync manually, it still is running in background, so removing the sync services keeps things clean.
Google backup services. No need since I use Ti Backup pro
Google package verification, restore, and reschedule services have been disabled in play store. No more pushing of system updates and apk monitoring. I use norton for scanning downloaded apk files.
Some streaming apps may not remember past usage. Blocked some services that track you.
I also use prevent running to keep memory usage low, and keep background apps from running when closed.
Will post a system battery level snap shot and developer system stats to show how things are running, once my battery level hits 5%

7.5 hrs and 19% battery left
Ok, I can assume with certainly, I can get 9.5hrs of continuous battery time from a single charge.
I tested with screen brightness set at auto, 1 hr of Miracast play back of a 720p video, 1.5 hrs of Miracast playback of two streamed shows from channel apps, 1 download of a 1.2gb torrent file, 1 movie download using vpn and channel app. Used Chrome Dev, Outlook and a few minor instances of other apps. Along with a 10 minute test on sleeping and a 10 minute hibernation, to verify no issues popped up with services disabled.
Here is my 7.5hr battery stats and developer apps stats...

12.5 hours always on moderate use
Yep, I get 8% battery use per hour with an mix of light app use. Mind you, most all apps I run are not memory resident. As Google and internet pros have led end users into believing that cached and background apps save on power and speed up multi tasking. Bah!
I did not have the time to run my device a full 9.5 hours in my test initially. So i had to cut short and use data to extrapolate that shutting down background un used services and killing cached and background apps have made an 8 hr device into a performance monster that does not eat battery power to do so.
Since then I have recharged and will try a test run with minimal screen time off and random sparatic app use. My calculations are 12.5 hrs max. Given the 8% per hour discharge with screen in auto brightness mode, power may increase as the environment brightens up.
I assume if using power save mode, having blocking mode on, and with grey scale enabled, my device could achieve 15 hrs always on run time. The only real way to break the 15 hrs always on run time would be to go into airplane mode or and have the display turn off when waiting, but never sleep.
This is all based on a 1% every 10 minutes discharge rate to be able to keep above 15 hrs constantly on run time.

Oops! Forgot to add
I don't reboot much, but realized some may shut down or reboot time to time. If a reboot is done one key component resets time to time on a reboot. Just go back into disable service and open google play services and search for injector. You will see two, but one may be disabled. Just disable the active one and It will take care of the Google services that had started in background. If both are active, something got reset in play services that helps re enable the injector service. You can restore the disable service backup and it should clear up any reset services. Though it will change what services you changed in apps that you needed a service to run. So be sure once you make a change, to back up, so if you need to re apply my play services settings after a restart, it won't undo any of your changes.

As an update... I do get 1 hr of use per every 8% of battery. It took a few discharges and full recharges to have the device recalibrate after doing my disable service setup to kill services not needed and Google play services that eat battery and performance.
I have done a few changes, but they seem to make a minor significance. Once I am done playing around with some tweaks and verifying, I my post an updated config backup, if they turn out to be improvements.

DELETED
======#Deleted#======

Update... 12 to 10 hours continual use on a single charge!
Yep I was board with Saturday Daytona rain... so what better to test my latest tweaks with the latest Play Store and Play Services.
Had to do a bit of digging, as there are many more services that I don't need but may come in handy later... like Google Pay, Ha! ? what a joke! Well actually with every freaking iteration of Google's services and Play Store, one hopes they don't muck up the mess by fixing, or hosing something you expect to run smoothly and efficiently. There is more to it than just way too many services running in background. It's about how the services run cleanly and not become a load when not used.
Well here it is... over 54 services killed in my list! With only one issue... Maps when promptly closed will error, but it is a visual annoyance if anything. So, don't close Maps before it runs for 30 seconds, or you will error closing.
Also don't try and send error reports or debug info, as they are not going to happen!
For the most part manual syncing within google and tied in apps are intact, but most all auto syncing is disabled.
Will post my latest and greatest DisableService backup config for everyone's use, once I go over a few test runs with reboots and other what nots.
Remember to kill History Injection Service manually after each reboot or wait for the reapplication of the backup config to complete.
Finally I see all the speed and battery improvements that KK once touted as major improvements over JP. It was a crying joke that lasted till now.
Only if Google and Samsung would make a tablet work as a tool not a smart phone, then the benefits of using a tablet for intensive tasks will out weigh getting by with ones pocket phone. This is what students need for their devices to be a 100% duty cycle device under high demands during a days use. No tablet can match that while being forced waist battery and resources for Google analytics, tracking, and social media tie in. Tablets are tools not some monkey device that most peeps have in their pocket!

Almost done!
11.5 hrs is currently obtainable on continuous use on a single charge, without Tasker, any battery apps, and greenify. With overlay disabled and forced GPU acceleration. Both are battery draining options, that nobody will enable when going for extending battery times.
I am trying my best to keep PlayServices down to 15% at device idle. It seems that the kernel with play framework will use 5% no matter what I do. Right now the bottle neck to obtain 12 hrs is what version of PlayServices you use.
I am not going to mess with testing each iteration of play services to get 12 hrs of continuous battery use on a full charge.
To obtain the best battery consumption, one may want to tweak their network by use of a sysctl.config file or shell script to run in init.d or smanager. I find ports waiting to end or close will eat at the battery by how the network or should i say by PlayService's active polling.
I find terminating after 45 seconds of waiting instead of 15 minutes more beneficial to longer battery time. As a wee cpu hit, it is not bad, but it compounds cpu hits by making throttling push the cpu at higher levels than without the polling of closed port termination.
You can watch what i explain when watching cpu performance, by turning on block background data while running a few apps, and comparing to the same apps while block background data is disabled. CPU stats will level off faster and be less prone to hit higher speeds when throttling.
As with my original statement, you will need to kill the locationhistoryinjector service as Google PlayServices will enable it at every boot. It Is a key component to find my mobile and device manager.
My config files disable device manager and find my mobile, along with tracking and Google background data.
What you end up with is a cleaner android that is mostly disconnected from Google, yet able to function better and use paid for play apps without issues, outside of some options tied to google services.
I included my app ops config along with my other updated configs. You will need to remove the .txt extension from the prevent.list and move it in the sdcard/android location for the piebridge app files folder.

Done
I removed all previous attachments on my config backups and posted the latest config backups that kill most of Google's chimera functions within android without breaking play store. All services in regards to NFC, Google Security, network location, automatic background sync, and system usage monitoring have been either disabled or hindered, to eliminate performance degradation and battery consumption.
What you get is a sleek fast running OS, that rivals any custom kernel. Believe me, I used what's available here for mods, and found through trial and error, the best method in keeping overall functionality is to slim things down by using the three apps I have configured.
Most feel what is the point to all this... well disabling features in settings, does not stop google from running the services in background. They run and are tied into other services you may use. Once manually disabled, you may find a service you use fail because it relied on the background service google uses to track and monitor. It is not a matter of killing your favorite app, it is a matter of using an app that does what you need privately and without need of so many background services hogging up resources. Google apps are not the best, just give you options in one package, which some like as to being simpler than having to switch between apps.
I may not be as fast as a custom kerneled device running at 1920mhz or throttled down to 100mhz with profiles enabled, but in all aspects to smoothness and overhead generated by kernel manager apps, greenify, Tasker, and amplify... what gains with customization are lost, compared to what you find in my simple yet very effective method to free your device from Google's constraints.
To be secure in apk installation I use Norton, by unfreezing it before installing apps. Then freezing when done.
For device security, I recommend what ever 3rd party apk meets your needs. As you cannot trust google or samsung with device management. You may find a paid app to perform the job, as most free ones will tie into Google's management or location api system, and fail to function. They must use their own set of services, to hook to existing features not Google's services api.
As for NFC this device has none, so it is a mute issue. Syncing of tied in Google services for social and messaging apps, deal with it... your phone should be primary for syncing. It only takes a quick pull down to sync if you are busy within an app or multi tasking.

One last update
I removed another set of backup configs.. luckily nobody got to them as they were intentionally placed a few replies previously. I do such things to keep peeps on their toes as to know what they are doing by actually reading first!
So... what prompted my change was my error log on certain functions and booting.
Made a wee change to clean up errors without loosing performance or battery gains from my weeding out services and background processes.
Also somewhere in my configs a while back locstionhistoryinjector stays disabled. So this Is a set it and forget it deal, no searching for the blasted service to disable after each reboot.
Alright here are my backup config files along with my frozen apps in screen shots. Missing are... ringtonesbackup and a number of widgets that were permanently removed. Also I have included other side loaded apps that are not part of our stock firmware.
Here is a wee trick nobody talks about... when you shut down or reboot, turn on airplane mode before you do so. Reason being, when the device starts up, it will only take 3 minutes from boot to home screen to fully recover into system idle. Once system is in idle, turn off airplane mode. It helps with less lag and a few apps from trying to gain network access during boot, and slowing down system boot tasks. Once network is operational from disabling airplane mode, the apps in my prevent run list will not wake for network access, until launched. Pretty cool beans, aye!
Also as another trick, because play store sends data when removing apps, I recommend using TouchWiz app removal in the app drawer to remove apps, as it does not send data to do so. Ti Backup does good as well, but depending on its settings may communicate with play store to update play store info.
Currently you can have up to 15 hrs of continuous run time with wifi and screen on during idle. Though I imagine about 2 days worth of mp3 playback time when screen is left off, as a player only, and no other app like Dolby Audio to tweak compressed audio.

In my previous reply i found some errors, and removed some attachments.
I have replaced my disable service backup config with a super modified one that give superior operation by removing tap and pay, fit, NFC, proximity, wearable, and allowed some main sources of required services to run, but made the secondary services associated with them disable, to make the primary service ineffective and keep polling down.
I assume either wearable or health have been a major cause to battery drain since KK was introduced. If you look at the txt file, there are about 100 sub services within the play services service that I disabled. 2x as many as I provided before.
Even though some of the services i have tried to combat from effecting the performance and optimizing battery for longer use, the few I had removed being blocked from running, don't seem to have much effect when their codependent services are disabled.
So, what I get is.. OS using 3% to 4%, Android system 2% to 3%, and screen using 94% to 95% of battery power at idle while the screen is on, and waiting for activity.
Though i will have to redo my screen shots for frozen apps, as i had used a testing config for frozen app effectiveness.
Some apps like Google contacts sync must be removed, as It is an evasive sync service. Samsung is not that way with all of its sync services.
What my super modified file does, is unleashes Android 4.4.x power of operation. For the first time with KK, I have eliminated stuttering and multitasking is more like what it should be with background apps or media being ran during tasks. It is the closest thing to running naked KK, but you have full ability to operate paid for apps and apps that require the latest play services.

so may i know what are the detailed steps in order to enjoy this battery trick? rooted device with xposed?

yweising said:
so may i know what are the detailed steps in order to enjoy this battery trick? rooted device with xposed?
Click to expand...
Click to collapse
Yep, I had to root my I467 with kingo root with a PC connection and install super su before removing kingo root.
I will post a revision to my settings soon. I found that I over did keeping google services from starting. So my new method is minimized to allow most all newer technology work. The only big things I killed are Chrome cast, as it is huge and really eats up battery. Thank god for Samsung ' s method to make miracast a user enabled service, not a constantly running one. Geofence and geocode as they are always running as well, and have little use for daily activities. I would think virtual gear Wil need it, but i live my life in the real world around me.
Again, I killed system updates, and some automated sync services that run constantly no matter if you have them disabled in the account.
The only drawback is maps will error if you don't wait for location to lock and the app has been running less than 30 seconds. Plus Network location will always be disabled.
I am finding my latest settings to be best all around.
Will post them by the end of the week.

I have made my disable service less restrictive as the main culprits to battery drainage can be stopped and kept from running without need to add more to the list on google services.
You will not be able to use geo code or geo fence, device manager, nearby services as Samsung's services are better and dont eat battery when not in use, apk ad and anyalitics, self update, chrome cast as it runs and consumes battery even if you dont connect, location history and sharing, network location, place detectioh, and some internal reporting services, along with some sync options in account... but you will still be able to auto sync gmail, photos, drop box, calander, and contacts.
It allows for the most robust google services to still be active, such as fit, wear, notifications, internal messaging system and tap and pay.
You go from over 8 minutes of activity after reboot down to 2 to 3 minutes of cpu activity depending on what apps you run and allow to load in memory.
Just download disable service from the play store, restore the backup file from the internal sdcard and wait for confirmation.
You will need root!
Xposed has two modules that I like to use both backup files are in my previous reply, a few back. I suggest after installing prevent run, to go into the android folder and find the piebridge folder near the bottom and place the backup there, and remove the txt file extension. Once you reboot to activate the xposed module, the app will see and load the backup, before replacing when you change the settings.

Closest to making google services not eat battery
yweising said:
so may i know what are the detailed steps in order to enjoy this battery trick? rooted device with xposed?
Click to expand...
Click to collapse
Here my last option to rid battery consumption.
I blocked most all of the internal services that deal with sending data back to google. A revised plan that started with killing the major services first instead of attacking bleeders as in pruning twigs from a branch. I went after the big branch first. So I was able to do more than before in smoothness and least amount of battery drain.
I think I left all the automatic sync still intact, as the reporting branch was more a problem, along with GMS services. Then intents to enable the services, and some upload syncs to kill off 90% of the reporting all together.
The only reports back are analytics and GCM with some GMS tied in. Google Mail and Maps function, but network location, places and geofence features are broken. Mainly because they leak data all the time.
The reason I had to attack my google services deeper, is because History Channel app needed some anti jitter done, as the new app would show a skip every so many seconds of play back.

i managed to flash back to 4.2.2 yesterday, will test it for few days after few cycles of battery charge. might test your backup file if it still cant stand for 6hrs.

wanna get better experience + faster tablet?
just flash CM13.0... I couldn't be happier with my Note 8.0...
samsung's KK is EOL already and slow.... many apps are incompatible anymore....

Crescendo Xenomorph said:
wanna get better experience + faster tablet?
just flash CM13.0... I couldn't be happier with my Note 8.0...
samsung's KK is EOL already and slow.... many apps are incompatible anymore....
Click to expand...
Click to collapse
I beg to differ... there is not one app I use that I cannot update. In fact a ton of them had been updated in the last 30 days.
Kk is stable, and with the latest google services, and framework 4.4.4 I am able to push 1 hr of continual use on just 6% battery use.
Fact CM as never had a stable build that allows perfect miracast and spen funtionality. Plus I like Samsung's built in features, peeps copy, yet cannot beat. Like S5 QuickConnect, grey scale for reading and low light, color blind for easier to recognize color various paterns developers go nuts with, and interaction control for blocking a user defined segment or segments from touch or spen interaction.
You just need to replace systemui and secsettings on a 4.4.2 stock late release rom on a ATT i467 and bam no brainer.
If I want speed, which is really not worth the trouble, is boeffla kernal.
Right now I am tweaking my settings backup to allow Samsung or Google management tracking, by not breaking any GMS and GCM services, while optimizing boot speed and battery savings.
I found another way to address battery consumption and cpu hogging by google background services.

modded disableservice backup config file to allow managment
NOTE### I will re post my file soon... the one I had posted had some errors in settings, I had locked down too much on play store.
Here is my modded config backup to allow most of the google play features to function. Yet, will block google system updates and monitoring, plus limit traffic on your data plan.
It has been trimmed down to only adust google play store and google play services. No other apps and services are touched.
I blocked automated nearby functions, places logging, network location, geo fencing, app data sync, people and contacts sync, most of the backgroud stats and logging, and playstore security (proven by me as of recent, that it fails miserably).
Replace with a standalone anti virus app that monitors apk installations. Problem is only a hand full will do the job and even fewer will not be resource hogs and compound my tweaks. I would specify my pick, but I don't get paid for my work that may seem to advertise a paid app. If they make money I should for endorsement. Its the yank way so accept it.
All without breaking GMS and GCM services, and syncs to built in calander and fit data. All exteral app syncs can still be managed in accounts. You still have SMS, notifications, management functions, and api functionality.
This version is more like my original that I started with, but has some cool features. One is quicker boot to semi idle than any kitkat google services ever released. Low battery consumption and higher performance in multitasking. Very smooth witout need of a custom kernel.
Note you will need version 4.4.4 Framework, which never got updated automatically. So you will need to sideload. And the latest versions of play store and play services.
Clear out framework data, play services data, and play store data then reboot. Setup play store and services install disable services on a rooted device and load the backup settings file.

Ho to get your battery life back.

Dear OP2 friends,
HUGE DISCLAIMER:
Below setup works for MY use and needs. If you are like me it will work for you too, if not go find information somewhere else and don't complain "I cannot get the same results" or things like that. It takes common sense and experience to achieve and understand below info. If you don't have common sense, I pity you, if you don't have experience it's OK. If you are polite and follow the XDA rules I don't mind answering your well structured questions, and maybe others don't mind too, there are a lot more experienced people on XDA than me.
If your question is related to any of the apps/threads mentioned below, please go to that (app) thread, that's why I have put the info right there, one click away.
battery life is something we all want to be endless, well we can't have that, but at least we can improve it from a certain point.
This is what I have been doing for the past weeks and the results are incredible, that's why I decided to share them.
First of all sharing this information is ambiguous because it's somewhat device and user dependent especially how people use it and what apps are installed.
I know that but I believe with the right approach you can get the same results as me, hopefully even better, on the OP2 and possibly other device as well.
I have 148 apps installed at the moment and sometimes even more than 200. If you control your apps properly there is no limit to the amount of apps installed related to battery life.
There are numerous threads on improving battery life out there already so please check out those threads first.
Extreme battery threads:
https://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
https://forum.xda-developers.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588
You can also post your BBS logs there, please don't do that in this thread as I will not investigate them.
Most useful info is already out there so I would appreciate it to go look there first before cluttering this thread. If not I will close this thread.
Let's get started:
improving battery life on Android is (unfortunately) always a combination of things, there is no 1-push button (yet).
In this case I use the following:
- privacy guard (baked in almost any Nougat ROM)
- custom kernel (I use Boeffla: original thread here, I use the Linaro version from ZaneZam)
- Greenify (original thread here)
- Wakelock blocker (built in ROM) + WakeBlock app (optional, original thread here)
- Alarm Blocker (built in ROM)
- Doze apps
- BetterBatteryStats (for finding your excessive wakelocks, thread here)
Obviously you have to be rooted to implement all of this.
The ROM of my choice is RR unofficial.
I like it because of the functionality and features but I believe any ROM with the above features should be able to achieve the same results.
Speaking of results, below screenshots are from my last cycle before writing this thread. One charge got me almost through 3 full days (66 hours).
I fully charged in the afternoon, got through the evening and the first night, then got through the full second day and night, then got through another full day and night and charged only again in the next morning.
If your still following, those are 66 hours of straight juice...
EXPLANATION: There is ALWAYS a tradeoff between SOT (screen on time) and how long your battery will last in one cycle. On my below cycle you can see that I have "only" 4 hours of SOT but almost 3 days of battery life. That is light usage.
If I would use my phone more (more SOT) the battery life cycle would have been significantly shorter. If you complain to me that you "only" have 24hrs of battery life but you show me a SOT of 7-8 hours, I would consider that great battery life! It's all relative...
I have never used one battery cycle from 100% to 0% in one go so I don't know the max SOT I would get with my setup. I would guess around 6.5-9 hours depending on the activity (gaming <=> ebook reading, mobile data <=> wifi, ...). It's all relative...
The screenshots in the bottom of the post might bring clarity for you.
See the following posts for more explanation.
Thanks to:
@nicesoni_ash
@Lord Boeffla
@ZaneZam
@oasisfeng @GioBozza @chamonix
@ssrij @The Peterle

Privacy Guard:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I enable this for all user apps because I don't want any app keeping the system awake. I even have this enabled for some system apps like:
Calendar storage
Google play services
Google play store
Google app
cLock
I mostly disable all locations (if it's not a location dependent app), keep awake, run in background and even start at boot (if the app doesn't need to start on boot) toggles.
Again, use your common sense to figure out if a app needs to run on boot (for example, youtube doesn't need to run on boot, tasker does for starting up along with the system boot).
obviously some system apps need to run in the background for example cLock or calendar storage otherwise your weather and calendar will not update...
You can also configure all the apps on a gradual basis. You let the privacy guard as is on clean install an if you see excessive wakelocks from a certain app, you start blocking it one by one.

Custom kernel:
I use Boeffla config app with always the latest version of his kernel compiled by ZaneZam (Linaro 6 version).
The latest as of the time writing this thread is LOS14.1-beta14 in combination with config app 2.4.34.
I use profile IMPULSE TUNED V3.0, no lags, good performance and crazy battery life.
Screenshots of my minor changes, the rest is identical to the stock IMPULSE TUNED V3.0 profile.

Greenify:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I Greenify a lot of apps, as much as I can basically, even system apps.
I cannot give too much advice on this part so please go to the Greenify thread to ask related questions. For me it's mostly a hit and miss and right now my config is a big hit.
If you want to know if you can Greenify a particular app you can ask me.
Configuration below in screenshots.

Wakelock Blocker (+ WakeBlock app):
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I personally think this feature is essential in getting good battery life so I'm glad it's integrated in the ROM of my choice (since we don't have xposed yet).
In combination with the WakeBlock app it basically works like Amplify on Xposed, but ROM integrated.
This part is the hardest to explain because it's different for most users. On the screenshots below you can find most of my blocked wakelocks (without losing functionality).
The procedure to block wakelocks is the same as all the other parts explained above and below:
Let your system run for some hours/days (essential!).
After that, trough BBS you can find your excessive wakelocks and through wakelock blocker you can block them completely. If you don't want to completely block the wakelocks you can use the WakeBlock app to put a timer like in Amplify for Xposed, for example I want wakelock x to run every 9999 milliseconds....

Alarm blocker:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
Another essential feature for keeping your device under control.
I block a lot of alarms (without losing functionality) so get ready...

Doze apps:
I use Force Doze from the Playstore to put my device in Doze mode as soon as the screen goes off.
Naptime is an alternative but I find it to generate too many wakelocks (sometimes up to 19 per hour).
I might change this app once in a while if there are better alternatives that come up.
Anyway Force Doze will work for now.

reserved. will add some advices.

CounterC said:
Doze apps:
I use Force Doze from the Playstore to put my device in Doze mode as soon as the screen goes off.
Naptime is an alternative but I find it to generate too many wakelocks (sometimes up to 19 per hour).
I might change this app once in a while if there are better alternatives that come up.
Anyway Force Doze will work for now.
Click to expand...
Click to collapse
Lesser wakelocks means not necessarily lesser drain, good example is definitely the very first lines from this Thread of an old friend from galaxy s3 lte times, he implemented microG on his device and achieved lesser wakelocks but no significant impact on his battery life(see here), what I want to point out is that this equation (more wakelocks - more battery drain) isn't so simple unfortunately, even if true for most of the time, regarding to franco's naptime, I personally made very good experience with this app in combination with his custom kernel, I think especially in this combination it's absolutely recommended..
Furthermore some inspiration about battery life a wonderful guide with plenty of useful information, the absolute majority is generally valid, so don't get confused by the i9305 tag...
Sent from my OnePlus 2 using XDA Labs

Sam Nakamura said:
Lesser wakelocks means not necessarily lesser drain, good example is definitely the very first lines from this Thread of an old friend from galaxy s3 lte times, he implemented microG on his device and achieved lesser wakelocks but no significant impact on his battery life(see here), what I want to point out is that this equation (more wakelocks - more battery drain) isn't so simple unfortunately, even if true for most of the time, regarding to franco's naptime, I personally made very good experience with this app in combination with his custom kernel, I think especially in this combination it's absolutely recommended..
Furthermore some inspiration about battery life a wonderful guide with plenty of useful information, the absolute majority is generally valid, so don't get confused by the i9305 tag...
Click to expand...
Click to collapse
Good point Sam, that's why I always say check BBS first if it's actually a wakelock, then treat it properly (disable or time-lapse it).

Overnight drain

does blocking the *alarm* wakelock cause the system to reboot!?

aditya_pan said:
does blocking the *alarm* wakelock cause the system to reboot!?
Click to expand...
Click to collapse
No, not with me.

Battery Saving Techniques

There's a lot of threads out there regarding battery saving techniques, but I didn't really see anything that went into a lot of detail on the OP3t. I own both an OP3t and an OP5T, and after running into some issues with the battery I have finally gotten my phone to idle fairly well on the devices and figured I would share my techniques.
Anyone that reads this and finds this useful, I encourage you to let me know the outcome of your battery after following this guide. Also if you have any suggestions/recommendations, please share them with me on here. I can update the original post and include your suggestions so that it can be helpful for other users as well.
The wakelocks category can be pretty intimiating because it's different for all users based on applications they have, but if you have some custom regex wakelocks or just standard wakelocks that you would like to share, please let me know.
Now to the guide...
Phone Specs:
OnePlus 3T - 64Gb
OxygenOS 5.0.3 (stock) & rooted with Magisk
Kernel - Bane Kernel https://forum.xda-developers.com/on...e-development/kernel-bane-kernel-r-1-t3801778
Recovery - https://androidfilehost.com/?fid=890129502657595792
Developer Options:
Developer - On
OEM Unlocking - Enabled
Advanced Reboot - Enabled
* Doze mode * - Disabled
-I need to highlight this, because I usually enable this option, and I know many others do as well. I'm not sure if my situation is an anomaly, however I must highlight if you use 3rd party battery saving apps such as naptime, forcedoze, leandroid, you should disable this mode. If you don't use these apps, then you should be okay to enable the option. I had this option enabled initially while using the 3rd party apps, and they were conflicting with my phone and my battery was draining very rapidly. It wasn't until after I disabled this option that I noticed a significant improvement with the battery.
USB Debugging - Enabled
Verify apps over USB - Enabled
Tools I use:
Amplify - https://forum.xda-developers.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874
Better Battery Stats - https://forum.xda-developers.com/showthread.php?t=1179809
ForceDoze - https://forum.xda-developers.com/android/apps-games/app-forcedoze-force-doze-mode-screen-t3377694
LeanDroid - https://forum.xda-developers.com/showthread.php?t=2743316
Magisk v16.0\5.8.3 - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Nova Launcher - https://forum.xda-developers.com/showthread.php?t=1389071
Xposed Framework v90 beta3 - https://dl-xda.xposed.info/framework/sdk26/arm64/xposed-v90-sdk26-arm64-beta3.zip
OOS Debloater v5 - https://forum.xda-developers.com/on...hemes-apps--mods/aroma-oos-debloater-t3615828
Amplify Settings:
WakeLocks:
Wakelocks(Allow every 900 seconds)
WakefulIntentService[GCoreUlr-LocationReportingService]
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
Wakelock regex:
*gms* 900 seconds
*facebook* 9999999 seconds (if you use facebook)
Alarms:
Alarms(Allow every 600 seconds)
com.android.internal.telephony.data-stall
Alarms(Allow every 1800 seconds)
com.oasisfeng.greenify.CLEAN_NOW (If you use greenify)
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_SAM PLE_INTERVAL_ELAPSED
com.facebook.common.executors.WakingExecutorServic e.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.AL ARM_WAKEUP_LOCATOR)
ALARM_WAKEUP_CACHE_UPDATER
ALARM_WAKEUP_BURST_COLLECTOR(com.google.android.gm s.nlp.ALARM_WAKEUP_BURST_COLLECTOR)
com.google.android.gms.location.fused.GPS_ALARM_BA LANCED_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
Alarms regex:
ALARM_WAKEUP[0-9]+ 9999999 seconds
ForceDoze
These are the options I have checked in Forcedoze settings. Everything else is unchecked.
Turn off while charging - checked
Show persistent notification - checked
Ignore lockscreen timeout - checked
Disable motion sensing for Doze - checked
LeanDroid
Disable​Wi-Fi - checked
Cellular data - checked
Cellular Radio - unchecked
Bluetooth - checked
Network location - checked
GPS location - checked
Switch​Cellular network mode to 2G - unchecked
5 min after screen off except (click except to add exceptions)
The only options I have checked under the exceptions are the following:
Except if tethering - checked
except if charging (AC) - checked
except if charging (USB/wireless) - checked
Disable (Under Exceptions settings)​The only options I have checked are
Under (wi-fi, data, network mode)
Except if active: limit 3KB/s - checked
Under Bluetooth
Except if connected - checked
Under Location
Except if GPS in use - checked
Now back to the Leandroid home screen the following settings under "Restore"
I have selected "After screen unlocked"
Every 60 min for 60 seconds after screen off - checked
except 11PM - 6AM - checked
Except below 15% - checked
Magisk
The only module I use in Magisk is "Sysconfig Patcher" - This is supposed to help with optimizing battery for the google services (that are normally exempt from battery optimizations)
Xposed
The modules I have enabled are:
Amplify
ForceDoze
No Device Check (this is a xposed module you can download from the app that helps make SafetyNet check pass)
Now in Android Settings --> Data usage
Click on the cellular data usage as well as the wifi data usage, you can click on an app that shows up in that list that uses up a lot of data and when you click on it, there is an option to toggle off the option "Background data"
I'm not sure if this is really needed, but what I did is I went through the apps that used the most data (including google play store and google play services) and I toggled the background data off
Android Settings --> Battery
Click "Battery Optimization" --> click the ellipses (top right corner) --> Advanced optimization --> turn this on
Android Settings --> Apps --> Special Access --> Usage Access
Turned off for google play store and google play services
Android Settings --> Apps --> Special Access --> Unrestricted data access
All apps are turned off
These are all my custom settings. If you would like to share any, let me know!

Probably you didn't search enough.
There are many helpful topics here or at Oneplus forum for Amplify, Betterbatterystats or with guides for increased battery.
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
Probably you didn't search enough.
There are many helpful topics here or at Oneplus forum for Amplify, Betterbatterystats or with guides for increased battery.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
There are several very useful posts each individually spread around these forums; the purpose of this thread is to have a unified source so people don't have to look all over like I did. I know you initially posted on my thread when I had terrible battery drain issues; and after I posted the information you requested, I haven't heard anything from anyone so I had to troubleshoot and fix it on my own. I guess what I'm saying is, I just want to help others in case they run into a similar situation because it can be frustrating when you're seeking guidance or help and no one responds.

I use Naptime and also had enabled the Doze mode in the settings, so like you say i disabled doze mode now and kept naptime running , ill update this post with my findings

manohar3787 said:
I use Naptime and also had enabled the Doze mode in the settings, so like you say i disabled doze mode now and kept naptime running , ill update this post with my findings
Click to expand...
Click to collapse
Yeah, keep me posted. I'd be interested to see if your results are similar to mine. Were you also having a lot of battery drain despite using naptime and doze mode?

manohar3787 said:
I use Naptime and also had enabled the Doze mode in the settings, so like you say i disabled doze mode now and kept naptime running , ill update this post with my findings
Click to expand...
Click to collapse
@manohar3787 - curious to hear about your phone after turning off doze. Any updates?

Leandroid app is responsible of a severe wakelock, I think is almost better not to have it? Any opinion?
Also, what about RILJ And RILJ_ACW_WL wakelocks? Are these safe to block?
Sent from my ONEPLUS A3003 using Tapatalk

RILJ was safe to block on nougat and below, but in Oreo+ it will actually cause a lot of trouble with the system. The other wakelock you mentioned "RILJ_ACW_WL", I'm not familiar with. What I woudl recommend is do a full backup in your recovery, then make the change to observe what happens. If it messes things up you can recover from your backup.
Regarding Leandroid, I haven't really heard any concerns with it. There have been some responses of users that didn't find it to help any, but I haven't heard of it having an adverse affect.
Another app I haven't tried, but am tempted to try at some point is called Island: https://play.google.com/store/apps/details?id=com.oasisfeng.island
Also a thread about it here: http://forum.xda-developers.com/android/-t3366295
@xNAPx - how is your SOT and your idle battery like? DO you use any 3rd party apps/tools to help with battery drain?

m0d hipp¥ said:
RILJ was safe to block on nougat and below, but in Oreo+ it will actually cause a lot of trouble with the system. The other wakelock you mentioned "RILJ_ACW_WL", I'm not familiar with. What I woudl recommend is do a full backup in your recovery, then make the change to observe what happens. If it messes things up you can recover from your backup.
Regarding Leandroid, I haven't really heard any concerns with it. There have been some responses of users that didn't find it to help any, but I haven't heard of it having an adverse affect.
Another app I haven't tried, but am tempted to try at some point is called Island: https://play.google.com/store/apps/details?id=com.oasisfeng.island
Also a thread about it here: http://forum.xda-developers.com/android/-t3366295
@xNAPx - how is your SOT and your idle battery like? DO you use any 3rd party apps/tools to help with battery drain?
Click to expand...
Click to collapse
My SoT is dependent on the usage, night drain is less than 1% a hour even 0% sometimes, SoT is between 7 and 5 h
About those wakelock I've heard the same about RILJ on Oreo, about the other one I don't know but is heavy as well.
About Leandroid I'm not very convinced. It messes up with notification and now I have another big wakelock to worry about
Sent from my ONEPLUS A3003 using Tapatalk

Unable to End Google play services
i am unable to doze google play services since am already running doze mode+magisk modules(sysconfig patcher + enable doze moe for gms )
Still i can see play services in Running services
Kind help needed

@xNAPx - do you have any custom settings or tools you use? Do you use Greenify?
What are the big wakelock issues that you have trouble with? Is it the one you mentioned "RILJ_ACW_WL" or other ones?
@Anusha Rao - Are you using doze mode within the Android system or 3rd party tools like I posted?
I don't think you want to use both magisk modules. As I mentioned in my post, I only use the sysconfig patcher. And make sure you reboot the phone after enabling that.
To check and see if google play services is being optimized for battery try going here:
Settings --> Apps --> Application List--> Google Play Services --> Battery
When I look at mine it shows 0m in use
0% battery usage
Battery Optimization:
Optimizing battery use
EDIT:
I'm posting screenshots of my googple play store and the google play services having battery optimization enabled and using 0% battery.
BTW, just so we're on the same page, you shouldn't completely "stop" google play services because it's essentially what drives the OS. Those services are important for letting your phone operate correctly. My thread is about optimizing those services not disabling/stopping them.
If you want to completely "freeze" certain apps and services you can try out that application I posted in my previous post called "Island". I'd be curious to hear how it works out.

That one plus "RILJ" plus "LEANDROID service" (which I un installed) , and also "AudioMix" and "xalarmx"
Sent from my ONEPLUS A3003 using Tapatalk

Amplify tells me I need to root my device but I have Magisk installed...?

I'm not familiar with the rom that you have "Dirty Unicorns". I use the stock ROM.
Most custom roms have root built in though so you might not even need to use magisk or super SU. You can check to see if there are any custom rom settings o maybe go into developer settings and see if you see a "Root" option.

Face unlock is not supported in the "Bane Kernel".

Does Lean Droid caused more battery Drain?

m0d hipp¥ said:
@Anusha Rao - Are you using doze mode within the Android system or 3rd party tools like I posted?
I don't think you want to use both magisk modules. As I mentioned in my post, I only use the sysconfig patcher. And make sure you reboot the phone after enabling that.
To check and see if google play services is being optimized for battery try going here:
Settings --> Apps --> Application List--> Google Play Services --> Battery
When I look at mine it shows 0m in use
0% battery usage
Battery Optimization:
Optimizing battery use
EDIT:
I'm posting screenshots of my googple play store and the google play services having battery optimization enabled and using 0% battery.
BTW, just so we're on the same page, you shouldn't completely "stop" google play services because it's essentially what drives the OS. Those services are important for letting your phone operate correctly. My thread is about optimizing those services not disabling/stopping them.
If you want to completely "freeze" certain apps and services you can try out that application I posted in my previous post called "Island". I'd be curious to hear how it works out.
Click to expand...
Click to collapse
Disable background data in Play Store and Play service will not disabling them right?

@Bintang Ksatria - Leandroid should be using less battery. @Rvl7 - No it won't disable them. I still use them, but it's on manual load, and not in the back ground. At least that has been my experience.

m0d hipp¥ said:
@Bintang Ksatria - Leandroid should be using less battery. @Rvl7 - No it won't disable them. I still use them, but it's on manual load, and not in the back ground. At least that has been my experience.
Click to expand...
Click to collapse
A good post , it helps us a lot .

How to disable/adjust the background task limit?

My background with android is long and rocky.
A long time ago in a galaxy far away, I had a Samsung Galaxy S, then a S2.
I can remember a Google Nexus phone in there somewhere.
Then at some point I switched over to Windows Mobile for many years.
A couple of hears ago I came back to android with a Samsung Galaxy S8+ and I hated it.
Recently I upgraded to a OnePlus 6T McLaren and here I am.
I had been expecting to see android happily use up 7, 8 or even 9GB of ram before the background task manager would begin to kill tasks.
Except that I seldom saw android use much more than 5GB of ram.
And worse, background tasks were being killed on a regular basis.
Widgets would stop working overnight, or even in just a few hours.
Spotify would close while a playing a playlist.
A quick search on XDA reveals that many users believe that Android will just use up as much ram as your phone has.
However, that is simply not true.
And so, I began my quest to have Android use as much ram as the phone could provide.
In my case, 10GB.
- I understand that there is an inherent trade-off between keeping background apps running and battery usage. I can live with extra battery usage in exchange for keeping my widgets running or Spotify running for an entire playlist.
- I realized very quickly that in order to achieve the results that I was looking for that the phone would have to be rooted. So rooting was one of the first things that I did.
Step 1.
I started with the basic stuff that a quick google search would provide;
- Settings -> Battery -> Battery Saver (off)
- Settings -> Battery -> Adaptive Battery (off)
- Settings -> Battery -> Battery Optimization -> widget app (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Spotify (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Deep Optimization (off)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Sleep standby optimization (off)
- Settings -> Apps -> Widget app -> Battery -> Background Restriction (app can use battery in background)
- Settings -> Apps -> Spotify -> Battery -> Background Restriction (app can use battery in background)
This helped but not enough to make the widgets or Spotify usable.
Step 2.
I supposed that my specific background tasks that I wanted to keep running were being killed because of the many other apps that were running in the background.
I searched for and found Tomatot DeBloater scripts for the Oneplus 6.
Excellent! Just what I was looking for.
I chose the Tomatot-Debloater-OOS-Light-2.3.zip and installed it.
This helped some more but not enough to make the widgets or Spotify usable.
Step 3.
I realised that there were still some apps running in the background that I didn’t use or want.
So I used Titanium Backup to freeze the following apps;
- Calendar
- Calendar Storage 9
- Contacts (O+)(I replaced with google contacts)
- Dashboard
- Drive
- Face Unlock
- Gboard
- Gmail
- Google
- Google partner setup 9
- Google play music 8
- McLaren AR
- Messaging (O+)(replaced with google messaging)
- OK google enrollment 9
- Oneplus system 1
- Youtube
Perfect! These apps were no longer competing for phone resources with the apps that I wanted to run.
This helped some more but not enough to make the widgets or Spotify usable.
This did make the phone feel faster and smoother.
The phone is much more responsive and fluid to my input.
This made me realize that the apps were being closed not due to a lack of phone resources, but a background task manager being aggressive.
Presumably for battery saving purposes.
I changed my focus to adjusting that background task manager.
Step 4.
Enable the recent screen ‘LOCK’ on the widget app and Spotify.
This didn’t do anything for me.
Everything that I’ve read on it says that it just stops the task from being killed when you click on kill all tasks.
The lock doesn’t lock the task from being killed by the background task manager.
Step 5.
Further google searching led me to believe that the OEM kernel was limiting background tasks.
I choose ElementalX-OP-3.09 and the EX Kernel Manager.
I had to read a lot of google university material to make any sense of the settings in here.
I’m not sure that I fully understand even now.
Eventually, I ended up with the following settings;
Memory
- Adaptive Low Memory Killer (disabled)
- dirty ratio (20)
- dirty background ratio (5)
- min free kbytes (12398)
- vfs cache pressure (100)
Memory -> Low Memory Killer
- apply on boot
- Foreground app (72mb)
- Visible apps (90mb)
- Secondary server (108mb)
- Hidden apps (200mb)
- Content Providers (587mb)
- Empty apps (783mb)
This helped a lot.
This almost made the phone usable to the state that I wanted.
But the widget and Spotify would still stop running overnight and by morning the apps would have to be reopened to get them to run again.
At least the apps would run most of the day without being killed.
Still not the behaviour that I expected from a phone with 10GB of ram.
Ram usage was still not going much over 5.5Gb even if I opened up many apps at once.
Can I ever get ram usage up to the 10Gb that I have?
Step 6.
The last thing that I tried yesterday afternoon was to increase the background task limit in the build.prop.
ro.vendor.qti.sys.fw.bservice_limit=5 (changed it to 60)
ro.vendor.qti.sys.fw.bservice_age=5000 (changed it to 10000)
Yes, I know that I am on PIE and there isn’t supposed to be any effect.
No, I don’t know yet if this had any effect.
I am hopeful.
The widget app didn’t close last night, but Spotify did.
I am getting closer!
This is the best that I could do on my own without asking for help.
So here I am posting my question and asking for help.
How do I get the apps that I want to run to not be killed by the background task manager?
OR
How do I get the phone to use the 10GB of ram?
I feel that I am missing something.
With any luck, one of you smarter persons will be able to point it out to me.
As an aside from all of these changes the phone feels very smooth and fluid.
Except for apps closing that I don’t want to, this phone is a great experience and a pleasure to use.
Apps that I want to run are staying open much longer then before I started.
It’s now just an overnight issue.
And getting the phone to use over 6Gb of ram.
I would suggest that I am 90% happy with it now.
KERNAL: ElementalX-OP6-3.10
ROM: STOCK OOS 9.0.11
PHONE MODEL: 6013 O+6T McLaren

Tomorrow I may try making this change to the build.prop file;
ro.vendor.qti.sys.fw.bservice_enable=true to false
Don't know if it will help or not.

Wow dude, interesting read, i will sign up for notifications from this thread hoping you get your answer because i have the exact same problem but with my work app, throwing it all out of whack and making me a target to big fines (in the $1,000's) and potentially reducing my marketability!
The attached screenies are from before i realized that the app getting killed in the background is what causes the problem (I've left it in the foreground HOURS a few times and it works perfectly!)

UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...

geeksquad2 said:
UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...
Click to expand...
Click to collapse
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference

UPDATE:
I am a silly goose.
I broke a cardinal rule while troubleshooting.
I may have had a few too many wobbly pops and made two changes at a time, thus when change was affected, I was unable to determine properly which change caused the affect.
The rule is, "only make one change at a time when testing".
Yes, all of my apps stay open all the time.
I am getting the behaviour that I was looking for.
However it wasn't necessarily changing the build.prop bgservice_limit from 60 to 120 that did it.
Let me back up a bit.
Earlier I had suggested that locking an app to the recent screen didn't do anything for me, and that in my reading it only locks the app from being killed by you when you try to close it manually.
However in reading up on the oneplus framework-res.apk I found a reference to an oneplus whitelist of apps that will never be killed, and a reference to the recent screen app lock that suggests that oneplus will add a locked app to the whitelist and not kill it.
In the course of a single day, I had inadvertently edited the build.prop and locked the widget app to the recent screen thus breaking the one change at a time rule.
So the next morning and the following days when all apps were staying open I attributed it to changing the build.prop not realizing that it could also have been the app lock.
Last night I realized my mistake.
I unlocked the widget app from the recent screen and went to bed.
When I woke up this morning the widget app was not running for the first time in days.
Also the notifications that I was receiving about the widget app consuming excessive battery have stopped.
It would appear that I was wrong in my earlier observations regarding the app lock mechanism.
It appears to be very useful for keeping apps running all the time.
Did changing the build.prop have any affect on keeping apps open?
Maybe?
I have noticed that my battery life has gone for a complete ****.
I can barely get 24 hours out of the phone.
Worse is that it doesn't matter if the screen is on or not, battery usage remains the same.
i.e. with the screen off and the phone put down, battery life appears to be used at the same rate as when the phone is in use.
I had expected the battery life to be not as good, but I didn't expect it to go to for a **** that badly.
There must be a balance between aggressive app management and acceptable battery life.
The phone didn't display this behaviour until I changed ro.vendor.qti.sys.fw.bservice_enable=true to false.
I think that today I will change ro.vendor.qti.sys.fw.bservice_enable= back to true and observe the battery tomorrow.

kantjer said:
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference
Click to expand...
Click to collapse
I think that ro.vendor.qti.sys.fw.bservice_limit= and ro.vendor.qti.sys.fw.bg_apps_limit= are essentially the same thing, except for android versions.
ro.vendor.qti.sys.fw.bg_apps_limit= is for Android 7: Nougat and below.
ro.vendor.qti.sys.fw.bservice_limit= is for Android 8: Oreo and above.
Someone more knowledgeable than me should chime in here though.

Do you think any of this could have to do with the way the phone keeps disabling push in Gmail? (Every other day I need to set my O365 exchange in Gmail back to push because it automatically changes to the default of checking every 30 mins.)

Any conclusion?

Did you guys manage to solve this issue please by editing the build prop?

Latest smurf kernel rc14b seems to have solved the RAM management issue. I haven't had any apps closing in background since using it.

thank you for the thread!

What did you find in the end?
How did you set this ?
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000

So what's the verdict on the buildprop edits? Do they make a difference?
I notice that sometimes my on-going weather notification doesn't update, or gets killed off. I also have an app that controls rotation per app, and that also seems to stop doing it's thing after a while.

Just want to share. If you are rooted with Magisk, try appsystemizer module. System apps don't get killed by oneplus as aggressively. Tried it with accubattery and it works.

I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.

scloss84 said:
I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.
Click to expand...
Click to collapse
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY

popy2006 said:
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY
Click to expand...
Click to collapse
I'm actually Oneplus 6, OOS 9.0.9.
I also read that it doesn't work on Android 10 because magisk doesn't mount /system in Android 10, but there is a magisk module workaround that you can use. And hopefully magisk will update in the near future to fix that. Just google "Android 10 can't edit build.prop" and you'll find heaps of info.

This is what I have in my build.prop file and it seems to help. I have Oreo it works great on my phone I don't know about later versions of Oreo.
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_age=5000
ro.vendor.qti.sys.fw.bservice_limit=5
ro.sys.fw.bg_apps_limit=64