Resolve Note 9 Pro region/codename before choosing a file; keep the gauguinpro 5G entry separate from 4G entries.
LMC 8.4 for Redmi: Device Evidence & XML Configs
LMC 8.4 for Redmi: model names, codenames and 4G/5G matter
A Redmi Note number is not a complete match. The Note 9 Pro entries distinguish joyeuse, curtana and gauguinpro. Note 12 Pro filenames identify the 5G/RUBY model, and the current Note 13 Pro heading explicitly says 5G. Use those identifiers to avoid importing settings for a similarly named phone. The Note 8 Pro also has an unusual release label: the Exotic file says R15 in its filename, while its source assigns R17+.
For Note 12 Pro and Note 13 Pro, read the full 4G/5G model name rather than selecting the first Pro result.
For Note 10 Pro, start with an exact-model current entry. The legacy file that says Mi Note 10 in its name is ambiguous.
Package and firmware guidance
The inspected Redmi entries do not document a universal snapcam, aweme, scan3d, Lens or iris recommendation. A model-matched XML is a settings choice; it does not establish which package is best for every Redmi firmware.
Use the catalog to narrow the files, then compare one scene at a time. DSLR or AllLens in a filename describes contributor intent; saved detail and working lens buttons still need checking on the actual phone.
Is a Note 13 Pro 5G XML also a Note 13 Pro 4G XML?
The current evidence is scoped to 5G. A distinct Note 13 Pro 4G recommendation is not established by these sources.
Why does an R15-named Note 8 Pro file appear for R17+?
The contributor's source text explicitly assigns Exotic--Vol-3--LMC-R15-for-MTK.xml to R17+. The displayed assignment is more informative than the embedded filename label.
Source notes: Hasli LMC8.4 R16+ community config index ↗ Hasli LMC8.4 R15 community config index ↗
Read the model-specific community evidence for Redmi. A successful setup on another regional variant, ROM or Android version may not transfer to your phone.
Choose an exact match
Use your device’s model code and chipset where the source distinguishes variants. The entries below retain release assignments, package recommendations and unresolved details. No model in this guide was tested by us.
Try defaults first, export working settings, then import a sourced XML. Follow the installation guide and XML setup. Select the documented package rather than guessing from the phone brand.
5 matching devices. Community evidence; check the variant details.
Community XML referenceFounder-reported APK testing
Redmi Note 8 Pro
Start here
For an R17+ experiment, use the Exotic file only with its documented R17+ scope. For a simpler comparison, keep the exact-model Comrade entry as a separate reference rather than mixing the two imports.
Choosing the configThe Comrade file gives an exact-model starting point. Exotic--Vol-3--LMC-R15-for-MTK.xml is a second option selected by its source assignment, not by the R15 label embedded in its name.
Model-specific setup checks
Read the assignment beside the file
Do not downgrade to R15 solely because the Exotic filename says R15. The contributor's current source assignment is R17+.
Keep Note 8 and Note 8 Pro files separate
Use a folder label or filename note that includes Pro. The source has separate headings; the shared Note 8 number does not make their camera settings interchangeable.
Compare HDR processing with a difficult scene
Use a bright window and a darker interior in the same frame. Inspect saved highlight detail and shadow noise while changing only the XML, so you can choose the more useful processing on your phone.
Test in this order
- Confirm the exact Note 8 Pro and installed release.
- Import one matching candidate and save a bright-window/shadow comparison.
- Check front capture and a second ordinary daylight photo before trying another file.
Keep separate: Redmi Note 8; Redmi Note 8T
Is Exotic--Vol-3--LMC-R15-for-MTK.xml an R15-only file?
The inspected source explicitly marks it for R17+. Preserve that assignment rather than interpreting the embedded filename label as a tested-release statement.
Profile source / instructions ↗ Profile source / instructions ↗
Variant limits and source evidence (4)
The source explicitly marks Exotic--Vol-3--LMC-R15-for-MTK as for R17+ despite R15 in the filename. Do not confuse Note 8 Pro with Note 8. Filename labels alone do not demonstrate compatibility.
Comrade_v6_LMC_8.4.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
Exotic--Vol-3--LMC-R15-for-MTK.xml
Release: R17+
Package: No verified package recommendation
Author: Not attributed in index
R16-HDR.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
Comrade_v6_LMC_8.4.xml
Release: R15 index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
Community XML referenceFounder-reported APK testing
Redmi Note 9 Pro
Start here
Check the full regional model/codename. Use the source section that matches joyeuse or curtana; use Redmi-Note-9-Pro-5G-gauguinpro-LMC-8.4.300.xml only for the separately listed gauguinpro 5G target.
Choosing the configA shared filename can have more than one documented target, but the grouping must come from the source. The 5G file is not a substitute for a 4G Note 9 Pro.
Model-specific setup checks
Keep the region in the backup name
Use joyeuse, curtana or gauguinpro alongside the XML and APK release. This prevents a later import from losing the regional decision that made the file relevant.
Treat the filename's LMC18 as a label
The selected Fsio entry is in the current index, but its filename does not itself establish an R18 compatibility test. Record the APK actually used in your successful setup.
Check saved framing after import
Photograph a fixed distant object with each exposed rear control. Inspect whether the saved angle of view changes as expected before interpreting a lens button as working.
Test in this order
- Resolve the regional model/codename against the matching source heading.
- Save a main-camera comparison with that section's file.
- Check front and exposed auxiliary captures; record the region, firmware and release together.
Keep separate: gauguinpro 5G for joyeuse/curtana 4G selections; Redmi Note 9; Redmi Note 9 Pro Max without its own entry
Which LMC file is for Note 9 Pro India?
The source groups Note 9 Pro India with Note 9S under curtana. Use that exact section; the gauguinpro entry is the separately listed 5G model.
Variant limits and source evidence (3)
The index separates global Note 9 Pro joyeuse, India Note 9 Pro/Note 9S curtana, and Note 9 Pro 5G gauguinpro. Match the exact regional model and codename. The 5G entry is not a recommendation for 4G models.
Fsio-ollLMC18.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
R16-HDR.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
Redmi-Note-9-Pro-5G-gauguinpro-LMC-8.4.300.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
Community XML referenceFounder-reported APK testing
Redmi Note 10 Pro
Start here
Begin with RN10Pro-intro555-v12.xml under the exact Redmi Note 10 Pro heading. Keep RTTG-Dlsr-Prime.xml as a separate style comparison after ordinary photo saving works.
Choosing the configThe exact-model current heading is the basis for the first choice. DSLR in the second filename is an aesthetic label, not evidence of matching a DSLR's optics, sensor or depth of field.
Model-specific setup checks
Compare texture before choosing the DSLR label
Use hair, leaves and a face in the same saved scene. Check whether the profile's sharpening and color suit the subject, with both results viewed at equal size.
Hold the ambiguous legacy entry back
LMC-8.4-V8-XML-for-Mi-Note-10-and-Pro.xml is filed under Redmi Note 10 Pro but names Mi Note 10. Prefer the unambiguous current choices until stronger target evidence exists.
Verify every lens you use
The selected entries do not establish a universal all-lens result. Make a short saved-photo checklist for the main, front and any exposed auxiliary controls before replacing the stock-camera routine.
Test in this order
- Save the same detailed daylight scene with default LMC and RN10Pro-intro555.
- Compare the DSLR-labelled file separately using the same position and light.
- Check front and exposed auxiliary captures, then preserve the chosen XML.
Keep separate: Xiaomi Mi Note 10; Xiaomi Mi Note 10 Pro; Redmi Note 10 without its own entry
Does a DSLR XML give Redmi Note 10 Pro DSLR hardware?
No hardware equivalence is established. RTTG-Dlsr-Prime is a community processing label; judge its saved color, sharpening and portrait output on the phone.
Profile source / instructions ↗ Profile source / instructions ↗
Variant limits and source evidence (3)
Current source lists the model directly. The older filename says Mi Note 10 although indexed under Redmi Note 10 Pro; treat that as an ambiguous legacy listing. No universal lens or Android-version guarantee is documented.
RN10Pro-intro555-v12.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
RTTG-Dlsr-Prime.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
LMC-8.4-V8-XML-for-Mi-Note-10-and-Pro.xml
Release: R15 index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
Community XML referenceFounder-reported APK testing
Redmi Note 12 Pro
Start here
Confirm the full 5G model identity before trying XML-RN12PRO-LMC8.4-V3-RUBY.xml or XML-RN12P5G-LMC-8.4-R16-V2.1.xml. A similarly named 4G or Pro+ phone needs its own evidence.
Choosing the configBoth files are model-identified community candidates. V3, V2.1 and R16 in their names do not provide measured quality comparisons or blanket release compatibility.
Model-specific setup checks
Use 5G/RUBY as the first filter
Do not let the omitted network suffix in a page heading override the more specific identifiers in the selected files. Keep the exact full model in any saved setup note.
Compare candidates on the same colors
Use a face, foliage and a neutral object for both files. Change only the XML so that lighting differences do not decide which result looks more natural.
Keep the actual APK release with V2.1/V3
A profile revision and an APK release are separate pieces of information. Record both rather than assuming the higher XML revision is automatically more stable.
Test in this order
- Confirm the full 5G/RUBY target.
- Save a main-camera reference with one model-identified file.
- Check front/auxiliary captures before comparing the second file on the identical scene.
Keep separate: Redmi Note 12 Pro 4G; Redmi Note 12 Pro+ without its own evidence; Redmi Note 12
Are these Note 12 Pro configs for 4G or 5G?
The selected filenames identify RUBY/RN12P5G. This catalog scopes them to that listed 5G case and does not establish a distinct 4G recommendation.
Variant limits and source evidence (2)
The index heading omits 4G/5G but filenames identify RUBY and RN12P5G. Treat these as the listed 5G/RUBY profiles; do not extend to a similarly named 4G phone or Pro+ without its own evidence.
XML-RN12PRO-LMC8.4-V3-RUBY.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
XML-RN12P5G-LMC-8.4-R16-V2.1.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
Community XML referenceFounder-reported APK testing
Redmi Note 13 Pro
Start here
Confirm 5G first, then compare PowerFull.xml with GarnetVividAllLens.xml as separate current candidates. Keep the exact model and APK release in your notes.
Choosing the configUse the explicit 5G heading as the model-match evidence. AllLens in a filename remains a contributor label; test the exposed controls rather than advertising verified all-camera access.
Model-specific setup checks
Resolve 4G/5G before the import
A search for Note 13 Pro can reach both marketed variants. This catalog's current recommendation applies to the source's 5G heading; an unmatched 4G search should return no verified recommendation.
Check AllLens with saved samples
For GarnetVividAllLens.xml, save a photo from each exposed lens control and compare framing. A successful main-camera image does not validate the other controls.
Avoid transferring the X6 Pro file
The shared heading is Poco X6 5G, while X6 Pro has its own source entry. The Pro suffix changes the target and must remain visible in the finder.
Test in this order
- Confirm Note 13 Pro 5G and save a default-camera reference.
- Try one current candidate and save a main photo.
- Check front and every exposed lens, then compare the other candidate if the first does not suit the scene.
Keep separate: Redmi Note 13 Pro 4G; Redmi Note 13 Pro+; Poco X6 Pro
Can I use a Poco X6 config on Redmi Note 13 Pro?
The current source explicitly groups Note 13 Pro 5G and Poco X6 5G. That grouping does not establish Note 13 Pro 4G or Poco X6 Pro support.
Profile source / instructions ↗ Profile source / instructions ↗
Variant limits and source evidence (4)
The current heading explicitly groups Redmi Note 13 Pro 5G and Poco X6 5G. The older generic Pro listing is region/model ambiguous. No distinct Note 13 Pro 4G recommendation is verified from these indexes.
PowerFull.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
GarnetVividAllLens.xml
Release: R16+ index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
Redmi-Note-13-Pro-Isma.xml
Release: R15 index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
RN13Pro5G-V11.xml
Release: R15 index; exact release unconfirmed
Package: No verified package recommendation
Author: Not attributed in index
No verified recommendation in our catalog. Check your exact variant and source notes; a similar model is not enough.
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.
Phone model / region
________________________
ROM and Android version
________________________
Full APK filename
________________________
Android package ID
________________________
XML filename / library
________________________
Lens and mode that you tested
________________________
Copy this checklist into your own notes. This page does not submit or save your device information.
Sources & review
Source access: 14 October 2026. Release dates are shown separately. APK testing is reported by founder Muzamil Ahad; individual phone-test records are not currently published.
Founder & APK reviewer: Muzamil Ahad. How the guide was researched · Report a correction.