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
res
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
On Wed, Jan 6, 2010 at 3:10 PM, Matt Kanninen wrote:
> 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
Got it. I don't think I need targetSdkVersion now that I have:
I want to target HVGA and up.
On Jan 5, 8:10 pm, Lance Nanek wrote:
> Can change defaults for supports-screens. Can also disable
> compatibility features, like reporting a smaller size than the actual
> display and scaling
Can change defaults for supports-screens. Can also disable
compatibility features, like reporting a smaller size than the actual
display and scaling your app up.
See:
http://developer.android.com/intl/zh-TW/guide/practices/screens_support.html
On Jan 5, 9:15 pm, Matt Kanninen wrote:
> What does
5 matches
Mail list logo
