Author Topic: Let's build for Android! (Read 26832 times)

Amir · « **Reply #40 on:** 23 Aug 2021, 08:54 »

Cool, but the size of my game is 1.47 GB. Does that mean I can't build for Google Play? I don't quite understand. Is there a limited size for .aab? earlier you could upload 2 obb files so 4 GB and what about the .aab format now?

eri0o · « **Reply #41 on:** 23 Aug 2021, 12:18 »

Unfortunately the absolute maximum has lowered now

- 150 MB for your Android App Bundle without the asset packs (once you add them in their directories, the AAB will include them)
- 1GB for all install-time Asset combined (which works with regular Android API)
- 512 MB for all on-demand assets (requires Play Store specific API)
- 512 MB for all fast-follow assets (requires Play Store specific API)

You can see info here or discussion here. I have not worked on on-demand and fast-follow assets - anyone else is invited to, I don't know how to work with those, it would be important to check if they break app compatibility with other stores, say if you don't use those but add a dependency to the Play Core Library and then push the app to Amazon (or other non-Google store), what will happen?

Is your game using compression for the graphics in AGS? AGS compression is very minimal but better than no compression. Do you have an estimate of what your game size breakdown is (graphics, music, voice...)? Here's a forum topic that talks about this.

You can also turn compression on in the asset pack itself and see what it does for you, but it may have a significant performance impact - or may not, you would need to try and test it for your case.

See also Managing Audio and Graphics Footprint in AGS-Manual.

Amir · « **Reply #42 on:** 23 Aug 2021, 14:40 »

Quote

Is your game using compression for the graphics in AGS? AGS compression is very minimal but better than no compression.

No, it's false. I thought it has disadvantages, so I didn't activate it. I can try it and see thereafter the game size.

Quote

The total download size limit for all asset packs in an Android App Bundle is 2 GB.

- 150 MB for your Android App Bundle without the asset packs (once you add them in their directories, the AAB will include them)
- 1GB for all install-time Asset combined (which works with regular Android API)
- 512 MB for all on-demand assets (requires Play Store specific API)
- 512 MB for all fast-follow assets (requires Play Store specific API)

That means my game is also possible. I will read more about it and about fast-follow and on-demand, I cann't understand a word now.

Thank u.

Crimson Wizard · « **Reply #43 on:** 23 Aug 2021, 17:36 »

IMHO it's also a good option to look for methods to optimize your game. Find out how much everything takes - sprites, audio, etc. There's always a way to reduce the space each of these types of resources demand.

I think in any case it's important to keep in mind that what works on PC will not necessarily work on mobile devices as-is, and may require to be adjusted.

Amir · « **Reply #44 on:** 25 Aug 2021, 20:51 »

Okay, I will.

eri0o · « **Reply #45 on:** 25 Aug 2021, 23:26 »

Amir, but did it ran in your device? Did it worked for you at least?

Amir · « **Reply #46 on:** 26 Aug 2021, 16:30 »

Quote from: eri0o on 25 Aug 2021, 23:26

Amir, but did it ran in your device? Did it worked for you at least?

Not yet. That scared me off:

Quote

You will need the following to build this project:

Android Studio
AGS engine native libraries.
A compiled AGS game (NOTE: Game must be < 1 GB total).

And I will get annoyed if it works and then I can't upload it on Google Play because of the size

but I will try it anyway.

Should I update the package name and do all updates befor I build in Android Studio, right?

And which compiled game files in the assets folder do u mean? acsetup.cfg gamename.ags somelanguage.tra? these files?

eri0o · « **Reply #47 on:** 26 Aug 2021, 16:45 »

Quote from: Amir on 26 Aug 2021, 16:30

Should I update the package name and do all updates befor I build in Android Studio, right?

And which compiled game files in the assets folder do u mean? acsetup.cfg gamename.ags somelanguage.tra? these files?

First do this with all your files from Compiled/Data dir:

Quote from: eri0o on 23 Aug 2021, 00:18

The real short version of the guide is, place your compiled game files in mygame/app/src/main/assets and click build in Android Studio and see if things work. Then read the guide for details and ask here in case of problems.

If you have your phone connected, after everything is done, it will even install and boot it there!

Also, please turn on sprite compression in the Editor and check the resulting size of the spritecache.

Then you do all the other things. If you are using Android Studio Artic Fox or newer there's even an easier way of doing the other steps but for now all the steps in the README should work fine - basically, on the newest Android Studio, you can have Java package files and android app IDs that doesn't match, so in theory, once everyone has updated their tools, all those steps can be a simple one line in the gradle file.

Amir · « **Reply #48 on:** 26 Aug 2021, 21:16 »

I can't believe my eyes, after sprite compression it's 321 MB

. I copied everything in the right place. I opened the project in Android Studio, the project must be mygame in Android folder. But i'm getting errors

Spoiler: Show

I just wanted to open it to update package name $:-\$ I don't know why it says BUILD FAILED, I didn't want to build. Do u know how to fix this? should I move the project to a different directory, to C:/ maybe? and should I add the line 'android.overridePathCheck=true' to gradle.properties file in the project directory?

It's Android Studio 4.2.2

eri0o · « **Reply #49 on:** 26 Aug 2021, 22:15 »

In your error message there's a character my browser can't render ("F�r") in your path, my guess is it's complaining about that. Make sure that the path to the android studio project has only "normal" characters (you know, things that are on the first half of an ASCII table, [a-zA-Z0-9_] , things beyond this will not work. Also to be safe, avoid space character in these directories!

Also if you can, please use Artic Fox (latest stable version of Android Studio) instead, there's a ton of bugs that have been fixed, specially for people on Windows. The version number now changed and it's something like 2020.3.X .

CW made a release today of AGS 3.6.0 and it has Android libs pre-built that you can use to avoid building native parts.

Amir · « **Reply #50 on:** 27 Aug 2021, 00:43 »

Oh I thought I have the latest version. Ok, I will download this 2020.3.1.

Quote

CW made a release today of AGS 3.6.0 and it has Android libs pre-built that you can use to avoid building native parts.

I'm using AGS 3.4.3 so I'm using Android libs of this version or do I have to use the libs of AGS 3.6.0?

Amir · « **Reply #51 on:** 27 Aug 2021, 13:29 »

I got the error Android\ndk\21.1.6352462 did not have a source.properties file code
in build.gradle I added

Code: Adventure Game Studio

android
 {
   ndkVersion '21.1.6352462'
  }
 

Now i'm getting another error:

Spoiler: Show

I read it might be because of the Gradle version. I took a look in my setting, Android Gradle Plugin Version 4.1.2 and Gradle Version nothing. This version is very old. Should I change Android Gradle Plugin Version and Gradle Version?

Amir · « **Reply #52 on:** 12 Sep 2021, 16:59 »

I tried again today and it worked. I mean I was able to create com.mystudioname.gamename I had to delete android {ndkVersion '21.1.6352462'} that what I added last time. I think it worked because of Windows updates that were running recently, I don't know. But when I'm trying to build APKs I'm getting 3 errors from CMake. As a precaution I downloaded the latest version of CMake cmake-3.21.2 and added its path in Windows, but that didn't help.

The errors:

Spoiler: Show

I think something is wrong with the CMake files in the ags-master from eri0o. Does anyone know what's wrong? And am I the only one who gets these errors? could anyone create APK file? or a bundle What ever.

Crimson Wizard · « **Reply #53 on:** 12 Sep 2021, 17:24 »

Do you have the Ninja tool installed? All these errors seem like refering to it.

The Android readme sais:

Quote

Ninja (at least 1.10.0 should be good), also needs to be added to PATH

I think you can get it here: https://ninja-build.org/

Amir · « **Reply #54 on:** 12 Sep 2021, 18:00 »

Quote from: Crimson Wizard on 12 Sep 2021, 17:24

Do you have the Ninja tool installed? All these errors seem like refering to it.

The Android readme sais:
Quote
Ninja (at least 1.10.0 should be good), also needs to be added to PATH

I think you can get it here: https://ninja-build.org/

Oh I didn‘t see that

ok I will download it and add the location to path and see if it works, thank u.

Amir · « **Reply #55 on:** 13 Sep 2021, 16:11 »

I added ninja.exe location to my path and added CMake as well to path then changed the version number of CMake in build.gradle. I'm using 3.21.2. Now it finds the ninja but something is still wrong, when I open the project I get one error:

Spoiler: Show

and when I try to build APKs I get this error:

Spoiler: Show

I tried refresh linked c++ projects but it didnt help. The 2 errors are related, it's still a matter of CMake and Ninja I think. Does anybody have some solution? I can't find a solution on the internet.

I can no longer see those red error messages

Before I got that last error, I fixed 2 errors.

eri0o · « **Reply #56 on:** 13 Sep 2021, 18:12 »

Hey Amir,

Instead of going this way try, closing Android Studio, and downloading the android prebuilt libraries here first: https://github.com/adventuregamestudio/ags/releases/tag/v.3.6.0.8

It's the file named AGS-3.6.0.8-android-libs-release.zip, then just go into the project directory and extract the libraries in the directory mentioned in the README, it should be here

https://github.com/adventuregamestudio/ags/tree/master/Android/library/runtime/libs

There's a txt file there, make sure the directory looks like it's mentioned in it! Don't download the debug libraries, use the ones marked release.

If all goes well Gradle will pickup the libraries.

The idea of using Artic Fox and newer android studio is that in them you can get both CMake and ninja without installing them externally, just by ticking the option in the SDL Tools menu, for cmake and ndk sideload. Regardless, if you use the pre-built libraries, neither ndk, cmake or Ninja are needed.

Amir · « **Reply #57 on:** 13 Sep 2021, 23:46 »

Ahaaa that was my question on August 27th.

Quote

I'm using AGS 3.4.3 so I'm using Android libs of this version or do I have to use the libs of AGS 3.6.0?

Quote

The idea of using Artic Fox and newer android studio is that in them you can get both CMake and ninja without installing them externally, just by ticking the option in the SDL Tools menu, for cmake and ndk sideload. Regardless, if you use the pre-built libraries, neither ndk, cmake or Ninja are needed.

Wow that's cool, good to know. but I've already downloaded everything, I'll leave everything as I downloaded, it doesn't do any harm I think. so I will try tomorrow the AGS-3.6.0.8-android-libs-release and let u know. Thank u. Good night.

eri0o · « **Reply #58 on:** 14 Sep 2021, 13:19 »

The way it works, is like this, gradle will look if there's a file libengine.so in the library/runtime/libs/arm64-v8a/ dir ( there should be one directory for each processor architecture in the zip file, all are needed). This is done in code in the build gradle here:

https://github.com/adventuregamestudio/ags/blob/bc79bb9fe1f4421f2cde15f33172a388bbe9a733/Android/library/runtime/build.gradle#L69

So no need to change anything, just extracting the libraries in this place, one directory for each architecture. Then the project will pickup the pre-built instead of rebuilding.

There has been a new AGS release now, so you can pickup the Android libraries here now: https://github.com/adventuregamestudio/ags/releases/tag/v.3.6.0.9

Once the SDL2 version of the engine is more stable these android libraries will be also linked in the forums, but for now, just pickup the 3.6.0.X releases from GitHub.

Also for reference, if anyone is reading and want to build the C++ native parts of the engine, the config to tick in Android Studio is here

Spoiler: Show

This is not needed when using the pre-built libraries.

Crimson Wizard · « **Reply #59 on:** 14 Sep 2021, 13:29 »

Quote from: eri0o on 14 Sep 2021, 13:19

Once the SDL2 version of the engine is more stable these android libraries will be also linked in the forums

I started linking them in 3.6.0 thread since yesterday

⚠ Cookies ⚠

Author Topic: Let's build for Android! (Read 26832 times)