Again, I strongly recommend not using compatible-screens. Why do you want to have a density requirement? There really is no need for such a thing. If you write you app correctly, you will work on any density. If you are using the UI toolkit, this comes from free. If you are using something lower-level like OpenGL it just requires a little scaling.
You also say you want to exclude tablets, but then say you are supporting xlarge screens, so I'm not sure which you mean. On Mon, Apr 16, 2012 at 6:37 PM, ToniL <tlugo...@hotmail.com> wrote: > Hi Dianne, > > I am using both supports-screens and compatible-screens as we are > targeting devices that have screen resolution from normal to xlarge > and density ldpi to hdpi. Is this the right thing to do or is there a > way to add the density requirement to supports screen section and > exclude the compatible-screens section entirely? We want to make sure > that we are excluding small screens handsets, tablets and any screen > with higher density than hdpi. Hibrid handset - tablet is ok. > The following is a snippet of the manifest file: > > <uses-feature android:name="android.hardware.touchscreen" > android:required="true"/> > <uses-feature android:name="android.hardware.screen.portrait" > android:required="true"/> > <uses-feature android:name="android.hardware.telephony" > android:required="true"/> > > <!-- Screens --> > <supports-screens android:smallScreens="false" /> > <supports-screens android:normalScreens="true" /> > <supports-screens android:largeScreens="true" /> > <supports-screens android:xlargeScreens="true" /> > > <compatible-screens> > <screen android:screenSize="normal" > android:screenDensity="ldpi" /> > <screen android:screenSize="normal" > android:screenDensity="mdpi" /> > <screen android:screenSize="normal" > android:screenDensity="hdpi" /> > <screen android:screenSize="large" > android:screenDensity="ldpi" /> > <screen android:screenSize="large" > android:screenDensity="mdpi" /> > <screen android:screenSize="large" > android:screenDensity="hdpi" /> > <screen android:screenSize="xlarge" > android:screenDensity="ldpi" /> > <screen android:screenSize="xlarge" > android:screenDensity="mdpi" /> > <screen android:screenSize="xlarge" > android:screenDensity="hdpi" /> > </compatible-screens> > > Thank you. > > On Apr 13, 6:58 pm, Dianne Hackborn <hack...@android.com> wrote: > > It shows up if what you have specific in your app filtering allows it to > > show up. > > > > If you say "I tailored the Manifest files to accepts any devices with > > normal, > > large and xlarge screen sizes and low, medium and high density", then it > > sounds like you are using: > http://developer.android.com/guide/topics/manifest/compatible-screens... > > > > And as the big caution says, don't use this. This is very fine-grained > > filtering, which pretty much guarantees that you will be missing devices > in > > ways you can't control very well. Just don't use this. It isn't good. > > > > Of course, there could be something else you are requiring (such as a > > feature) that some devices don't support. Use "aapt dumpt badging > > <path-to-apk>" to see details on all the requirements being defined by > your > > app. > > > > > > > > > > > > On Thu, Apr 12, 2012 at 11:16 AM, ToniL <tlugo...@hotmail.com> wrote: > > > Could somebody tell me what makes a device qualify to show up in > > > Android Marketplace filter when you upload an apk? Do they have to be > > > CTS certified only or it needs to meet other criterias? > > > I tailored the Manifest files to accepts any devices with normal, > > > large and xlarge screen sizes and low, medium and high density. This > > > configuration should include most of the newest handsets that are > > > already on the market but it doesn't. > > > For example there is Motorola Atrix 2 that doesn't appear in the > > > filter but I can download any app from the Market place using Play > > > Store. > > > > > Thanks, > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Developers" group. > > > To post to this group, send email to > android-developers@googlegroups.com > > > To unsubscribe from this group, send email to > > > android-developers+unsubscr...@googlegroups.com > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > 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 android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer hack...@android.com 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
