Android - Google Play filtering out xxhdpi

Question

I currently have a problem with Google Play filtering and the new density class xxhpdi, which was introduced in API Level 16. My app is splitted into 3 APK files (I know that is not the best practice, but due to a bad planning, I have to do it like this at the moment). The interesting part is the version for Android 4.0, Smartphones only. I have setup market filter in AndroidManifest.xml like this:

<uses-sdk android:minSdkVersion="14" android:targetSdkVersion="17"/>
<compatible-screens>
    <screen android:screenDensity="ldpi" android:screenSize="small"/>
    <screen android:screenDensity="mdpi" android:screenSize="small"/>
    <screen android:screenDensity="hdpi" android:screenSize="small"/>
    <screen android:screenDensity="xhdpi" android:screenSize="small"/>

    <screen android:screenDensity="ldpi" android:screenSize="normal"/>
    <screen android:screenDensity="mdpi" android:screenSize="normal"/>
    <screen android:screenDensity="hdpi" android:screenSize="normal"/>
    <screen android:screenDensity="xhdpi" android:screenSize="normal"/>
</compatible-screens>

The problem is now, that new devices with 1080p screens like the HTC Droid DNA can't see or install my app, because I did not specify that it also supports the xxhdpi screens. The problem is, because i set my minSdkVersion to API Level 14, which is Android ICS, I cannot simply add the line:

<screen android:screenDensity="xxhdpi" android:screenSize="normal"/>

This is because API level 14 does not know the xxhdpi class. Is there any solution for my problem, without having to create a 4th seperate APK file?

Thank you.

Answer 1

I found the solution: Instead of adding the

<screen android:screenDensity="xxhdpi" android:screenSize="normal"/>

line to the compatible-screens section, it seems like the numeric value is working as well:

<screen android:screenDensity="480" android:screenSize="normal"/>

Answer 2

There seems to be an open issue regarding this problem: code.google.com/p/android It sucks but I can't think of a better workaround.