VR build is not displayed when headset is in standby upon initial launch

Workaround:
Download the Meta Quest Developer hub which allows you to disable the Proximity Sensor. The app is available on Windows (https://developers.meta.com/horizon/downloads/package/oculus-developer-hub-win) and Mac (https://developers.meta.com/horizon/downloads/package/oculus-developer-hub-mac)

Reproduction steps:

1. Create new VR Template project
2. Build the Player for Android
3. Upload the .apk to Meta Quest device (e.g via SideQuest)
4. Launch the .apk from ADB using command: “adb shell am start -n com.unity.template.vr/com.unity3d.player.UnityPlayerGameActivity“ (Make sure that the VR headset is not currently used)
5. Put on the headset
6. Observe the result

Expected result: After putting on the headset, the application is loaded and shown to the user
Actual result: After putting on the headset, the application is not shown in the headset

Reproducible in: 2022.3.1f1, 2022.3.60f1, 6000.0.45f1 6000.1.0b13, 6000.2.0a8
Cannot test with: 2022.1.X (build failure, unsolvable errors)

Reproducible on: Windows 11

Using  "com.unity.xr.openxr": "1.14.1",
Not reproducible on: No other environments tested

Reproducible on these devices:
Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12
(User reported) - Meta Quest Pro, CPU: Snapdragon XR2+, GPU: Adreno 650

Notes:

• If the issue does not reproduce the first time, try launching the Player again, or re-upload the .apk again
• The app can be displayed by repeatedly putting the headset on and taking it off. Then, press the 'Home' button on the right controller to open the OS menu and click the 'Resume' button.
• After some tries, it seems to reproduce via Build & Run as well. Although, it seems that the issue is more prone to reproduce on the first try on any latest active stream version, specifically 6000.0.45f1 or 6000.1.0b13