Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8261281
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T03:21:12+00:00 2026-06-08T03:21:12+00:00

I’m developing an app and I encountered a serious problem (really big failure in

  • 0

I’m developing an app and I encountered a serious problem (really big failure in Android in my personal opinion).
If you try to support multiple screens prior to API 13 (that the “small width” feature was added), you have to use the screen size (small, medium etc) and density (ldpi, mdpi etc) to supply different layouts for different screens.
All working well and good, until you want to support both 10″ tablets and 7″ tablets.
For example, a 10″ tablet with 1280X800 resolution and a 160 density (most of tablets), and Kindle (1024×600, density 160, 7′) are the same for Android, that means that prior to API 13 (not all tablets run 3.2 yet) I can’t supply different layouts/dinmension values for each one of them seperately.

I really don’t want to do all the nasty calculations inside the code just for determining the size of the text. I’m pretty sure that a lot of people encounter this problem.

Does anyone knows a solution for this?

Thanks,
Elad

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T03:21:14+00:00Added an answer on June 8, 2026 at 3:21 am

    Using the old qualifier system, a 7" tablet will register as a large screen and a 10" tablet will register as an xlarge screen (the latter qualifier introduced in Gingerbread).

    Edit: From the latest Android Compatibility Definition Document (CDD):

    Specifically, device implementations must report the correct screen size according to the following logical density-independent pixel (dp) screen dimensions.

    • Devices MUST have screen sizes of at least 426 dp x 320 dp (‘small’)
    • Devices that report screen size ‘normal’ MUST have screen sizes of at least 470 dp x 320 dp
    • Devices that report screen size ‘large’ MUST have screen sizes of at least 640 dp x 480 dp
    • Devices that report screen size ‘xlarge’ MUST have screen sizes of at least 960 dp x 720 dp

    Devices wishing to be eligible for Google Play must adhere to this document’s rules. Technically, devices like the Kindle Fire aren’t required to follow these rules since they use their own app store, but I have not personally seen them stray. The Fire by these rules is large because it’s smallest width is < 720dp.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am writing an app with both english and french support. The app requests
link Im having trouble converting the html entites into html characters, (&# 8217;) i
I have a string like this: La Torre Eiffel paragonata all&#8217;Everest What PHP function
I'm parsing an RSS feed that has an &#8217; in it. SimpleXML turns this
We're building an app, our first using Rails 3, and we're having to build
I am currently running into a problem where an element is coming back from
I am using Paperclip to handle profile photo uploads in my app. They upload
I ran into a problem. Wrote the following code snippet: teksti = teksti.Trim() teksti
I have a .ini file as follows: [playlist] numberofentries=2 File1=http://87.230.82.17:80 Title1=(#1 - 365/1400) Example
That's pretty much it. I'm using Nokogiri to scrape a web page what has

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.