from what i can tell, the debug.sf.hw=1 can either be a value of 0 or 1. 0 is where the mod is disabled, and 1 is where it is enabled. it supposedly activates the gpu in the droid (still need verification on this).
the density mod is like resolution on your computer screen. 240 is the default. lowering the value gives you more desktop space (makes the icons smaller). 210 is what i have found to be a good value. if you dont want to permantly change this value, try LCD Density in the market. it makes the mod but it won't persist on hard reboot. good luck
Interesting....it could be placebo effect but setting debug.sf.hw=1 seems to have made a difference. Then again, my phones performance is always pretty good after a reboot for a few hours at least.
Quandrant doesn't agree with it though....my score went down but then again, I don't really give much credence to Quandrant. It really doesn't seem to be an accurate reflection of real-world performance.
debug.sf.hw=1 doesn't enable the GPU per se, that's always enabled. It simply tells the phone to use the GPU for rendering the UI and animations, as opposed to the CPU. This is why it seems to make swiping and scrolling seem much snappier. It could account for the lower quandrant score also, being that the GPU is taking on an additional load, resulting in fewer resources for the 3D render tests that quadrant performs.
I tried the debug.sf.hw =1 and everything seemed to be working very smoothly. But when I tried to play a video, the sound would work fine but the picture seemed to be frozen. Anyone else encounter this? Or maybe I did something wrong when entering tthe line in build.prop?
Sent from my Droid using DroidForums
I take it we should probably reboot after applying the change/changes to the /system/build.prop file? Regarding the lcd.density, I think that is a pretty useful tweak that can have it's benefits in certain situations, but at 210 my keyboard was just soooo freaking small in portrait mode haha, I thought I had the tiny cellphone from Zoolander.
Last edited by meishkov; 05-13-2011 at 10:18 PM.
My only issue is that ever since I flashed CM 7 (started on CM 7.0.2) I've missed some text messages and I'm still getting pretty frequent redraws. Additionally, Screebl shuts down pretty regularly. Obviously, that's not good. Apparently this is because Gingerbread uses too much RAM for the OG Droid? I've seen a few posters talking about the Supercharge script and the build.prop edit. The supercharge script seems pretty simple....looks like you just run it through Scriptmanager and it does the rest. Is that correct?
Can you or somebody explain (step by step) how to do the build.prop edit?
Also, are there any potential negatives to the supercharge script or the build.prop edit? Sorry for the noob questions. I'm really good at following directions, but i'm still learning some of the terminology. Some of the instructions out there are still a bit overwhelming to me.
Thanks in advance.