Forum Discussion
Solved
Quest 3 ADB permissions
Hello!
I recently upgraded from Quest 2 to Quest 3.
But my MQDH Custom Buttons to grab logs & bugreport don't work anymore.
I don't seem to have any permissions on the headset via `adb`
I can see the device with `adb devices`;
I can shell into the device with `adb shell`
But whenever I tried to pull a file or use `cat` I get a permission denied error on all the files in my
sdcard/Android/ ... folders.
Any advice would be much appreciated!
Joel
Joel, this is the exact same issue we are having. The fix ended up being an engine change to how file permissions gets applied when the Unreal application makes new files on device. The change was suggested in this post by Norman3D: https://developer.oculus.com/first-access/forums/quest/posts/7188174094527160/
Basically this is the engine change: https://i.imgur.com/dfznYEl.png
Apparently this is only an issue in the Unreal 4 flavor of the Oculus Unreal engine and is fixed in the Unreal 5 version.
8 Replies
🛜Wi-fi
I had the same problem and this post was the solution:
Killing the server with
adb kill-server
and starting one as sudo with
sudo adb start-server
made the device go from "no permissions" to "unauthorized", and I was able to authorize the system inside the headset.
Hi Joel, I am experiencing the same issue. The device is detected but failed to receive any adb commands. Have you resolved it?
Hey Joel. We've been having the same issue. I created a similar post for the same issue here: https://developer.oculus.com/first-access/forums/quest/posts/7462453453765888/
I should mention I am working on an Unreal Engine project using the Oculus 4.27 branch
Joel, this is the exact same issue we are having. The fix ended up being an engine change to how file permissions gets applied when the Unreal application makes new files on device. The change was suggested in this post by Norman3D: https://developer.oculus.com/first-access/forums/quest/posts/7188174094527160/
Basically this is the engine change: https://i.imgur.com/dfznYEl.png
Apparently this is only an issue in the Unreal 4 flavor of the Oculus Unreal engine and is fixed in the Unreal 5 version.
💝แรงใจ
