Chapter 3 can't make the session enter into ready mode in Meta Quest3

Open

#152 opened on Sep 11, 2025 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: cpp
Domain: ar-vr-xr

Research direction

Start with the Chapter 3 tutorial and trace the session-state handling around RenderFrame, especially why m_sessionState remains XR_SESSION_STATE_IDLE. Reproduce the issue on a Meta Quest 3 using the reported runtime details, then confirm that the session reaches ready mode and RenderFrame can be called.

Written by the indexing model from the issue text.

Description

synced to gitlab

My debug device information is follow:

ro.product.system_ext.device]: [eureka]
[ro.product.system_ext.manufacturer]: [Oculus]
[ro.product.system_ext.model]: [Quest 3]
[ro.product.system_ext.name]: [eureka]
[ro.product.vendor.brand]: [oculus]
[ro.product.vendor.device]: [eureka]
[ro.product.vendor.manufacturer]: [Oculus]
[ro.product.vendor.model]: [Quest 3]
[ro.product.vendor.name]: [eureka]
[ro.product.vendor_dlkm.brand]: [oculus]
[ro.product.vendor_dlkm.device]: [eureka]
[ro.product.vendor_dlkm.manufacturer]: [Oculus]

version information:

ro.vendor.build.version.sdk]: [34]
[ro.vendor_dlkm.build.version.incremental]: [51154110164300520]
[ro.vendor_dlkm.build.version.release]: [14]
[ro.vendor_dlkm.build.version.release_or_codename]: [14]
[ro.vendor_dlkm.build.version.sdk]: [34]
[ro.vndk.version]: [34]
[ro.vros.build.version]: [79]

09-11 17:40:24.883 27242 27863 D openxr_tutorial: OpenXR Runtime: Oculus - 79.1289.0

I try to understand openXR and follow this Turotials. When I try to run Chaper3, it could not enter the call the RenderFrame. The m_sessionState is always XR_SESSION_STATE_IDLE. How can I solve this issue. Appreciate for any comments.

Dominant language: C++
Stars: 136
Forks: 27
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues