Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
25 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,25 +1,30 @@ | ||
| # Preload | ||
| Preload application preloads data to RAM to significantly increase read speeds. It works both with and without ROOT access. Recommended to use only on devices with 6+ GB RAM. | ||
| Preload application preloads data to RAM to significantly increase read speeds. It works both with and without ROOT access. Recommended to use only on devices with 6+ GB RAM. App doesn't lock processes in RAM, files data only. | ||
|
|
||
| >> Without ROOT access app will preload data in RAM as cache (\'readahead\' method). Cache is kept while there is enough free RAM. Once there is a need for more free RAM, system will free this cache - in such case you will get lower read speed.\n | ||
| >> Without ROOT access:\n | ||
| — You can preload user apps (for OS 10 and below), files and folders - read speeds will be boosted\n | ||
| — You can\'t preload apps if you are on OS 11+ due to Scoped Storage\n | ||
| — Preloaded data may be released by OS in a while (depends on amount of available RAM) and you will get regular read speeds\n | ||
| — You don\'t need to care of unpreloading data - OS will handle it all automatically\n | ||
| — App\'s RAM indicator may show incorrect values due to the system may quickly release preloaded data\n | ||
| — Safe\n\n | ||
|
|
||
| >> With ROOT access app will preload data in RAM and lock them there (\'mlock\' method). All preloaded data will be kept in RAM and won\'t be freed, unless you press the \'Unpreload\' button, uninstall Preload app or reboot device.\n | ||
| >> With ROOT access:\n | ||
| — You can preload any user apps, files and folders on any supported OS version\n | ||
| — Preloaded data will be kept in RAM as much long as you wish with boosted read speeds\n | ||
| — You have to manually unpreload data if you want to free used RAM\n | ||
| — Accurate app\'s RAM indicator\n | ||
| — Possible risk of OOM in system. Don\'t overload RAM with preload data\n\n | ||
| >> Without ROOT access app will preload file data in RAM as cache ('readahead' method). Cache is kept while there is enough free RAM. Once there is a need for more free RAM, system will free this cache - in such case you will get lower read speed. | ||
| >> Without ROOT access: | ||
| — You can preload user apps (for OS 10 and below), files and folders - read speeds will be boosted | ||
| — You can't preload apps if you are on OS 11+ due to Scoped Storage | ||
| — Preloaded data may be released by OS in a while (depends on amount of available RAM) and you will get regular read speeds | ||
| — You don't need to care of unpreloading data - OS will handle it all automatically | ||
| — App's RAM indicator may show incorrect values due to the system may quickly release preloaded data | ||
| — Possible restrictions due to OS permissions | ||
| — Safe | ||
|
|
||
|
|
||
| >> The indicator shows how much RAM is used/available for preload - memory measure method depends on the ROOT access availability.\n | ||
| >> While preloading apps, their cache files are ignored. If obb or files folders of the app are not fitting in RAM to preload - they will be skipped. Also avoid preloading files with special characters in name.\n | ||
| >> You can\'t preload data which is bigger in size than available RAM. Also 10% of available RAM is always reserved to avoid low available RAM and potential system lags.\n | ||
| >> In order to automatically preload the desired app on system boot longpress on it in the list. Longpress on same app again to disable the feature.\n\n | ||
| >> With ROOT access app will preload data in RAM and lock them there ('mlock' method). All preloaded data will be kept in RAM and won't be freed, unless you press the 'Unpreload' button, uninstall Preload app or reboot device. | ||
| >> With ROOT access: | ||
| — You can preload any user apps, files and folders on any supported OS version | ||
| — Preloaded data will be kept in RAM as much long as you wish with boosted read speeds | ||
| — You have to manually unpreload data if you want to free used RAM | ||
| — Accurate app's RAM indicator | ||
| — No possible OS permission restrictions | ||
| — Possible risk of OOM in system. Don't overload RAM with preload data | ||
|
|
||
|
|
||
| >> The indicator shows how much RAM is used/available for preload - memory measure method depends on the ROOT access availability. | ||
| >> While preloading apps, their cache files are ignored. If obb or files folders of the app are not fitting in RAM to preload - they will be skipped. Also avoid preloading files with special characters in name. | ||
| >> You can't preload data which is bigger in size than available RAM. Also 10% of available RAM is always reserved to avoid low available RAM and potential system lags. | ||
| >> In order to automatically preload the desired app on system boot longpress on it in the list. Longpress on same app again to disable the feature. | ||
|
|