Hi
I have done the 1-click lagfix that relies on ext2.
I have also installet autokill (the one that changes the internals of the system)
I have 2200 point in qualcom.
STILL I have massive lagg now. It started out well after the rooting, but now its worse than ever. In fact I have even failed to answer a call due to the lagging.
(I have installed Tasker and have 4 tasks set up, i really hope this is not the reason because I would really miss tasker)
I can notice a big differense if I start the dialer and press Home istead of Back. Assuming Back actually kills the process? If I use Home, I can bring it up again in a split second. Using Back and it an take everything from 300 ms to 4000 ms.
I have now started to experiment with Launcher Pro (who some claims to be faster) but this is actuall just a shell and I cannot dedect any differense.
I have tried different presets in autokill, but since this lag is probably not due to lack of memory, i have now set it to "system default".
Is there a way to keep important processes in memory all the time? Like the dialer, contactbook, sms etc? I dont really care if it takes 500 ms longer to start up google maps or facebook, but the PHONE FEATURES must work properly on the phone.
I run a stockrom JM2
hello, as well as the lag fix, I also disabled ui animations and installed autokiller set to strict or optimum and the lag is now minimal for me, it's still there at times but not as bad as you describe.
ironicly i didnt have this problem before lagfix/autokill. It was there so i decided to run the fix (and the qualcom-score is always cool i thought). But now its worse.
Does anyone have experience with tasker as a performance-killer?
This is my 2nd n7 "wifi model" Despite trying different roms and kernels i get lag, bad battery life and weird rendering, especially on websites. I usualy do not overclock and i use stock voltage. Right now im running carbonrom + the dmore kernel. Its weird becuase carbon runs flawless on my note 2.
Any suggestions?
fix-this! said:
This is my 2nd n7 "wifi model" Despite trying different roms and kernels i get lag, bad battery life and weird rendering, especially on websites. I usualy do not overclock and i use stock voltage. Right now im running carbonrom + the dmore kernel. Its weird becuase carbon runs flawless on my note 2.
Any suggestions?
Click to expand...
Click to collapse
I'm not sure how to advise somebody with over 1400 posts to their name... but here goes... I suggest you boot into recovery and clear CACHE and DALVIK... and reboot.
(I use TWRP... but I assume there would be similar options in CWM)...
This clears a lot of crap out... and upon reboot you should see the following message (after the boot animation)...
'Android is upgrading... optimising app 69 of 209'... and so on and so forth, until DALVIK is rebuilt again.
I have experienced some speed gains by doing this intermittently.
-------
You should also check out this app...
LagFix (fstrim) - http://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en
This helps a lot.
-------
With regard to battery life...
Turn OFF everything you don't use... Google enables a lot of stuff by default.
So, in...
SETTINGS>>WIRELESS & NETWORKS>>WIFI>(Menu)>>KEEP WIFI ON DURING SLEEP... set to NEVER.
SETTINGS>>WIRELESS & NETWORKS>>BLUETOOTH... disable.
SETTINGS>>WIRELESS & NETWORKS>>More... disable NFC.
SETTINGS>>DISPLAY... disable auto-brightness, and manually set your own level.
SETTINGS>>DISPLAY... set SLEEP to as short a time as tolerable.
SETTINGS>>BACKUP & RESET... disable 'Backup my Data' to Google servers, if you have backups elsewhere.
SETTINGS>>ACCOUNTS>>Your Google Account...disable auto synchronization of anything you don't use.
So any these these...
CALENDER, CHROME, CONTACTS, GMAIL, GOOGLE CURRENTS, GOOGLE PHOTOS, GOOGLE PLAY BOOKS, GOOGLE PLAY MAGAZINES, GOOGLE PLAY MOVIES, GOOGLE PLAY MUSIC - they're all enabled by default!
-------
Beyond these tips, and my own custom ROM/KERNEL recommendation (see SIG), I can only add that I have never experienced any serious lag on my Nexus 7... even with factory stock.
-------
I tend to get around 7 hours screen time over two days.... from one charge... which I don't think is that bad really.
Hope this helps....
Rgrds,
Ged.
More detail would help a lot.
Does it lag after a clean install before losing any apps
Are you restoring apps - if so how
How are you flashing (wipes, etc)
Does it lag on stock
What launcher are you using
Is there an app in particular that lags
And anything else that might be helpful
Current: Note 2 - Nexus 7 - Charge
Retired: Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
Hello!
I have a problem with CM13. Since I installed it, android became slower. It often feels like it has full memory and it cannot open new apps, aswell sometimes foreground apps are getting killed (lack of memory?). Going back to "desktop" makes it load again, as it was killed before.
Never had so much problems with memory on stock android. Lately it has even killed waze running foreground twice, while I was using it to navigate.
I dont have much of apps running (checked under developer options - services). Any idea what settings to change, so it doesnt behave as bad as it does?
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
So this is really bizarre. This is my 4th Galaxy phone and I've never had a problem with screen lag (Note 4, S7 edge, Note 8, S10+). This phone has wicked choppy transitions when switching apps or scrolling. Verizon, US pre-order.
BUT, here's the weird part: I tried to run a few different screen capture apps to post here as examples. As soon as I turn on screen recording, the lag STOPS and the phone is lightning fast. Recorder off -> back to lag. I can't even begin to guess why this is happening. Anyone smarter than me have an idea?
Would go with one of these:
- battery optimization settings (maybe you're on moderate power saving or something?) That would give you an answer to why lag disappears while doing screen recording (phone switches to performance mode)
- problem with transitions? Maybe reduced animations or settings in developer options (animation length?)
- check running services / memory if something is not using too much power in the background
......
- wipe cache / factory reset if not solved
Currently in performance mode - same deal
Memory cleared, cache wiped
Haven't enabled or touched developer options.
I should mention the phone is bone stock. Even still has a bunch of the bloat ware.
REALLY want to avoid a reset. I have a bunch of authentication apps that have to be reset by my helpdesk at work. Ordeal.
Other thoughts? This is baffling.
Check my guide, you can follow some points without doing a full reset.
Thanks, I just did all the things you suggest in your guide. No joy. Laggy as hell unless screen recording. One thing I did do when be was use smart switch to transfer. Any way to roll back what was done?
Maybe you can try to reset all app settings one by one except the authenticator?
Not a bad idea. I'll give it a try.
The smart switch app screwed things up for me. Luckily I'm the Sr. Engineer of my network so I was able to handle the authenticator apps without my help desk since I set up all of those systems!
androidfilesharing said:
The smart switch app screwed things up for me. Luckily I'm the Sr. Engineer of my network so I was able to handle the authenticator apps without my help desk since I set up all of those systems!
Click to expand...
Click to collapse
So did a reset fix it?
Still don't understand why screen recording makes it work fine...
For me. the following 2 steps saved me from occasionally laggy transition animations.
1. setting → battery → disable adaptive power saving
2. special access → optimise battery usage → untake for the app "One UI Home"