I figured out how to fix the issue where packaged new projects based on Top-Down or Sidescroller templates end up creating an APK of 18mbs and an OBB of 2.1gb - i unchecked the “include starter content” in the new project and when packaged for android the sizes are much like Swing Ninja - 17.1mb for APK and 78mb for the OBB (expansion) file.
My problem is that I’m trying to deploy a “hello, world” kind of project - I make a new project based on a topdown or sidescroller template, i try it in the editor and it kinda works, I package it for android and end up with 100mb, and then I deploy to my Samsung Nexus device - run the project and it silently crashes on startup. I just see a black screen that vanishes without the ANR dialog after a few moments. I don’t get to see the “blank game” so to speak, or test it’s responsiveness like I can do in the Editor.
Since I managed to get pretty much all examples from the marketplace running on this device, I wonder what’s going wrong here now. Do new projects simply not work straight out-of-the-box when packaged and deployed on Android?
If they do work, which I believe they do, what am I doing wrong in this series of steps? What additional work is required to make a project compatible to work on Android?
That’s not very far from “not working”, is it?
I don’t understand why the still-new project works in UE4’s simulator, yet doesn’t show up at all when installed on the device. I too have gotten empty irresponsive black screens, without ANR dialogs.
So the question remains - is there anything I can do to fix that or should I just wait for 4.2 to come out and hope it’ll be resolved?
Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes. If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, could you please submit a new report for it.
