I'm trying to get some of the basic examples included with the SDK to build and run on the Gear. However, every single example I try to build seems to crash on the splash screen. I've tried a few examples in the SDK (and copying over the ProjectSettings) as well as creating one from scratch and following the setting guidelines in the Unity Integration doc. I've tried a bunch of things and am pretty stumped, so I would appreciate any help I could get here. I'm pretty sure my signature is set up correctly (Plugins/Android/assets) as I couldn't get to the splash screen until I had it in place.
I'm using Unity Pro, 4.5.5p5 I do NOT have Android Pro, but my understanding is that it is supposed to work (perhaps without some optimizations like multithreading and profiler access?).
I missed that step the first time (it's only in the dev environment setup guide, not the Unity guide) and had the same problem with even the example projects crashing on the splash screen.
Yeah I did that 😞 I had a different crash when I didn't have it in there so I'm pretty sure it is something different. I'm using Sprint version of the Note 4.
any luck with this? im seeing something similar. In my case it launches but to a black screen. If I hit back I see the scene for a split second. The Note4 says it stopped. Unity4.6 Pro
Nope.. no luck yet. I will post if I get something working, and please if anyone with Sprint is able to run a custom build please let everyone know here.
My understanding is that it does require Android Pro, at least in Unity 4.X. I'd suggest requesting an Android Pro trial license directly from Unity; they are usually pretty generous about giving people a chance to test it out and see if it's worth it for them.
I made a new build, and some stranger behavior happened. The splash screen appeared, and stayed there for about 30 seconds. Then, I could hear that the Unity Scene loaded up.
However, I couldn't see anything. The splash screen never disappeared!
When I pressed the back button, the "BlockSplode has closed unexpectedly" filled my screen once again.
I then downloaded the patch for 4.5.5p1, made a build, and the same behavior was happening.