|
||||
|
Re: Touch Pro2 program memory leak???
i had no problems on stock.ive tried mm,and gsm to wcdma 6.5 and both suck up ram.i didnt try energy long enough to tell
|
|
||||
|
Re: Touch Pro2 program memory leak???
even on the sprint stock rom it's kinda high 70% or higher with nothing installed...
|
|
||||
|
Re: Touch Pro2 program memory leak???
I had this fix working on my stock VZW 6.1 rom, but now on MR 6.5 the registry change will not stay at 0 after a soft reset, it always changes to a different number. Anyone experienced this?
Last edited by cambunch; 10-31-2009 at 06:15 PM. |
|
||||
|
Re: Touch Pro2 program memory leak???
I'm on 6.5 (CFAY) and have the same issue. the reg change reverts back to the default setting on soft reset
|
|
||||
|
Re: Touch Pro2 program memory leak???
my phone starts up with 53% which i think is still too high. it actually starts at 43 and jumps up to 53 after everything is loaded i believe. next thing i know, the phone is freezing up more then it usually does and the memory is up to 64%
__________________
Phone: Nexus 6p | Carrier: StraightTalk Att
Kernel: Stock | ROM: Stock Oreo |
|
||||
|
Re: Touch Pro2 program memory leak???
Is there any problem with having only 20% of RAM free. I understand having more free at default gives you more memory to play with, but when do slow downs and crashes happen? 5% free? 10% free? 0%? What is the performance difference between using 55% and 70%?
__________________
|
|
||||
|
Re: Touch Pro2 program memory leak???
Quote:
__________________
Droid Incredible (rooted on Virtuous v2.5 ROM)
--------------- (retired) VZW TP2 (retired) VZW TP (retired) VZW 6800 |
|
||||
|
Re: Touch Pro2 program memory leak???
Quote:
Quote:
For some reason, after I make this change, it doesn't seem to survive a soft reset... It changes back to default (131072). Anyone else experience this? Anyone know a work around? |
|
||||
|
Re: Touch Pro2 program memory leak???
Yes, I have the same prob.
Seems like this tweak will no longer work wih WinMo 6.5....or does anyone have a workaround? |
![]() |
|
|
|