Koreader on Meta Quest 3

[TenKOhms]

I know this is going to sound silly/obscure, but has anyone gotten koreader working properly on Meta Quest 3? It seems to ignore my "clicks" in book. I can use the main file browser ui to open an epub but once open, I can't go to next page or even open up the top/bottom menus.

[pazos]

Yup, sounds fun.

Without having the device I cannot tell you but based on how it behaves on tvs and chromebooks it seems to fail to detect input events if there's no explicit hook on the android view hiearchy.

Fortunately we have workarounds for those, see https://github.com/koreader/android-...ice.kt#L24-L28

If that works a workaround for the meta quest is welcome

[TenKOhms]

Hey thanks for the info! Anyway to test this for meta quest without having to recompile an APK?

[pazos]

Originally Posted by TenKOhms

Hey thanks for the info! Anyway to test this for meta quest without having to recompile an APK?

Nope. You're expected to modify the backend, rebuild the APK and test if that works.

But, for the moment, you can safely assume that KO won't run flawless on VR headsets or cars

[TenKOhms]

Originally Posted by pazos

Nope. You're expected to modify the backend, rebuild the APK and test if that works.

But, for the moment, you can safely assume that KO won't run flawless on VR headsets or cars

You read my mind with the cars

I've downlaoded the docker container koappimage and tried to compile for android but running into cmake issue:

ko@59bb6d677c06:~/koreader$ ./kodev release android-arm64
make TARGET= KODEBUG= VERBOSE= android-ndk android-sdk
make TARGET= KODEBUG= VERBOSE= po
make ANDROID_ARCH=arm64 TARGET=android KODEBUG= VERBOSE= update
************ Building for MACHINE: "aarch64-unknown-linux-android21" **********
************ PATH: "/home/ko/koreader/base/toolchain/android-ndk-r23c/toolchains/llvm/prebuilt/linux-x86_64/bin:/home/ko/x-tools/*/bin:/home/ko/.luarocks/bin:/home/ko/local/bin:/usr
/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" **********
************ CHOST: "aarch64-linux-android21" **********
************ NINJA: ninja -j1 -l8 **********
************ MAKE: make -j1 -l8 **********
Warn about uninitialized values.
Re-run cmake no build system arguments
CMake Error: The source directory "/home/ko/koreader/base/build/aarch64-unknown-linux-android21/cmake" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
base/Makefile:69: recipe for target 'base/build/aarch64-unknown-linux-android21/cmake/build.ninja' failed
make: *** [base/build/aarch64-unknown-linux-android21/cmake/build.ninja] Error 1
ko@59bb6d677c06:~/koreader$

Any tips/suggestions? Thanks

[pazos]

Yup. You'll need the docker image for the target platform. In your case it is https://hub.docker.com/r/koreader/koandroid

But I never used docker to build KO.
Up to date instructions to build are in https://github.com/koreader/koreader...ing_targets.md

[TenKOhms]

Thanks! was having issues installing koandroid using docker pull, but was able to find and download the image via docker desktop.

Compiled an APK successfully (it looks like) but getting issue:

CORE: Checking for WSA...
CORE: Checking for WSA returned 0
CORE: Checking for ADB...
CORE: ADB Found - Installed by WSATools - C:\AndroidADB
CORE: Preparing APK at C:\Users\bbmis\OneDrive\Desktop\koreader-android-arm-v2024.11-130-g9b444cba8_2025-01-09.apk
CORE: Preparing APK encountered an error: Could not find any recognizable digits.
CORE: Attempting connection to WSA - Attempt n 1 (Max 10)
CORE: Connected to WSA
CORE: Installing APK at C:\Users\bbmis\OneDrive\Desktop\koreader-android-arm-v2024.11-130-g9b444cba8_2025-01-09.apk
INSTALL: Performing Streamed Install
INSTALL - ERROR: adb: failed to install C:\Users\bbmis\OneDrive\Desktop\koreader-android-arm-v2024.11-130-g9b444cba8_2025-01-09.apk: Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES: Failed to collect certificates from /data/app/vmdl691535830.tmp/base.apk: Attempt to get length of null array]

Any thoughts? Thanks!

[TenKOhms]

scratch that, figured out needed to sign the APK. Onto testing

[Frenzie]

If you run it with -d (--debug, as in kodev release -d android-arm64) it'll sign it with a development key. But since you already built the non-debug version it'll probably take less time to just sign that one.

[TenKOhms]

Thnx all, got APK build and signed and installed on my meta quest 3, but unfortunately making the following changes:

    val needsView = when (activity.platform) {
        "android_tv" -> true
        "chrome" -> true
        else -> true
    }

(test out just making needsView always true)

To
./platform/android/luajit-launcher/app/src/main/java/org/koreader/launcher/device/Device.kt

and rebuilding apk still did not resolve issue of not being able to use click/touch event when in reading mode. Still able to navigate the file browser to open up book.

[pazos]

Thanks for testing.

Enabling "needsView" is just the beginning of the journey (you can always disable it if you don't find any input changes on the logs)

Our motionEventHandler might need some work too, they're in: https://github.com/koreader/koreader...ut_android.lua

Never played with an VR headset, so I have no idea how they implemented input events. It might be different.

There's also a not so slightly chance that Oculus failed to implement required frameworks properly. I know it sounds strange but it isn't. There're a bunch of partially broken frameworks out there, not only on e-ink devices.

[TenKOhms]

Was worth a shot testing regardless, thanks for the info and help!