Reporting Bugs

Reporting Bugs

What to send

1. Everything in Documents/Severed Chains/logs/ — especially any crash-*.log. No crash file + a truncated debug-*.log means a native driver crash (still useful — say so).
2. What you see — instant close? Black screen? Freeze? "App isn't responding"? Stuck at setup/disc import?
3. Device + Android version and which APK (release or debug).
4. GL fallback level if you know it — it prints in the debug log as GL fallback level: N.

Logcat (if you have adb)

Right after reproducing:

adb logcat -d > logcat.txt

A native crash shows a DEBUG: backtrace naming the faulting library (e.g. libGLESv2_adreno.so vs libart.so). Hidden-API denials (hiddenapi: Accessing hidden method ... denied) are Java-side and land in crash-*.log too.

Tips

• Debug builds (severedchains-debug.apk) write verbose engine logs; release builds only write crash logs.
• The setup screen can be reopened any time with adb shell am start -n com.legendofdragoon.severedchains/legend.game.android.MainActivity -e force_setup 1.
• The ES 3.1 fallback path can be forced for testing with -e force_es31 1 on the same intent.