[Resolved] Restrict Android build to tablets only?

Solar2D General Questions/Discussion
1

How can I target my Android game to only be available for tablets or a certain minimum screen size?

(I figured to research creating a Manifest file, but apparently that’s not an option in Corona.)

Thanks! [import]uid: 10284 topic_id: 24116 reply_id: 324116[/import]

2

http://www.base2solutions.com/walkabout/Corona%20Tips.html#7

A bit old post.
Still you might find this useful! [import]uid: 64174 topic_id: 24116 reply_id: 97320[/import]

3

Thanks!! [import]uid: 10284 topic_id: 24116 reply_id: 97333[/import]

4

@Philipp, you can use supportsScreens, as described in the following thread: http://developer.anscamobile.com/forum/2012/01/01/differentiating-between-small-or-large-screen-similar-screen-resolution. [import]uid: 29384 topic_id: 24116 reply_id: 97351[/import]

5

Thanks, that’s a lifesaver! One question, should I support largeScreens in (addition to xlargeScreens) if I want to target tablets only? I get the feeling largeScreens may be e.g. the first Galaxy Tab (a screen size somewhere in-between iPad and iPhone).

http://developer.android.com/guide/topics/manifest/supports-screens-element.html [import]uid: 10284 topic_id: 24116 reply_id: 97433[/import]

6

I added

settings = {  
 android = {  
 supportsScreens = {  
 smallScreens = false,  
 normalScreens = false,  
 largeScreens = true,  
 xlargeScreens = true,  
 },  
 },  
}

to my build.settings but am now getting the error

"AndroidManifest.xml is corrupt" when I try to submit with Google Play? [import]uid: 10284 topic_id: 24116 reply_id: 97436[/import]

7

Philipp,

Remove the “xlargeScreens” line from your file. That will fix it.

This is because “xlargeScreens” is an Android 2.3 feature, but Corona apps are built for Android 2.2. Thus, that setting is not supported. [import]uid: 32256 topic_id: 24116 reply_id: 97451[/import]

8

Joshua, thanks – most of my apps are specifically made for tablets (and just tablets), how will not having xlargeScreens in affect my discoverability for those devices? And do you know when Corona will support newer versions of Android?

Thanks again! [import]uid: 10284 topic_id: 24116 reply_id: 97475[/import]

9

Google documents this setting here…
http://developer.android.com/guide/topics/manifest/supports-screens-element.html#xlarge

Their documentation does not make this clear, but my understanding is that it will still be purchasable and extra large devices will use “screen compatibility mode” with your app, which should scale up your app much like what iPad does with iPhone apps. [import]uid: 32256 topic_id: 24116 reply_id: 97553[/import]

10

@Phillip If you are really serious about promoting your apps for tablets you have no choice but to edit the manifest file yourself after it’s built by Corona. It isn’t just the xLargeScreens feature that’s missing but the targetSdk as well. Because Corona is still using targetSdk = 8 (Android 2.2) your app will appear on the market as not supporting Honeycomb and later versions and will be put in compatibility mode. It also won’t be featured on the Tablet section of Google Play. On top of all that it will show the useless menu soft button and the compatibility zoom feature when running on Android 3.0+, making it look like it’s not designed for tablets. [import]uid: 61899 topic_id: 24116 reply_id: 98230[/import]

11

Because Corona is still using targetSdk = 8 (Android 2.2) your app will appear on the market as not supporting Honeycomb and later versions and will be put in compatibility mode. It also won’t be featured on the Tablet section of Google Play.

This would be horrible news :confused:

On top of all that it will show the useless menu soft button and the compatibility zoom feature when running on Android 3.0+, making it look like it’s not designed for tablets.

Can you explain what this means? What is the soft button? What does compatibility zoom look like? Is this an Android 3 issue? I got a Xoom tablet running the latest Android 4 and Google Play tells me my apps are compatible, and when I run it on the Xoom it looks OK.

Thanks so much for this feedback, I’d love to hear more. [import]uid: 10284 topic_id: 24116 reply_id: 98233[/import]

12

Compatible isn’t the same as Designed for. Most users probably won’t tell the difference, but I’m a perfectionist so it bothers me that my games, which I designed with tablets in mind, aren’t proper tablet games.

Take a look here:

http://imageshack.us/photo/my-images/10/p20110921191131.jpg/

On the pink rectangle is the soft menu button which was deprecated in Android 4.0 (or was it 3.0?) and is only around for compatibility with older apps. On the green rectangle is the compatibility zoom feature that only shows up when an app doesn’t target Android 3.0+ and doesn’t declare support for xLargeScreens. These two items are enough to have your apps/games rejected at a site like tablified.com which only lists proper tablet apps. [import]uid: 61899 topic_id: 24116 reply_id: 98238[/import]

13

Thanks, I understand now – yep, I see those with my tablet apps on the Xoom. So you follow the advice at http://base2solutions.com/walkabout/Corona%20Tips.html#7 to edit the manifest?

Any chance Corona for solving this (I mean natively)? [import]uid: 10284 topic_id: 24116 reply_id: 98246[/import]

14

That’s right. It’s a very good guide, but it’s for Windows only. I do it on Ubuntu and it’s slightly different. I’m not sure if there’s a apk manager for Mac Os. Once you get the hang of it you can do it pretty fast, although having the option to customize the manifest with Corona would prevent all the hassle. [import]uid: 61899 topic_id: 24116 reply_id: 98309[/import]

15

Thanks, I’m on Windows so this fits perfectly. Right now, compiling and uploading to Google Play is a matter of just some seconds, it’s so easily done with Corona. I’ll see how long it takes with the manifest work. [import]uid: 10284 topic_id: 24116 reply_id: 98340[/import]