If LMC crashes after importing an XML, return to your saved settings or defaults and retry the same action. If it fails before an XML is loaded, check permissions and the exact APK/package for your phone. Change one thing at a time.
Use the symptom to choose a check
| Symptom | First check | Next action |
|---|---|---|
| Crash at launch | Camera permission, exact release and model guidance | Back up accessible XMLs. Test defaults after a settings reset; use an alternative package only when it is documented for that phone. |
| Crash immediately after importing XML | The XML device, release and library requirements | Return to your backup or defaults. Confirm that the camera works before importing another file. |
| Main camera works; telephoto or ultrawide fails | Firmware access, package choice and XML camera IDs | Read the exact model instructions and test one lens at a time. |
| Crash after capture | Capture mode, changed processing settings and free storage | Try a basic photo with defaults. Undo recent processing changes individually. |
| Video fails | Lens, resolution, frame rate and contributor caveats | Try a basic video setting on the main camera. Photo success does not establish video support. |
| APK will not install | Complete file, free space and a same-ID signature conflict | Read the installer error and the installation guide. Export settings before removing an existing app. |
Make one change at a time
- Write down your exact phone model code and region, chipset if known, firmware, Android version, APK filename, package and XML/library.
- Repeat the failing action with the same lens and mode. Keep a stock-camera reference for your own comparison if image output is the problem.
- Export or copy your XML before resetting anything. Clearing cache and clearing app storage have different effects; clearing storage removes app settings.
- Check the camera with defaults. If it works until you import the preset, inspect the XML requirements before reinstalling the app.
- Read the device source notes for package or library requirements. Copying camera IDs or a library from a different phone can introduce another mismatch.
- If the documented combination still fails, send the developer discussion channel the exact steps and symptom. Remove personal information from any log or screenshot.
When there is no verified combination
Use the device finder to check model and firmware limits. A port can open the main camera while the firmware restricts another lens or mode. Keep the stock camera available for functions your LMC setup cannot provide reliably.
Muzamil Ahad reports APK testing across the listed models. Individual firmware and settings results are not published. Record what happens on your own setup and use the release notes to choose a relevant change. The XML guide explains how to restore a backup and isolate preset problems.
Check the result before continuing
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 your working setup recorded
Save these details with your backup so you can restore the setup or report a failure.
________________________
________________________
________________________
________________________
________________________
________________________
Copy these fields into your notes or download the blank device-test worksheet. Nothing in this checklist is submitted to the site.