Closed sujay-digilens closed 5 months ago
The developer workflow is for building Gecko not Chromium. AFAIK we haven't published any docs about how to build the Chromium port (we should! but we haven't had time). Also you mention that you're using Gecko 124. The current version of Wolvic is still using 121 so we cannot offer any stability promise with that newer version. Last but not least there is no trace of the crash so very little we could do with this report.
Got it.
Let's say there's a prebuilt binary for the Chromium available, is there a way in the project to point to the Chromium build?
Yes you need to add chromium_aar=PATH_TO_DIR_WITH_CHROMIUM_AARS
to the local.properties
file
Any tips on how to build/where to find these AARs?
I'm going to close this because it has nothing to do with Chromium. The logcat shows a execution of Wolvic with Gecko using the NoAPI backend. That backend is meant for testing on regular phones, as the name suggests it does not use any VR SDK so it is not able to access controllers, it is not capable of hand tracking either, nor generating stereo views.
The problem seems to be in the codecs of the platform you're using. There is a lot of errors in OMX-VDEC-1080P
component in the logs. Then at some point the VP9 decoder is selected Found target decoder OMX.qcom.video.decoder.vp9
but soon after that Wolvic dies. I suspect that your platform does not really support VP9 decoding. Please reopen if this analysis is incorrect and/or inaccurate.
Thanks for your analysis, Sergio.
I will look into that.
Sujay Nayak Anil Software Engineer
@.***
From: Sergio @.> Sent: Tuesday, June 4, 2024 12:51 AM To: Igalia/wolvic @.> Cc: Sujay Anil @.>; Author @.> Subject: Re: [Igalia/wolvic] App crashes when trying to a play video on any website with v0.9 Chromium release (Issue #1414)
I'm going to close this because it has nothing to do with Chromium. The logcat shows a execution of Wolvic with Gecko using the NoAPI backend. That backend is meant for testing on regular phones, as the name suggests it does not use any VR SDK so it is not able to access controllers, it is not capable of hand tracking either, nor generating stereo views.
The problem seems to be in the codecs of the platform you're using. There is a lot of errors in OMX-VDEC-1080P component in the logs. Then at some point the VP9 decoder is selected Found target decoder OMX.qcom.video.decoder.vp9 but soon after that Wolvic dies. I suspect that your platform does not really support VP9 decoding. Please reopen if this analysis is incorrect and/or inaccurate.
- Reply to this email directly, view it on GitHubhttps://github.com/Igalia/wolvic/issues/1414#issuecomment-2146845762, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYZV3YTKTCPGA2FM35B46NTZFVWWNAVCNFSM6AAAAABHLWFL5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBWHA2DKNZWGI. You are receiving this because you authored the thread.Message ID: @.**@.>>
NOTICE: This email (including any attachments) may contain DigiLens Confidential Information and is intended for the recipient(s) of this message. If you are not an intended recipient, you are hereby notified that any dissemination of this message is prohibited. Please permanently delete all copies and any attachments and notify the sender immediately by sending an email to @.***
Configuration
Wolvic version: release/chromium/0.9 Wolvic build ID: Gecko version: firefox-124.0.1 Active Build Variant: noapiArm64GeckoGenericDebug, Active ABI: arm64-v8a
Hardware: Digilens ARGO
Steps to Reproduce
Current Behavior
Trying to play any video on the web crashes the app
Context
I’m trying to build a version of the Wolvic XR Browser with the latest Chromium updates for our ARGO smart glasses platform.
Error Logs and Stack Traces