The camera doesn't use memory (for the most part) that would be accounted against the app and thus cause you to run out of memory. It is, however, a higher megapixel camera, and the resulting bitmaps you are making due to that in combination with the additional memory needed for higher density resources could easily account for you using too much memory.
On Fri, Jan 8, 2010 at 2:38 PM, Matt Kanninen <[email protected]> wrote: > Diane, > > I try hard not test on the emulator, and have access to the Android > phones users are using. This bug happened only on the Droid, and our > application depends on the Camera and Mic to function. > > More details on the bug here: > > http://groups.google.com/group/android-developers/browse_frm/thread/100ce8c4e5cade6a/df64df59143b8e98?lnk=gst&q=mathiastck#df64df59143b8e98 > > and other threads related to: > > > java.lang.OutOfMemoryError: bitmap size exceeds VM budget > > Sometimes out of memory errors, especially DEVICE SPECIFIC MEMORY > ERRORS, are best fixed in the framework, or the specific devices code. > > I can't help debug this issue too much longer either, I'll be off the > project, and on to other Android applications soon. > > -MK > > On Jan 6, 4:27 pm, Dianne Hackborn <[email protected]> wrote: > > On Wed, Jan 6, 2010 at 3:10 PM, Matt Kanninen <[email protected]> > wrote: > > > <supports-screens android:smallScreens="false" > > > android:normalScreens="true" android:largeScreens="true" /> > > > > If you don't specify anyDensity, then the system will run your app in > > density compatibility mode on high and low density devices. You really > want > > to avoid this, since it can result in some artifacts in the UI such as > some > > text being clipped. > > > > If you are designing your app to support different screens/densities, I > > highly recommend that you make the target SDk version at least 4, since > this > > will allow the system to do the correct default configuration to make it > > work correctly. It also allows various other compatibility features to > be > > turned off, which we try to document under each API version here: > > > > http://developer.android.com/reference/android/os/Build.VERSION_CODES... > > > > As for running out of memory -- it is probably because outside of > > compatibility mode the system is being allowed to pre-scale some of your > > loaded bitmaps to allow them to be drawn faster. I would guess this is > just > > a matter of you being close to the memory limit, and this pushing you > over > > (the high density or large screen devices should always have a higher > memory > > limit to account for this... though I don't think the emulator changes > > this, come to think of it, so it could just be an emulator issue). > > > > -- > > Dianne Hackborn > > Android framework engineer > > [email protected] > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
