- Home /
Size too big for android
Ok so for my school project, i did a android platformer game. I've been working on it for a few months and now that I want to publish it, I realise that the max size for the Google play store is 100mb.
At the begining, my game was 1 gb which is crazy but whatever, I realised that i could split my app binary (adding a obb file). After spliting, my obb was big but somehow, my apk too which was 200mb. When I knew that the apk contains the data for the first scene, i made a blank loading screen, which in my output log is nearly 0kb. I also changed the texture compression to ETC2 and my device filter to ARMv7 only. After all of those changes, my obb is at 550mb while my apk is still at 128mb which is still too much for the Google play store (100mb).
Heres my output log here because I have no idea what to remove. The dlls take 3.9mb and the script all take 1 mb and as far as i know, that's the only thing (including the first scene which is 0kb for me or almost) that ares included in the apk while the rest (like the textures) are in the obb. Even if sounds were included, they only occupie 13mb totale which still doesnt explain the 128mb.
I know my textures are big but i dont care, i just want to have my apk 100mb so i can publish on the google play store.
Answer by kskjadav007 · Mar 27, 2018 at 05:27 AM
Textures need to be reduce .
I compressed most of my texture to smaller resolution and everything lowered.
thanks
Answer by TauseefCVS · Mar 27, 2018 at 05:28 AM
your game textures are very high and have too much space in apk that why you game size 550 MB, you compress the texture with the minimum resolution and your game texture have 27md its too much size you converted in compression.
I tried to delete some texture and compress some other but all that did is reduce the size of the obb. The apk actually increased like 50kb which is weird because i didnt add anything.
The textures are still probably the problem so do you know which ones affect the apk. Like is it the textures in the 3 first scenes or is it completely random.
Thanks
Answer by Koen-Matthijs · Apr 06, 2018 at 12:43 PM
Hi
When you split the build in an APK and an OBB, the following applies:
The APK contains only the executable files (dll's compiled c#, java) and all the data related to the first scene. Be careful: this is the scene with index 0 !
The OBB contains everything else (gfx / sound / object data / ...).
If you've added an empty scene 0 (which then loads the actual first scene) you should have little to no data related to that scene in your APK. The rest should be very small (+- 12 MB from the standard binaries + 20 MB from your compiled code [deducted from your output log].
If the APK remains large, you should extract it to see what's inside. An APK is acutally a ZIP file. So just give it the extension .ZIP and extract it. This will give you the manifest file, potential included resources and the compiled code as a .dex file. This way you should be able to tell what makes it so big.
Hope this helps
Kind regards
Koen Matthijs
Your answer
Follow this Question
Related Questions
My build size randomly doubled Andriod 1 Answer
Android / Split apk / obb can't load a scene 1 Answer
Android APK Expansion Files Process? 3 Answers
Size of apk too big 1 Answer
50mb limit with Unity 3.5 + Android license (not! pro) 0 Answers