Related
Many of you have probably noticed that performance of Sense roms degrades significantly over time. At least for me, it gets painfully slow after only few hours of usage and I have to reboot to restore the performance.
It appears that cause of this is lack of free RAM, because a lot of applications are still sitting inside RAM even after you stop using them and Sense needs A LOT of ram. A good way to fight this is to tweak settings of android's built in task killer, so it will kill more apps to free more memory for sense to use.
One way to do this is to:
1. Install "System Tuner" application (free on market)
2. Inside application go to Memory screen
3. Click presets and select "Aggressive". If performance is still horrible after performing this tweak, try switching to "Very aggressive"
4. If you wish this tweak to persist after reboot, select "Boot Settings" and enable "Re-apply memory limits".
That's it. For me it changed Sense roms from unbearable to snappy. It will of course significantly reduce multitasking ability of the ROM, but for me it is worth it.
So do you think there would be a better way to go about this then to close certain apps that aren't meant to be closed? It seems some
developers suggest not to use task killers because of this very reason. Would there be any other benifits or negatives in doing this?
You're not using task killers, but just tweaking android's built-in task killler, which means that system apps are safe.
User apps that are not meant to be closed usually provide option to enable notification, which makes them foreground apps and that means that they will probably never be closed.
I was thinking that by switching it to "very aggressive" you may end up closing tons of system apps that aren't meant to be closed. Thanks for clearing that up.
The Ultimate Guide to Speeding Up Androidby BeastSpencer
Have any tips? Let me know!
REQUIREMENTS:
- your phone
- a brain
- (optional) root access
THESE STEPS CAN BE IN A RANDOM ORDER, I AM ADDING THEM AS I GO!
As for some quick speeding up, you can download the attached apk and install it (android 4.3 and up). It makes use of TRIM support, which trims your device of old crap on a schedule to help your device run faster.
FIRST THINGS FIRST! If you have ART, use it! The AOT Compiler makes booting up apps way quicker! Keep in mind enabling it with cause some apps to crash (ie Xposed).
First up, I recommend downloading Clean Master and SD Maid to clean up your phone from all the crap. Run every task in both apps, then you can uninstall them. Next, go get Greenify and RAM Booster from the Play Store. In Greenify, go ahead and hibernate ALL the apps. (don't worry, nothing will become obsolete.) In RAM Booster, go ahead and grant it root access and enable it.
Next, go into the My Files app on your phone (or use a different file manager) and clean out ALL empty folders, as Android gets slowed down with having so many. You can also get rid of old files that you never use. It makes browsing through quicker, too.
Turn off ALL the unused features on your phone except for the necessities, such as mobile data, wifi, sync, from the notification bar. Now, go into your app manager and clean out all the apps that you don't use anymore or haven't used in a while.
OPTIONAL: Get a faster launcher such as Nova Prime or GNL and enable the "stay in memory feature" if it has one. Also on the launcher, try to limit the amount of widgets and apps you have on your home screen, and try to use a static wallpaper instead of a live one.
Next, if you have a custom recovery, go ahead and wipe the cache. On first boot, your device will take longer to boot up and apps will take longer to open, but on second boot it will be BUTTERY smooth.
Now, download ROM TOOLBOX and first go to DNS Changer. Click on Google DNS and apply it. Your data speeds should be a bit faster now. Also, try "Android Browser" or "Naked Browser" from the Play Store for faster browsing speeds.
Next, go to build.prop tweaks, click the capacitive menu key, click Edit, then edit or add these tweaks:
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
dev.bootcomplete=0
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=5
ro.ril.enable.a53=1
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.rill.enable.a53=1
debug.sf.hw=1
persist.sys.purgeable_assets=1
Then, your device should boot faster, have quicker internet, and be smoother.
If you can, install a custom kernel optimized for speed.
Now, install Xposed Framework from dl.xposed.info then install Wanam Xposed from Google Play. Activate it and reboot. Then, go to System in Wanam and uncheck "Enable Touchwiz DVFS" and uncheck "Scrolling Cache." Next Install BootManager and activate it in Xposed. Then check ALL the apps. Press the capacitive menu key and click on settings. Then click on enable fastboot. Your phone should boot way faster now and be smoother at scrolling.
Next, get Safestrap if you don't have it already and flash Walter.White's Debloater. It will get rid of all the crap and free up RAM. If you think it gets rid of too much, then use my light version.
Go back into ROM Toolbox and go to CPU control and slide both meters all the way up. WARNING: this may cause your phone to warm up and drain battery quicker.
Now, go into Settings, go to the 4th tab and scroll down to About Device. Click on that and scroll down to Build Number. Then tap that 7 times.
Go back, and now click on developer options, then scroll down to the 3 boxes with "animation scale" and set them to .5x or off.
Then go into Account settings and go into each account and disable the sync options you don't need.
Go to the Google Play store and download App Cache Cleaner and run it, then uninstall it if you want.
That's about it folks! If you have any suggestions or other speed tweaks, let me know. - Beast
Moderator Edit: Direct download links to paid apps are considered warez/piracy/not allowed on xda. Link removed
This is some good information/advice. Thank you!
:good: Let me know if you have anything to add or change.
BeastSpencer said:
Go to the Google Play store and download App Cache Cleaner and run it, then uninstall it if you want.
Click to expand...
Click to collapse
If you looking for an App Cahce Cleaner, take a look at AppWererabbit.
It is FREE, no ads and no analystics.
https://play.google.com/store/apps/details?id=com.aw.AppWererabbit
Thanks bro !!! GREAT POST !!
Your the man!
These are the best tips anyone could use so many people are missing out! Everyone should do this. Great Job!:highfive:
Does greenifying everything affect some of the apps live updates/ notifications?
Also when you say all empty folders do you mean literally every folder that has nothing in it?
derek.urben said:
Does greenifying everything affect some of the apps live updates/ notifications?
Also when you say all empty folders do you mean literally every folder that has nothing in it?
Click to expand...
Click to collapse
no, i think as long as u have sync enabled with them ur fine
sync settings will wake the apps when needed
i greenify gmail and i still get my XDA emails etc
greenify just kills them running in the background when not needed
i dont know if its the same for u tho
and yes for the folders, it also makes navigating through your phone way quicker without having to go through all those useless lol
Amazing guide. Thanks a lot...
Moderator Comment: Links to paid apps/warez not allowed. Thread closed.
When I updated to Marshmallow I was very disappointed to see their task/memory manager had been dumb down just to take the average memory use of apps. Instead of several versions before showing the running apps in live time.
With that now missing are there any good apps to use with or without root with a good task mananger? Preferably one without a bunch of other junk like clean master and the other apps like that. The one I've found that's the best so far is Task Manager by Hard Infinity.
Thanks in advance!
I should have added a poll from the beginning since I was looking for what most people were using and some possible suggestions. So I have added a poll in hopes to get some responses. Everyone of us has the occasion when an app goes rogue screwing things up, or sucks battery juice to no end, or just freezes up, so it just needs to be shut down. I would love to hear what everyone is using.
NOTICE: I do not condone killing tasks/processes just simply to 'free up' memory. That is the Android System's job, let it do its job.
Check out developer options then Running Services (6th from the top) to see actual live memory usage instead of the averages.
I personally have enjoyed a 'clear all' option in App switching mode from my days of my S4. I use gravity box now and integrated it in my navigation bar to clear and also indicate how much ram is free.
Lastly if you're having issues with any apps stuttering it can help to experiment with background process limit also in developer options, I believe it resets that setting after a restart though.
Hope that helps.
Didn't know about the dev options. The default task manager is really disappointing, couldn't figure out why my RAM was always at 80%. I figure that's no issue, but I like to be aware. Really miss the battery life in my Xperia Z3 and was hoping this would compare with the large battery and doze, but couldn't find the background processes that could be possibly draining my battery.
I have not seen real comparisons yet of battery at all 3 resolutions. Has anyone tested? I'm running at the lowest today just to see. Honestly screen is fine and can barely tell the difference at lowest res
curious for this as well. Got fairly good life out of it with factory settings at 1080. Switched to 1440 last night and cant really tell a difference in resolution but i think battery life is hurting.
EDIT: Tmo S8 with update, for reference.
Because I also couldn't tell a difference, I immediately switched to the lowest resolution. With the following settings, I had 92% battery left at the end of a work day where I would have had about 60% on the Nexus 6p:
- Brightness always at max and disable auto brightness. Bluetooth on, WiFi off.
- Disable pretty much every Samsung feature, gesture, and Samsung app. Made as Nexusy as possible (still using Samsung launcher, which is fine, and I uninstalled Google because I don't really use Google Now and suspect it's a battery hog. The only voice feature I was using was "ok Google navigate home", but now the maps app just let's you save directions as home screen shortcuts).
- Going through the permissions settings in the advanced app options menu in Samsung settings, I disabled all permissions for each app except the ones I know they need.
- Installed Package Disabler Pro and blocked a **** ton of stuff, including in the system packages. Anything with the word bixby in it, all of the T-Mobile apps except visual voicemail (anyone know if I can disable that and still get visual voicemail via the Samsung phone app??), and most of the Samsung apps except things with the word clock or calendar in them because I assumed the overall ROM relies on them but I could be wrong.
- Once done with everything, close all apps then go into settings > device maintenance > optimize now, then reboot the device.
- This CAN have VERY good (potential) battery life, better than the Nexus 6p when reviews were suggesting it was pretty bad.
.psd said:
EDIT: Tmo S8 with update, for reference.
Because I also couldn't tell a difference, I immediately switched to the lowest resolution. With the following settings, I had 92% battery left at the end of a work day where I would have had about 60% on the Nexus 6p:
- Brightness always at max and disable auto brightness. Bluetooth on, WiFi off (only whole at work).
- Disable pretty much every Samsung feature, gesture, and Samsung app. Made as Nexusy as possible (still using Samsung launcher, which is fine, and I uninstalled Google because I don't really use Google Now and suspect it's a battery hog. The only voice feature I was using was "ok Google navigate home", but now the maps app just let's you save directions as home screen shortcuts).
- Going through the permissions settings in the advanced app options menu in Samsung settings, I disabled all permissions for each app except the ones I know they need.
- Installed Package Disabler Pro and blocked a **** ton of stuff, including in the system packages. Anything with the word bixby in it, all of the T-Mobile apps except visual voicemail (anyone know if I can disable that and still get visual voicemail via the Samsung phone app??), and most of the Samsung apps except things with the word clock or calendar in them because I assumed the overall ROM relies on them but I could be wrong.
- Once done with everything, close all apps then go into settings > device maintenance > optimize now, then reboot the device.
- This CAN have VERY good (potential) battery life, better than the Nexus 6p when reviews were suggesting it was pretty bad.
Click to expand...
Click to collapse
Did you actually know what you were disablinh in pdp
km8j said:
Did you actually know what you were disablinh in pdp
Click to expand...
Click to collapse
Kind of, but not entirely.
It has a section for verified safe-to-disable apps. If that isn't enough, there's a section for "system" packages where I avoided disabling anything that I want pretty confident wouldn't affect the overall system (like I didn't disable anything that has to do with sound or audio for example, even though a few of them looked like bloat). I'm the system section however is where you can disable bixby and carrier related ****. There's a search section, which is very helpful (e.g. search "bixby' and disable everything).
I have the advantage of having messed with phones and done trial and error with a much less organized app that essentially does the same thing, which has always been very popular for topped devices, called Titanium Backup.
Finally, when you're done blocking everything you want to block, hot the menu button (top right) and clear the data of disabled packages! VERY good app overall in my opinion, beat $1.50 spent in a long time!
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