API to bring up Settings->Guiardian>Desk from game as in the Horizon Workroom
I'd like player to scan their desk so I can align a panel in the game with their physical desk. In the Horizon workroom, it brings up the settings menu and ask the player to add/edit the desk and then goes back to the app and generates a table top. How to achieve the above flow in my game/app? I've only find APIs around the whole scene capture and it looks very different than what happened in the Horizon workroom
Developer section has disappeared inside Quest 2 Settings
Inside the Quest 2 (consumer edition) after update to software 35.0.0.140.341, the Developer section in Settings has suddenly disappeared. Seen from the Oculus app, the headset is still in developer mode. We have remote customers with same issue, and disabling/re-enabling developer mode is not an option for them. In Settings, I currently have Guardian disabled, and the Guardian menu is grayed out, and telling me to go to the Developer section of cause. So I know the headset is still in Developer mode. But where has it gone ?
Can't find more settings to access developer mode on Oculus app (quest 2)
I'm signed up successfully as a developer on Oculus. My headset is synced to my phone app perfectly, it says it's connected. I want to go into developer mode through the app, and every tutorial I find on how to achieve this says I have to access settings to do so. However, there are only two settings options I can find -- Account Settings, and Privacy Settings. Neither of these contains what I'm looking for. Supposedly there is a "more settings" option somewhere, but it doesn't seem to exist. Why won't it allow me to go into Developer Mode on the app?
Not able to find "more SEttings" on the mobile App // link my headset into Unity
Hello, I am connecting my headset to my PC and have been trying to move through the developer setup steps at https://developer.oculus.com/documentation/unity/unity-enable-device/ But there is no "settings" or "more settings" on the Iphone Oculus app now and therefore I cannot find the place to turn on developer mode for my headset,. Did anyone find a workaround for this? I tried reloading the app, and looked for other versions of the app, to no avail. Also, although developer mode appears in the settings list on in my headset, I am not getting the Quest 2 option in Unity >Build Settings. I am using a Nexigo cable to connect my headset to my PC, which should be ok-it's being recognized in my headset. Would much appreciate solves for both issues above.
Platform settings in Unity takes the wrong credentials
Hello there, In Unity, the Oculus Platform settings state that the credentials used are these from the Oculus application. Looks like this is not the case for me, and I'm not able to resolve the situation so far. I reinstalled the Oculus desktop app, I used that "Restart Oculus" feature from the desktop app in the Beta section, deleted the plateform settings and letting Unity regenerate these, still somehow connected to the wrong account. What am I supposed to do ? Thank you.
PACKAGE_USAGE_STATS permission not allowed on quest 2?
I am making an app that requires this permission. its a native android application so its not vr, doesnt use oculus sdk etc. The tool works fine on the regular quest, but when trying to open the activity to grant the permission on the quest 2, settings crashes. The crashing happens when clicking on the name of the app, to grant permissions for that app. crash log: 10-23 16:12:13.341 8723 8723 E AndroidRuntime: FATAL EXCEPTION: main 10-23 16:12:13.341 8723 8723 E AndroidRuntime: Process: com.android.settings, PID: 8723 10-23 16:12:13.341 8723 8723 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.widget.SearchView.isIconified()' on a null object reference 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at com.android.settings.applications.manageapplications.ManageApplications.onSaveInstanceState(ManageApplications.java:511) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at androidx.fragment.app.Fragment.performSaveInstanceState(Fragment.java:2799) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at androidx.fragment.app.FragmentManagerImpl.saveFragmentBasicState(FragmentManagerImpl.java:2276) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at androidx.fragment.app.FragmentManagerImpl.saveAllState(FragmentManagerImpl.java:2335) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at androidx.fragment.app.FragmentController.saveAllState(FragmentController.java:151) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at androidx.fragment.app.FragmentActivity.onSaveInstanceState(FragmentActivity.java:513) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at com.android.settings.SettingsActivity.onSaveInstanceState(SettingsActivity.java:472) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.Activity.performSaveInstanceState(Activity.java:2037) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.Instrumentation.callActivityOnSaveInstanceState(Instrumentation.java:1485) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.ActivityThread.callActivityOnSaveInstanceState(ActivityThread.java:5312) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.ActivityThread.callActivityOnStop(ActivityThread.java:4638) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.ActivityThread.performStopActivityInner(ActivityThread.java:4602) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.ActivityThread.handleStopActivity(ActivityThread.java:4677) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.servertransaction.StopActivityItem.execute(StopActivityItem.java:41) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2024) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7385) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492) 10-23 16:12:13.341 8723 8723 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930) Is this because this permission is blocked on the quest 2 or is this a possible bug?
