Open build.prop from system/
Edit then find line
ro.sys.fw.bg_apps_limit=30 (default in emui)
And change to
ro.sys.fw.bg_apps_limit=60 try "60" or more
Save and reboot.
It will make ram managament better.
It means more apps in memory (better using of 4gb ram).
WYPIERDAALAAC said:
Open build.prop from system/
Edit then find line
ro.sys.fw.bg_apps_limit=30
And change to
ro.sys.fw.bg_apps_limit=60
Save and reboot.
It will make ram managament better.
Click to expand...
Click to collapse
Any verified source for this, and maybe a detailed explanation of what the setting does?
All my searching has only turned out info from the Oneplus 3 folks who did this to force use of their 6GB RAM. Even setting this to =42 on the OP3 resulted in RAM use of around 5GB... which is 1GB more than what we have.
With that in mind, going to =60 might just give us OOM errors earlier. Or not.
To begin with, my Nougat Honor 8 (L19) doesn't even have the original ro.sys.fw.bg_apps_limit line in build.prop.
That said, gonna test the setting nonetheless, but not with such an extreme value as 60 right off the bat.
eiraku said:
Any verified source for this, and maybe a detailed explanation of what the setting does?
All my searching has only turned out info from the Oneplus 3 folks who did this to force use of their 6GB RAM. Even setting this to =42 on the OP3 resulted in RAM use of around 5GB... which is 1GB more than what we have.
With that in mind, going to =60 might just give us OOM errors earlier. Or not.
To begin with, my Nougat Honor 8 (L19) doesn't even have the original ro.sys.fw.bg_apps_limit line in build.prop.
That said, gonna test the setting nonetheless, but not with such an extreme value as 60 right off the bat.
Click to expand...
Click to collapse
Ok. I tried this with buggy Lollipop on LG G2M.
And it worked.
30 value is default in Honor 7 , so in Honor 8 we can increase it even more than 60 i think.
It will gives you more apps in memory. Ram managament of emui is very agressive and it kills apps in memory too often.
WYPIERDAALAAC said:
Ok. I tried this with buggy Lollipop on LG G2M.
And it worked.
30 value is default in Honor 7 , so in Honor 8 we can increase it even more than 60 i think.
It will gives you more apps in memory. Ram managament of emui is very agressive and it kills apps in memory too often.
Click to expand...
Click to collapse
I'm trying out 40-50 for now, as the OP3 folks do 60 and they have 6GB RAM lol.
What's actually important is that we find documentation on this setting and how it works. If that value is absolute or is taken in percentage form (e.g. is 60 = 60 or 60 = 60% of the total RAM).
If it's absolute, too high might be a problem. If it's a taken in percentage, it might not matter.
Plus, like I said before, I didn't even have the string to begin with in my original build.prop lol.
eiraku said:
I'm trying out 40-50 for now, as the OP3 folks do 60 and they have 6GB RAM lol.
What's actually important is that we find documentation on this setting and how it works. If that value is absolute or is taken in percentage form (e.g. is 60 = 60 or 60 = 60% of the total RAM).
If it's absolute, too high might be a problem. If it's a taken in percentage, it might not matter.
Plus, like I said before, I didn't even have the string to begin with in my original build.prop lol.
Click to expand...
Click to collapse
No matter if 6 or 4 gb ram. Is not about percent, its about apps in background, for example:if default 30 you can have only 30apps at once. Low devices have for example just 12 etc
Yeah, if no line like this in our build.prop it does not mean we cant test it. System anyway has some default value.
Just tweak the LMK values. It's a whole lot easier to test.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Just tweak the LMK values. It's a whole lot easier to test.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Any recommended settings for LMK?
eiraku said:
Any recommended settings for LMK?
Click to expand...
Click to collapse
I use this one.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
I use this one.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Thanks, testing those settings out through Kernel Auditor, which I need running to hack SELinux anyway, it's good that it has LMK setting too for me to test out.
I went to the battery settings page and turn off the Close All after screen lock option, then added a handful of apps that are listed as power intensive and ones I don't mind re-launching, works great.
Related
hi, i have jit on my stock generic world 2.1 firmware. After jit enabiling my build.prop on 32 vm heapsize, i changed after reading some in an motorola milestone forum , it to 36 vm heapsize with rootexplorer. I can not explain why, but i have the feeling that most of my apps go smother when i launch they. I think my phone is smother. Im newbie, but i have the feeling after change it, try the xda app, for example,find it is faster loading.
sry for bad english, and please make a backup before change it
Do you get more points in Linpack and Quadrant now?
Tried, and all it does is brick your phone
When you restart it ofc! Haha
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Flo95 said:
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Click to expand...
Click to collapse
The more cache heapsize, the faster big apps (like huge games) are running. But small and medium size apps run slower.
The less cache heapsize is, the faster small apps run, but this can be cause of FC of huge apps.
for example, with 12 MB heapsize, small apps will fly on your phone instanly, but medium-size and huge apps will crash everytime.
If u are not playing games and use huge apps, u can set cache heapsize to 24 MB, else the 32 MB is good solution for all in my opinion
Flo95 said:
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Click to expand...
Click to collapse
Hm how did that work?
I'm on 2.1 JIT enabled, global FW... I'm restoring it to the J+Z W 2.1 anyways haha!
I might try it again though, if I can be bothered, I'll post results I'll do it more carefully next time
changed to 36m on mine now. SE-Shipped-Lite ROM
hmmmm...seems smoother
Well, guys... same here) Changed to 36, and have everything smoother. Even if everybody recommends changing between 12-32 only, 36 fits perfect our x10s.
hi, thanks for feedback
i have played with my phone these day, and have no problems
linpack now 17.186 before believe at 16, but not over 17
when somebody have problems, you can go back to 32 or 24 vm heapsize
Alakasam said:
Hm how did that work?
I'm on 2.1 JIT enabled, global FW... I'm restoring it to the J+Z W 2.1 anyways haha!
I might try it again though, if I can be bothered, I'll post results I'll do it more carefully next time
Click to expand...
Click to collapse
I changed 32 to 36 with Root Explorer, saved it and rebooted my device. That's it.
Sent from my X10
Placebo effect.
I made that change and did not notice anything different or more smother, Linpack and Quadrant give lower values
Flo95 said:
I changed 32 to 36 with Root Explorer, saved it and rebooted my device. That's it.
Sent from my X10
Click to expand...
Click to collapse
I think I missed out the 36(m <--) bit XD silly me T_T
Will changing it make running 3D gameloft game smoother? Is the build file under /system folder
tiggerbcn said:
Placebo effect.
I made that change and did not notice anything different or more smother, Linpack and Quadrant give lower values
Click to expand...
Click to collapse
Right. Little apps are slower than before.
I changed it back to 32.
Has someone found a value, that makes the X10 faster? With better benchmarks etc
has anyone tested 18 or 24?
hi you can test it and report it
think it's just a feeling, maybe a bit of fine-cut not for the dramatic performance gains
Flo95 said:
Right. Little apps are slower than before.
I changed it back to 32.
Has someone found a value, that makes the X10 faster? With better benchmarks etc
Click to expand...
Click to collapse
It does say that a smaller vm will make smaller apps faster and larger apps slower. I tend to use news readers and browsers rather than games and the like, so I would if I could be bothered, take it down to 24
Edit: just changed it to 24 and it does feel faster. I was able to use it sooner after boot and my custom animations were lovely and smooth. Thanks for the tip op
Sent from my X10i using XDA App
If you are not a gamer and are an average user with the average apps, then 24 is good. I changed down to 24.
IMO the default value 24 is the best fit for our X10i. Never have a problem and can't feel any different when changing it to 32. Even when I'm in 32, I have to relaunch several apps twice before it works correctly.
So I think I'll stick with 24. ^^
The original heap size of the X10 are 24?
And JIT changes it to 32?
I think 32 is better, because the benchmarks are much better.
Hey there,
Just have a few questions about the V6 Supercharger script by zeppelinrox.
1. Is it worth it on the Atrix? I know that he says it's great for all devices as you can set your own values as well as have it rearrange the memory groupings but I was wondering if I would see any performance improvements?
2. Can it be applied to the Atrix? With our locked bootloader and all, I have very limited knowledge about this and how scripts work but it talks a lot about init.d and I was wondering would anything need to be changed so that it works with our phones/2nd-Init?
3. If it works and is worth it, what do you suggest I put for values?
- If you want a tutorial that, in my eyes, seems easier to understand then you can find it here. -
Thanks in advance
- DarkRyoushii
would rather bump than make a new thread.. I'm really eager to apply this as it rearranges memory groupings so that it's better for multitasking..
"You must be root of course!"...Check
"Using CyanogenMod 7.x.x!".....FAIL
That is just for the simplified guide. Check the first link or the original thread for it, it says it works on standard Rom
Sent from my MB860
As long as your rooted it will work.
But I'm curious about a few things...
With 1 gigabyte of ram is there ever any lag?
If the phone gets laggy, how much free ram do you have when this happens?
What are the default minfree values?
I was surprised initially that some V6 presets improved droid X2 and evo4g performance but V8 will include megamemory settings, with 512mb devices in mind, of 6, 12, 75, 125, 150, 175 mb
Hey,
How would I go about finding out the default minifree values?
For me I see quite a bit of lag when the ram hits near 200mb however I am also plagued with horrendous lag when using live wallpapers so I'm willing to try everything haha
DarkRyoushii
Sent from my MB860
zeppelinrox said:
With 1 gigabyte of ram is there ever any lag?
Click to expand...
Click to collapse
No, Ive never experienced any lag on the Atrix. Its fast! Some peeps complain about lwp lag, but I dont have a prob with that either. If anybodys Atrix is lagging its because they are doing something wrong.
DarkRyoushii said:
Hey,
How would I go about finding out the default minifree values?
For me I see quite a bit of lag when the ram hits near 200mb however I am also plagued with horrendous lag when using live wallpapers so I'm willing to try everything haha
DarkRyoushii
Sent from my MB860
Click to expand...
Click to collapse
Run the script.
It will tell you your current minfrees right when you open it under the list of options.
edit: Test this set 6, 12, 150, 200, 250, 300 mb
If it's the ones listed as system default in autokiller memory optimizer then they are:
6, 8, 16, 20, 22, 24
Sent from my MB860
Are you FKM?
lol
Freaking stock telus froyo minfree values are more aggressive at 8, 12, 24, 28, 32, 32
Google's GB values are 8, 12, 16, 24, 28, 32 which are still slightly more aggressive...
Unbelievable.
wow just applied "this set 6, 12, 150, 200, 250, 300 mb" and on reboot my phone is sitting on ~600MB free RAM instead of ~300MB!
DarkRyoushii said:
wow just applied "this set 6, 12, 150, 200, 250, 300 mb" and on reboot my phone is sitting on ~600MB free RAM instead of ~300MB!
Click to expand...
Click to collapse
And the verdict on LWPs?
still just as broken :/
phone feels snappier when loading menus and stuff though.. like going through settings and stuff.
Heh... well adjusting the mifrees to get more free ram is the easy part.
The hard part is the OOM grouping fixes that always keeps the launcher snappy and finding minfree values high enough that the phone never lags but not so high that it deters multitasking.
So the big question is, is multitasking just as good as before?
When you leave an app and go back to it later, it still remembers what you were doing?
well I'm not usually a big multitasker but I'm able to switch between 5 apps (2 of which are games) seamlessly.. not sure if it's good or not as it's probably the most I've tried at once :3
Probably gonna call it quits for the night though, nearing 3am and I gotta be at work tomorrow morning. Thanks for all your help! really appreciate it
EDIT: Interesting? After Reboot I looked at my new minfree values using your script and found they are different from what I set, they are now 12, 18, 36, 121.094, 128.906 and 136.719
seems slightly odd but okay, still snappier than what I started with anyway I better sleep, will be back tomorrow night!
Akmo or amm may be applying settings on boot
Sent from my Milestone using Tapatalk
I uninstalled both before running this script to avoid that
Sent from my MB860
maybe those are your roms default values?
either way, the V6 settings arent sticking... so you need SM to load at boot either /data/99SuperCharger.sh or /system/etc/init.d/99SuperCharger
Updated V6 SuperCharger includes MegaMemory setting... check it out!
Thanks! how do apply this megamemory setting? also I noticed that after my friend played a game on my atrix it never quit after closing it, the phone ended up getting REALLY hot to the point where I felt it through my pants in class later and looked to find my batter on 17% after 5 hours of being unplugged.. I guess I just have to screw with the minfrees or MegaMemory settings depending on which will help me more..
Is there any rom based on cm13 enables to customize screen colours saturation ????
like the features present in custom kernel for miui (screen colour)
I'm currently working on CM13 based kernel with KCAL support. The first beta should be ready in the next couple of days. Can't give exact time because I'm testing it right now, but boy with the lack of custom kernels currently for RMN3, this probably will be on every rooted phone here
ktomov said:
I'm currently working on CM13 based kernel with KCAL support. The first beta should be ready in the next couple of days. Can't give exact time because I'm testing it right now, but boy with the lack of custom kernels currently for RMN3, this probably will be on every rooted phone here
Click to expand...
Click to collapse
Could you add kernel same page merging to it? It reduces RAM usage a lot
Grantius said:
Could you add kernel same page merging to it? It reduces RAM usage a lot
Click to expand...
Click to collapse
Yeah, but on cost of cpu. I don't really see a reason to have it on a device with 3gb of ram. Will think about it but that's on the end of the feature list that I need.
Edit: Well that was easy. You'll have KSM in the kernel.
Personally, i don't understand why people complain about "omg ram usage too high" on 2gb or 3gb devices. It's like they expect to see 80% free ram all the time. Some even have a habit of constantly killing all apps/processes to get ram back from the system. The truth it though, letting android fill it up with cache seems to make more sense to me. Like in a PC, what's the point of having 16gb ram if i'm going to make sure it's always 80% free ram. Android clears the ram out when it needs it anyway. But that's just a personal opinion.
I think i would settle for Qualcomm Assertive Display, quite useful under sunlight. Then again, contrast/gamma adjustment would be awesome too. HAHAHA looks promising
shaanyt said:
Personally, i don't understand why people complain about "omg ram usage too high" on 2gb or 3gb devices. It's like they expect to see 80% free ram all the time. Some even have a habit of constantly killing all apps/processes to get ram back from the system. The truth it though, letting android fill it up with cache seems to make more sense to me. Like in a PC, what's the point of having 16gb ram if i'm going to make sure it's always 80% free ram. Android clears the ram out when it needs it anyway. But that's just a personal opinion.
I think i would settle for Qualcomm Assertive Display (QAD), quite useful under sunlight. Then again, contrast/gamma adjustment would be awesome too. HAHAHA looks promising
Click to expand...
Click to collapse
True, I'm happy with 3GB of RAM, and always running my phone with all of my favourite apps till the Free RAM is just about 300MB. Killing apps like a Madman is not Multitasking. Just run it and minimise it, let the Android manage the tasks for us, switching between apps would be quicker, no constabt apps reload, and so on.
Forget about it because I would like to discuss about Qualcomm Assertive Display.
In every CM13 ROMs out there, the property for QAD was present in the build.prop, but it's pointing to the wrong path, the config file for QAD was never existed in CM13. So I study how MIUI handles QAD and modify current CM13 build.prop (I'm using the TheStrix build with F2FS support, plus TWRP he made for F2FS) on my phone.
Original property for QAD on CM13 ROM:
Code:
# Qualcomm
ro.qualcomm.cabl=2
ro.qcom.ad=1
ro.qcom.ad.calib.data=/data/misc/display/ad_calib.cfg
Check that '/data/misc/display/ad_calib.cfg' on your phone, it's missing and nowhere to be found.
So I take the calibration config file from MIUI 8 (/system/etc/calib.cfg) for the QAD and then put the file into current CM13 setup on my phone (/system/etc) and edited the CM13 build.prop following the MIUI build.prop, to become like this:
Code:
# Qualcomm
ro.qualcomm.cabl=2
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/calib.cfg
ro.qcom.ad.sensortype=2
And LiveDisplay now works flawlessly by setting it on Automatic, not bugged/stuck anymore.
Dude, let's try and share your experience. My eyes are not that color sensitive, so maybe you could see the difference.
Sent from my Redmi Note 3 using XDA Labs
MOVZX said:
True, I'm happy with 3GB of RAM, and always running my phone with all of my favourite apps till the Free RAM is just about 300MB. Killing apps like a Madman is not Multitasking. Just run it and minimise it, let the Android manage the tasks for us, switching between apps would be quicker, no constabt apps reload, and so on.
Forget about it because I would like to discuss about Qualcomm Assertive Display.
In every CM13 ROMs out there, the property for QAD was present in the build.prop, but it's pointing to the wrong path, the config file for QAD was never existed in CM13. So I study how MIUI handles QAD and modify current CM13 build.prop (I'm using the TheStrix build with F2FS support, plus TWRP he made for F2FS) on my phone.
Original property for QAD on CM13 ROM:
Code:
# Qualcomm
ro.qualcomm.cabl=2
ro.qcom.ad=1
ro.qcom.ad.calib.data=/data/misc/display/ad_calib.cfg
Check that '/data/misc/display/ad_calib.cfg' on your phone, it's missing and nowhere to be found.
So I take the calibration config file from MIUI 8 (/system/etc/calib.cfg) for the QAD and then put the file into current CM13 setup on my phone (/system/etc) and edited the CM13 build.prop following the MIUI build.prop, to become like this:
Code:
# Qualcomm
ro.qualcomm.cabl=2
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/calib.cfg
ro.qcom.ad.sensortype=2
And LiveDisplay now works flawlessly by setting it on Automatic, not bugged/stuck anymore.
Dude, let's try and share your experience. My eyes are not that color sensitive, so maybe you could see the difference.
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
I'll try later tonight hahaha. But i think it's easier to notice if u point a flash light at the light sensor, then drag down notification, if the super dark gray toggles become like light gray (since QAD is mainly for sunlight visibility, it changes "dark stuff" into less dark so that we can see that there's something there), then it works that's how i tested last time when i was using MIUI... it's very very high tech testing method.
Update : Just tried it. it boots, but no changes in contrast / black level under intense light. Usually for QAD if there's strong light on the ambient light sensor, QAD causes the black levels to become more gray so we see better, i tried this and nothing happened. Perhaps it needs to be kernel supported or something. #sad hahahha
shaanyt said:
Check that '/data/misc/display/ad_calib.cfg' on your phone, it's missing and nowhere to be found.
So I take the calibration config file from MIUI 8 (/system/etc/calib.cfg) for the QAD and then put the file into current CM13 setup on my phone (/system/etc) and edited the CM13 build.prop following the MIUI build.prop, to become like this:
And LiveDisplay now works flawlessly by setting it on Automatic, not bugged/stuck anymore.
Dude, let's try and share your experience. My eyes are not that color sensitive, so maybe you could see the difference.
Sent from my Redmi Note 3 using XDA Labs
I'll try later tonight hahaha. But i think it's easier to notice if u point a flash light at the light sensor, then drag down notification, if the super dark gray toggles become like light gray (since QAD is mainly for sunlight visibility, it changes "dark stuff" into less dark so that we can see that there's something there), then it works that's how i tested last time when i was using MIUI... it's very very high tech testing method.
Update : Just tried it. it boots, but no changes in contrast / black level under intense light. Usually for QAD if there's strong light on the ambient light sensor, QAD causes the black levels to become more gray so we see better, i tried this and nothing happened. Perhaps it needs to be kernel supported or something. #sad hahahha
Click to expand...
Click to collapse
Then I'm sure it's that 'Automatic Contrast' settings under MIUI which controls the QAD. And unfortunately there are no custom kernel at this point that supports that MIUI feature since no source code given.
Sent from my Redmi Note 3 using XDA Labs
MOVZX said:
Then I'm sure it's that 'Automatic Contrast' settings under MIUI which controls the QAD. And unfortunately there are no custom kernel at this point that supports that MIUI feature since no source code given.
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
i suppose the config library thingy depends on a certain variable being set to tell it to start its job. Maybe if we know what it depends on, we can activate it or something. Or, just a random thought, the sensortype thing is wrong, at least, for CM13, maybe it should be another number? Since i have no idea what that string means.... i know it declares sensortype, but i don't know what 2 is
shaanyt said:
i suppose the config library thingy depends on a certain variable being set to tell it to start its job. Maybe if we know what it depends on, we can activate it or something. Or, just a random thought, the sensortype thing is wrong, at least, for CM13, maybe it should be another number? Since i have no idea what that string means.... i know it declares sensortype, but i don't know what 2 is
Click to expand...
Click to collapse
I shall try to compare Stock MIUI kernel with CM13 kernel later...
Sent from my Redmi Note 3 using XDA Labs
MOVZX said:
I shall try to compare Stock MIUI kernel with CM13 kernel later...
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
Weird thing is, even the QCOM AOSP 5.1.1 ROM that was "leaked" doesnt have assertive display activated LOLLLL
Update : BTW I have two redmi note 3s; 1 on MIUI, 1 on CM13. QAD (when it works) does make the screen easier to look at under strong lighting as it shifts the black level and contrast, but i found out that QAD is very buggy on China Developer ROM MIUI 8, it rarely works. Sometimes u need to reboot a few times for it to work, then if u reboot, it's gone again...
So I'll just wait for this kcal kernel hahaha
@ktomov Elementalx nice man. Looking forward to this kernel. Then we can unlock our dragon
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 Honor 8 Pro performs when multitasking. A higher rating indicates that the Honor 8 Pro 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!
6gb ram is enough for anything you through at it. All the apps once loaded are staying in the ram for almost ever. For once in the first week with my phone, I was playing contra on it and then left it as is. After few days, I wanted to switch to some other app and found contra there, it was still paused with contra shooting. I don't even remember how many days it was like such.
There is a feature where you can blacklist an app or allow it to be closed on locking of the device which will remove the app from the memory. This is to optimize the battery life. So other than the social apps and certain apps which I switch to mostly, I've blacklisted all other apps.
aKp1 said:
6gb ram is enough for anything you through at it. All the apps once loaded are staying in the ram for almost ever. For once in the first week with my phone, I was playing contra on it and then left it as is. After few days, I wanted to switch to some other app and found contra there, it was still paused with contra shooting. I don't even remember how many days it was like such.
There is a feature where you can blacklist an app or allow it to be closed on locking of the device which will remove the app from the memory. This is to optimize the battery life. So other than the social apps and certain apps which I switch to mostly, I've blacklisted all other apps.
Click to expand...
Click to collapse
Are u working for huawei?
mab71 said:
Are u working for huawei?
Click to expand...
Click to collapse
LOL! I am impressed by this device doesn't mean I work for huawei:laugh:
aKp1 said:
LOL! I am impressed by this device doesn't mean I work for huawei:laugh:
Click to expand...
Click to collapse
:laugh:
So far, so good. Switching apps is fast.
Ram management has been hit after the recent update.
Sent from my Honor 8 pro using Tapatalk
K.khiladi said:
Ram management has been hit after the recent update.
Sent from my Honor 8 pro using Tapatalk
Click to expand...
Click to collapse
just curious... how bad was it? can elaborate?
Where exactly is this feature?
aKp1 said:
6gb ram is enough for anything you through at it. All the apps once loaded are staying in the ram for almost ever. For once in the first week with my phone, I was playing contra on it and then left it as is. After few days, I wanted to switch to some other app and found contra there, it was still paused with contra shooting. I don't even remember how many days it was like such.
There is a feature where you can blacklist an app or allow it to be closed on locking of the device which will remove the app from the memory. This is to optimize the battery life. So other than the social apps and certain apps which I switch to mostly, I've blacklisted all other apps.
Click to expand...
Click to collapse
Where exactly is this feature in honour 8 pro? Please share
lovelifeusilly said:
Where exactly is this feature in honour 8 pro? Please share
Click to expand...
Click to collapse
Settings-> Battery -> Lock Screen Cleanup
K.khiladi said:
Ram management has been hit after the recent update.
Click to expand...
Click to collapse
How much apps it can keep in the background?!
6 would be enough for me
PalakMi said:
How much apps it can keep in the background?!
6 would be enough for me
Click to expand...
Click to collapse
It has gotten totally right now. I had reset my phone and it became better after sometime.
Sent from my Honor 8 pro using Tapatalk
K.khiladi said:
It has gotten totally right now. I had reset my phone and it became better after sometime.
Click to expand...
Click to collapse
That's a relief
6gb ram is soooo goddamn sweet.
It handles multitasking single handed.
Good RAM management, all apps are stored in RAM quite well.
multitasking is handled pretty well. 6 GB RAM is handling this exceptionally well.
6gb ram is enought for multitasking and also relly impress with management.
ram is more than enough for heavy multi tasking..
You can leave all apps in memory and you'll still have some left.
Hi,
I used to love my Kenzo 2 gb version, untill I found out that his 1,8 gb of ram are so so low. But, is that true?!
I mean 2 gb are the minimun requirement for MM or NG I think, but with miui, miui port, NG based rom (didn't try oreo, or lineage MM), custom kernel, anything the ram management is really really bad.
After only two days of usage, free ram became 200mb or even 100mb with no social media app (just telegram and instagram with no notification allowed) or anything. Doze, greenify, clear ram or not clear it, doesn't change the situation, used ram increase day by day untill the phone is laggy and unusable.
So you have to restart the phone at least every two day. It's crazy today.
On custom ng roms the situation is a bit better but on miui, damn, the ram is so full that sometimes I can't even open the keyboard or camera.
Every 2 gb phones has this issue? is an MM/NG problem? or is a kenzo problem? is there something I (or we) can do to menage ram more efficently (I don't want free ram, I want a ram used in the correct way).?
thank u
Very good question, i suggest you make manual tweaks to lmk (low memory killer), it has helped my rn3 2gb multitask better on oreo
Sent from my Redmi Note 3 using Tapatalk
I have too faced that problem. It's mainly due to ROMs. Some ROMs have lag no matter which kernel you use or how much tweak it. I have literally tried each and every custom rom which are updated and found only some ROMs which have less noticable lag. Default miui rom, aex, RR by movzx, nos some builds and Oreo, and slim rom. On other rom I tried different kernel and when tweaked it to max but still lagged as hell. Even opening dialer app sometimes froze the system leave aside heavy gaming. This is really serious issue on 2gb because of which we are restricted to certain ROMs.
I too have a 2GB kenzo, but never had such problems...currently using NOS Oreo and it is fluid & fast. Same on miui.
Right now system occupies around 700MB + around 400MB apps, rest is available. Never had RAM problems myself...luckily.
Buy MI device unlock bootloader next day > Flash custom ROMs > RIP ****UI
That is the main reason why I've changed my Kenzo 2gb. I wasn't able to use miui at all with this phone, app killing and lagging was a daily basis. So I used the most Ram friendly rom with this phone, but still keeping more than 3 apps in the memory was a problem.
Idk, but maybe it's because of the x64 architecture (similar to pc, this architecture uses more ram). I had many phones with 32gb and x32 architecture and ram was never an issue.
So trust me, I've tried everything to improve the ram efficiency, but not much has changed. The only solution for me to change the phone.
Sent from Note 3, Xiaomi Redmi Note 3.
man use rambexpander app you can have 4 GB RAM and it does work very well
Sent from my Redmi Note 3 using XDA-Developers Legacy app
[email protected] said:
Very good question, i suggest you make manual tweaks to lmk (low memory killer), it has helped my rn3 2gb multitask better on oreo
Click to expand...
Click to collapse
I don't know how to turn the lmk aggressive on radon I know that I have to edit the radon.sh script but I don't know what I have to write there.
Oreo I think is pretty unstable for me know better wait some months
diyar95 said:
man use rambexpander app you can have 4 GB RAM and it does work very well
Click to expand...
Click to collapse
I read that that app bricked some devices. Does it really help? It just create a swap partition I believe
RealPsygnosis said:
I don't know how to turn the lmk aggressive on radon I know that I have to edit the radon.sh script but I don't know what I have to write there.
Oreo I think is pretty unstable for me know better wait some months
I read that that app bricked some devices. Does it really help? It just create a swap partition I believe
Click to expand...
Click to collapse
Oreo is unstable, but i can't go back
I use agni, so its easy af to change lmk settings
Anyway, you should set it to light, not aggressive bro
Sent from my Redmi Note 3 using Tapatalk
Ram to sd for konzo
Does ram to sd like some app works really i havent rooted my phone still on stock miui reply soon... I also face ram management problem on my kenzo 2gb
i have around 400-500 mb of free ram, i'm using greenify often and set background process limit to 4.
i uninstalled every apps that not really used and yeah less lag noticed