УВЕЛИЧЕНИЕ ПРОИЗВОДИТЕЛЬНОСТИ ДЛЯ Р

УВЕЛИЧЕНИЕ ПРОИЗВОДИТЕЛЬНОСТИ ДЛЯ РЕСУРСОЕМКИХ ПРИЛОЖЕНИЙ (НЕОБХОДИМЫ ROOT-ПРАВА!)

Есть способ ускорения работы приложений(например, более лучшее отображение дескстопных версий страниц в браузере). Для этого нужны 2 вещи-рут и приложение root explorer. С помощью последнего заходите в system, кликаете вверху справа на права r/o и открываете фаил build.prop в текстовом редакторе. В конце файла есть строки:
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=32m
dalvik.vm.heapsize=256m
(Значения могут быть другими). Меняете эти строчки на
dalvik.vm.heapstartsize=32m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=512m
Смысл этого-увеличить оперативную память, которая выделяется приложениям. Первая строчка-сколько мб выделится для данного приложения при запуске, третья строчка-сколько максимально может выделится оперативной памяти данному приложению. В принципе вы можете поставить там любые значения, не превышающие 1024 мб, но все же лучше больше 512 мб не ставить-это среднее число свободной ОЗУ при работе с нашим телефоном. После смены значений сохранить изменения в файле и перезагрузить телефон. Прибавка к производительности неплохая-10-15%(страницы в браузере прорисовываются заметно быстрее)

Если что, делаем Бэкап файла build.prop в той же папке.

Тестите..

ผลลัพธ์ (อังกฤษ) 1:

INCREASED PERFORMANCE FOR RESOURCE-INTENSIVE APPLICATIONS (REQUIRES ROOT RIGHTS!)Is there a way to speed up applications (for example, better display of deskstopnyh versions of pages in the browser). You need 2 things-Ruth and root explorer application. With the last visit in the system, click at the top right of the law r/o and open the build.prop file in a text editor. At the end of the file there is a line:dalvik.vm.heapstartsize = 5 mdalvik.vm.heapgrowthlimit = 32 mdalvik.vm.heapsize = 256 m(Values may vary). Change these lines todalvik.vm.heapstartsize = 32 mdalvik.vm.heapgrowthlimit = 64 mdalvik.vm.heapsize = 512 mThe point of this is to increase the memory that is allocated to applications. The first line-how many MB is highlighted for this application at startup, the third line-how much can stand out of RAM to that application. In principle you can put there any values not exceeding 1024 MB, but still better than more 512 MB not to-this is the average number of free RAM at work with our phone. After changing values, save changes to the file and reboot the phone. The increase in performance is not bad-10-15% (the page in a browser are rendered visibly faster)If that do build.prop file in the same folder.Testite..

ผลลัพธ์ (อังกฤษ) 2:

Increased performance for demanding applications (ROOT-LAW NEEDED!) There is a way application acceleration (for example, a better display deskstopnyh versions of pages in the browser). This requires two things, Ruth and application root explorer. With the latter go into system, click on the button at the top right of the right r / o and open Fail build.prop in a text editor. At the end of the file there may be different). I have these lines on dalvik.vm.heapstartsize = 32m dalvik.vm.heapgrowthlimit = 64M = 512M dalvik.vm.heapsize meaning of this, increase the memory that is allocated to applications. First-line stand out as MB for the application when you run third-line as much as possible can allocate memory to the application. In principle, you can put there any value not exceeding 1024 MB, but still better more than 512 MB ​​is not to the average number of free RAM when working with our phone. After the change of the values ​​to save changes to a file, and restart the phone. Increase performance-good 10-15% (page drawn in the browser much faster) If that makes backup build.prop file in the same folder. test ..

ผลลัพธ์ (อังกฤษ) 3:

Increase the performance of resource intensive applications (the need for the root right!)

ways to speed up the work of the application (for example, more should he, kappa,,, 'by hallux were the best version of the browser display pages).This requires 2 things - Ruth and the explorer of the annex. The system of the last in kappa PI, kappa alpha is, by the top right corner of the R / O rights and phi alpha, PI build.prop in text editor open. At the end of the file there is a string: dalvik.vm.heapstartsize = 5000000 dalvik.vm

.Heapgrowthlimit = dalvik.vm.heapsize 32m 256M

(value can be other). These changes in = dalvik.vm.heapstartsize 32m


dalvik.vm.heapsize 64M dalvik.vm.heapgrowthlimit = = 512M
- increases the application of nonvolatile memory, the prominent.The first line much MB's allus betel which has led to for a given application at startup, a maximum of three lines of the memory can's allus betel which has led to the attachment. You can put any value in principle there,No more than 1024000000000000, but it's best to keep more RAM 512MB is the average number of free jobs when working with us. After the change of the save file and restart your phone.A very good - the productivity of pay 10% to 15% (in the browser page ',,,,, Liapunov's allus been pgfla elixir, C,

If significantly faster), build.prop backup file in the same folder.

, is, to me, is...