title: Any way to use LargeHeap for v3.x and ignore for 2.x in Manifest?
body: <p>I'd love to use the <em>Android:LargeHeap="true"</em> option in the Manifest to get a bit extra memory (we're dealing with 5+ MB bitmaps on high-res 1980x1200 displays and expect even larger displays shortly. </p>
  
  <p>I've run out of all the normal tricks to dealing with the poor memory handling in Android for bitmaps (i.e. there is no way to know if there is a hole large enough in fragmented memory other than to try and pray it doesn't crash). I've already spent weeks optimizing, trimming and applying other tricks to minimize memory and prevent crashes. It's a trick of what features can be done in 2.x vs 3.x/4.x, yet keep it all in a single app. No need to point to a "how to optimize for bitmaps" - I've already gone through these and applied what I could.</p>
  
  <p>LargeHeap is not supported on version 2.x, and I use different images for lower res screens that do not need the LargeHeap option in 2.x. (no out of memory issue either).</p>
  
  <p>When android:minSdkVersion="8", it will not allow the Android:LargeHeap option at all.</p>
  
  <p>Is there any way to conditionally include LargeHeap for systems with 3.x, and have it ignored for 2.x? Or have the application itself attempt to set LargeHeap if 3.x is detected?  I can't find any way to do this, but perhaps I've overlooked some trick.</p>
  
  <p>I also realize LargeHeap is rather awful, but we are running out of other tricks. Ideally, it would be nice to do LargeHeap programatically, only when really needed (and allowed) at the program OnCreate.</p>