Database Users

How to disable WM automatic RAM handling?

Hi,
in my struggle to free as much ram as possible (by moving to storage/SD every single bit i could) i was able to reduce the (static) RAM i'm using to 1.68MB, even retaining all my needed application (in SD) and two Today plugin in RAM.
With an available total RAM size of 57.41MB, i should be able to use 57.41-1.68 MB of dynamic RAM.
The problem is WM won't let me to do it.
To free more dynamic RAM, i should move to the left the static-dynamic memory slider in Start->Setting->System->Memory BUT whenever i try to lower it under about 9mb, WM reset the slider to it's original position (about in the middle of the bar).
This way i'm forced to allocate more than 10MB (9 + 1.68) to static RAM even if i'm using ONLY 1.68MB and i'm not going to use anymore.
Is there a way to AVOID the S.O. resetting the slider or, at least, to let me assign the static RAM no more than 3 or 4MB???
What's the point in relocating every program, dll, htm and so on to SD card if i'm still obliged to waste 10MB of precious RAM???
PLS help me!!!
Bye bye,
Isidoro

I think you will be able to further lower the Storage memory when your Program memory reached about 0.75 of its allocated slot.
Have you ever try using almost all your allocated Program memory, and see if you can reduce the Storage memory even further? I'd like to see if it can be done.

billabong said:
I think you will be able to further lower the Storage memory when your Program memory reached about 0.75 of its allocated slot.
Have you ever try using almost all your allocated Program memory, and see if you can reduce the Storage memory even further? I'd like to see if it can be done.
Click to expand...
Click to collapse
Uhm... i should try. Maybe when using pocketgba. I'll let you know.

billabong said:
I think you will be able to further lower the Storage memory when your Program memory reached about 0.75 of its allocated slot.
Click to expand...
Click to collapse
There isn't a way to reduce this value? (0.75?)

Adjusting storage memory and program memory

Hi, is there a way to adjust the memory usage for the program, like adjust the storage and give it to program. Not like xda, the prophet does have a slider for the memory but could not be adjusted. Is there anyway how to go over this ?

Prophet, as well as many new WM5 devices have (physically) separate program and storage memories. And thus there is no built in way to adjust the amounts of the two.

The Prophet has a 64MB Ram and a 128MB Flash Size with a storage size of 42.55. Where did the 44.01 MB program came from? Is there a way to increase the MB size for the program? Because I believe that even though you can install several program using the storage, a portion of the program memory gets filled up until at the critical level, which will later play an important part once you start running a program which needs a higher memory. Any remedy to this?

The 64MB RAM is what I think should be called 'box figure'. It's what's printed on the box.
In reality you get 50+ actual RAM at leas 10 of which go to various OS functions and the rest is left for running programs to use.
Under WM5 non of it is used for files, but when you run programs, even built-in ones there are sometimes memory leaks which means that even though you closed the program some of the memory (sometimes more them 1MB) remains occupied.
The only known way to fully reclaim memory is to soft reset the device. I do it on my Jamin once a week when I am left with 12-10MB free.
Unfortunately, there is no way to add RAM to device.

{App} Awesome life saving app! boost up's the ram to almost twice(Memory booster lite

Hey guys . i found this app in the android market ---Memory Booster ... it is much better than the advanced task killer ! and it can free a lot of ram ! just try it out once ..i freed 86 mb ram in one go ...i had 55 mb available ..and after using this i got 141 ram total free ! just type memory booster in android market search ..and download the first one !
Info -
Description
Memory Booster is a powerful mobile Memory & RAM boosting tool specially designed for Android smartphone users. It is a handy memory optimizer tool that will keep your Android smartphone running faster and efficiently. It increases your cell phone's performance by making more memory available for both your applications and the mobile system.
Memory Booster is designed to tackle the difficult but crucial problem of memory management for Android smartphone users. Memory is the most precious resource in your smartphone; when it becomes low, your cell phone will slow down severely or crash. If the mobile system cannot handle your memory properly by itself, your smartphone will slowly lose memory over time and bring you to a critical state. Memory Booster solves these problems by reclaiming lost memory for your programs. It helps your smartphone run at optimum speed by efficiently defragmenting your smartphone's memory, recovering memory leaks from poorly behaved application, flushing unused libraries temporarily out to disk and so on. By all this optimization tricks your favorite applications and games will run faster and efficiently with Memory Booster running in the background.
Memory Booster is optimized for all series of Android OS smartphones, which can monitor your mobile system in the background, freeing resources when needed. It uses many advanced features to keep your smartphone running at optimum speed. But more importantly, it's designed with all users in mind; whether you're a power-user or a novice, Memory Booster will give you the features you want without confusing or limiting you.
Praised by both individual users and large companies alike, Memory Booster is the best utility of its type available. Memory Booster from DownloadAndroid.Info, represents the best technical and design efforts as Android system tool, to bring you a technically superior, yet easy-to-use memory management utility.
Product Features:
•Real-time Smartphone Memory Status Report & Monitor Memory Booster gives you professional, easy-to-read status report on your smartphone's memory usage. A live chart demonstrates your total available memory and current memory usage. Memory Booster makes it easy to see how well your smartphone is performing, and whether your system is overloaded.
•Setting Your Performance Target
Using Memory Booster's Settings function, you can boost phones by setting performance goal fits your profile. Memory Booster will work to keep your memory at desired levels, and act immediately if memory drops below critical level.
•One-click Quick Memory Boosting
In addition to monitoring and reclaiming your memory automatically, Memory Booster allows you to boost your memory manually. By using the Quick Boost feature, you can observe Memory Booster reclaiming more memory for your system. In the mean time, Quick Boost will smartly remember the settings that work best for your smartphone.
•Auto-boosting in the Background
Your memory is the most important resource on your smartphone, and how it is used can drastically affect performance. With Auto-boosting feature, Memory Booster can run in the background and automatically reclaim unused memory on your Smartphone. It oversees the allocation of memory resources through its unique cache management technique.
•Android system crash protection
The majority of smartphone crashes come when system resources are inadequate. Memory Booster automatically watches and cleans up your Android's system memory when it reaches a critical point. By using Memory Booster, you don't need to know anything about your smartphone system; Memory Booster will provide all the technical know-how.
•And there is more.
Other features include embedded Advanced Task Manager, Whitelist Manager, Boost Level Manager & Memory Boost Log, which allow you to manually quit the running applications safely, to protect items from being killed during Memory Booster's boost operation, to easily adjust Memory Booster's boost strength according to users' demands, and manually check Memory Booster's boosting history to trace the effectiveness it improves your smartphone's performance.

will try bro! i am from new delhi too

Uh... the HD2 has 576mb (when using Tmob radio) of ram, and assuming the android builds can access it all, that means we *don't* need 3rd party memory managers.
Secondly, Android always tries to use up as much memory as possible for caching for a smoother UI experience, so having as much "free memory" as possible is pointless. In fact, using "memory managers" that go and kill everything might actually make your phone MORE unstable, not less.
Thirdly, the inbuild Android memory manager is already very efficient - it *automatically* kills apps that aren't used in the background. If you want to tweak it to be more aggressive at killing unneeded apps to save battery life, more useful apps would be AutoKiller and Auto Memory Manager.
EDIT: Both of those apps are free also.

OPs app is a BS app like internet boosters. hardware is like it is and you dont "boost" it

Amazon tablet optimization. Memory load pressure cured.

Favorite rom -
Faux clock / any kernel tuner -
Enable kms - (setting recommended from Google for low memory device)
Set kms page_to_scan to 100
Set kms sleep_milleseconds to 500
Enable set io scheduler from 2048k - 4096k
Ram memory pro - (this setting help with memory swap when using kms, zram, and swap file combinations)
Enable at boot setting
Set balance tuning for apps and multitasking
Setxperia - (not available in store for tablet/must find and sideload) (setting recommended from Google for low memory device)
Enable zram with 400 MB size (zram have priority before using swap file / that where the magic at) (least used data get page out to zram and then to the page file)
Set swap file to data partition with 200 MB size
Set swappiness set to 100
Create swap. Total swap setting aside should equal to 615 MB
Use zramcc to check if zram/swap working. Swap total size should be 615MB. (reduce swap file size from 400 to 200 to minimize lag when all available swap are used up)
Link2SD - no need for explanation. I used this with a fast flash card to hold my titanium backup and app linkage. This app allow me to have all my apps that I used.
Seeder 2.0 - no need for explanation. This just classic lag free app. Check the entropy resources before and after usage before complaining how old and useless this app is.
Misc -
Unload/uninstall any memory hogged app, like Facebook Messenger (takes up almost 50MB), that like to stay in the system memory permanently. Can't even kill it with task manager. DO NOT USED ANY MEMORY CLEANER OR ADVANCE TASK KILLER. This will cause a swap overload. Let android manage the memory task. Reboot the tablet once all the settings have been applied. The tablet will behave very well and feel like a more expensive tablet.
I have the stock opengapps replace all the core stock rom app. Afterward, I removed any gapp that I do not use.
My Amazon Fire experiences:
My launcher is loaded with widgets and I can pretty much open any application that I used without any freeze or as little lag as possible. I game on this table now and no longer use my phone. Brave frontier and valkyrie crusade.
https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1
Sent from my KFFOWI using Tapatalk

Kms or Ksm???

Update on information
Is all of this information still up to date? Any new additions/tweaks?
Also for some reason, after using zramcc I don't see 615 I only see 415 total.

svvparakala said:
Is all of this information still up to date? Any new additions/tweaks?
Also for some reason, after using zramcc I don't see 615 I only see 415 total.
Click to expand...
Click to collapse
Err...not really...although much of the guidance is reasonable albeit not optimal IMHO. Check out "L Speed" if seeking a quick tuner with a large following and solid reputation. Tweak one thing at a time and assess benefits before moving to the next item.

[Custom ROM] What to do with that huge cache partition

You may have noticed the ~1 GB cache partition on 3rd gen HDX devices that was used as temporary work space for chunky FireOS OTA updates. Typically <5% is used by Android which leaves a sizable block of space completely wasted. While it is possible to adjust partition boundaries to to expand either the System or Data partition that task is not for the faint of heart on an Android based device.
One option is to utilize a portion of the Cache partition for eMMC backed swap, especially since the stock kernel does not support zRAM. This can be attractive for those who run large or numerous apps that consume the 1.8 GB of available RAM. While Android's LMK will typically prevent OOM (out-of-memory) conditions under heavy pressure the constant recreation/reloading of killed activities can be annoying.
It is pretty easy to create a swap file in the Cache partition with an app like App2SD (just an example; not an endorsement). Suggest starting with 128 or 256 MB. You may want to crank down the swappiness value (default on most ROMs is 60) to limit write activity to eMMC which has a finite lifespan. Tuning LMK is also part of the game; lots of apps can handle that including the fan favorite L Speed or any of the popular Kernel Manager apps (EK Kernel Manager, Kernel Adiutor, etc).
eMMC backed swap has its pros and cons. While experimenting won't hurt you'll probably want to do a little research before making swap a permanent part of your config.
Enjoy!
edit: A tool like DiskInfo can help illuminate how partitions are allocated/utilized on your device.
FWIW - the following values returned acceptable results for my typical usage scenario:
- LMK thresholds (in MB): 16/32/48/64/80/96
- swappiness: 40
- vfs cache pressure: 70
Edit 04/18: Over time I have stopped twiddling with most VM parameters (accepting default values) as there was not a sustained, meaningful difference in performance to justify maintaining custom settings. However, I have found increasing the LMK "empty app" threshold provides a noticeable increase in response time with light to moderate multi-tasking. New LMK settings as follows:
LMK thresholds (in MB): 16/24/32/48/64/128.
I have found these values work well on most devices equipped with ~2 GB of RAM. In fact setting appropriate LMK values can all but eliminate the benefits of file based swap on this device. Obviously YMMV.

Quick follow-up: The config outlined in the OP remains on my daily driver and continues to enhance the overall enjoyment of this device. Over time I refined a few tunings for my workflow. Difference are subtle but yield better resource utilization. YMMV.
- swappiness: reduced to 20 to further discourage cache file writes
- VFS cache pressure: restored device default (100)

Davey126 said:
Quick follow-up: The config outlined in the OP remains on my daily driver and continues to enhance the overall enjoyment of this device. Over time I refined a few tunings for my workflow. Difference are subtle but yield better resource utilization. YMMV.
- swappiness: reduced to 20 to further discourage cache file writes
- VFS cache pressure: restored device default (100)
Click to expand...
Click to collapse
Hello Dave, I've follow your posts and managed to get 256MB for swap space but used only about 50KB. Is it work or not? How to check does a swap helps a system as android?
BR!

iksel said:
Hello Dave, I've follow your posts and managed to get 256MB for swap space but used only about 50KB. Is it work or not? How to check does a swap helps a system as android?
BR!
Click to expand...
Click to collapse
Likely working...give it time. You will see swap file utilization slowly creep up but will likely remain at a small fraction of the available space. Note: the swap file is reset (flushed) on reboot.
Setting swappiness to 20 discourages the use of the swap file except under high memory pressure. In most cases that is what you want as RAM is several magnitudes faster than eMMC. The benefit kicks in under high memory loads:
- older content in the memory cache can be (quickly) written out to the swap file freeing up RAM for current demands
- context of loaded but less frequently accessed apps is likely to be fully/partially retained avoiding a complete restart
Bumping swappiness to 40 or higher will increase swap file utilization and also change the composition of swapped contents. The default on many devices, especially on low RAM configs and/or those with zRAM, is 100. That aggressive setting will likely hurt overall performance on a 2GB device with no zRAM support (like the HDX).
Keep in mind the swap file resides in an area of permanent storage that goes largely unused on a HDX fitted with a custom ROM (FireOS uses this area for processing OTA updates). If that file were taking space away from the data partition this tweak would be of questionable value.

Davey126 said:
Likely working...give it time. You will see swap file utilization slowly creep up but will likely remain at a small fraction of the available space. Note: the swap file is reset (flushed) on reboot.
Setting swappiness to 20 discourages the use of the swap file except under high memory pressure. In most cases that is what you want as RAM is several magnitudes faster than eMMC. The benefit kicks in under high memory loads:
- older content in the memory cache can be (quickly) written out to the swap file freeing up RAM for current demands
- context of loaded but less frequently accessed apps is likely to be fully/partially retained avoiding a complete restart
Bumping swappiness to 40 or higher will increase swap file utilization and also change the composition of swapped contents. The default on many devices, especially on low RAM configs and/or those with zRAM, is 100. That aggressive setting will likely hurt overall performance on a 2GB device with no zRAM support (like the HDX).
Keep in mind the swap file resides in an area of permanent storage that goes largely unused on a HDX fitted with a custom ROM (FireOS uses this area for processing OTA updates). If that file were taking space away from the data partition this tweak would be of questionable value.
Click to expand...
Click to collapse
Good to know, thanks again!

Davey126 said:
Quick follow-up: The config outlined in the OP remains on my daily driver and continues to enhance the overall enjoyment of this device. Over time I refined a few tunings for my workflow. Difference are subtle but yield better resource utilization. YMMV.
- swappiness: reduced to 20 to further discourage cache file writes
- VFS cache pressure: restored device default (100)
Click to expand...
Click to collapse
Yet another update. After making modest tweaks to dirty/dirty background ratios I noticed a subtle increase in momentary (<1 sec) lag switching between previously loaded apps. Such behavior is symptomatic of increased memory cache pressure and potentially unnecessary swapping and/or LMK activity. Flushing the cache cured that (for awhile) but is clearly not the ideal solution. Ultimately bumping swappiness to 40 addressed the problem. Guessing the previous value (20) allowed stale application pages to remain in memory a bit too long increasing cache pressure which became evident when actively multitasking.

Bumping this thread as reminder/reinforcement of the beneficial effects for some workflows. In short, a small static swap file significantly improves the multitasking UX if returning to previous app context is important. Newer devices leverage zRAM for this purpose; HDX kernel doesn't support that.
Over time I have gravitated back to defaults for swappiness, dirty timeouts, cache pressure, etc as custom values did not yield significant measurable (or subjective) improvement to warrant changing. Less knobs to turn/tweak which is always good thing in my book!

This is what I usually do - just resize and move the extra space to userdata partition. If only the days of roms that are installed by simply extracting the files on to system partition still continues, we could get some space of the system partition out too :silly:

pipyakas said:
This is what I usually do - just resize and move the extra space to userdata partition. If only the days of roms that are installed by simply extracting the files on to system partition still continues, we could get some space of the system partition out too :silly:
Click to expand...
Click to collapse
Yep - done that too on some devices. Resizing partitions is not for the faint of heart which is why I opted to excluded it from the guide.

I had kown how deal with it ,we can rest our disk partition to make it change to data
I had kown how deal with it ,we can rest our disk partition to make it change to data or system to use!!!

Davey126 said:
Yep - done that too on some devices. Resizing partitions is not for the faint of heart which is why I opted to excluded it from the guide.
Click to expand...
Click to collapse
Why not provide that info? It is no different than flashing custom roms. You are warned by the devs that doing so brings a risk of bricking your device...proceed at your own risk.
I think it would be valuable to those that want to use that wasted space or optimize the use of the storage space available.
Hopefully you will reconsider.

droiduzr2 said:
Why not provide that info? It is no different than flashing custom roms.
Click to expand...
Click to collapse
lol - not comparable, at least with the vast majority of mobile devices that I have been exposed to. Including this one. Those who wish to muck with resizing Android partitions will find copious detail on the net...usually from those who have spent 100X the initial resizng effort trying to recover their device. Because, ya know, it is no different than flashing custom ROMs.

Davey126 said:
lol - not comparable, at least with the vast majority of mobile devices that I have been exposed to. Including this one. Those who wish to muck with resizing Android partitions will find copious detail on the net...usually from those who have spent 100X the initial resizng effort trying to recover their device. Because, ya know, it is no different than flashing custom ROMs.
Click to expand...
Click to collapse
I am pretty sure everyone on here that goes to flash a rom (change from stock) read the disclaimer and assume the risk that they can brick their device. If there were a tool or clear directions to optimize the use of storage space considering we are stuck with 16gb (no usb otg support, no external sd card) then being able to use every Mb much less Gb seems to be a helpful thing imo.
Also it's not about mucking around with just any Android device, it's about this specific device and what one would have to do.
If you are saying it is not an easy task then so be it.