Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Try setting targetSdkVersion to 9 (or 10) <strong>and</strong> adding <code>&lt;supports-screens android:xlargeScreens="false" /&gt;</code> to your AndroidManifest.xml (docs for <a href="http://developer.android.com/guide/topics/manifest/supports-screens-element.html#xlarge" rel="nofollow">supports-screens</a>). This tells the system that your application does not explicitly support xlarge screens and that it should offer the compatibility zoom/scale option for users that use the app on xlarge devices. Note that this will <strong>not</strong> cause the app to be hidden from xlarge devices on the Play Store (<code>supports-screens</code> only causes Play Store to filter apps from smaller screens if they are designed to run on larger screens, not the other way around).</p> <p>The reason I think this is happening once you set targetSdkVersion to 9+ is because supports-screens xlargeScreens was added in API Level 9 and (I believe) defaults to true (for API Level 9+ at least). Once xlargeScreens is true the system will disable the compatibility zoom/scale mode.</p> <p>Supporting docs (where it does say this but is fairly convoluted):</p> <ul> <li><a href="http://developer.android.com/guide/practices/screen-compat-mode.html" rel="nofollow">http://developer.android.com/guide/practices/screen-compat-mode.html</a></li> <li><a href="http://android-developers.blogspot.com/2011/07/new-mode-for-apps-on-large-screens.html" rel="nofollow">http://android-developers.blogspot.com/2011/07/new-mode-for-apps-on-large-screens.html</a></li> <li><a href="http://developer.android.com/guide/topics/manifest/supports-screens-element.html" rel="nofollow">http://developer.android.com/guide/topics/manifest/supports-screens-element.html</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POAndroid Tablet Zoom option missing
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAdamK
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAndroid Tablet Zoom option missing
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI tried adding a `support-screens` item, but it wasn't recognised because my app is built against the 2.1 SDK; I think I need to build against 2.3 to use that? Could I do that and still support 2.1?
      singulars
      1. PO
      1. USFish
    2. COyes, you should build against the same version as targetSdkVersion. you just need to be careful you don't use any API calls from earlier versions without checking API levels first (the new Android Lint tool has a rule to help identify this).
      singulars
      1. PO
      1. USAdamK
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload