Samsung continues to be looking for a strategy to a memory leak factor that’s been plaguing the Samsung Galaxy S6, however a few cunning XDA developers seem to have found a dirty fix in the meantime. The repair comes to a simple edit of your tool’s build.prop document.
If you’re now not positive what it's, a build.prop record retail outlets plenty of details about tool main points and configurations. Changes within the report may just do as low as adjust your telephone’s construct identify, or up to tweaking flags for the kernel.
You do want to be rooted with a view to edit your build.prop record, and we will have to additionally point out that is dangerous stuff and will have to most effective be performed if you realize what you’re doing and are prepared to are living with any unexpected effects that can surface as a end result.
That stated, when you’re transparent of the risks and able to accepting duty for what you do on your software, you'll be able to make the next adjustments (use this app, or use a root record supervisor to edit the record your self):
In your build.prop beneath #DHA Properties amendment those strains:Code:ro.config.dha_cached_max=12 ro.config.dha_empty_max=36
Add those 4 strains:ro.config.dha_th_rate=2.3 ro.config.dha_lmk_scale=0.545 ro.config.sdha_apps_bg_max=70 ro.config.sdha_apps_bg_min=8
Scroll down past the DHA homes the place the opposite homes are saved and cast off replica entires ofro.config.dha_cached_max= ro.config.dha_empty_max= ro.config.dha_th_rate= ro.config.dha_lmk_scale=
Finally this one will amendment your LMK values:
When all is claimed and performed, you will have a software that takes it simple on guzzling your RAM, even though the developer notes that customers would possibly nonetheless have issues while the use of apps that depend on WebView. That’s a small caveat to simply accept, although, so we’d provide it a move besides in case you’re uninterested in ready on Samsung to ship the products.