Guys, about that mem problem there seems to be a bit of a confusion about the different parameters for different 'memories'. Chainfire, after investigating a bit more and testing with a tool called 'Elixir' (free on the market), your FAQ seems to describe the wrong parameter and/or the wrong memory type.
If you look at the attached screenshot, you'll see, that there are two memory size parametes. A "per-app" size (the middle value of 48m, marked with the nice German word 'Speicherlimit'
), which is set to the fatal 48m and which is reported as too low by DSLR Controller. In the bottom you see the value for the virtual machine (dalvik) memory, which is named 'max memory for the VM'. When you alter the value for "dalvik.VM.heapsize" in the build.prop, THIS is the mem value changed. I tried it with 196m and promptly Elixir reported the 196m in the bottom line. But it didn't change the per-app value. So the description in the FAQ is ... well, 'a bit missleading'
. It also explains the fact I stated, 2.3.6 comes already with 128m set - that was for that global memor for the VM, not the per-app value. I still think, also all stock 'build.prop's have the 128m value preset. That's why the rocket dev couldn't remember to have it changed
.
Anyway, as I said I'm not an Android coder, so I wouldn't know the right screw to turn to set the proper 'per-app' value easily. It would be interesting also, if you (Chainfire) would check your Note with Elixir too and try to find out, why your 2.3.6 is working. What's it reporting in that screen (tap on the RAM line). If it shows 128m for both values on your side, it would be interessting, how you achived that - I'm willing to bet a few bucks, it wasn't the dalvik.VM.heapsize
.
Anyway, thanks so far for all the constructive answers here, great!
