Guest Posted January 6, 2011 Report Posted January 6, 2011 Sorry if I've been thick here and I have searched but how do I know a change has taken effect and is holding firm after manual reboots? Even if I root, change it to the recommended 32(that's right isn't it?) and reboot when they ask if I go to do it all again both boxes show the 24 is it it starts at????
Guest Afrodude Posted January 6, 2011 Report Posted January 6, 2011 (edited) How are you editing this? (Using VM Heap Tool or Manually editing build.prop?) Edited January 6, 2011 by Afrodude
Guest lpinho Posted January 6, 2011 Report Posted January 6, 2011 Sorry if I've been thick here and I have searched but how do I know a change has taken effect and is holding firm after manual reboots? Even if I root, change it to the recommended 32(that's right isn't it?) and reboot when they ask if I go to do it all again both boxes show the 24 is it it starts at???? I read somewhere that the value that appears in the tool, doesn't represent the real value of the heap size, its only a default value.
Guest Posted January 12, 2011 Report Posted January 12, 2011 I read somewhere that the value that appears in the tool, doesn't represent the real value of the heap size, its only a default value. Using the app. No easy way top know worked then? 32 recommended value??
Guest That-Guy Posted January 12, 2011 Report Posted January 12, 2011 I use 32 and no problems with any apps yet :D
Guest Len Ash Posted January 12, 2011 Report Posted January 12, 2011 Using the app. No easy way top know worked then? 32 recommended value?? Try this for certainty... http://android.modaco.com/content/zte-blad...b/#entry1552349
Guest martino2k6 Posted January 15, 2011 Report Posted January 15, 2011 Using the app. No easy way top know worked then? 32 recommended value?? It does show the current value, and it did even before the 2.0 changes. How do I know? I coded it ;)
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now