[Bug]: android 14/16 support

[zxx-ha]

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

After the application is launched on Android 14 or Android 16, the loading fails. Debugging proot check failed.

Steps to reproduce

1

Expected behavior

1

Actual behavior

1

OpenClaw version

20260408

Operating system

adnroid14/16

Install method

No response

Model

1

Provider / routing chain

1

Additional provider/model setup details

No response

Logs, screenshots, and evidence

avc: denied { search } for name="tests" ... permissive=0 app=gptos.intelligence.assistant
avc: denied { execute } ... libproot.so

Impact and severity

No response

Additional information

No response

[cruelgrim]

Proot check failed

[nermindurma81-ui]

Proot check failed

[friuns2]

can you guys try old version does it work? https://github.com/friuns2/openclaw-android-assistant/releases/tag/v369

[nermindurma81-ui]

Installed

[friuns2]

Status update: we are still seeing Android 14/16 startup failures in feedback logs, but the raw avc: denied lines by themselves are not enough to conclude that proot execution is universally broken. Some of those SELinux denials are noisy and expected.

What we are focusing on now:

1. startup/runtime dependency mismatches in the bundled environment
2. low-memory gateway kills / restart loops on some devices
3. setup/bootstrap failures that leave the app stuck before the environment becomes usable

If you can still reproduce this on the latest build, please send a fresh in-app feedback report right after the failure. The most useful files are setup.log, gateway_logs.txt, and logcat.txt from the same run. That will tell us whether your device is failing in proot validation, rootfs setup, or gateway startup.