cancel
Showing results for 
Search instead for 
Did you mean: 

S7 Network Error Occured

chrisvarnz
Explorer
Hi guys,

I am attempting to run my GearVR application which I have deployed to a stock S7 and I get the first-run GearVR setup thing, which refuses to install with a network error. The network is definitely working, I can browse and update apps etc. Is this a known issue? Attached some screenshots.bllibs0avzqv.jpg2iduavg0c4cr.png

Deets:
Model: Galaxy S7 SM-G930F
S/N: R58HB0T6WRJ
Relevant logcat output:
05-31 16:03:01.404 21182 22637 D VRSetupWizardLib/CheckPackagesInfoTransaction: Attempt to read from null array
05-31 16:03:01.414 21182 21182 D VRSetupWizardStub: [Error] EVENT_ERROR_OCCURRED
05-31 16:03:01.414 21182 21182 D VRSetupWizardLib/ThreadTransaction: [Working] stopAllTransaction()
05-31 16:03:01.414 21182 21182 D VRSetupWizardLib/ThreadTransaction: [Working] stopProgressTimer()
05-31 16:03:01.414 21182 21182 D VRSetupWizardLib/ThreadTransaction: [Working] stopCheckCountryCheckTransaction()
05-31 16:03:01.414 21182 21182 D VRSetupWizardLib/MultiTransactionStub: [Working] interrupt() isCanceled : false
05-31 16:03:01.414 21182 21182 D VRSetupWizardLib/ThreadTransaction: [Working] stopDownloadTransaction()
05-31 16:03:01.414 21182 21182 D VRSetupWizardLib/ThreadTransaction: [Working] stopProgressTimer()
05-31 16:03:01.414 21182 21182 D VRSetupWizardLib/ThreadTransaction: [Working] stopInstallTransaction()
2 REPLIES 2

chrisvarnz
Explorer
Still having this error. No amount of reflashing, deleting the cache for various Oculus / Facebook apps etc has any effect. We have this issue on both of our Exynos S7's, bit not on any other devices (although some of the other devices have other show-stopping issues). If someone at Oculus could share any insight it would be greatly appreciated.

Currently downloading a new firmware from SamMobile to see if that fixes it https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXU1DQD7/131262/

chrisvarnz
Explorer
Flashing the new firmware and then performing another factory reset / cache wipe resolved the issue for me.