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 9071925
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 16, 20262026-06-16T18:02:36+00:00 2026-06-16T18:02:36+00:00

I am having issues getting my Manifest file to be compatible with a lot

  • 0

I am having issues getting my Manifest file to be compatible with a lot of the newer phones when I upload a new APK file and I don’t understand why. I am testing it on a brand new HTC Evo V, but for whatever reason, that device won’t show up in the compatibility list.

I’m compiling against API 17 with a minimum support of API 10, so that should encompass a large majority of the phones.

What I’ve tried:

  • Removed all permissions; no change
  • Tried making WIFI not required; no change
  • Removed installLocation to see if it made a difference; no change
  • Even tried adding small screen support to see if it’d show up; no change

What I’ve read:

  • http://developer.android.com/google/play/filters.html
  • http://developer.android.com/guide/practices/screens-distribution.html
  • http://developer.android.com/guide/practices/compatibility.html
  • http://developer.android.com/guide/topics/manifest/manifest-intro.html

My manifest file:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
      package="com.somecompany.appname"
      android:versionCode="10"
      android:versionName="1.0"
      android:installLocation="preferExternal">

    <!-- For expansion pack downloads -->
    <!-- Required to access Android Market Licensing -->
    <uses-permission android:name="com.android.vending.CHECK_LICENSE" />
    <!-- Required to download files from Android Market -->
    <uses-permission android:name="android.permission.INTERNET" />
    <!-- Required to keep CPU alive while downloading files (NOT to keep screen awake) -->
    <uses-permission android:name="android.permission.WAKE_LOCK" />
    <!-- Required to poll the state of the network connection and respond to changes -->
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <!-- Required to check whether Wi-Fi is enabled -->
    <uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
    <!-- Required to read and write the expansion files on shared storage -->
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

    <uses-sdk android:minSdkVersion="10" android:targetSdkVersion="17"/>
    <supports-screens android:normalScreens="true"/>
    <supports-screens android:largeScreens="true"/>
    <supports-screens android:xlargeScreens="true"/>

    <compatible-screens>
        <screen android:screenSize="normal" android:screenDensity="mdpi" />
        <screen android:screenSize="large" android:screenDensity="hdpi" />
        <screen android:screenSize="xlarge" android:screenDensity="xhdpi" />
    </compatible-screens>                      
    <application android:icon="@drawable/icon" android:label="@string/app_name" android:allowBackup="false">
        <activity android:name="somecompany.appname.SplashScreen"
                  android:label="@string/app_name"
                  android:theme="@android:style/Theme.NoTitleBar"
                  android:screenOrientation="portrait">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
        <activity android:name="somecompany.appname.SoundAndCallActivity" android:screenOrientation="portrait" android:theme="@android:style/Theme.NoTitleBar"/>
        <activity android:name="somecompany.appname.MainScreenActivity"   android:screenOrientation="portrait" android:theme="@android:style/Theme.NoTitleBar"/>
        <activity android:name="somecompany.appname.SettingsActivity"   android:screenOrientation="portrait" android:theme="@style/Theme.Transparent"/>
    </application>
</manifest>
  • 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-16T18:02:37+00:00Added an answer on June 16, 2026 at 6:02 pm

    I wanted to post this question and also an answer because I found this to be so frustrating to figure out at first. However, this changed my number of supported devices from 499 to 1968. Hopefully this will help more people in the future since it seems to be an obscure topic.

    Technique 1: The reason why more devices wouldn’t show up was because Google filters more aggressively when you use the <compatible-screens> tag. In my case, I didn’t have enough of the different screen sizes and density combinations, so it filtered out all of the ones I left out (see Technique 2 below).

    If you instead ONLY use the <supports-screens /> tags, then you will enable your app to be found by many more devices. So do yourself a favor and remove all of those other tags in the <compatible-screens> block.

    You can use a shortform like this:

    <supports-screens android:largeScreens="true" android:normalScreens="true" android:smallScreens="true" android:anyDensity="true"></supports-screens>
    

    Quoted from the original article:

    Google Play filters the application if the device screen size and
    density does not match any of the screen configurations (declared by a
    “screen” element) in the “compatible-screens” element.

    Caution: Normally, you should not use this manifest element. Using
    this element can dramatically reduce the potential user base for your
    application, by excluding all combinations of screen size and density
    that you have not listed. You should instead use the
    “supports-screens” manifest element (described above in table 1) to
    enable screen compatibility mode for screen configurations you have
    not accounted for with alternative resources.

    Technique 2: Another technique you can use is to be more specific with your <compatible-screens> tag and get rid of the <supports-screens /> tags. You can base those decisions on your app requirements and also on the latest device distribution numbers.

    In the example below, I don’t want to support small screens or the ldpi densities of the normal, large, or xlarge screens, so I left them out.

    <compatible-screens>
        <!-- all normal size screens -->
        <screen android:screenSize="normal" android:screenDensity="mdpi" />
        <screen android:screenSize="normal" android:screenDensity="hdpi" />
        <screen android:screenSize="normal" android:screenDensity="xhdpi" />
        <!-- all large size screens -->
        <screen android:screenSize="large" android:screenDensity="mdpi" />
        <screen android:screenSize="large" android:screenDensity="hdpi" />
        <screen android:screenSize="large" android:screenDensity="xhdpi" />
        <!-- all xlarge size screens -->
        <screen android:screenSize="xlarge" android:screenDensity="mdpi" />
        <screen android:screenSize="xlarge" android:screenDensity="hdpi" />
        <screen android:screenSize="xlarge" android:screenDensity="xhdpi" />
    </compatible-screens>
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am having issues getting the -e and -d file test operators to work
I'm having some issues getting file uploads to work correctly and the following code
I'm having issues getting the customer.xml layout file to work properly for the customer's
I am having issues getting an embedded video file to play using MPMoviePlayerController. My
I'm having issues getting a php form to write to a file hosted with
I am having issues getting my database to build from my YAML file. Here
I'm having issues getting jQuery to work correctly while testing on Localhost. The function
I'm having issues getting kohana to come up at all. I'm somewhat new to
I'm new to cakePHP and I'm having issues getting all of my models to
Im having issues getting this to work, maybe its not even possible? I have

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.