Download the exact LMC release and package you chose, open the APK with the Android installer, then check that the camera saves a photo before importing an XML. Back up an existing LMC setup first.
Before you install
Find your exact model in the phone finder. Check the chipset, regional variant and firmware, then read the package advice. Two files from the same release can use different Android package IDs, which can affect access to extra cameras.
Use the original archive linked from the release guide and match the full filename. The separate owner-provided APK has package com.lmc84.app and version 1.0.0; its Hasli release remains unverified. Its download is disabled while a reachable location is prepared.
If another LMC installation already works, export its settings and copy the XML somewhere safe. Note its APK filename and package before updating. Uninstalling or clearing app storage can erase the settings you want to recover.
Install step by step
- Export your current settings. Keep a copy of the XML outside the private app directory so it remains available after an uninstall.
- Choose one release and package from its original release archive. Wait for the APK download to finish, then find the complete file in your browser downloads or file manager.
- Open the APK. On Android 8 or later, allow that browser or file manager to install unknown apps if prompted. Older Android releases use an Unknown sources setting; manufacturer menu names vary.
- Read the app identity and any installer warning. Install only if you trust the source. Keep Android device protection enabled.
- Open LMC and allow camera access. Allow microphone access when recording video with sound. Review file or media requests for the feature you are using.
- Take a photo with the main rear camera and open the saved file in your gallery. Check selfie, other lenses and video separately. Import a matching XML after the default setup works.
Updating or trying a second package
Android uses the package ID to identify an app. A file with a different ID may install alongside your current camera. A file with the same ID may update it, or the installer may reject it when signing keys conflict. Export your settings before removing an existing installation.
If installation fails, write down the actual installer message. Check the completed download, free space and release requirements. A camera that installs but crashes belongs in the crash diagnosis; it is a different problem from a package that never installs.
The Android requirement shown for the owner-provided file comes from that file's manifest. It does not establish a minimum Android version for every Hasli build. Follow the requirements attached to the exact artifact you choose.
After installation
Revoke the browser or file manager's install permission when you no longer need it. Save the APK filename, package ID, Android version and XML name with your backup.
Before relying on LMC for an occasion, check the functions you use: saved main-camera photos, selfie, exposed auxiliary lenses and video with sound. If a failure begins only after loading an XML, return to your backup or defaults and isolate the preset using the crash guide.
Check the result before continuing
Keep the backup outside app data
Export settings, copy the XML to a separate place and record the package ID. Uninstalling an app can remove app data; a settings backup is more useful than remembering a short release number.
Use the actual installer message
An incomplete file, unsupported build, insufficient space and a signing conflict need different checks. Re-download the exact authorized artifact when a file is incomplete; do not rename an incompatible package to make it appear to match.
Capture and reopen one photo
Confirm the unconfigured main camera saves a usable file and that the gallery can open it. Only then test selfie, auxiliary cameras and a matched XML. This sequence tells you which change introduced a problem.
Do you need to remove the old app?
Not automatically. Different package IDs can sometimes coexist. The same ID may update the existing app, or fail if signing requirements do not match. Read the Android message and keep the old APK/XML details before changing anything. Signing certificates have not been inspected for every listed source file.
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.