Support ONLY Galaxy S3, similar, and above?

Solar2D Android
#1

What would be the best way to filter out Android devices, so that I’m limiting support/availability to Galaxy S3 and similar caliber devices only?

I tried the following in the build.settings, but I have over 1400 devices showing up including Galaxy S (1)!  How can this be?

    android = {

        usesPermissions = {

            “android.permission.INTERNET”,

            “com.android.vending.CHECK_LICENSE”,

            “com.android.vending.BILLING”,

        },

        supportsScreens =

              {

                 smallScreens = false,

                 normalScreens = true,

                 largeScreens = true,

                 xlargeScreens = true,

                 requiresSmallestWidthDp = 600,

              },

        usesFeatures =

            {

                { name = “android.hardware.sensor.gyroscope”, required = true },

            },

    },

#2

As far as I know, Corona doesn’t support supportsScreens in build.settings.
If you want to modify it, you’ll have to edit your APK’s manifest after compilation with something like apktool.(https://code.google.com/p/android-apktool).

I believe the Galaxy S1 is considered a normalScreen, so it will be included if it’s true.
Also requiresSmallestWidthDp is only effective on devices running Android 3.2 and later (API level 13).

I’ve found it difficult to limit supported Android devices due to the sheer number of manufacturers and models.
If you’re worried about performance then I personally think that the Android version (API level) is the easiest approach to limit the number of supported devices since the later Android versions are mostly installed on devices with capable hardware.

If you only target version 4 and above (API level 14) you’ll reach over 70% of all devices. The remaining 30% is mostly Android 2.2 / 2.3 which includes many weaker devices. (http://en.wikipedia.org/wiki/File:Android_historical_version_distribution_-_vector.svg)

#3

As far as I know, Corona does support  supportsScreens  in build.settings.

I uploaded an apk to google play a couple of days ago and it did filter out devices when using it.

#4

OK, in that case… my bad.

Couldn’t find it in the docs though…

#5

Thank you for the info.  

Is there a way to specify android:minSdkVersion on build.settings file? 

#6

It is not possible to set the minSdkVersion in the build.settings.

#7

Thank you for all the info, but I hope we can do this in build.settings in the future, because the other way looks like a pain…

#8

As far as I know, Corona doesn’t support supportsScreens in build.settings.
If you want to modify it, you’ll have to edit your APK’s manifest after compilation with something like apktool.(https://code.google.com/p/android-apktool).

I believe the Galaxy S1 is considered a normalScreen, so it will be included if it’s true.
Also requiresSmallestWidthDp is only effective on devices running Android 3.2 and later (API level 13).

I’ve found it difficult to limit supported Android devices due to the sheer number of manufacturers and models.
If you’re worried about performance then I personally think that the Android version (API level) is the easiest approach to limit the number of supported devices since the later Android versions are mostly installed on devices with capable hardware.

If you only target version 4 and above (API level 14) you’ll reach over 70% of all devices. The remaining 30% is mostly Android 2.2 / 2.3 which includes many weaker devices. (http://en.wikipedia.org/wiki/File:Android_historical_version_distribution_-_vector.svg)

#9

As far as I know, Corona does support  supportsScreens  in build.settings.

I uploaded an apk to google play a couple of days ago and it did filter out devices when using it.

#10

OK, in that case… my bad.

Couldn’t find it in the docs though…

#11

Thank you for the info.  

Is there a way to specify android:minSdkVersion on build.settings file? 

#12

It is not possible to set the minSdkVersion in the build.settings.

#13

Thank you for all the info, but I hope we can do this in build.settings in the future, because the other way looks like a pain…