Skip to main content
Shayd0ce
Participant
April 27, 2016

[Solved][Gear VR] Thread priority security exception with 4.11.2

Hello people, I will explain:

this problem is driving me crazy, I can deploy and run perfectly an apk to GearVR Galaxy S6 with Android 5.1 and UE 4.10.4, ok here.

The problem comes when I try to run an apk to GearVR Galaxy S6 with Android 5.1 or 6.0 and ---> UE 4.11.2 <---, I have always (with UE same settings) Thread priority security exception or Downloading OBB error (when I try other settings)

I have UE 4.10.4 installed in the default directory C:\Program Files\...
I have UE 4.11.2 installed in the default directory C:\Program Files (x86)\... (keep in mind why the hell is installed in x86?)
I have copied in both versions the OSIG in the correct directories

So, I can run my apk with UE 4.10.4 but I can't run the same apk with UE 4.11.2 in the GearVR Galaxy S6

I need to solve this problem because the phone has now Android 6.0 and the apk build with UE 4.10.4 show all materials in black, is for that I need run the apk with UE 4.11.2 but always get Thread priority security exception, WTF.

Anybody known this problem and can help me to solve it?

Thank you so much for your attention.
This topic has been closed for replies.

10 replies

artyom17
Up and Coming
April 28, 2016
Check the state of the 'Project Settings' -> 'Platform' -> 'Android' -> 'Advanced APK Packaging' -> 'Remove Oculus signature files'. Uncheck it.
Epic fixed that checkbox in 4.11.2, previously it worked by quite opposite way (therefore, most likely it is checked right now).
Shayd0ceAuthor
Participant
April 28, 2016

artyom17 said:

Check the state of the 'Project Settings' -> 'Platform' -> 'Android' -> 'Advanced APK Packaging' -> 'Remove Oculus signature files'. Uncheck it.
Epic fixed that checkbox in 4.11.2, previously it worked by quite opposite way (therefore, most likely it is checked right now).


I'll try and report ASAP, thank you artyom17.
motorsep
Inspiring
April 28, 2016
Why do you use OBB and not a single apk ?
Shayd0ceAuthor
Participant
April 28, 2016

motorsep said:

Why do you use OBB and not a single apk ?


Hi motorsep,
the OBB was only for test with 4.11.2, in UE 4.10.4 runs perfectly with and without OBB ("game inside apk")

We can retry today, I will post the results soon, thank you!
Shayd0ceAuthor
Participant
April 29, 2016

artyom17 said:

Check the state of the 'Project Settings' -> 'Platform' -> 'Android' -> 'Advanced APK Packaging' -> 'Remove Oculus signature files'. Uncheck it.
Epic fixed that checkbox in 4.11.2, previously it worked by quite opposite way (therefore, most likely it is checked right now).


Hi artyom17, we has tryed Checked and Unchecked and still showing the same message, Thread priority security exception.

We don't know what to do more :/ 
artyom17
Up and Coming
April 30, 2016
Make sure the proper osig file is in Engine\Build\Android\Java\assets directory. I am going to try the 4.11.2 as well to make sure it really works.
You also may make sure that the osig file is in .apk by opening the .apk as a .zip file (which it is) and checking the 'assets' directory.
artyom17
Up and Coming
April 30, 2016
Yeah. 4.11.2 works for me (with the 'remove osig file' unchecked).
Shayd0ceAuthor
Participant
April 30, 2016
Wow, all files are in the correct directory and the OSIG is in .apk confirmed, I will try to reinstall UE 4.11.2 because is a very weird situation, I'll report soon my advances, thank you artyom17 ;)
Shayd0ceAuthor
Participant
May 7, 2016

artyom17 said:

Yeah. 4.11.2 works for me (with the 'remove osig file' unchecked).


Hi artyom17, can you confirm that you have the same settings?

This is the config that works for us with UE 4.10.4 but can't work with 4.11.2, the screens are in 4.11.2

Thank you for your feedback.


Shayd0ceAuthor
Participant
May 13, 2016
OK, i found that "Mobile HDR" was marked it by default, I uncheck that and the materials are showing normal now in UE 4.11.2, I tested it on a new Galaxy S7 and didn't get the "Security Exception error" (I have the OSIG obiously)

Is solved.
Terms & ConditionsAccessibility statement