Related
Note: I would've added this info to the appropriate thread but as a new user I cannot.
I've got the latest version of the Samba Filesharing app installed on a rooted but otherwise stock Verizon S III and for the record the reported FCs for this app are seen on this phone, even if I am not actually using the app. I suspect it's causing some other WiFi problems while contending for resources in the background (I'll know more once I freeze/uninstall it). It's also reported to cause unexpected traffic even when "disabled" (seen by firewall users), which could be a source of other issues.
The whitelist workaround doesn't help (e.g., enable whitelist with an empty whitelist and then check manual start).
Also, SU doesn't seem to be involved in any way with the app starting in the background... in this testing I'm not even enabling the filesharing function, yet I still get the lag followed by a FC whenever I disable WiFi. Thus the SU notification workaround appears to be irrelevant (it was originally supposed to address the relatively new lag seen when enabling the filesharing function though it doesn't appear to solve that problem either). **
** If you toggle Wifi off and back on in a relatively short time you may not see the FC issue, as it seems to take a few seconds for the app to come back to life in the background after a FC / force stop... it also seems to take longer (around a minute) to restart itself after the latter.
Reading the thread above, it seems that this useful app may unfortunately not be under active development anymore - if it is I hope the issue is resolved eventually, and if not then I hope this information saves others from further headaches. I do like this app, but it doesn't have a true on-demand mode such that when it's disabled it's truly disabled - staying hooked into WiFi whenever running in the background is not good (leading to FCs and other confirmed and unconfirmed side-effects). It's not clear to me why the app starts itself whenever WiFi is turned on but it indeed does that (neither the FC or force-stop leave it dead for long).
OK, so it seems to be a common thing here where people are wanting to HIDE the navigation buttons as much as possible, but I'm the other way around - I want them on my screen at all times unless there's an actually good reason to hide them.
Some apps, like MX Player Pro, have an option to hide or show the navigation bar - status bar gets hidden by default, as the phone would be in landscape mode for watching videos.
Others do not. Thinking about apps like Netflix, Vudu and such... and the fact that the S8's screen is wider than 16:9, I really don't see a good reason to disable the navigation buttons, except for them possibly being distracting (which they aren't, not to me)
My understanding is that even using the adb commands found in other threads on XDA, you can set it to hide the navigation bar and/or status bar for any apps you want, but NOT the reverse. I tried opening Super Mario Run (that's another one that uses immersive mode, and I'm not quite sure WHY), opening adb shell while it was going, and no matter what command I ran the bar would not show back up. It's like apps can overwrite the system-wide immersive mode preset.
Is there ANY way to do this short of editing the .apk files to remove immersive mode from their manifests so they can't attempt to enter it? The obvious problem with doing that is that any time there's a Play Store update I'd have to redo the modification, and reinstall it from scratch because of .apk signatures.
Based on how MX Player works, and how some apps start immersive and then go back to normal (Pokémon GO seems to use immersive mode for the Niantic logo, but then returns to normal right after that), I'm assuming it's an option inside the app that can be toggled on and off, much like full-screen videos on a PC. But like how web browsers ask if you want to allow a site to use fullscreen, I wish I could do the same to my apps.
+1
Sent from my SM-G950F using Tapatalk
drfsupercenter said:
OK, so it seems to be a common thing here where people are wanting to HIDE the navigation buttons as much as possible, but I'm the other way around - I want them on my screen at all times unless there's an actually good reason to hide them.
Some apps, like MX Player Pro, have an option to hide or show the navigation bar - status bar gets hidden by default, as the phone would be in landscape mode for watching videos.
Others do not. Thinking about apps like Netflix, Vudu and such... and the fact that the S8's screen is wider than 16:9, I really don't see a good reason to disable the navigation buttons, except for them possibly being distracting (which they aren't, not to me)
My understanding is that even using the adb commands found in other threads on XDA, you can set it to hide the navigation bar and/or status bar for any apps you want, but NOT the reverse. I tried opening Super Mario Run (that's another one that uses immersive mode, and I'm not quite sure WHY), opening adb shell while it was going, and no matter what command I ran the bar would not show back up. It's like apps can overwrite the system-wide immersive mode preset.
Is there ANY way to do this short of editing the .apk files to remove immersive mode from their manifests so they can't attempt to enter it? The obvious problem with doing that is that any time there's a Play Store update I'd have to redo the modification, and reinstall it from scratch because of .apk signatures.
Based on how MX Player works, and how some apps start immersive and then go back to normal (Pokémon GO seems to use immersive mode for the Niantic logo, but then returns to normal right after that), I'm assuming it's an option inside the app that can be toggled on and off, much like full-screen videos on a PC. But like how web browsers ask if you want to allow a site to use fullscreen, I wish I could do the same to my apps.
Click to expand...
Click to collapse
Did you find the way?
I'm looking for this too but preferably a shell command to use in tasker on a per app basis
Sent from my Samsung Galaxy S8+ using XDA Labs
paolo200 said:
Did you find the way?
I'm looking for this too but preferably a shell command to use in tasker on a per app basis
Sent from my Samsung Galaxy S8+ using XDA Labs
Click to expand...
Click to collapse
No
But given what I've read, and from experimentation, it looks like it's impossible to do this without having root.
I'm not sure *why* but unless someone can prove otherwise, it seems that the System UI can't override apps - even user-installed apps! Sorta weird if you ask me...
What I was trying to do instead was decompile the .apk and remove the function that puts the app in immersive mode. Problem is, I don't understand the smali language at all... my trials just resulted in failures to compile the app again. Bah. If anyone knows about Android app development and actually somewhat understands smali, let me know...
drfsupercenter said:
No
But given what I've read, and from experimentation, it looks like it's impossible to do this without having root.
I'm not sure *why* but unless someone can prove otherwise, it seems that the System UI can't override apps - even user-installed apps! Sorta weird if you ask me...
What I was trying to do instead was decompile the .apk and remove the function that puts the app in immersive mode. Problem is, I don't understand the smali language at all... my trials just resulted in failures to compile the app again. Bah. If anyone knows about Android app development and actually somewhat understands smali, let me know...
Click to expand...
Click to collapse
Ok I'll let you know. As for the knowledge I'm a beginner too... I'm trying to learn a bit about what can be done using Tasker but I haven't found anything. As you said it seems impossible to force the bars to stay visible if the app hides it. When I was on KitKat there was an Xposed module called app settings that allowed just that, among other things, but I'm on Nougat now and Xposed is not available so... We'll keep looking
Sent from my Samsung Galaxy S8+ using XDA Labs
That's what I mean - you need root to do it (Xposed obviously requires root), and I don't really understand why since in theory a user app from the Play Store shouldn't be able to overwrite system settings. If it was a matter of getting the built-in camera to not be immersive or something, that's another story.
The most you can do with Tasker, really, is mess with secure_settings. I've tried this extensively, and all you can do is set the SYSTEM DEFAULT to immersive on or off - changing it to on makes it so apps not normally in immersive become immersive, but changing it to off does nothing because, well, the default is off anyway...
drfsupercenter said:
That's what I mean - you need root to do it (Xposed obviously requires root), and I don't really understand why since in theory a user app from the Play Store shouldn't be able to overwrite system settings. If it was a matter of getting the built-in camera to not be immersive or something, that's another story.
The most you can do with Tasker, really, is mess with secure_settings. I've tried this extensively, and all you can do is set the SYSTEM DEFAULT to immersive on or off - changing it to on makes it so apps not normally in immersive become immersive, but changing it to off does nothing because, well, the default is off anyway...
Click to expand...
Click to collapse
Hello,
I have root and I also cannot disable immersive mode. I haven't found any xposed module that allow this and App Settings prevent fulscreen also doesn't change anything. Do you know any other solution with root access?
Thanks in advance!
Borchuck said:
Hello,
I have root and I also cannot disable immersive mode. I haven't found any xposed module that allow this and App Settings prevent fulscreen also doesn't change anything. Do you know any other solution with root access?
Thanks in advance!
Click to expand...
Click to collapse
Sadly, no I don't. I've still never found a solution for this, with or without root. And more and more app developers are updating their apps to support the screen ratio... Super Mario Run is now locked to "fullscreen" mode, you can't put it back into windowed compatibility mode anymore, and it takes up 100% of the screen with no room for the navbar anyway.
drfsupercenter said:
Sadly, no I don't. I've still never found a solution for this, with or without root. And more and more app developers are updating their apps to support the screen ratio... Super Mario Run is now locked to "fullscreen" mode, you can't put it back into windowed compatibility mode anymore, and it takes up 100% of the screen with no room for the navbar anyway.
Click to expand...
Click to collapse
That really sucks... I don't know what is all about, why it is so hard to achieve. Anyway, thanks for answer!
Hi,
It has been a while since I have been able to play with custom ROMs as my previous phone was not well supported.
I have just now switched over to the Axon 7 and have just started setting it up as my daily driver. I Installed NucleaROM with LIGHT PATCH, Open GApps and ARISE Sound System. All seems to be working fine but I have one issue and I think it may be a feature from not just the Custom ROM of choice but the underlying source (ResurrectionROM/LineageOS).
When I first setup the phone, it had an option on the lock screen to customize how apps are closed (i believe the term was Smart Close) when the device is idle and the screen is off. I remember looking through it and having options for which apps are closed and which are to remain running.
Since then I have installed a collection of apps, one of which is the Garmin Connect which I need to run when the screen is off.
I am unable to find how to get to these options now. I have looked through the power options and cannot see it.
If anyone can help me, I would greatly appreciate it.
Thanks for your assistance.
As I have started to use the phone a little more I have noticed that this is having another effect.
It seems to be closing my keyboard app so every time I unlock it goes back to the stock keyboard and I need to select SwiftKey again.
I hope someone knows where these settings are.
I have found a workaround for now, but if anyone knows how to control the SmartBattery application, it would be greatly appreciated.
I believe this function is coming from the System App called Smart Battery. I have gone into Settings -> Apps then selected the menu to show system apps. From there I was able to locate the SmartBattery app and disable it.
This seems to be working for me as by Garmin Fitness tracker was losing BlueTooth to the phone before but not now with that app disabled.
I'm not entirely positive about this, as I've never heard of that app. At first, I thought you were talking about the screen lock cleaning feature from the power manager on stock. After your follow up post indicating you had actually found reference to the app on your system and a bit of Googling, I was able to find some reference to it. Nothing useful, I'm afraid.
Try using an app that can launch activities, like Nova Launcher or Tasker. Try to find the app in the list, and see if you can launch it by calling for one of its activities.
P.S., if you're running RR, if you have a look at the extended settings, there might be a way to set the nav keys long-press action to a custom activity. Remember to enable the app, otherwise it might not show up in any lists.
On the Zenpad I have the issue where the YouTube app is vastly over sharpened to the point it harms the visual experience. I can't find a way to turn this off, I have tried force stopping Splendid but it doesn't work. Anyone know of a fix? Ideally lineage os is what I need to get away from this Zenui (it's alright I guess but has weird things that can't be turned off, like this visual enhancement)
I think it's the "Tru2Life" Program, I think it is only removed thru root
Yes, it's the Tru2Life app, aka VisualMaster. The way it makes YT look is total BS. But it's not just YT. There's a database of about 15000 eek apps that it applies different display profiles to. These apps are mostly video, photo, games and other multimedia.
So you do need to have root to disable it. Or at least a custom recovery. The easiest method is probably to use a root-level app manager that can safely disable Tru2Life, which is a system app. Or you can manually edit the package manager config files yourself if you have the skills and don't want root.
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