I haven’t done much Android work in the past, mostly proof of concept work. I had some projects from awhile back (4.13, 4.14 I believe) that I had saved in the event I wanted to go back and build off of them.
Recently a friend of mine had asked to see one of the projects, so I updated it to my current version of 4.18 and went to launch it. Using the old method of just clicking on the Launch button then clicking on my device (Android) there is the chirp, the little popup screen in the bottom, then nothing. The engine freezes and I need to restart it. The project still plays fine in the editor.
I later found out that some people were having success going to Launch->Project Launcher->Then Launch on the android there. This works, and the project goes through the standard packaging normally.
In the past I had used an old Galaxy S3 and my then-current Galaxy S5 to test out the project. I recall launching taking maybe 5 minutes, tops, with the splash screen throughout the deployment process followed by the game starting automatically.
However, though the project is deployed to my device (I get the splash screen and can see the package on my home screen) the project doesn’t launch. On the log file it just repeats the following:
Waiting for server to start…
Waiting for server to start…
Waiting for server to start…
Waiting for server to start…
The package is on the phone, but it won’t start.
The same error happens on my old Galaxy S3 which I am 100% positive had not been touched since I last used it for Android deploying (one of the old deployments is still on there and works!). I tried again using a generic Top-Down project, and still the same result.
Anyone got any suggestions? I’ve noticed that the Android deployment settings have changed since 4.14 so I am pretty sure I made the required adjustments:
APKPackaging->Platform Files are writeable
Android SDK->Folders are correctly assigned. The ndk is r12b, ant is 1.8.2, java is 1.8.0_77
SDK API Level: matchndk
NDK API Level: latest
I have the default test map set up to be included in the package.
I also noticed that there was a new setting about enabling Gradle instead of Ant. I messed around with that, but both cases result in the same Waiting for Server… loop.
If anyone has gotten this issue and found a way around it any help would be much appreciated. Attached is the log file for launching if anyone can make anything of it.link text