Oculus Go font loading SEGV
See original GitHub issueLoading <canvas>
2D bootstraps the font system in Skia, which tries to load default system fonts. This fails on Oculus Go, resulting in a segfault:
0x0000007f74d46fb4 in SkFontMgr_Android::SkFontMgr_Android(SkFontMgr_Android_CustomFonts const*) () from /home/a/exokit/android/app/src/main/arm64-v8a/libnative-main.so
We need to make sure the requisite font location is correct/the default font loads successfully to unlock <canvas>
2D on Android.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Solved: oculus go browser not working - 937343 - Oculus Forum
Solved: browser has suddenly stopped working on oculus go, no updates so its not thgat, crashes whenever you try to open vr. very...
Read more >Oculus go infinitely loading menu : r/OculusGo - Reddit
Hi,. My Oculus go is stuck, when I turn it on I just see the Oculus logo and then 3 dots that indicate...
Read more >How to get rid of the persistent three dots on Oculus Go & Quest
Follow these steps to get past the screen with the 3 dots loading screen: Start the VR headset; Open the Oculus app on...
Read more >Three Dots Issue: Connecting the Oculus Go to the ... - YouTube
Welcome to Rilix support! In this video, we will explain how to connect your Oculus Go to the internet by using the Oculus...
Read more >3 Grey Dots Loading When Turning On?
Why is my Oculus Go stuck showing 3 dots loading when I turn it on? This is a known issue with the Oculus...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
found a reference for android env variables:
source
Found the culprit. The reason for this error is that we are literally using the magic leap build of
skia
in the android build, and that build has an OS-specific hack to loadfonts.xml
from the package instead of the operating system: https://github.com/modulesio/skia/pull/6/filesWe’ll need to rebuild
skia
and somehow make this hack contingent on theANDROID
/LUMIN
difference. Ideally it’s detected at runtime so we can continue to share the lib across both platforms…