Couln’t run any android project since 4.8. All result with black screen. So I thought I give it a shot with newest 4.9 Preview 3 Build straight from launcher.
In this case I tested with a 3rd person blueprint project. According to the logs the app seams to start but the screen stays black.
The only interesting bug line was the one with unimplemented OpenGL ES call.
I first tried with old tadp coming with the engine, then tried with AndroidWorks R1. Same result.
I know this OpenGl error sometimes even appears when game works fine, so I dont know if this the reason. Until 4.7 S4 was supported. Also with latest KitKat. S4’s Adreno 320 was in the DeviceProfiles until 4.7, now it is just under mid range devices. Maybe some problem there?
Didnt try with latest source build yet…
Logs from AndroidWorks R1 try are attached
Does 3rd Person template run on your S4 device with AndroidWorks on PreviewBuild 3 from launcher?
I was to quick about marking this solved. I am able to start a empty project with 4.9 from Github, but I am unable to make my project work migrated from 4.8. After switching branches, recompiling engines, redirecting blueprints, copying code line by line I just cant find out where the problem is.
The app always starts on Galaxy S4 Lollipop and then stops at the line:
D/UE4 (18320): ***** RequestedContentScaleFactor different -1580012432 != -1610612736, not using res cache
It still responds to the menu button so it didn’t crash.
I really tried solving it myself with the new Nsight Tegra Debugger both in the R1 and R2 Version, and both with api 19 and 21.
But it seams S4 is not supported for R1 and gives “nvidia android Uknown ELF architecture parama arch” when trying to debug in VS. And with R2: “Cannot debug on this device, because run-as is not working correctly”. I guess 2nd is because R2 is not integrated on this UE Branch.
My guess so far was that somehow bDontLoadBlueprintOutsideEditor wasn’t working correctly on Android, because that was one of the reason the Win64 build didn’t work before with parented blueprints.
I also attached again the device log, but I can’t see anything different there than from the device log when the empty project starts successfully on the device.
I marking this solved as Galaxy S4 is currently unsupported in AndroidWorks R1. I think the problem was a false “Active Redirection” in the DefaultEngine.ini when updating the project.