User Tools

Site Tools


devices:oculus_quest_2

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
devices:oculus_quest_2 [2025/05/04 08:25] Sean Rhonedevices:oculus_quest_2 [2025/05/16 21:39] (current) – external edit 127.0.0.1
Line 13: Line 13:
  
 ===== Versions ===== ===== Versions =====
 +
 +  * 2025/05/04
  
 ==== System Version ==== ==== System Version ====
Line 111: Line 113:
 ====== Notes ====== ====== 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   * Hold PWR + Vol- to access bootloader menu to perform Factory Reset on-device
   * ''%localappdata%\Oculus'' contains Logs   * ''%localappdata%\Oculus'' contains Logs
Line 233: Line 235:
  
   * Last updated: 2022/07/11   * 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   * It looks ideal to either use 120Hz, or limit encode resolution for lower refresh rates to ~2560 in order to avoid the 4ms spike
  
C:/www/wiki/data/attic/devices/oculus_quest_2.1746361547.txt.gz · Last modified: by Sean Rhone