Differences

This shows you the differences between two versions of the page.

--- devices:oculus_quest_2 [2024/07/01 08:12] – external edit 127.0.0.1
+++ devices:oculus_quest_2 [2025/09/11 06:43] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== Device Set-up ======
+===== Factory Reset =====
+  * https://www.meta.com/help/quest/software_update/
+  "%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge_proxy.exe" --app="https://www.meta.com/help/quest/software_update/"
+===== MQDH =====
+  * https://developers.meta.com/horizon/downloads/package/oculus-developer-hub-win/
+  * Last tested: ''Meta-Quest-Developer-Hub-5.5.0.exe.zip''
+===== Versions =====
+  * 2025/05/04
+==== System Version ====
+****
+  51540840076700150
+==== Firmware Version ====
+****
+.0.0.595.312
+==== Firmware Build ID ====
+****
+  UP1A.231005.007.A1
+==== Firmware Build Date ====
+****
+  Wed Apr 23 18:16:44 PDT 2025
 ====== ADB Commands ======
@@ Line 72: / Line 113: @@
 ====== Notes ======
-  * :!: Developer mode needs manually re-enabled from Oculus app on mobile after Factory Reset ((any issues with pairing will prevent enabling Dev mode; [[https://www.reddit.com/r/OculusQuest/comments/1bkixqx/adb_not_finding_quest_3/kw0q2tj/|possible workaround]]))
+  * :!: Developer mode needs manually re-enabled from Oculus/Meta app (mobile or MQDH) after Factory Reset ((any issues with pairing will prevent enabling Dev mode; [[https://www.reddit.com/r/OculusQuest/comments/1bkixqx/adb_not_finding_quest_3/kw0q2tj/|possible workaround]]))
   * Hold PWR + Vol- to access bootloader menu to perform Factory Reset on-device
   * ''%localappdata%\Oculus'' contains Logs
@@ Line 194: / Line 235: @@
   * Last updated: 2022/07/11
-  * :!: TODO
-  * Latency at H.264 is 4ms at 1080p@144, 6ms at 1440p@144, and 10ms at 4K@30 ((HEVC tests didn't run on 22.5.2))
+  * Latency at H.264 is 4ms at 1080p@144, 6ms at 1440p@144, and 10ms at 4K@30
   * It looks ideal to either use 120Hz, or limit encode resolution for lower refresh rates to ~2560 in order to avoid the 4ms spike