search

Igalia / wolvic

A fast and secure browser for standalone virtual-reality and augmented-reality headsets.
https://wolvic.org
Mozilla Public License 2.0
801 stars 101 forks source link

wolvic 1.5 @huawei vr glass， controller cannot work #1053

Closed dingsing2021 closed 1 year ago

dingsing2021 commented 1 year ago

Configuration

Wolvic version: 1.5 Wolvic build ID:

Hardware: huawei vr glass

Steps to Reproduce

1. 2. 3.

Current Behavior

controller cannot work.

Expected Behavior

Possible Solution

Context

xrStringToPath error.

Error Logs and Stack Traces

``` ```
svillar commented 1 year ago

Which error do you get?

dingsing2021 commented 1 year ago

xrStringToPath error. it seems that v1.5 do not get the huawei controller profile. but v1.4 is ok. maybe you can check the difference between v1.4 and v1.5.

svillar commented 1 year ago

xrStringToPath error. it seems that v1.5 do not get the huawei controller profile. but v1.4 is ok. maybe you can check the difference between v1.4 and v1.5.

3DoF, 6DoF or both?

dingsing2021 commented 1 year ago

xrStringToPath error. it seems that v1.5 do not get the huawei controller profile. but v1.4 is ok. maybe you can check the difference between v1.4 and v1.5.

3DoF, 6DoF or both?

3dof only.

svillar commented 1 year ago

Also which package are you using? The one from wolvic.com/dl ? The one in the overseas store?

dingsing2021 commented 1 year ago

Also which package are you using? The one from wolvic.com/dl ? The one in the overseas store?

Wolvic-hvr-arm64-world-gecko-generic-release.apk 97.4 MB 2 weeks ago

svillar commented 1 year ago

Hmm I've just tried that package and everything looks normal.

https://github.com/Igalia/wolvic/assets/1826122/b5c779e8-f9a5-4512-8ed4-38f5508d53fd

Are you trying in different hardware other than the Huawei glasses? Because controllers won't be shown if the device is different. For example what does this command adb shell getprop ro.product.vendor.model output in the console?

svillar commented 1 year ago

Are you trying in different hardware other than the Huawei glasses? Because controllers won't be shown if the device is different. For example what does this command adb shell getprop ro.product.vendor.model output in the console?

Hmm I think I've just found the reason. We're using a Huawei Mate 40 for testing which reports kirin9000 as vendor model. However the Huawei glasses are ment to be used with different phones so the filtering we're doing is not correct. I'll upload a patch for that.

@dingsing2021 Could you confirm that you are testing it in a different phone model?

matlu commented 1 year ago

Yes likely testing with other model. The supported models are listed here: https://www.vmall.com/product/comdetail/index.html?prdId=10086373799016&sbomCode=3102170004302 image

Let's see if we can get a list.

@svillar

dingsing2021 commented 1 year ago

Hmm I've just tried that package and everything looks normal.

output.mp4 Are you trying in different hardware other than the Huawei glasses? Because controllers won't be shown if the device is different. For example what does this command adb shell getprop ro.product.vendor.model output in the console?

hi svillar, this bug happend in 3dof mode. i think you should try the 3dof controller.

dingsing2021 commented 1 year ago

wolvic1.4 3dof mode， /interaction_profiles/huawei/controller , it is correct. wolvic1.5 3dof mode，it runs in /interaction_profiles/khr/simple_controller，it is not correct profile for huawei vr glass.

so why it happpend in wolvic1.5 , here is some log for reference.

10-07 16:16:30.720 17447 17626 I HxrFunctions: [@SDK]HxrFunctions.cpp:hxr_xrEnumerateViewConfigurationViews: In hxr_xrEnumerateViewConfigurationViews 10-07 16:16:30.720 17447 17626 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 10-07 16:16:30.720 17447 17626 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 1 10-07 16:16:30.720 17447 17626 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 1_1 10-07 16:16:30.720 17447 17626 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 1_2 10-07 16:16:30.720 17447 17626 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 2 10-07 16:16:30.720 17447 17626 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 3 10-07 16:16:30.720 17447 17626 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 4 10-07 16:16:30.720 17447 17626 I VRB : OpenXR Available color formats: 1 10-07 16:16:30.720 17447 17626 E VRB : OpenXR systemName: Haliday: G3HMD by Huawei 10-07 16:16:30.720 17447 17626 E HxrInstance: [@SDK]HxrInstance.cpp:hxrSuggestInteractionProfileBindings: non-supported profile /interaction_profiles/khr/simple_controller 10-07 16:16:30.720 17447 17626 E VRB : openxr xrSuggestInteractionProfileBindings error with '/interaction_profiles/khr/simple_controller': XR_ERROR_PATH_UNSUPPORTED 10-07 16:16:30.720 17447 17626 I HxrInstance: [@SDK]HxrInstance.cpp:hxrSuggestInteractionProfileBindings: Current attached profile: /interaction_profiles/huawei/controller 10-07 16:16:30.720 1663 2714 I HwPCUtils#HwPCManagerService: onDisplayAdded, displayId:27

10-07 15:28:36.659 4702 5043 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 2 10-07 15:28:36.659 4702 5043 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 3 10-07 15:28:36.659 4702 5043 I HxrInstance: [@SDK]HxrInstance.cpp:getSystemByID: In getSystem by ID 4 10-07 15:28:36.659 5359 5417 I Ids_AbsOldArchController: environment is master 10-07 15:28:36.659 4702 5043 I VRB : OpenXR Available color formats: 1 10-07 15:28:36.660 1663 1857 I HwDisplayPolicyEx: initialNavigationSize navBarHeight:122 navBarHeightMin:0 configuration:{1.0 ?mcc?mnc [zhCN#Hans] ldltr sw5dp w5dp h5dp 480dpi smll hdr widecg port -touch -keyb/v/h -nav/h winConfig={ mBounds=Rect(0, 0 - 1152, 2376) mAppBounds=Rect(0, 120 - 1152, 2376) mMaxBounds=Rect(0, 0 - 1152, 2376) mWindowingMode=fullscreen mDisplayWindowingMode=fullscreen mActivityType=undefined mAlwaysOnTop=undefined mRotation=ROTATION0 mPopOverMode=0} suim:1 extflag:8 s.17 fontWeightAdjustment=0} 10-07 15:28:36.660 4702 5043 E VRB : OpenXR systemName: Haliday: G3HMD by Huawei 10-07 15:28:36.660 1663 1857 I HwDisplayPolicyEx: screen width:16; mIsLandscape:false 10-07 15:28:36.660 4702 5043 E HxrInstance: [@SDK]HxrInstance.cpp:hxrSuggestInteractionProfileBindings: non-supported profile /interaction_profiles/khr/simplecontroller _10-07 15:28:36.660 4702 5043 E VRB : openxr xrSuggestInteractionProfileBindings error with '/interaction_profiles/khr/simple_controller': XR_ERROR_PATHUNSUPPORTED 10-07 15:28:36.660 4702 5043 W HxrSession: [@SDK]HxrSession.cpp:hxrAttachSessionActionSets: left profile XR_ERROR_PATH_UNSUPPORTED 10-07 15:28:36.660 4702 5043 E VRB : XrResult failure [XR_ERROR_PATH_UNSUPPORTED] /home/felipe/Igalia/wolvic/wolvic/app/src/openxr/cpp/OpenXRInput.cpp: 61 10-07 15:28:36.660 1663 1857 D WindowManager: initDisplayRoundCorner screenWidth 16 screenHeight 16 mRoundCornerSafeInsets[0]= Rect(1, 1 - 1, 1) mRoundCornerSafeInsets[1]= Rect(1, 1 - 1, 1) mRoundCornerSafeInsets[2]= Rect(1, 1 - 1, 1) mRoundCornerSafeInsets[3]= Rect(1, 1 - 1, 1) 10-07 15:28:36.660 4702 5043 I VRB : OpenXR XrEventDataSessionStateChanged: state XR_SESSION_STATE_UNKNOWN->XR_SESSION_STATE_IDLE session=0x0 time=0 10-07 15:28:36.660 4702 5043 I VRB : OpenXR XrEventDataSessionStateChanged: state XR_SESSION_STATE_IDLE->XR_SESSION_STATE_READY session=0x0 time=0 10-07 15:28:36.660 4702 5043 I VRB : XR_SESSION_STATE_READY 10-07 15:28:36.660 4702 5043 I HxrFunctions: [@SDK]HxrFunctions.cpp:hxr_xrBeginSession: In xrBeginSession 10-07 15:28:36.660 4702 5043 I HxrSession: [@SDK]HxrSession.cpp:beginSession: In beginSession

dingsing2021 commented 1 year ago

Yes likely testing with other model. The supported models are listed here: https://www.vmall.com/product/comdetail/index.html?prdId=10086373799016&sbomCode=3102170004302 image

Let's see if we can get a list.

@svillar

@ mats, svillar , this is the list of huawei vision glass , not huawei vr glass. and wolvic do not need consider the phone model, because huwei vr sdk and runtime have do the work, if the phone could not support vr glass, when you connect it to the phone, the vr glass cloud not start.

matlu commented 1 year ago

Yes likely testing with other model. The supported models are listed here: https://www.vmall.com/product/comdetail/index.html?prdId=10086373799016&sbomCode=3102170004302 image Let's see if we can get a list. @svillar

@ mats, svillar , this is the list of huawei vision glass , not huawei vr glass. and wolvic do not need consider the phone model, because huwei vr sdk and runtime have do the work, if the phone could not support vr glass, when you connect it to the phone, the vr glass cloud not start.

@dingsing2021 You are correct. I searched for Huawei VR Glass but Vmall gave me the Vision Glass :-( As discussed I suggest we have list of supported decvices added to the FAQ. It was available on the Vmall page but that page is now gone. But for the Wolvic App I suggest to allow all devices as proposed in: https://github.com/Igalia/wolvic/pull/1056 @svillar

matlu commented 1 year ago

Here is the complete list of supported devices (For the FAQ): https://consumer.huawei.com/cn/support/content/zh-cn00757272/

@svillar