Related
does MinFreeManager and apps similar to it actually work on our phones? can anyone confirm they work even though we are still Nand locked?
Yes, it works. My personal choice for such a task is Autokiller.
http://www.appbrain.com/app/com.rs.autokiller
xvenom89 said:
Yes, it works. My personal choice for such a task is Autokiller.
http://www.appbrain.com/app/com.rs.autokiller
Click to expand...
Click to collapse
how did you confirm that it actually works?
on MinFreeManager i just set empty to 200, and the next one to 100 and i still have only 110MB free.
i know 200 is a ridiculous number to set it to, but shouldn't i see things getting killed and a number closer to 200 when i check available memory? i would just like to see it do something.
EDIT: i really don't think MinFreeManager is working. i set the values to 200, 150, 100, 50, 25, and 10. i still only have 106MB free according to System Panel. i know these are really high values, but i would think i would see it doing something.
ok, it actually may be working.
with my crazy high values set i opened pretty much every single app i have on my phone and the memory never dropped below 95MB or so.
i then set the values much much lower (the mild setting) and was able to get it down to the mid 60's. so i guess it's working, but it just isn't as aggressive as i expected.
what do you think?
xvenom89 said:
Yes, it works. My personal choice for such a task is Autokiller.
http://www.appbrain.com/app/com.rs.autokiller
Click to expand...
Click to collapse
Minfreemanager might be the most lightweight, but I like AutoKiller the best too -- big battery saver, our RAM isn't close to being challenged yet, but it prevents background processes from hogging RAM. I like the "extreme" or "strict" settings -- and yeah, when I up the preset, the amount of RAM available jumps up as the Java VM grabs RAM back. Also, I like White Killer, for the quick-kill of everything but what you think you need.
I'm giving Autokiller a go right now. I have it set at 150, 100, 75, 25, 10, and 5.
I had been using either Autokiller or Auto Memory Manager on my rooted Moto Droid since day one and it worked great on it. i just wasn't sure it was working on the Inc since we aren't quite as rooted as the Droid yet.
jasonb1985 said:
I'm giving Autokiller a go right now. I have it set at 150, 100, 75, 25, 10, and 5.
I had been using either Autokiller or Auto Memory Manager on my rooted Moto Droid since day one and it worked great on it. i just wasn't sure it was working on the Inc since we aren't quite as rooted as the Droid yet.
Click to expand...
Click to collapse
It works by using commands available in the stock command console, just like Phone Prioritizer manipulates renice frequency to make the phone go more fast Or . . . Memory for Lemmings prompts Java VM to check to see what memory it can take back from dormant apps.
jasonb1985 said:
ok, it actually may be working.
with my crazy high values set i opened pretty much every single app i have on my phone and the memory never dropped below 95MB or so.
i then set the values much much lower (the mild setting) and was able to get it down to the mid 60's. so i guess it's working, but it just isn't as aggressive as i expected.
what do you think?
Click to expand...
Click to collapse
I've only had an android phone now for a few weeks...my first smartphone, but I'm very interested in the inner workings so bear with me.
I'm with you on whether or not it is working. I set my values really high...250 for my last three numbers really expecting to see something happen such as all the apps that were "empty" being killed to free up some memory. Instead my memory got down in the 180s. Are we just confused about how the internal memory manager should work with these values?
Just thought i should share this...
I have been running MIUI for quite a long time now , but the amount of RAM available gets very low with usage..sometime even 32MB . So I had to kill the background services to get more RAM as.. with less RAM phone becomes very laggy
Yesterday I found one app "AutoKiller Memory Optimizer"....its not a task killer...it manages memory.
This app just did the trick...my phone is not at all laggy now...and RAM available is in range of 100 now.
I used optimized preset ...no other change.
I think free one does not have presets
Here are the settings preset gave me, if you want to manually change in free version
foregorund app 6
visible app 8
secondary serve 16
hidden app 40
content provider 50
empty app 60
I think any one with ram issue should try it.
My wife and I had Motorola Milestones before the Vibrants and they had extremely low memory with this (which is where I learned so much about memory and battery management). When I say low, I mean 256mb total. So that meant on start up, we could get about 60-80 free RAM and then once the processes started and it settled down, it hovered around 55-60. That is not a lot when it comes to everyday "fun" stuff. I have been using AKMO for sometime now and I agree that if you are having memory problems (I forgot where my keys are), then this is a good app for you.
Some things though.
To start out, you should use the presets. Optimum is a great place to start.
Once you get the hang of it and what it does, switch to Strict. It ups the page settings.
Then if you think you know what you are doing, go into settings and hit advanced tweaks and you can adjust the settings for all 6 delineations. **If you do this, do not set it to auto-start at boot until you know that your custom settings will work correctly. It also has a 2 minute delay to start after boot for this very reason.**
These are my settings for my wifes Motorola 16,16,64,64,70,94
And finally. AKMO does NOT play nicely with Supercharger. So it is a one or the other type thing. Some people don't use Supercharger or don't understand it. For those types this is a good app for you.
I chanced upon an app that could enable android users the ability to true multitask. Android is designed to cleverly close apps in the background that it deems unimportant. This feat is brought to fruitation through the assigning of minfree values. The higher the minfree value, the more seceptible the app is in being axed to conserve ram and computing space which inturn conserve battery.
With this in mind, theoretically, if we assign an app with a minfree value of 0, the apps will not be killed even when kingdom come. Pardon my attempt at humour if you aren't chuckling.
Now to the crux of this post. There is an inherent difficulty to assign minfree values and not everyone is a coder. Luckily there is an app on the market which let users assign minfree values and better yet, filters the apps into hidden apps and stuff. Simply download this free application from the market:
https://play.google.com/store/apps/...t=W251bGwsMSwxLDEsImNvbS5ycy5hdXRva2lsbGVyIl0.
Go to settings, enable advanced mode to get access to the first three values. One simply inputs "0,0,0,0,0,0". And voila, theoretically all hidden/background apps will not be killed and true multitasking is achieved.
A quick test of some programs that are designed to close after home button is pressed does not close now. Am happy to report that this trick does not close any background app. Only downside is user has to manually close the apps, which for me is more than ok. Hope this helps!!
[Update] I have changed all fields to 0. So technically what I am telling the GSIII is "do not have coffee breaks,toilet breaks and oh, "I own your sorry ass".
Am excited to report that N.O.V.A. 3 still continued running after opening maps with GPS, XDA, Maps, Internet browser. All of which are running.
[Update 2] Edited the values to "0,0,1,1,1,1" as a failsafe in case all rams have been used up. E.g. NOVA3 and MC3 concurrently running due to carelessness. Will report any drastic behaviour or successfully implementation without much drawbacks.
Sent from my GT-I9300 using xda premium
I'm interested to know how this affects battery life.
jiggytom said:
I'm interested to know how this affects battery life.
Click to expand...
Click to collapse
I am pretty sure this will suck the bejesus out of the battery. : ) Plus we aren't using the software for its intended use.
I did the same
Interesting to try...
sebarkh said:
I did the same
Interesting to try...
Click to expand...
Click to collapse
If in the event u have reached a satisfactory value do share! I was inspired by the "backgrounder" program of jailbroken IOS devices. It does the same thing except our way is different. From my Iphone days I have fetishes of true multi tasking. : )
Sent from my GT-I9300 using xda premium
The Linux/Android kernel WILL run OOM-Killer (Out-of-memory) with SIGKILL (removes the process from RAM and CPU without letting it any chance to save data or report) when the memory is full and it cannot continue operation otherwise.
Dalvik _should_ work around a full memory but by disabling this feature it won't so you might experience some data loss.
Consequently it is necessary to have a sufficiently large Swap-Partition on your SDcard to allow the kernel to get more memory whenever needed. It won't be fast when it hits the limit but at least it still works.
d4fseeker said:
The Linux/Android kernel WILL run OOM-Killer (Out-of-memory) with SIGKILL (removes the process from RAM and CPU without letting it any chance to save data or report) when the memory is full and it cannot continue operation otherwise.
Dalvik _should_ work around a full memory but by disabling this feature it won't so you might experience some data loss.
Consequently it is necessary to have a sufficiently large Swap-Partition on your SDcard to allow the kernel to get more memory whenever needed. It won't be fast when it hits the limit but at least it still works.
Click to expand...
Click to collapse
Well on top of that, the Minfree was programmed so that the CPU doesn't have to overwork and so it can run at lower frequencies.
Interesting app, but I'm going to leave the programming to the experts.
Plus prog is too much of a hassle for too little gains in this case. Hahaha.
I have to say that I miss the way the Palm Pre multitasked the best. I also like how pre handled contacts with multiple numbers/IM/google etc (something that ios6 is finally going to attempt to do). It would incorporate all of them into one message window using icons. If only some of that could be incorporated into Android!
Hello everyone.
My issue is rather simple.
I used to have a Galaxy S3 that had a really poor multi-tasking experience with its very limited 1Gb of RAM.
So I bought the Note 3 that was bound to provide me with enough RAM for a better multitasking experience.
So far it was OK and way better than S3 capability but then KitKat came along and this is where my nightmare began.
Simply put, I cannot take benefit of the 3Gb of RAM I have on my device.
My Galaxy Note 3 is the international version bought in France with a Snapdragon S800 and 3Gb of RAM.
During my every day usage, I ofently switch between a certain sets of applications so to me, it is very important that these applications are not killed.
My original settings :
OOM is untouched, though I tried to set it to light with System Tuner but it did not help.
I have a few services that are launched when the device boot : Network Speed to measure bandwith in real time, OS Monitor to display CPU and RAM usage in real time as well and finally System Tuner.
Under develpoment options in the Settings, the limit of apps in background is set to standard (by default)
This is a sequence of test runs I made to show what is going on and why I deem my multitasking experience poor.
In the aim to offer accurate data, this is the list of apps I am using a lot :
app 1 = World War - a 2D non dynamic video game ;
app 2 = iMobster - same as above ;
app 3 = TweetCaster - a twitter client
app 4 = EvolveSMS - a SMS client. Can take a lot of RAM if many SMS are loaded (over thousands of SMS = 100Mb of RAM)
app 5 = Google Chrome - the web browser (not beta) with one tab loaded, two tabs saved but unloaded
Here we go.
Reboot phone -> 1.5Gb of free RAM (1.9Gb at the beginning then 1.5Gb in average after waiting for the aforementioned on-boot apps to be launched)
Launch app 1 -> 1.4Gb of free RAM
Launch app 2 -> 1.3Gb of free RAM
Launch app 3 -> 1.0Gb of free RAM
Launch app 4 -> 800Mb of free RAM
Launch app 5 -> 600Mb of free RAM
Upon each launch I waited for the app to be completely loaded (no splashscreen or loading screen). Then I check with both OS Monitor and System Tuner's widgets to check up the free RAM (sometimes their data differ, but not a lot ~100/200mb).
Repeating this particular sequence bears the same results : when launching app 5 (Google Chrome), app 1 and 3 are closed.
Some time only one of them. But most of the time two apps are closed.
Futhermore, I notice I can't not get less than 500Mb of free RAM. Unless I use Google Chrome to load heavy websites, there is no way than by launching more apps I will get under this limit.
Simply put, I cannot have more than 4 to 5 apps running in background.
I tried different ROMS :
- 2 based on Samsung KitKat ROMs : Jackyaway and S5 port V6. I have the same issue.
- CM 11. : too unstable at the time but perhaps better because the OS takes less RAM than Samsung.
So here I am.
When I was on Android 4.3, it was nice, Moving to 4.x is a disaster.
What can I do ? How is your experience ? How many apps do you manage to keep in the background ?
You are aware that the default setting for 'keep in background' equals 4?
Sent from my SM-N9005 using Tapatalk 2
ShadowLea said:
You are aware that the default setting for 'keep in background' equals 4?
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
Then how can I change it ???
This is really common and isn't an issue. Android will cache a lot of resources in RAM. When that RAM space is needed, the cache is freed. Do not worry.
Colton127 said:
This is really common and isn't an issue. Android will cache a lot of resources in RAM. When that RAM space is needed, the cache is freed. Do not worry.
Click to expand...
Click to collapse
Sorry but no.
How come ..
In Android 4.3 I had better multi-tasking experience (more apps in background) while having a smooth system ...
In Android 4.4,x I have an horrible multi-tasking experience (less apps in background).
I mean I have been doing more tests and it's driving me CRAZY ! After just rebooting my phone, I have about 1300Mb of FREE RAM and then after starting my 4 usual applications, it still have 1Gb of FREE RAM, why, please tell me why would Android feel the need to kill one of these apps after I launched a 5th one ?
This is getting ridiculous ! In what world could Android based on Linux kernel simply decide to kill my apps when it has 1Gb of FREE RAM !
When I was on 4.3 I could have ;
- my 2 2D video games
- my twitter client
- my SMS application
- chrome with 3 tabs opened
- play store opened,
- galerie displaying a picture
etc etc.. all stayed in background. They just got killed whenever I started a heavy application such as a 3D video game and in that case it's completely normal.
Heck I even recalled playing to Asphalt 7 then having a phone call while replying to an SMS (or checking my tweets) all at the same time.
Guess what I can do, now in KitKat ?
Oh god I hate my self for moving to kitkat. Makes me want to throw my phone away.
Search for zeppelinrox's V6 supercharger, I recall it has a feature to allow more apps to run in the background.
I am yet to do this myself, noticed the poor multitasking also.
Someguyfromhell said:
Search for zeppelinrox's V6 supercharger, I recall it has a feature to allow more apps to run in the background.
I am yet to do this myself, noticed the poor multitasking also.
Click to expand...
Click to collapse
That could be a solution. I used in on my Galaxy S3 but it did little help since the phone was lame at the beginning.
I never believed I would use it again on the phone I deemed good for multitasking.
But I am glad to hear that I am not the only one thinking the same thing.
I will try the fix and post here my findings. Should you try the same thing, do not hesitate to share your experience here.
Bump
Quite some time have passed since my last post here ... but my problem remains still.
I've juste moved to Cynogen Mode 11 as of last Snapshot (stable) version.
Overall, the system is stable. Much faster, way smoother. I won't miss TouchWiz I think.
RAM usage is lower : now on boot with the same services I like to have, it sill have over 1.6Gb of free RAM.
That's quite a lote I would like to use, but still can't.
But I must be fair, my multitasking experience is slightly better. First because I can finally have other options to switch between apps other than by long-pressing the home button.
But also because it seems I can finally have a few more apps staying in the background.
When looking for solutions to my problem, I ran across this : RAM and multitasking...so bad.
I said : "finally, someone understanding me".
I read all replies, and this is what seems to come out : KitKat seems to have a built-in feature that auto-kills app whenever a limit of active apps is reached.
This limit is around 10 and 20. I don't know where this limit is set, how it is defined, where I can find, how I can change, and why it exists.
I believe V6 Supercharger did change that limit on Jelly Bean and ICS. I thought this limit disappeared in 4.3.... did it come back in 4.4 ?
Does it work on KitKat ?
Well, I hope someone here can help me. Thanks !
Bump to this. I have a Xperia Z3 Compact and experience the same problem... I never have this problem before with other devices in 4.3.. The multitask since Kitkat is just horrible.
This thread is for the fortunate subset of 5th Gen Fire devices that are rooted and rocking a custom ROM. It should also work on rooted FireOS (5.3.1 and below) that have both ads and OTA updates blocked.
There have been numerous posts regarding uneven performance while multitasking along with sluggish response after waking the device from a long slumber. Most recognize this is due to excessive swapping associated with limited user addressable RAM. While there are a number of incremental 'tweaks' that can marginally improve this behavior my objective was to realize a more substantial improvement with minimal effort, knob turning and side effects. To date I have realized the benefit (minimal lag; responsiveness approaching devices with twice the RAM; woohoo!) but still working on the automation that will make it largely transparent. Lacking the time to work on the latter I thought it best to toss out the high level config and let others, if interested, work through both validation and implementation details.
As an aside, I have used the same technique on a 2nd gen HD running CM 11 that had been shelved for many months due to the same issues. It now hums along at a respectable pace and is once again a joy to use.
The secret sauce is simple: expand zram space allocation and add a small, secondary swap file in a normally unused location in permanent storage.
Tools (or adb/shell/terminal commands for those with furry chests):
- EX Kernel Manager (EXKM) or other tool/technique that can manage zram parameters (note: I find current builds of Kernel Adiutor too unstable for this work)
- Apps2SD Pro or other tool/technique that can create/manage traditional swap files and swap space priorities
- BusyBox Installer (v1.27.2+) or other tool/technique to insure startup scripts are properly executed
- L Speed (optional) - for ease of implementing a few discretionary performance tweaks
- DiskInfo PRO (optional) - visualize partition utilization
- RAM Truth (optional) - simple app to visualize RAM utilization
Technique (highly abbreviated):
- boot device to rooted ROM; install above tools or equivalents
- use EXKM to resize zram to 128 MB (note: zram must be temporarily disabled)
- use Apps2SD to:
* add a static, 128 MB swap file in the cache partition which remains largely unused with custom ROMs
* important: reassign swap file priorities (button at top right): 0 for the static file; 1 for zram
* increase swappiness to 100 if necessary (EXKM can also be used to set swappiness and other VM parameters)
* verify both swap spaces are enabled via sliders
Note to geeks: I understand how swappiness, vcache pressure and other virtual memory tunings really work; let's not debate that here. Same with the merits of running a static swap file in combination with zram or the 'dangers' of placing that file in the volatile cache partition. We're talking a hand held device with very modest resources...not the server room with a 99.9x SLA. Yes, zswap would be better. However ...
Optional tweaks:
- use EXKM or L Speed to set LMK parameters to: 24, 32, 40, 48, 56, 64
- use EXKM or L Speed to set write deferral (aka 'laptop mode') to 5 sec
- toggle KSM off/on in L Speed (sets performance enhancing parameters)
- with zram disabled enable zram tweak in L Speed which will establish a 96 MB space along with other optimizations; I find the smaller size ideal for my workflow; YMMV zRAM size can be set with EXKM or another kernel manager.
Challenges:
While the options exist none of the tools noted above can reestablish custom zram space or automatically create a static swap file on boot. I believe this is a kernel issue but have not ruled out interference by Lineage 12.1 which is the ROM I have been testing with. Unfortunately, I lack the time (and quite frankly motivation) to toss Nexus or another ROM on to a spare device to verify the culprit. I might do a bit more testing my my HD 7 which uses a different kernel and ROM. --> Turns out an old version of BusyBox was the culprit; updating to 1.27.2 solved the problem allowing the suggested configuration to be automatically reestablished on reboot. I added my favorite BusyBox installer to the prerequisite tools.
Another issue is the potential for maintaining 'stale' annon pages in zram for a period of time but that's a left field item that probably won't effect most users. A quick fix is occasionally swiping away all apps.
Provide discussion/feedback in this thread. I may or may not respond depending on available time. I love a deep dive (shared above) but once the goal has been reached my interests move elsewhere.
Edit: struck-out references to L Speed after developer/maintainer acknowledged "cooperation" with Kingo Root team (borderline malware).
Quick follow-up: I continue to enjoy benefits noted in the OP with a dual cache configuration. Device remains responsive after waking and typically returns to 'full' performance within a few seconds. I can easily switch between a handful of apps (browser, mail, Play Store, XDA labs, etc) with minimal lag and context preservation; no reloading web pages after switching away. No notable impact on battery life. Really no disadvantages at all - at least with my work flows.
Regardless of tuning one has to keep in mind the modest hardware resources on Fire 7s. Load up a game or two or a couple heavy Amazon/Google apps and things go south pretty quick. That said, responsiveness far better than any stock config, even when the device is clearly overburdened.
Another quick note. Simply adding a classic swap file (suggest 128 GB) to the largely unused cache partition can yield a decent improvement in multi-tasking performance without the complexity of tinkering with zRAM. All steps can be accomplished with the free tool Apps2SD or equivalent. Happy to document if there is sufficient interest.
Note: Be sure to change zRAM swap priority to "1" so it receives preferential treatment over the classic swap file. zRAM will almost always be faster than classic swap but there is only so much if it. The swap file will be used once zRAM is fully utilized (not entirely accurate but generally true).
FWIW - depreciated references to L Speed app in OP after developer acknowledged "cooperation" with Kingo Root team. While nefarious behavior is unlikely there are other options that avoid any potential conflict of interest.
Davey126 said:
...
Technique (highly abbreviated):
- boot device to rooted ROM; install above tools or equivalents
- use EXKM to resize zram to 128 MB (note: zram must be temporarily disabled)
- use Apps2SD to:
* add a static, 128 MB swap file in the cache partition which remains largely unused with custom ROMs
* important: reassign swap file priorities (button at top right): 0 for the static file; 1 for zram
* increase swappiness to 100 if necessary (EXKM can also be used to set swappiness and other VM parameters)
* verify both swap spaces are enabled via sliders
Note to geeks: I understand how swappiness, vcache pressure and other virtual memory e)
Click to expand...
Click to collapse
When you say Cache partition for the swap file are you referring to "/cache" or the second partition for app2sd?
rjmxtech said:
When you say Cache partition for the swap file are you referring to "/cache" or the second partition for app2sd?
Click to expand...
Click to collapse
"/cache" partition which resides on faster internal storage. Anything on external storage will be significantly slower due to interface limitations.
@Davey126 it has been about a day or two and I can confirm that by following these instructions it has brought new life into my KFFOWI 5th gen. This paired with some L Speed Tweaks (even though you say not to trust them, I opted to use it for a few performance tweaks) and the Lineage ROM from @ggow makes my user experience on the device quite pleasing.
rjmxtech said:
@Davey126 it has been about a day or two and I can confirm that by following these instructions it has brought new life into my KFFOWI 5th gen. This paired with some L Speed Tweaks (even though you say not to trust them, I opted to use it for a few performance tweaks) and the Lineage ROM from @ggow makes my user experience on the device quite pleasing.
Click to expand...
Click to collapse
Thanks for the feedback.
As for L Speed I don't distrust the current developer/maintainer but no longer feel comfortable providing an implicit endorsement. Who you associate with makes a difference IMHO. Each person needs to make their own call. There is no magic in L Speed; it simply offers a convenient UI to various well publicized system 'tweaks' that can be implemented using other tools/techniques.
Davey126 said:
Optional tweaks:
- use EXKM or L Speed to set LKM parameters to: 24, 32, 40, 48, 56, 64
- use EXKM or L Speed to set write deferral (aka 'laptop mode') to 5 sec
- toggle KSM off/on in L Speed (sets performance enhancing parameters)
- with zram disabled enable zram tweak in L Speed which will establish a 96 MB space along with other optimizations; I find the smaller size ideal for my workflow; YMMV zRAM size can be set with EXKM or another kernel manager.
Click to expand...
Click to collapse
Thanks for the guide, it already seems to have helped a lot with smoothness but I wanted to know how to set these options using EXKM.
I'd never heard of the app before today and I've had a good look through the menus but can't seem to find somewhere to set these values. I'm guessing these are the usage % values used by the CPU governor to jump up and down power states?
NeuromancerInc said:
Thanks for the guide, it already seems to have helped a lot with smoothness but I wanted to know how to set these options using EXKM.
I'd never heard of the app before today and I've had a good look through the menus but can't seem to find somewhere to set these values. I'm guessing these are the usage % values used by the CPU governor to jump up and down power states?
Click to expand...
Click to collapse
No, governor tunning is a different beast not addressed in the OP (although I do that on some higher end devices).
With regard to EXKM:
- LMK values can be set under memory -> low memory killer
- KSM toggle can also be found in the memory section
- it appears laptop mode can not be set in EXKM (not that important)
As an alternative to laptop mode you can twiddle 'dirty ratio' and 'dirty background ratio' in EXKM. Suggest setting to 30 and 15, respectfully.
Edit: you may also want to take a peek at Kernel Adiutor (correct spelling). While I find it a bit flaky it exposes more controls vs EKKM and costs less too.
Davey126 said:
No, governor tunning is a different beast not addressed in the OP (although I do that on some higher end devices).
With regard to EXKM:
- LMK values can be set under memory -> low memory killer
- KSM toggle can also be found in the memory section
- it appears laptop mode can not be set in EXKM (not that important)
As an alternative to laptop mode you can twiddle 'dirty ratio' and 'dirty background ratio' in EXKM. Suggest setting to 30 and 15, respectfully.
Edit: you may also want to take a peek at Kernel Adiutor (correct spelling). While I find it a bit flaky it exposes more controls vs EKKM and costs less too.
Click to expand...
Click to collapse
Ah, LMK, not LKM. Thanks again.
Also, just a small suggestion but wouldn't it be better to remove the references to L-Speed and leave an edit message at the bottom rather than having the red, striked through text in the middle?
NeuromancerInc said:
Ah, LMK, not LKM. Thanks again.
Also, just a small suggestion but wouldn't it be better to remove the references to L-Speed and leave an edit message at the bottom rather than having the red, striked through text in the middle?
Click to expand...
Click to collapse
Thanks for noting LKM/LMK typo in OP - fixed that.
I will likely clean-up the OP at some point as there are other refinements (eg: tweaking dirty ratios) that may prove beneficial to a larger community.
Davey126 said:
Thanks for noting LKM/LMK typo in OP - fixed that.
I will likely clean-up the OP at some point as there are other refinements (eg: tweaking dirty ratios) that may prove beneficial to a larger community.
Click to expand...
Click to collapse
I was wondering what differences need to be made for a 7th gen hd 10. I know this guide is written for a 5th gen (1gig RAM, 8 gig drive), but I have a 7th Gen (2gig RAM, 32GIG drive) with 2gig zram (priority 1) and 4 gig swap on the /data partition (priority 2). What would be the best LMK values? Also, is it ok to have the swap on /data vs /cache (my /cache only has 400mb)?
Thanks for any help!
edit: in the OP, it says to set laptop mode using L-speed, and then L-speed is crossed out (I understood why), but no alternative is listed for doing this. I just wanted to add that you can use kernel adiutor to change laptop mode. It's on virtual memory settings.
mistermojorizin said:
I was wondering what differences need to be made for a 7th gen hd 10. I know this guide is written for a 5th gen (1gig RAM, 8 gig drive), but I have a 7th Gen (2gig RAM, 32GIG drive) with 2gig zram (priority 1) and 4 gig swap on the /data partition (priority 2). What would be the best LMK values? Also, is it ok to have the swap on /data vs /cache (my /cache only has 400mb)?
Thanks for any help!
edit: in the OP, it says to set laptop mode using L-speed, and then L-speed is crossed out (I understood why), but no alternative is listed for doing this. I just wanted to add that you can use kernel adiutor to change laptop mode. It's on virtual memory settings.
Click to expand...
Click to collapse
It appears you have priorities reversed. Higher values receive preference. The magnitude of the difference is irrelevant. zRAM is considerably faster than eMMC based storage; the latter should only be used when zRAM is exhausted or momentarily unavailable for whatever reason.
The container sizes also seem excessive. 2 GB of zRAM effectively leaves no uncompressed memory on a HD 10 which is highly inefficient. I wouldn't go over ¼ available RAM or ~½ GB. Toss in a 500 MB of eMMC based (overflow) swap file and you're good to go. If you regularly use more than 1 GB of swap on a relatively low end Android device then something else is amiss.
I am aware Kernel Adiutor can set laptop mode but did not want to introduce another tool into the mix...especially one that has demonstrated inconsistent behavior. FWIW - recent testing suggests 1-2 sec may be a better choice vs the 5 sec mentioned in the OP as the latter may trigger lockouts during sustained writes (eg: large file download on a fast connection). I currently use 1 sec and happy with the results. I will likely update the OP with this info once satisfied that the benefit is worth the effort.
All things being equal I see no reason to change LMK values suggested in the OP. Especially given the availability of zRAM and swap.
Thanks for these instructions, Davey126!
I just tried this process on my 5th Gen Fire 7" which I recently installed with the LineageOS ROM. I was not familiar with the EX Kernel Manager and Apps2D Pro tools, but it was reasonably clear how to make the settings changes you recommend.
I added the 128Mb swap under /cache and increased the zram swap to 128Mb, setting it to priority 1. Maybe it's my imagination but my device does seem a lot snappier when switching between running applications, and better at returning to previously displayed data in applications instead of reloading pages.
Cheers!
Matrey_Moxley said:
Thanks for these instructions, Davey126!
I just tried this process on my 5th Gen Fire 7" which I recently installed with the LineageOS ROM. I was not familiar with the EX Kernel Manager and Apps2D Pro tools, but it was reasonably clear how to make the settings changes you recommend.
I added the 128Mb swap under /cache and increased the zram swap to 128Mb, setting it to priority 1. Maybe it's my imagination but my device does seem a lot snappier when switching between running applications, and better at returning to previously displayed data in applications instead of reloading pages.
Cheers!
Click to expand...
Click to collapse
Thanks for sharing first impressions. Time will tell if the benefits are durable; certainly have been for me with no adverse side-effects.
Another suggestion to reduce wake lag: install Greenify (or similar tool) and add commonly used apps to the action list even if not flagged as background abusers (you may need to override Greenify's sensible defaults via the gear icon). This prevents multiple apps from becoming simultaneously 'active' on wake which is a huge contributor to lag on lower end devices with limited resources (CPU and RAM). Hibernated apps will launch when needed with minimal delay and NO loss of context. Works a treat.
Be sure to add your favoriate browser, mail, messaging and social media apps to the hibernation list as all like to 'check in' after a long slumber.
Although Greenify can auto-hibernate apps on most devices (works best with Xposed Framework) I use an automated approach that invokes Greenify's widget when the screen goes off. There's still some momentary lag on wake but the device remains responsive which is a huge improvement.
Hi Davey126,
thx for the guide, it seems to work awesome.
However, i have the one problem thats the settings in EXKM regarding to "zRAM Size", "dirty ratio" and "dirty background ratio" are lost after rebooting the device. Is there a way to make the settings reboot proof? Interestingly for the "LKM" settings there is an option "Apply at bootime", which does the trick for me, but only for the LKM options.
Kind regards,
Stephan
IronMan1977777 said:
Hi Davey126,
thx for the guide, it seems to work awesome.
However, i have the one problem thats the settings in EXKM regarding to "zRAM Size", "dirty ratio" and "dirty background ratio" are lost after rebooting the device. Is there a way to make the settings reboot proof? Interestingly for the "LKM" settings there is an option "Apply at bootime", which does the trick for me, but only for the LKM options.
Kind regards,
Stephan
Click to expand...
Click to collapse
Likely BusyBox is missing or outdated. Try installing this (I use the pro version).
Davey126 said:
Likely BusyBox is missing or outdated. Try installing this (I use the pro version).
Click to expand...
Click to collapse
Ok. I bought BusyBox Pro and updated to Version 1.28.1-Stericson. Still all settings in EXKM besides LMK get lost after rebooting the device ...
IronMan1977777 said:
Ok. I bought BusyBox Pro and updated to Version 1.28.1-Stericson. Still all settings in EXKM besides LMK get lost after rebooting the device ...
Click to expand...
Click to collapse
- verify BusyBox is property installed w/no conflicting builds
- uninstall/reinstall EXKM
- test if behavior can be duplicated with another (free) kernel manager like KA