Database Users

Nexus 6P Utility Apps?

I just received my Nexus 6P and absolutely love it.
I am wondering if any of you have had good experiences with any utility/tool apps for this device. Apps such as Greenify, CM Cleaner, etc. are a couple I've heard of and was curious if these are helpful or not.
Thanks!

I don't use any utility apps so my response is probably not what you're looking for. There's not really a need for Greenify anymore since Marshmallow introduced Doze unless you want Aggressive Doze mode found in Greenify -- which is again unnecessary if you're using Android N Developer Preview which features an aggressive Doze mode.
Not sure too much on CM Cleaner, but if I had to use one I'd probably use CCleaner since I use it frequently on the PC and it works really well. If you choose to not use a cleaner, someone on here or Reddit reported clearing your cache every-so-often from Settings > Storage & USB > Cached data is useful and may even improve battery life.

Synapse - for use with AK kernel.
Naptime and Servicely by Franco are both nice apps.
Recently by chainfire helps keep recent apps section from being over crowded and adds some extra features.
Then you have the more common stuff you likely already use like "better battery stats", "adaway", " afwall+",.... Not sure about greenify on Marshmallow, I believe the Doze feature built into android does something similar to all apps, but do not quote me on that as I don't really know how how they work, just greenify put apps to sleep and then google calls it doze which is just another word for sleep.

+1 to the not necessary argument.

Get viper4android to improve your audio. Ex Kernel Manager is also pretty awesome. Otherwise explore and see what fits your needs!

jdawggs316 said:
I just received my Nexus 6P and absolutely love it.
I am wondering if any of you have had good experiences with any utility/tool apps for this device. Apps such as Greenify, CM Cleaner, etc. are a couple I've heard of and was curious if these are helpful or not.
Thanks!
Click to expand...
Click to collapse
You definitely don't need anything like CM Cleaner, those things are total rubbish, they use more resources than they claim to save. Doze is pretty good at getting the device to sleep when it isn't in use, but some people still use Greenify. I use BetterBatteryStats to monitor to power consumption, f.lux to automatically adjust screen temp at night, Faster GPS to aid in getting a quick GPS lock, and Flashfire for flashing certain things when I absolutely need to on the go.

I use All in One Toolbox to control the myriad of aggressive apps that feel they should launch/run everything i start my phone.

Thanks for the replies guys!
I plan on rooting the 6P today, and I have had experience with such apps as SetCPU, Rom Toolbox, etc. But that has probably been about 2 years ago.
What are the go-to root apps for stock android (not sure I'm ready for ROMs yet)?

1. Flashfire, very powerful tool for flashing things (especially useful for taking OTAs when rooted).
2. Ampere Measures current going in while charging, (pretty useful when my fast charger broke).
3. Naptime , improves standby time immensely (Doze on screen off).
4. Faster GPS, much faster GPS lock as I dont really like leaving location on all the time.
5. BetterBatteryStats, huge info on power consumption.
6. F.lux, (Changes colour temperature based on location and sunsets, warmer colours after sunset, less obtrusive to the eyes.
7. Adaway, gets rid of ads ... yay
8. Viper4Android, best EQ and FX processor available.

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.

Guide for hunting down wakelocks and battery drain (No Root)

I've posted this guide on reddit already, but thought it might be useful here as well. A lot of users promote intense usage of package disablers to reduce battery drain, but this is not required to such an insane extend.
---
After experimenting with my S8 for 2-3 months now, I've collected some data and constructed some basic idea on how to fight wakelocks without having to root your device. I'll try to lay down everything here under a few categories.
First of all, I'll say that I tried using my S8 with a package disabler with hundreds of apps and services disabled, and also tried using it with no package disabler at all. I did not see a significant difference. It's too hard to determine if there is one, but I have to note that disabling TOO MUCH can actually hurt your battery usage.
Finally, I settled on using the device with a disabler again, only this time I disabled things strategically after some investigation with battery stats measurement and wakelock detection.
The apps I used were:
BK Package Disabler + BK Plugin
Better Battery Stats or GSam
These are paid apps, but I am happy with what they can do. BK can be replaced with another disabler (as long as it gives you control over individual package services) and BBS can be replaced with GSam Battery Stats, which is free.
General tips on using these apps:
BBS will require your device to have USB debugging enabled, so that you can connect the phone to your PC and unlock the permission manually. You need an ADB command prompt to do that, and you need to give it the following permission with the following command (read more here).
Code:
adb -d shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
You can use BBS if you do not restart your phone while testing. If you do, it will wipe stats and likely not activate for another few hours, or until you charge again.
You should be using BBS to observe Deep Sleep percentage in the Summary tab (which should be above 95% when the phone is left in idle mode for hours), and Partial Wakelocks to find individual wakelocks that come from apps. Kernel wakelocks are hardly ever something you can do anything about and shouldn't be observed too much, no point in that unless you are rooted. The highest kernel wakelocks should be the ones related to your screen-on time - they are easy to point out as their awake time equals your screen on time.
BK Package disabler, or any other disabler for that matter, WILL require admin privileges to work on your device, so keep that in mind.
BK Package disabler should be used in tandem with BBS, only once you have found wakelocks and/or managed to understand which service is the actual cause. I will give examples below.
---
So, let's start.
Google Play Services battery drain
This one really sucks and it seems to plague any Android device at some point. Most often than not, this problem will occur after you do a system update without doing a factory reset. Last time it occurred on my S8 was right after I did the AQI7 update, after having very good idle drain previous to updating.
What to do in this case?
Log out of your Google account(s).
Enroll for Google Play Services BETA. To enroll, scroll down on this page and find the beta button OR Find Play services in your App list, and do "Uninstall updates", then update it right after that.
Turn off your phone and then boot it in recovery mode (Hold volume up + bixby key, then also hold power button) and select Wipe Cache - This will erase Dalvik cache.
Reboot the phone and delete system cache from the Storage settings
Log back into your Google account(s).
Charge your device and then observe idle drain overnight, or over a few hours.
If this process does not help your problem at all, you might have to do a factory reset to cure the services issue, or the problem might be related to something else, like a google service from some particular app. Use BBS to investigate wakelocks as you check your idle drain.
If this process helps you, but you see the issue again in future without changing anything, try going to the Developer Settings, look for active processes, and find Google Play services. Open them and then hit 'STOP' for each of their sub-services. Don't worry, they will restart on their own. After doing this, you might reboot your phone as well. Last time this little chore helped me out and the drain went away.
---
General Wakelocks
It's normal to get wakelocks even on a perfect system, but BBS will show exact percentages on each of them. Normal wakelocks usually show 0-1% of awake time for a session. If you start seeing numbers like 3%, 7% , 9%, or more, on some specific wakelock, then there is definitely a problem.
Wakelock battery drain will usually appear in your Android System/OS drain stats, so it's impossible to determine without an app.
The most common wakelocks for me are:
- *net_scheduler* wakelock - this one can be related to your WiFi connection. In order to fix it you should have access to the router's settings, and that is not always possible. If you do have access, you can try changing the Wi-Fi channel (choose channel based on Channel Width, for example 40Hz width on 2.4GHz network could use channel 11), and Beacon Interval (set the interval to the highest possible). I found this helped in my case. This wakelock can also be related to google play services - check the previous part of the post on how to possibly resolve the GPS issue. Also, the wakelock can appear under the icons of other apps, when there is little you can do to track down exactly why it happens.
- *com.google.android.gms.measurement* wakelock - this is a VERY common one in my case, and BBS usually shows it comes from Google Services, but always has a specific app icon next to it. In order to resolve this wakelock I had to do the following:
Open my package disabler and go through each app that might be using background data, or the app that is shown next to that wakelock, and then open their lists of individual services. I searched for:
1. AppMeasurementService
2. AppMeasurementJobService
3. Firebase... any service starting with Firebase in its name
These services are related to apps collecting some usage statistics on how you use them and sending them back somewhere, probably the app vendors. You do not need them for any app to be functional, and many apps don't have them. For some reason they can keep your device awake for long periods of time. I disabled them on ALL apps I could find them in and it seemed to resolve a lot of wakelocks after investigating the next following days. This process was probably one of the things that helped me the most with hunting down daily wakelocks as the drain is very stable for me now. For example, today I came back from work with 20 hours of phone usage since charge, almost 1h of SoT and 75% battery left. Other days, I have come back from home with 10 hours of usage, 1.5h of SoT and ~60%. I've seen a lot of improvement lately after doing all of the suggested things and keeping Google services at bay in parallel to that.
---
Bluetooth wakelock
This one was the most inexplicable to me. I never use Bluetooth, or turn it ON for any reason at all. I could not understand why the wakelock occurs.
Ultimately, my solution was to completely disable the Bluetooth System package and all services in it through the BK disabler.
I know this solution doesn't sound good to anyone, but at the same time it might be useful if you also do not use BT at all.
I plan to buy BT headphones in the near future and will be re-enabling this, and at that point I will start observing the behavior of the package once again and maybe turn it on/off at will if the wakelock re-appears too often.
---
Other wakelocks
The general rule here still applies. First, you record your usage with BBS. Then you note down which wakelocks appear on top, and google them as best as you can. Search is your friend here, as the wakelocks are endless and it is impossible for me to list them all and give solutions for even a small percentage of them. Sometimes you might get lucky and find an easy fix. In other times, there will be no easy explanation, or no explanation at all. Such is the nature of Android.
In some cases the wakelocks might be specific services that you can disable for specific apps. In other cases, they will be too general and it will be unclear why they occur. For example, I sometimes get *net_scheduler* wakelock with the Viber app, that can last for 20-30 minutes at random times, and still have not found a way to resolve that, other than uninstalling Viber completely (which is not a bad idea but sadly some of my contacts insist on using that crap. Telegram is your friend).
---
General Tips:
Use an AMOLED black theme. System theme from Samsung Themes (!) and individual app themes / status bar from Substratum. Do not use overlays for the system UNLESS you do not use samsung themes. I found out that Samsung themes do a better job at painting all system apps black, while some substratum overlays miss a few things. It will also be a LOT less painful to update overlays as you uninstall all of them and re-install them, because using Samsung for the system means less packages from Substratum to be installed. REMEMBER to always uninstall system overlays and statusbar overlays (ALL overlays if you want to be super safe) before doing a system update! Otherwise you can soft-brick your device.
Use auto-brightness and make sure to make it as low as you are comfortable with in rooms that you stay often in (like your own room, your office room, etc). Smart auto-brightness will remember you preference and you will hardly ever use more brightness than you need.
Turn off notifications for any apps that are not essential to you. In fact, I have turned off everything except Gmail, because I have a habit of checking my phone very often and do not miss out on anything, while notifications have become a bit annoying to me anyway.
Put almost all of your apps to 'Always Sleeping' in the device optimization app.
Do NOT always sleep apps that you need to be awake, like your Messaging app, Home Launcher, utility stuff like Navbar Apps, Keyboard. Put those in the 'Unmonitored' category instead.
DE-OPTIMIZE your fingerprint scanner from battery optimization settings if you are having issues with waking up the device with it. It is optimized by default if I remember correctly.
If you are feeling BRAVE, you can do your own investigation for each app that you use often to look for any services that might look like Analytics services. Experiment at your own risk, but generally such services are always a benefit to turn OFF for both battery and privacy reasons.
---
Overall, that's it. If I remember something, I will update the thread. Hopefully this can help someone.
In my personal results, I've managed to achieve a 0.3% idle drain per hour with Wi-Fi active during a test of 12 hours of standby. As visible in the screenshot, the Wi-Fi signal is not even perfect.
Here is an example of idle drain with about 1h 10m of SoT at the time it was taken.
---
Feel free to use this guide in conjunction with Neomancr's general battery and performance tuning guide

Thanks!

magarto said:
Thanks!
Click to expand...
Click to collapse
No problem!

This should be on top! Thanks a lot!
The "Service Disabler" functionality has been removed from the latest app version due to Google Play policies.
Fortunately we can find the previous apk version in the developers website.
https://kunkunsoft.wordpress.com/news_2/
Cheers!

hey thanks a ton for this article! My battery is horrible...REALLY. 2 h ost...I've just completed the first part. please explaind better what do you mean with "sign out from Google accounts" step by step. and in my case BBS was not adb enabled...I was not able to see wakelocks. the command explained here https://alexus.org/howto/better-battery-stats-no-root/amp (the google play store version) granted permissions for me. maybe you want to update the guide! I'll let you know how it goes.
cheers

@brokich
Could you please point us exactly to what are the main apps with AppMeasurement and Firebase services?
Until now I have found only the Google play store app.
Thanks for your great guide.

Thanks for the guide. Starting to debug battery issues. Meanwhile tried setting up the black theme. What do you mean by installing only Samsung theme? Do you mean a specific theme made by Samsung electronics or any black theme from Samsung theme market?

Here are the correct adb commands to BBS, as shown in the app in first start:
adb -d shell pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats android.permission.DUMP
adb -d shell pm grant com.asksven.betterbatterystats android.permission.PACKAGE_USAGE_STATS

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