Embedding in an Android application

Embedding is appropriate when the engine is part of an existing Android application. Standard export is simpler for a standalone game.

Prepare the host

1. Include a compatible engine AAR and native libraries for required ABIs. Package project data where the selected launch configuration can locate it.
2. Use ReckfellFragment and the ReckfellHost contract. The fragment forwards onPause, onResume and onDestroy to the engine; do not add a parallel manual lifecycle on top.
3. Supply launch arguments through the host and handle readiness callbacks. Creating a fragment does not mean renderer/project initialization has finished.
4. Check back navigation, permission results, Activity rotation/recreation and background return. Do not retain an old Activity in a static field.
5. Connect Android UI and game through a small explicit interface. Service Android Views on the UI thread and Entities on the engine thread.

Result and diagnosis

A successful integration starts the level and restores input/rendering after pause/resume. A black screen does not alone establish a renderer failure: inspect initialization logs, project paths, surface creation and native libraries first.

Do not assume multiple independent engine instances in one process without separately validating lifecycle and global services. The host/fragment API was source-reviewed; no host application or Activity recreation scenario was executed.