Database Users

Strange behavior on my G1, causes extreme unresponsiveness

A couple of days ago I decided to wipe my phone which was running cyanogen's 4.2.13 because it felt slightly sluggish and I figured it was because I've been through so many rom updates and havent wiped, coming from before the whole google/cyanogen cease and decist.
i wiped the phone, reflashed 4.2.13 and enoch theme and began restoring all my data and apps. I noticed very strange behavior coming from the phone shortly after this though. sometimes the phone would just become completely unresponsive, not even the red button would put it to sleep mode. only option was to pull the battery which allowed the phone to run fine after a reboot.
this has happened a total of 3 times since I wiped/reflashed it (monday night). today it happened again and I decided to let the phone run until I was able to open advanced task manager. to my surprise, about every single application I have on my phone was running in the Applications tab. after killing all, the phone was back to being responsive again. I did not execute anything to open these apps, the phone simply started lagging out and I suppose the reason is because every app was trying to get some use of the CPU.
now I am keeping a heavy watch on my advanced task manager list to see if this will happen again, and I noticed that the Messaging application has spawned itself on the list. is this normal? is something wrong with my phone? has it been compromised? I haven't downloaded anything strange, just the same apps I had before wipe/reflash.

No your location hasn't been compromised and there isnt any spyware or viruses on your phone. Those are services, just like on computers that do numerous things.Sometimes settings becomes active after using power control.You could just put the widget for the taskiller on you home screen if your concerned about speed. If your home screens are filled with hundreds of widgets try removing some and see if the speed increases.The 10MB hack might be helpful if you switch b/t a lot of apps.Or you could try another rom if you wanted.

im pretty sure an app like AK notepad doesnt run as a service, but it was populated a few times on my applications tab, along with other things such as calculator.
i don't use the power control widget either. leaving the task killer widget on my home screen to kill the processes as they fork bomb my phone is just a sloppy way to fix whatever is wrong.
and my home screens arent filled with widgets. the only widgets I use are weather, calendar, curvefish's bluetooth wifi silent screenlock, and overclock widget.

If all your apps keep running in the background try using advanced task managers auto end list

the lag vs apps

Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.

robnil said:
Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.
Click to expand...
Click to collapse
I haven't used it in a while, but "spare parts" in the marketplace tells you which apps are consuming your processor IIRC. This will obviously give you a temporary hit to your ability to load and run processes but will let you know more details about your phone that you don't already have and the battery use section of settings obviously only talks about what is using your battery but that isn't going to tell you the whole picture.
I am also someone who says you shouldn't use ATK, at least the way you do, but I have it installed and use it a bit differently. What I try to do is kill all tasks after I've used the marketplace or before I do anything intensive (gaming, GPS tracking) and I kill all apps including ATK. ATK will consume processor, battery and will free up memory which then Android uses to open more tasks you don't need (using processor and battery in the process -> repeat cycle). If you need to free up memory 1-5 times a day I think my way will save maybe 15-30% of your battery over a 24 hour period while costing you less than a minute of hassle (too much for some, sure). Again, I only kill after marketplace (because everything opens to check for updates, AFAIK) and before something that will use heavy memory and processor.

robnil said:
Now when installed a lot of apps including juicedefender and advanced task killer (set to aggressive when screen off with lots of exclusions) the lag has become more of an issue.
Now tell me whats the logic behind having installed a lot of apps and a lag? Running several apps multitasked will offcource produce performance-dips but just having them installed?
What exactly is "aggressive" on the task killer anyway? Some people say its just bad to kill tasks.
I have the idea that its the widgets that causes trouble, since they actually needs to run in the background all the time. I noticed today that the fancy-widget got stuck on upboot for like 60 seconds, that caused the 4 buttons below to not load properly. Alto the rather useless "daily brefing" seems to slow down.
I dont want to root and hack with sd-hacks now when froyo is confirmed to be released officially soon.
Do you have experice with sertain apps/widgets causing lag. If so, it would be great to make a list of "bad" apps.
PS, I tested the 30-day navigon today in car and it worked with no problems at all. Fix in 2 seconds and right on track.
Click to expand...
Click to collapse
Forgot the first part of your question, forgive me. I believe, the reason for more apps causing more lag is at least 2 fold. There are more apps that can be opened when you have free memory (in the vicious cycle I described above). There is also something that might be a bit unique to our phone, and I've only recently read this, it's a bit of speculation so I'm not trying to pass it off as fact but I think it's likely to be knowledgeable on the issue, even if not completely correct. Samsung's internal storage method is an SD card, that allows extra apps to be written to the internal storage but comes with a trade off of lag due to a potential combination of:
slow random-access
bad partition
I think I'm missing an important reason, I'll try to look and edit.

When I initially got my SGS I loaded it with a heap of apps and suddenly noticed the lag and quick battery drain. Problem was I couldn't track down the culprit.
I recently reset my device and was a bit more organized with what I installed. One of the things I started doing was checking what services were being used in the process which you can find under the manage apps part of the system.
So while you can load apps and they may/may not be killed by android or a task killer, the services will always be running - taking up memory, sometimes cpu, network. Things like weather checking, news checking, even email sync are some examples. These services plus any apps you run are I think what starts the lag. You need to be aware of which apps are also run as services.
Yes, there are some bad apps (last Facebook version was found to be a heavy drain) but I think they tend to add up with all the other services running.
As for 'Aggressive' depends on the app killer but my understanding (with the one I use), is that there is a memory limit before the app is killed. Once the limit is reached on aggressive, it doesn't take much before memory is cleared.
One thing to install is SeePU as this gives an indication of CPU, memory and network on the top menu bar. This also helps when the system lags (usually CPU is high and memory is low) and helps to know when to clean (or what threshold to set).
Hope this helps.

RAM manager - clear memory??

Once in a while if I notice a slight lag, I bring up the task manager (bottom left when accessing recent apps), go to the "RAM" tab and tap clear memory. What's really confusing me is that it always closes a very high number of apps, even if it's only been a day since I've last cleared it. i.e. I just cleared it and it said "27 apps closed"! There have been times where it was even more...once it was almost 40.
I use the phone a lot, but it's always the same handful of apps... at most, even in a given week I don't exceed using about 6-10 different apps.
So can someone please explain to me what the hell are all these dozens of "apps" being closed? ??? I assume they're including system apps in with the regular apps, but what apps could they be? That's around 20 apps I had no idea were even running...

siciliano777 said:
Once in a while if I notice a slight lag, I bring up the task manager (bottom left when accessing recent apps), go to the "RAM" tab and tap clear memory. What's really confusing me is that it always closes a very high number of apps, even if it's only been a day since I've last cleared it. i.e. I just cleared it and it said "27 apps closed"! There have been times where it was even more...once it was almost 40.
I use the phone a lot, but it's always the same handful of apps... at most, even in a given week I don't exceed using about 6-10 different apps.
So can someone please explain to me what the hell are all these dozens of "apps" being closed? ??? I assume they're including system apps in with the regular apps, but what apps could they be? That's around 20 apps I had no idea were even running...
Click to expand...
Click to collapse
They're system apps, if you're rooted you could install an app like Clean Master and take a look at which system apps are running.

H910: hot and slow

My phone is super slow and gets very warm/hot. I changed the battery to a new one directly from LG, removed the SD card, several apps including Facebook. Still a problem.
What can I do? I wasnt able to figure what is causing all of this. I can see running processes but it doesn't say how much they load the phone.
Any ideas? Sometimes it lags so bad it might take a few secs to scroll.
Sent from my LG-H910 using Tapatalk

You need to provide more info, like:
* Are you rooted
* Did this just start or has it been that way
* Did you install anything recently that coincided with the phone heating
-- Brian

haris163 said:
What can I do? I wasnt able to figure what is causing all of this. I can see running processes but it doesn't say how much they load the phone.
Click to expand...
Click to collapse
Settings -> General -> Battery & Power Saving -> Battery Usage -> Battery Use Details
Make note of the most parasitic applications.
Then go into Apps and Force Stop downloaded or Play Store installed apps that top that list.
It would be highly unusual for factory installed Apps to cause severe battery drain.
The only exception is Chrome. Sometimes there are web pages that don't play well.
If Chrome turns out to be an issue, you need to go through and close tabs.
It may also require going into Chrome -> Storage -> Clear Cache / Manage Space

runningnak3d said:
You need to provide more info, like:
* Are you rooted
* Did this just start or has it been that way
* Did you install anything recently that coincided with the phone heating
-- Brian
Click to expand...
Click to collapse
No.
It was made more severe a few weeks ago.
Not that I am aware of.
Now it's ok, see my next post.
Sent from my LG-H910 using Tapatalk

Hash-82 said:
Settings -> General -> Battery & Power Saving -> Battery Usage -> Battery Use Details
Make note of the most parasitic applications.
Then go into Apps and Force Stop downloaded or Play Store installed apps that top that list.
It would be highly unusual for factory installed Apps to cause severe battery drain.
The only exception is Chrome. Sometimes there are web pages that don't play well.
If Chrome turns out to be an issue, you need to go through and close tabs.
It may also require going into Chrome -> Storage -> Clear Cache / Manage Space
Click to expand...
Click to collapse
Thanks. After removing any app showing up as running (without me running it and not seeing a legitimate reason that it should be running) and installing Powerful Monitor https://play.google.com/store/apps/details?id=com.glgjing.marvel
Cleaning cache using Powerful Monitor
Replacing TrueCaller with Hiya (TC was more anoying for sure)
Now my phone is so fast it feels weird. I even put back the SD card with no issues.
I am still not sure of the cause nor the solution.
On other note, after that I realized that I was two firmware updates behind (I was aware of being one behind) despite repeatedly and regularly checking for updates. Long story short, after calling AT&T the updates came through right away.
Sent from my LG-H910 using Tapatalk

It happened again. The solution this time was to remove all the offline Google map areas from the SD card and only store my current area in the phone's memory. So far, so good.
Sent from my LG-H910 using Tapatalk

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