Start with a clean, unconfigured camera session and identify the action that causes the crash. A release, package, XML, lens or capture-mode mismatch needs a different remedy; changing all of them together makes the cause harder to find.
Use the symptom to choose a check
| Symptom | First useful check | What to try next |
|---|---|---|
| Crash at launch | Camera permission, exact release and device evidence | Back up accessible XMLs; reset app settings to remove a bad config. Try a documented alternative package. |
| Crash immediately after importing XML | Model and release of the XML | Return to your backup or defaults before selecting a matched file. |
| Main camera works, telephoto or ultrawide fails | Firmware camera access and config camera IDs | Use only a package recommendation documented for that model. Test lenses one at a time. |
| Crash after capture | Mode, processing settings and available storage | Test default settings and a basic photo mode. Undo recent processing changes individually. |
| Video fails | Resolution, frame rate, lens and known config caveats | Test a basic video setting. A working photo config does not prove video support. |
| APK will not install | Incomplete file, free space or same-ID signature conflict | Review installer message. Export settings before uninstalling any existing app. |
Make one change at a time
- Record phone model code, chipset if known, ROM, Android version, full APK filename and loaded XML.
- Reproduce the problem with the same lens and mode. Keep a normal stock-camera sample only for your own comparison.
- Export or copy existing settings before a reset. Clearing cache is different from clearing app storage, which removes app settings.
- Try the default camera without an imported XML. If this works, investigate the preset rather than reinstalling repeatedly.
- Consult the device’s source notes for package or library requirements. Do not copy another phone’s camera IDs or shared library blindly.
- If a supported combination still fails, collect the exact symptom and relevant error log for the developer’s discussion channel. Remove personal data before sharing a log.
When there is no verified combination
The device finder reports the evidence available, not guaranteed operation. Firmware can hide auxiliary cameras or expose incomplete Camera2 behavior. Keep the stock camera for functions that the port cannot provide reliably.
Muzamil Ahad reports APK testing across the listed models; a result for your exact firmware and settings is not currently published. Use these diagnostic steps to check your own combination. Read release notes to choose a documented change and the XML guide to isolate configuration problems.
Make the next step easy to verify
Does a default main-camera photo save?
Back up accessible XMLs, remove the newly imported preset from the test, and use the exact source build’s default setup. Check camera permission and available space.
Focus on the change that failed
If the failure began after an XML, investigate its release, model and library requirements. If it begins only on another lens or mode, isolate that lens/mode and read its source notes.
Check the app and firmware combination
Read the installer/release requirements and the exact model’s package guidance. Keep a stock-camera fallback. An XML cannot guarantee missing firmware camera support.
When HDR processing never finishes
The GCam FAQ identifies old-build/new-Android mismatches, background-process restrictions and app cloning as possible causes. Use the original source-listed package, inspect relevant battery/background behavior for that app, and test a simpler capture mode. Do not assume every processing delay is a crash.
Separate a cache reset from deleting settings
Clearing cache and clearing app storage are different actions. Clearing app storage resets settings. Export or copy a backup first, then record whether default operation changes. Reinstalling the same bad preset immediately after a reset can reproduce the same problem.
Keep a simple setup record
Save these details with your backup. They make it possible to repeat a working setup or describe a problem accurately.
________________________
________________________
________________________
________________________
________________________
________________________
Copy this checklist into your own notes. This page does not submit or save your device information.