Status

Released

Release Date April 2013 4/2013
Available for MMF2 Icon MMF2 Developer Icon CF 2.5 Icon CF 2.5 Developer Icon

The Android/OUYA Export Module exports creations for Android-powered devices (smartphones, tablets, and the OUYA). It was first released for purchase in April 2013 and exports to the APK format, ready for installation on Android or for publication to Google Play, or other marketplace services.

Contents

Requirements

Dependencies

In order for the exporter to work, a few external dependencies need to be installed on your computer:

  • Java Development Kit (JDK)
    • The first time you build an Android application, you’ll be prompted for the pathname of the JDK directory.
      • Example Path: C:\Program Files (x86)\Java\jdk1.8.0_25
      • This can also be changed later in Fusion’s preferences.
    • For 64-bit machines, it is advisable to install at least the 32-bit version, not only the 64-bit version, as it is known is cause a conflict with the Flash Exporter.
  • Android SDK (Tools Only)
    • Not to be confused with the ADT Bundle or Android Studio.
    • Install at least the Android 4.0 platform package (API #14).
    • The first time you build an Android application, you’ll be prompted for the pathname of the Android SDK directory.
      • Example SDK Tools Path: C:\Program Files (x86)\Android\android-sdk
      • Example Android Studio Path: C:\Users\your_user_name\AppData\Local\Android\sdk

Note that Fusion 2.5 will attempt to detect the JDK and Android SDK automatically.

Releasing Applications

  • You will need a certificate to sign your applications before being able to release them.
  • If you want to publish applications on Google Play, you will need to register to be a developer. There is one-off fee of $25.

You will also need to read Google’s documentation, especially how to design, publish and test your application properly. You can find this documentation on the Android Developers site.

Android Requirements

Applications exported by Fusion will work on Android devices that meet the following criteria:

  • Android 2.3 “Gingerbread” or above.
    • The MMF2 version of the exporter runs from Android 1.6 “Donut”.
  • Device has a GPU (graphic processor).
    • Applications can run without a GPU but they will be very slow.

Understanding APIs

APIs are the framework that apps are built upon for specific platform versions. Each new platform version adds new APIs that are not available in the previous version, thus, lower APIs maintain compatibility with future versions whilst newer APIs work with newer features of Android. Fusion by default uses API 14 (Android 4.0-4.0.2), but it is advisable to use the latest API possible.

Fusion will be unable to build your application if the selected Build API is not installed in the Android SDK. Alternately, if builds fail with specific APIs, try a different one.

Some features require specific API versions to be installed in addition to your target API level, but these do not need the Build API in Fusion to be changed.

This table is a dump from the previous MediaWiki instance. It needs cleaning up.

API Android Version Required for...
8 Android 2.2 Froyo No longer supported in Fusion 2.5
10 Android 2.3.3 Gingerbread Admob
14 Android 4.0 Ice Cream Sandwich
15 Android 4.0.3
16 Android 4.1.2 Jelly Bean
17 Android 4.2.2 OUYA
18 Android 4.3.1
19 Android 4.4.2 KitKat
20 Android 4.4W.2
21 Android 5.0.1 Lollipop OUYA
22 Android 5.1.1
23 Android 6.0 Marshmallow Temporarily incompatible until future update

Permissions

For certain features (such as vibration) to work on Android, you must declare which permissions required for your app. When the user installs the app, they will be presented with them and can choose to accept. You should only use the permissions that are necessary for your app.

There are two PDF documents available on the Community Forums from Fernando that details each of permissions. Alternately, they are available on the Android Developers website.

https://community.clickteam.com/threads/84241-Android-Permissions?p=616495&viewfull=1#post616495

Compiling from Android Source

By default, Fusion will delete the project (temporary) files after compiling. If you require the source code to modified before compiling, you can use a trick to prevent it from being deleted.

Retrieval

  1. Disconnect your Android device from the PC and perform a Build & Run. Fusion will become stuck after compiling.

  2. Type into Windows Explorer:
    %temp%
    

    Which should open a path similar to:

    C:\Users\<username>\AppData\Local\Temp
    
  3. Sort the folder by date and you’ll find the latest AndXXXX.tmp folder.

  4. Wait for the RuntimeAndroid-X.apk files to appear in the bin directory. Fusion will have finished compiling.

  5. Copy the entire folder elsewhere on the system.

Compiling

  1. Delete the contents of the bin directory.

  2. Open a command prompt on the root of the folder. (Tip: Hold Shift and right-click the folder)

  3. To compile for release:

    ant release
    

    Or, compile for debugging:

    ant debug
    

Instructions were sourced from this post