Unity Build for Gear VR is not working anymore...

So about 2 months ago me and a teacher followed a tutorial named "Creating a Gear VR app in Unity Free" on YouTube. We got it working, and I was able to build a Unity project and put it on the Samsung Galaxy S7 to work on the Gear VR.
So...a week after I got it working on my main project, I built another small project, copied the necessary files over to the new Unity project folders; 'project settings files (17 files in total)', and the 'oculussig' (within assets>plugins>android>assets. And again it worked, I built it on the phone and had it working on the Gear VR. Unity was able to locate where the SDK file was stored on my PC aswell.

Now the problem. I did the exact same method, making a new project for my 3rd year of University, and copying over the correct files. All of a sudden it wont build on my phone. It gets built as an .apk, but it doesnt even ask me to plug in the phone when its being built (something it did a few months ago). I updated Android Studio, Unity is fine, triple checked the settings, changed the 'product and company name', and nothing seems to be fixing it. I even drag the .apk file onto the phone but nothing...

I have spend this whole day ripping my hair out, trying to find a solution but I cant. Which is why I plead for help on here lol. Does anyone know why I cant seem to build correctly.

P.S I even tried building the old Unity files that were working before, trying to build them again today with different names but nothing. I have no clue, was something changed or updated with Unity or Samsung? Is it easy to fix?

.

 

Yes its building the .apk file. And its the same phone.

why would I need a new oculussigfile? I opened command window 'cmd.exe', pasted " adb devices " (no quotes), but get a " Windows Command Line: 'not recognized as an internal or external command, operable program or batch file"

Also, how do I check android logcat output ? I tried looking on google but nothing

Edit: I downloaded my oculus signature file by entering my Device ID on OSG generator, but its the exact same file number as before

 

So what does entering "cd C:\Users\<insert username here>\AppData\Local\Android\sdk\platform-tools\" in the cmd path actually do? A quick video mentioned something about moving the file or something...I dont feel comfortable tampering with files and moving them etc? What am I trying to do exactly?

 

Ok well I shall try it with my teacher tommorow at University if I get the chance, thanks for the help so far. By the way, have you come across my situation before? Is it a one off strange dilema? Why did it do this all of a sudden?

 

Hello, so the problem has been fixed...sort of..?

So after Unity built the .apk I had to manually drag that file inside the phones folder(when I connected the phone to my PC). This is what I had been doing before I raised the issue here, but for some reason it was not placing it on the phones desktop main page, like it did for the other ones months ago.

For some strange reason, the .apk files that were being built from Unity were on the phone, however they were being placed inside 'MyFiles>Device Storage' and I had to scroll down to find the .apk file.
Then I had to click the file, and a message popped up saying 'install blocked'. So I had to click settings, then switch on 'Unknown sources', and install it. Then it was placed on the phones front page.

I now know why it was being placed in the 'MyFiles' section...because I dragged it there after it was built. However that does not explain why it did not get placed on the front page in the first place, and why I had to go inside 'MyFiles>DeviceStorage' and manually install it like that.

Do you know why the install was blocked? It never used to do this, I dont want to have to manually do that all the time. I used to build it and it used to replace the .apk on the home screen. Also when it was being built, I didnt even have to pllug my phone in, which is what it used to ask!

 

I'm having similar problems with Unity 5.5.3f. Have done build for Note 4 running Android 5.1.1, tried on galaxy S6 and S7 with same results. App builds and runs on device, but without split screen/dual camera and doesn't ask to be placed into gear VR device? Not sure what to do/try next.

 

Ended up installing Unity 5.6

 

@joejo I am currently using Unity 2017.1 and I am having a similar issue regarding the app icon not being displayed after installation. I successfully build the apk file, load it onto my Galaxy S8, open it in MyFiles and install it successfully. Then it gives me two options "Done" or " Open". If I press open, the app will open fine, but if I hit done, the app icon is nowhere to be found... Any ideas what is going on? I do get an error after auto installing to the device when I ctrl+b with my phone connected to the computer which says "No activity in the manifest with action MAIN and category LAUNCHER. Try launching the application manually on the device." Any idea?

 

VirtualJosh, does that phone have an "Applications" app separate from the Launcher? It may still be listed there.

However I am grappling with the very same issue although I have been using 5.5.1p4. OTOH the Unity VR sample app worked for me... once... so you might try that.

I'm really confused as to what I am doing wrong. (My app works fine in the editor via "split".) I have created an osig file and put it in Plugins/Android/assets. VR support is set with Oculus selected. When my app runs on the phone, even if Gear VR developer is set on, trying to load oculus [even though I thought it should be enabled on start] doesn't succeed.