I was wondering if there was a lock home in memory tweak as well for our ICS Transformer as well as what the best heapsize and such would be for opening large pdf and ppt files. Would I need to increase heapsize to a number greater than 54? I am currently having some issue with loading large, +50mb files as well as difficultly zooming and changing pages and the pictures are not loading correctly (or not at all). Thanks you for your time!

Originally Posted by Danzano

You may want to go through and edit parts to do with V6 Super charger as it tends to edit kernel aswell as vm and oom groupings. Now most is good but some things need re-editing because what works best is not generic and some of the v6 settings are and look more suited to a phone than a tablet.

Glad everything is working well for you though.

Also under build.prop get rid of the v6 3g tweaks our devs already have tweaks for internet speed based on this tablet. Oh and if dalvik.vm.heapsize is in there remove it and use the stock one in build.prop and change it to 64

Theres little things i have noticed just have not had time to write them down or add a tut i will add more little tweaks when i can though

Sent from my Transformer TF101 using XDA Premium HD app

I have no 3g module in my device so perhaps these misgivings missed me, everything goes fine. Should I set the heapsize to new value will see by changing it to 64 right now. Though I had no prob with 160 mb pdf file with it opening and panning when tablet goes with 256 heapsize which is default value for ARHD 3.1 ROM.

Originally Posted by Koserman

I was wondering if there was a lock home in memory tweak as well for our ICS Transformer as well as what the best heapsize and such would be for opening large pdf and ppt files. Would I need to increase heapsize to a number greater than 54? I am currently having some issue with loading large, +50mb files as well as difficultly zooming and changing pages and the pictures are not loading correctly (or not at all). Thanks you for your time!

Theres 2 or 3 ways to lock home in memory the easiest is V6 supercharger then bulletproof the home apk and die hard etc 2nd way is a script you put in init.d and the last one is an app but only the paid version i think.

Mine can open pdf and ppt files fine but i think oc also comes into it because at stock speeds i can still see a little lag but oc to 1.5 and i see none.

Sent from my Transformer TF101 using XDA Premium HD app

Originally Posted by garryveda

I have no 3g module in my device so perhaps these misgivings missed me, everything goes fine. Should I set the heapsize to new value will see by changing it to 64 right now. Though I had no prob with 160 mb pdf file with it opening and panning when tablet goes with 256 heapsize which is default value for ARHD 3.1 ROM.

Thats what i meant by generic go look at your build.prop bet those tweaks are there right down the bottom

256 heapsize or heapgrowth limit? maybe i should re word op some more let me know

Sent from my Transformer TF101 using XDA Premium HD app

Mine are:

dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m

Should I change these values for more nice results?

Originally Posted by garryveda

Mine are:

dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m

Should I change these values for more nice results?

Wondering the same thing....

Sent from my Transformer TF101 using xda premium

heapsize=256m **its written as m always!!** **I had it as mb because I was thinking in mb**
growth=64m

Sorry put mb and that I had the op worded wrong before and that these are the actual settings

Sorry worded things wrong 2 or 3 times now and had people read them or get the wrong idea

In future I will write everything down to the letter and make sure everything is worded as clearly as possible

Sent from my Transformer TF101 using XDA Premium HD app

Originally Posted by Danzano

heapsize=256mb
growth=64mb

Sent from my Transformer TF101 using XDA Premium HD app

Anyone got this working with stock rooted?
Also as a note, if you do try.. make sure you have your "going in to recovery" sorted, as I gave it a whirl but only to get stuck in boot loops..
Had to reflash the Rom to get it back to normal..

Just to confirm in my build.prop before the change also had the same as Garry and a few others.

dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m

I changed the values and to the *mb and I have a feeling this might be what caused the boot loop. As yet can not not confirm if there is the difference between *m or *mb as the cause.