Related
Hey,
I was using swiftdroid last two days and it appears to be killing all apps almost as soon as I quit it. I checked with Advanced Task Killer and it appears swiftdroid is trying to keep at least 45MB free even after I enabled 32MB swap with built-in VRAM.
This is very annoying. It keeps quitting facebook chat and IMO chat as soon as I switch to another app. I'm aware GT540 has very low memory but the thing is in stock, I didn't have any problem even though I didn't have VRAM/swap. I usually get around 25MB RAM free all the time and most apps stay in memory. I'm usually like able to launch the IM app, facebook app and still be able to use the browser or file expert or messaging app.
So, is there's a workaround? It's really annoying when it keeps quitting the IM app just like that!
Sorry for saying it's annoying. I know we get this for free and I shouldn't be complaining at all. It's just that it pissed me by quitting IM app, the only app I want to stay in the memory.
What version of Swiftdroid are you using
The latest one (M5), has improved RAM management a lot
And comes with better battery life, too
I got the same thing. Always 40-45mb free and apps being killed quickly. I'm on M5. Someone said that Joestone's AOSP is better in this aspect, but I didn't test it yet.
Mitalca:
I'm on M4. I downloaded M5 only today. I don't think it lacks good RAM management. It's just that its memory management settings have been tweaked to keep maximum possible amount of RAM free so that any new app will launch faster. Am sure there must be a switch to change it.
EazyLuke:
I don't really have any problems with stock 2.1. I checked out Joe's AOSP and swiftdroid. The only real advantage apart from speed is voice input. In Joe's AOSP, I couldn't get voice to work. In swiftdroid, it worked.
that's what I meant with RAM management
Maurik changed the settings on M5
mhoangtr said:
In M4 rom, lowmemorykiller setting is 6,8,16,20,32,40 MB so apps killed too fast.
If you want to keep apps longer, try set to 6,8,16,20,22,24 MB (this is default value of android).
Click to expand...
Click to collapse
But I don't know how can you change that setting in M4
Try M5, if it ain't working for you, go to Joe's
Mitalca said:
that's what I meant with RAM management
Maurik changed the settings on M5
But I don't know how can you change that setting in M4
Try M5, if it ain't working for you, go to Joe's
Click to expand...
Click to collapse
@Mitalca: That's the whole purpose of the post. I couldn't find the option where I can change 6,8,16,20,32,40 MB to 6,8,16,20,22,24 MB.
How do I change it?
You can change these values with e.g. this application https://market.android.com/details?id=com.lim.android.automemman&feature=search_result
I installed this app: https://market.android.com/details?id=com.rs.autokiller
It does the same thing.
I set the values to 6-8-12-18-20-20. Now I'll have to see if that brings an improvement.
EDIT: Tested it for a few minutes. And it seems to be an awesome improvement! I can switch from Facebook, Twitter and Browser, and everything is kept in memory, meaning these apps don't have to reload everything!
And it seems to be stable. I also use some of the "advanced system tweaks settings".
Thanks you guys.
XDA memebers. Useful as ever.
I'm gonna try both the apps and keep the app with slicker interface.
M5 isn't working.
Says assert failed when trying to flash via recovery.
Trys v6 SuperCharger!
http://forum.xda-developers.com/showthread.php?t=991276
It Works Perfectly on our GT540!
I found this problematic, too.
I installed M5 yesterday. Everything is great except this (and I don't like oversensitive accelerometer, but it's not urgent problem ).
Last night I listened Music player, and surfed via Miren. After two opened tabs, Music player shut down . After four opened tabs, phone rebooted. Factory widgets' widgets are useless with this agressive RAM menagment.
hash87 said:
You can change these values with e.g. this application https://market.android.com/details?id=com.lim.android.automemman&feature=search_result
Click to expand...
Click to collapse
Thanks man.
Works excellent .
EazyLuke said:
I installed this app: https://market.android.com/details?id=com.rs.autokiller
It does the same thing.
I set the values to 6-8-12-18-20-20. Now I'll have to see if that brings an improvement.
Click to expand...
Click to collapse
To bad - it want access to too much permissions.
Access to too much permissions? Use LBE Privacy Guard!
What permissions?
And by the way, I wrote a PM to Mur4ik and asked him to try this app out. Maybe he'll change the numbers for RAM-management in his next release if he thinks it's an improvement.
EazyLuke said:
What permissions?
And by the way, I wrote a PM to Mur4ik and asked him to try this app out. Maybe he'll change the numbers for RAM-management in his next release if he thinks it's an improvement.
Click to expand...
Click to collapse
There are plenty of custom ROMs that use Mur4ik's config. It boils down to personal preference. Do you want newer apps to launch really fast or do you want certain apps to stay in memory all the time?
Multi-taskers would prefer to have all apps in memory while people who like doing one thing at a time or who use phone for gaming mainly would prefer Mur4ik's config which launches apps faster.
The best thing for Mur4ik is to include an option to change the memory management config depending on user.
After changing the numbers my apps don't really seem to open slower.
In my opinion Mur4ik could lower the numbers a little bit, to allow better multitasking, but still let new apps open fast (just my personal opinion).
But I don't say he HAS TO do that, just a suggestion, if he doesn't like it it isn't a problem at all, because everyone can simply adjust the numbers easily .
That's true. xD
If I were to suggest, I'd suggest to add the option to change these settings. Apps opening fast depends on what individual apps are in the memory and what new app you are opening.
For example, if you open Angry Birds while your memory is at 16MB, you certainly can't expect it to open fast.
On the other hand, if you open messaging app while memory is at 16MB, it certainly will open faster.
But, I really disliked the apps Swiftdroid had in the latest release. I had to get rid of the whole GO suit with Uninstaller for Root.
nibras_reeza said:
But, I really disliked the apps Swiftdroid had in the latest release. I had to get rid of the whole GO suit with Uninstaller for Root.
Click to expand...
Click to collapse
Try M6, was released yesterday, it's completely clean! Only Tonepicker and QuickSettings are added.
SWEETTTTTTTT!!!!!!!!!!!!! xD
you could also try to put mur4ik rom in the kitchen and play with autokiller settings ...
this is michalak8 from android.com.pl (mike's froYo dev) looking for that magic 10 posts to post my rom) Could someone close the rom thread in development section - I would like to post it my self without google-translate bugs
mikegapinski
So yeah, I've been using nexus 5 prior I got this phone. It had 2 gigs of ram too. When I was getting RN2 I thought I won't face any ram related problems, but I was wrong. It feels like I have 1 gig of ram judging on phone's ability to keep apps in memory. Chrome is capable of keeping only 1 tab in memory, and not for a long time. I'm sick of seeing everything being reloaded every time I go back to it. Any thoughts on this?
PS
No need to tell me about 'lock' feature in recents, it's just useless.
I set up my own battery profile using the security app. Security - Battery - Battery Profiles. In here I changed the Clean Memory to never.
Sent from my Redmi Note 2 using Tapatalk
I use the default profile, and it already has 'never' option picked. And as far as I can judge, this features is meant to be an automatic task killer sorta. The device's problem is in poor ram management, 2 gigs of ram is simply not enough for it, which is kinda 'wtf', considering my nexus experience.
Try freeze build in apps, root first, then use titanium backup or link2sd
If you're using MIUI, there's nothing you can do to lower RAM used by the system and get more RAM available for your apps. I personally clear my apps before use, but the apps I got start fast and are mainly utilities. The only app I lock is School Assistant because it warns me of my classes and exams at University.
sxeMonster said:
So yeah, I've been using nexus 5 prior I got this phone. It had 2 gigs of ram too. When I was getting RN2 I thought I won't face any ram related problems, but I was wrong. It feels like I have 1 gig of ram judging on phone's ability to keep apps in memory. Chrome is capable of keeping only 1 tab in memory, and not for a long time. I'm sick of seeing everything being reloaded every time I go back to it. Any thoughts on this?
PS
No need to tell me about 'lock' feature in recents, it's just useless.
Click to expand...
Click to collapse
Hi.
Im on Xiaomi.eu 5.10.16 with Google Now launcher. No problem having a lot of tabs open in Chrome.
Its smooth and stable. No ram issues. No better or worse than my Nexus 5.
My experience is that using task killers etc only making things worse. We better leave ram management to the os alone
Thanks
Knievel.
Well, I don't use any task killer or something. I just experience ram shortage symptoms.
Kinda late, but eh...
It's not really RAM shortage, but MIUI's asinine memory "optimization". It basically kicks any apps (even active ones!) from RAM after a while. I've been foaming at the mouth blaming my media player for simply disappearing mid-song randomly without any error messages, when I stumbled over the "memory optimization" setting in developer options. Looking around on the net brought me here. Disabled that sucker, rebooted, no disappearing apps anymore. The phone feels as smooth as it did before, so the usual low memory killer settings work. Tweaked them a bit using kernel adiutor and I'm more than happy. You could also try this in addition, but I wasn't able to get it to run smoothly - apparently an exception. Idle RAM usage fell significantly, though.
Crim Soukyuu said:
Kinda late, but eh...
It's not really RAM shortage, but MIUI's asinine memory "optimization". It basically kicks any apps (even active ones!) from RAM after a while. I've been foaming at the mouth blaming my media player for simply disappearing mid-song randomly without any error messages, when I stumbled over the "memory optimization" setting in developer options. Looking around on the net brought me here. Disabled that sucker, rebooted, no disappearing apps anymore. The phone feels as smooth as it did before, so the usual low memory killer settings work. Tweaked them a bit using kernel adiutor and I'm more than happy. You could also try this in addition, but I wasn't able to get it to run smoothly - apparently an exception. Idle RAM usage fell significantly, though.
Click to expand...
Click to collapse
You're talking about 1 or 2 ?
One, memory optimization. Disabling two, MIUI optimization, is a bit overkill, since it also removes the recent tasks management.
Crim Soukyuu said:
... since it also removes the recent tasks management.
Click to expand...
Click to collapse
There are a thousand and one apps that do that.
@Crim Soukyuu Task manager doesn't dissappear - it can be re-assigned to any button by going into Settings - Additional Settings - Buttons
DarthJabba9 said:
There are a thousand and one apps that do that.
Click to expand...
Click to collapse
But why would you want to use them instead of the built-in one? If you disable MIUI optimizations, you might as well use an un-mutilated AOSP/CM ROM.
jajk said:
@Crim Soukyuu Task manager doesn't dissappear - it can be re-assigned to any button by going into Settings - Additional Settings - Buttons
Click to expand...
Click to collapse
I based my statement on what DarthJabba9 said in the Skinny Pro thread:
DarthJabba9 said:
Disable "Turn on MIUI optimization" in the developer options (if you have enabled developer options). After this, you will have to close down recent apps manually (I use "RecentTask" from the Play Store).
Click to expand...
Click to collapse
In any case, to get rid off the symptoms @sxeMonster was having, it's enough to disable "Memory optimization" in the developer options.
maow425 said:
I set up my own battery profile using the security app. Security - Battery - Battery Profiles. In here I changed the Clean Memory to never.
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
I can confirm the clean memory setting is a major reason for poor battery life,
I've set it to never and my battery life is much better.
Regards
---------- Post added at 05:02 PM ---------- Previous post was at 04:57 PM ----------
Crim Soukyuu said:
One, memory optimization. Disabling two, MIUI optimization, is a bit overkill, since it also removes the recent tasks management.
Click to expand...
Click to collapse
That's correct, no need to disable MIUI optimisation.
Memory optimisation option is basically Zram,
I've got it disabled, too.
Haven't had any ram issues and it can still keep a dozen or so apps on the background before android starts killing them.
Regards
Crim Soukyuu said:
But why would you want to use them instead of the built-in one? If you disable MIUI optimizations, you might as well use an un-mutilated AOSP/CM ROM.
Click to expand...
Click to collapse
Non sequitur. MIUI optimizations are not the only (or even the main) difference between MIUI ROMS and AOSP/CM ROMs.
Sequitur or non sequitur, you haven't answered my question - why would I want to disable MIUI optimization instead of only memory optimization?
Crim Soukyuu said:
Sequitur or non sequitur, you haven't answered my question - why would I want to disable MIUI optimization instead of only memory optimization?
Click to expand...
Click to collapse
Your question was "But why would you want to use them instead of the built-in one?" The answer is "This is a very small price to pay for removing MIUI optimization". Disabling memory optimisation may do the deal for you - but it did not solve all my problems.
I will refer you to the following which is in response to issues that have been raised here.
http://forum.xda-developers.com/redmi-note-2/development/b-skinny-pro-t3347906/page9#post66369078
I disabled a few things given by @jajk , I think the most important one for multi tasking is the battery saver, it closes apps and restricts backgroud activity.
Not only that but too much crap is held in memory by miui.
Get disable service and disable:
InCallUI - CallRecordingRemoteService
Security - SecurityCenterAnalyticsService + SecurityCenterService + PowerSaveService --- it still works just not held in memory
Settings - MiuiWifiService + ObserverService ---- Wifi still works
GooglePlayServices - I disabled a few things I don't need and everything works for me except Gmail account sms verification, I had to put in the code manually.
Default SMS app stays in memory for some reason, I disabled it and using google messenger, just gotta disable wearable service
If disabled it breaks SMS, just disable SmsReportService, SMS works that way. Also in settings disable auto download MMS.
I'm getting 600-700 free ram and apps stay in cache much longer. Outside of settings it reaches 800 Free memory + all apps still in cache
Screenshots: https://www.dropbox.com/sh/a7lq8k5jzo2htcc/AAByd8UBFR4AKAiS9Rcg-dWTa?dl=0
I would prefer better memory management than High Free Memory, because Linux is good already with Memory Management.
Sent from my Redmi Note 2 using XDA-Developers mobile app
You're busy and don't have time to wait, which is why you need to stop reading this thread and get back to organizing your Pogs. Rate this thread to express how the Google Pixel 3 XL performs when multitasking. A higher rating indicates that the Google Pixel 3 XL keeps many apps in memory so that they don't need to reload, and that when moving between apps, transitions are smooth and performance is excellent.
Then, drop a comment if you have anything to add!
Does a poor job of memory management. Apps to be reloaded. I am quite surprised this is occurring.
Chrome pages rarely stay in memory even when jumping to one or two other apps for a short bit. Even the messaging app dumps out frequently. These are Google's own apps too, what's their excuse?
Slightly off topic but I love how safari on iOS devices keeps the last page stored so hitting the back button to the last webpage is instant vs chrome having to reload a page
Seems quite good to me. I loaded Spotify, messages, Viber, what's app, chrome and nest and no reloading. Seem to normally have about 750mb free
I haven't seen much reloading. I do mostly use apps that start each time I open them (like games like Clash Royale, etc), so I'm sure that has something to do with it, but for my most used normal apps I can open Gmail, Chrome, Instagram, YouTube, G+, and some others, and rarely will an app need to pause to reload. They mostly open right where I left off. Maybe if I cycle eight or so apps is when I see a pause/reload.
Seems great to me. I can swap between Discord/Camera/Snapseed/Twitter/YouTube music with no reloading. Taking pictures or videos doesn't pause or completely stop YouTube music like I've seen some YouTubers/reviews comment. I even bumped it up to about as stressful as I could - HDR on, highest mp, take raw, nothing I could do would get the music in the BG to close
I will experience redrawing when I open a game such as FGO or Dragalia Lost, but that shouldn't be shocking, in my opinion
I've tried both streaming apps and local playback of a downloaded podcast and have gotten process kills for every situation. How is it some people have no issue and others don't if it's just a software issue?
Only thing I've noticed is aggressively closing Pandora is I've been out of my car a few minutes. It's a little annoying but doesn't really bother me. Spotify and slacker stay open.
Other than that I haven't had the other issues reported like the camera closing Spotify etcetera
could this be related to the SWAP thats being used aggresively? if someone has root maybe they can test disabling swap, and changing the swappiness value should make things perform better.
Zenoran said:
I've tried both streaming apps and local playback of a downloaded podcast and have gotten process kills for every situation. How is it some people have no issue and others don't if it's just a software issue?
Click to expand...
Click to collapse
I've found it to be due to Adaptive battery. Turn the adaptive battery setting for the app off.
virtyx said:
could this be related to the SWAP thats being used aggresively? if someone has root maybe they can test disabling swap, and changing the swappiness value should make things perform better.
Click to expand...
Click to collapse
How is SWAP adjusted with root?
Battery management seems to be the culprit. I have turned it off as it makes my phone almost unusable; it allows me to use two apps, MOST of the time, but it constantly closes everything else, even when I have told it NOT to optimize specific programs. This is a terrible user experience. TERRIBLE. I hope they make the program less aggressive with a future software update.
As an aside, this was not how things were with Oreo on the Pixel 2 XL, and things weren't this way with the first release of Pie on the XL 2, either. However, I started seeing this after an update to Pie on the XL 2, and it has been constant on the XL 3.
rohmbd said:
How is SWAP adjusted with root?
Click to expand...
Click to collapse
there should be a magisk module
'torpedo' something i think its called
you can also change swappiness to 0 (i think its in /proc/sys/vm )
if you have root you can try swapoff -a in terminal with su
report back on your finding please
RAM management is worse than phones from 2016
So I just got my pixel last week and one of the biggest issues is the RAM.
Sometimes I'll only have THREE things open, Chrome, Podcast Addict, and YouTube for isntance. And the pixel will kill off the podcast (while I'm listening to it still).
The same thing happens when I'm browsing the web, and want to take a picture, boom, kills the music I'm listening too.
It's a BIG issue, happens daily for me.
virtyx said:
there should be a magisk module
'torpedo' something i think its called
you can also change swappiness to 0 (i think its in /proc/sys/vm )
if you have root you can try swapoff -a in terminal with su
report back on your finding please
Click to expand...
Click to collapse
I did that last night - swap is off and, while I'm still getting reloads of Chrome tabs (really the only negative thing I noticed before), the phone *is* a bit more responsive. I've switched back and forth between swap and no swap, and there's definitely a non-placebo difference. I'd give it a shot if you're rooted (I used the Torpedo module in Magisk).
Roll3r said:
I did that last night - swap is off and, while I'm still getting reloads of Chrome tabs (really the only negative thing I noticed before), the phone *is* a bit more responsive. I've switched back and forth between swap and no swap, and there's definitely a non-placebo difference. I'd give it a shot if you're rooted (I used the Torpedo module in Magisk).
Click to expand...
Click to collapse
thats great news!
how many chrome tabs are you using? is it only in chrome tabs that the reloading happens? how about recent apps?
im sure there are a few settings in /proc/sys/vm that can be adjusted to get better ram management
virtyx said:
thats great news!
how many chrome tabs are you using? is it only in chrome tabs that the reloading happens? how about recent apps?
im sure there are a few settings in /proc/sys/vm that can be adjusted to get better ram management
Click to expand...
Click to collapse
I haven't kept track of *any* of that. The phone just feels a bit (hate this adjective) snappier. And from what I understand (don't have the links in front of me) adjusting the LMK settings is going to be difficult.
I keep getting low memory warnings while playing wgt golf. Sucks
is this issue too bad on pixel 3?
i use a pixel 1 xl now and wants to buy a new phone.
getting really concerned and thinking if i should just buy a note 9 or not.
what do you guys suggest?
wtharp2 said:
Battery management seems to be the culprit. I have turned it off as it makes my phone almost unusable; it allows me to use two apps, MOST of the time, but it constantly closes everything else, even when I have told it NOT to optimize specific programs. This is a terrible user experience. TERRIBLE. I hope they make the program less aggressive with a future software update.
As an aside, this was not how things were with Oreo on the Pixel 2 XL, and things weren't this way with the first release of Pie on the XL 2, either. However, I started seeing this after an update to Pie on the XL 2, and it has been constant on the XL 3.
Click to expand...
Click to collapse
You turned off the adaptive battery feature?
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
When you hand your phone to granny to take a photo of you, can she get the job done? Rate this thread to express how you deem the Realme X2's camera software. A higher rating indicates that the software is easy to use, fast, uncluttered, and inclusive of advanced features for when you need them.
Then, drop a comment if you have anything to add!
Holding a RMX1991 Realme X2 8/128.
RMX1991_11_A.10 ROM
The software is nothing to shout about, it seems poorer than my RedmiNote4MTK.
Developer options cannot stay open & uninterrupted by the notification screen.
Overly aggressive power profiles.
Inconsistent - does not have scrollbar in some parts of the settings where it is needed while some parts have a row of alphabets at the LHS, while some don't.
Phone seems to "forget" power profile and permission settings.
How to change realme x2 Chinese version to global
How to change realme x2 Chinese version to global
I have Chinese version RMX 1991 and i want to swap to global kindly help !?
hamood tayeb said:
How to change realme x2 Chinese version to global
I have Chinese version RMX 1991 and i want to swap to global kindly help !?
Click to expand...
Click to collapse
you cant. wait for twrp and flash roms
Color os is really not that bad my x2 just arrived last night and it's the Chinese version and all i had to do is to uninstall all those apps + adb tutorial for the grayed out apps and i was set to go, there was nothing wrong with it at all + i did the latest update and all is good
The only downside so far is that you can't hide the notch in system apps like ... Youtube or Chrome. Gaming mode is better than on MIUI 10, no permanent white line on the left screen, so no burn-in risk in gaming mode.
Do you guys have problems with notifications? I have china version and aplicatios like WhatsApp and instagram doesnt able me to recive notification when they are closed, i can recive only when they are on task lista. I tried changing everycing in configuration and reinstall , still not working... HELP PLS!
SergioDani47 said:
Do you guys have problems with notifications? I have china version and aplicatios like WhatsApp and instagram doesnt able me to recive notification when they are closed, i can recive only when they are on task lista. I tried changing everycing in configuration and reinstall , still not working... HELP PLS!
Click to expand...
Click to collapse
me too. fb and messenger
I want a better camera quality and better software, is the worst aspect in this phone.
SergioDani47 said:
Do you guys have problems with notifications? I have china version and aplicatios like WhatsApp and instagram doesnt able me to recive notification when they are closed, i can recive only when they are on task lista. I tried changing everycing in configuration and reinstall , still not working... HELP PLS!
Click to expand...
Click to collapse
jorgeee said:
me too. fb and messenger
Click to expand...
Click to collapse
#1. Have you tried App Management / (choose the app) / Auto Startup ?
You are only allowed to have 5 apps that auto-startup but I picked the 5 most important one for me.
#2. Have you tried App Management / (choose the app) / Power Saver / Allow Background Running ?
TyTN4Me said:
#1. Have you tried App Management / (choose the app) / Auto Startup ?
You are only allowed to have 5 apps that auto-startup but I picked the 5 most important one for me.
#2. Have you tried App Management / (choose the app) / Power Saver / Allow Background Running ?
Click to expand...
Click to collapse
tried everything nothing changes. you must run the apps background to receive notifications