Error: Failed to call nativeSendMessage: UNKNOWN: UNKNOWN: Can not find OpenCL library on this device

[Kokoabassplayer]

As this screen capture show.

And input bow also hard to access because the home ui did not hide (see screen shop above)

Device: Samsung note 20 ultra 5g

[kingxy]

Same problem here on my Xiaomi 15.

[AbdulRehmanNazar]

Same problem on Samsung A55, Android 16 OS version

[ithiria894]

Hey, two things here:

1. The OpenCL error — v0.5.0 now has automatic GPU-to-CPU fallback, so the app should handle missing OpenCL gracefully instead of erroring out.

2. The input bar being covered by the navigation bar — we've reworked the UI layout in recent updates, this should be better now.

Could you try v0.5.0 and let me know if both issues are resolved? https://github.com/agents-io/PokeClaw/releases/tag/v0.5.0

If everything works, I'll close this. If anything's still off, just update this issue. Thanks for the screenshots, really helpful!

[ithiria894]

I traced this a bit further on main.

There were two separate issues mixed together here:

• the OpenCL path still had a gap during initial engine creation on some devices
• the chat input bar needed an extra navigation-bar inset pass on gesture-nav devices

Both are now patched on main in commit 58932c0:

• local engine init failures now retry on CPU, not just runtime send failures
• the chat input bar now sits above the navigation bar more reliably

This is not in a public release yet, so please keep the issue open for now. Once the next public build is out, I want to re-check both the OpenCL error and the covered input bar on Samsung/Xiaomi devices.

[ithiria894]

@Kokoabassplayer @kingxy @AbdulRehmanNazar tagging everyone in the thread: the extra OpenCL init fallback + input-bar inset fix is on main now, but it is not in a public release yet. Please wait for the next public build, then retest there.

[ithiria894]

Thanks for the detailed report and screenshot!

In v0.6.0 we've improved the GPU-to-CPU fallback path — when the device doesn't have a usable OpenCL library, PokeClaw should now fall back to CPU mode automatically and show the correct backend status (no more misleading "GPU" label when it's actually running on CPU).

We also fixed the local model runtime to better handle engine creation failures on devices with limited GPU support.

Please grab the latest from Releases and let us know if it works on your Samsung Note 20 Ultra. If the input bar overlap issue persists, feel free to open a separate issue for that.

Feature requests are always welcome too!

[ithiria894]

Quick update on this OpenCL/GPU family.\n\nI found another gap on our side: we were marking GPU as healthy too early. On at least one real device, the engine can initialize on the GPU path, but the first real inference still fails and the app falls back to CPU. So "GPU init succeeded" did not actually mean "GPU inference works".\n\nI'm tightening that now so PokeClaw only treats GPU as verified after a real inference succeeds. That should make the backend status a lot more honest and stop us from pretending a broken GPU path is usable.\n\nIf you're still hitting this on the latest build, please send a debug report from Settings -> About -> Share Debug Report. That gives me the backend state and makes this much easier to compare across devices.