title: Allow auto scaling in Android Drawables for various densities?
body: <p>A lot of blogs and best practices for Android Development says </p>
  
  <p>"<strong>You don't need to supply bitmaps for every possible density, Android will scale your bitmaps (typically when they are loaded) to match the current density</strong>."</p>
  
  <p>Reference Link : <a href="https://plus.google.com/105051985738280261832/posts/6eWwQvFGLV8" rel="nofollow">https://plus.google.com/105051985738280261832/posts/6eWwQvFGLV8</a></p>
  
  <p>I tried it works well.
  But i couldn't understand one thing.</p>
  
  <p>For instance i created a sample app with 5 full screen images of around 1.5 MB each in a view pager.</p>
  
  <p>I created heavy images for 7 inch MDPI devices like Galaxy Tab 2 and put them in "drawable-large-mdpi" folder. It was bit jerky but didn't crash and let me scroll through all the images.</p>
  
  <p>Now i tried to use the app on my Nexus 7 which is almost a large HDPI device. The app crashed with "OOM error" while decoding the bitmap. </p>
  
  <p>*<em>If i move the images from large MDPI to large HDPI, it works well on both the devices with out any crash. *</em></p>
  
  <p><strong>So i have two questions.</strong></p>
  
  <ol>
  <li>Does this result incline towards, we can only put the graphics assets in the highest density drawable folder and let it scale down automatically in its range ?</li>
  <li>What happens internally why it crashed for the first time ?</li>
  </ol>