In addition to what was said above, if you study the <supports-screens> directive carefully and set it properly in your manifest, that will most likely clear things up.
On Fri, Oct 22, 2010 at 11:43 AM, TreKing <[email protected]> wrote: > On Mon, Oct 18, 2010 at 3:35 PM, Wri <[email protected]> wrote: >> >> In the old project, I did not specify a target SDK (the manifest did not >> contain something like: <uses-sdk android:minSdkVersion="8" />). > > Be careful here ... "target SDK" is NOT the same as "minSDK". Was that a > typo or are you not clear on this? > >> >> The new project now uses <uses-sdk android:minSdkVersion="8" /> in the >> manifest. > > So you're app is designed to work ONLY on 2.2 (SDK 8) or is that what your > "target" (what you're testing on) is? > >> >> Why is this happening? How can I load them without scaling while still >> declaring the minimum SDK? > > This I don't know - I haven't had to deal with all this screen support stuff > as the defaults work out fine for me for now, but I would double check you > really want min SDK to 8 and read over this: > http://developer.android.com/guide/practices/screens_support.html > > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered devices > > -- > 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 -- 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
