What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Optimizations!

I dont know if someone has made a thread here like this already, but I think we should put all and any kind of useful optimizations for our Droid 2's into area. I know im always looking for ways to make my Droid more efficient. So here are the ones I know(not too many).

vmheap = 32m
wifi scan = 90
undervolt of course
zipalign_apks
deodex

now everybody share yours. I really wanna know some new things to do with my Droid 2
 
WiFi scan is how often your phone scans for access points when not connected to a WiFi signal (battery drainer. The value at 90 would mean that it is scanning every 90 seconds for a signal.

Sent from my Droid using DroidForums app (free in market)
 
VM heap size is maximum memory an application can consume; it does *not* mean it's total memory footprint, just how much *data* it can allocate at the same time. Therefore, the more resource-intensive application, the more heap it *requires* to run; this effect is very visible with LWP's and launchers which operate on large amounts of uncompressed bitmaps. Additionally, JIT pretty much requires large VM heap as the basic idea behind just-in-time optimizer is to trade memory efficiency for operating speed. VM heap is also roughly the biggest chunk of per-app virtual memory space that kernel can't "fake", share between multiple apps, silently drop and reload when accessed or do any of the other memory management tricks that allow to squeeze multiple apps that would each require hundreds of megabytes of memory under naive (e.g. DOS-and win95-like) memory allocation schemes into a handful of MBs that are actually available. Since it cannot be made disappear from physical memory to make room for something else without corrupting app state, the more complex apps grow, the more often they have to be killed --or force closed in Android terminology.
 
Alrighty.....missinterpretted what I read elsewhere then. But this makes sense as well.....

Sent from somewhere...
 
Back
Top