Compare the changes you need and the settings to recheck when switching builds. Read the R18 versus R17 guide for the two most recent 8.4 releases.
R17
R17: practical focus
R17 adds highlight, Sabre-noise and sharpening-radius controls, plus Samsung metering under System Setup. Choose it when you want those manual adjustments, then compare saved output with your existing settings.
Consider it when
You need those specific patcher controls or want to test Samsung metering.
Migration checks
Save an untouched copy of your XML.
Confirm Sharp Gain is above zero before evaluating Radius Gain.
Change one processing option at a time and compare the same scene.
Config: Radius controls do not activate while the main Sharp Gain is zero.
R18 adds a larger exposure slider, popup controls and button vibration. It also loads custom noise/AWB models and offers viewfinder frame-rate controls. Hasli describes it as a usability update with no image-quality change.
Consider it when
You want easier viewfinder controls or need the revised default auxiliary-camera IDs.
Migration checks
Export your working settings before changing builds.
Recheck every lens after importing your existing XML.
Restart after choosing a custom noise or AWB model.
Config: Earlier configs are supported, but lens access still depends on the device and package.
RAW format selection, additional Sabre options, and noise-level presets were added.
6
Dates identify hub listings. Separate fix-artifact dates are not confirmed; the R8 count includes Lite files.
Keep a working backup
Record the full filename and package ID of a working installation. Export settings before an update, and test defaults before importing an older preset. Same-ID packages may update or conflict; different IDs can be installed separately if Android allows it.
Version numbers mean different things
8.4 is the camera family; R8 through R18 identify Hasli releases. F1 and Fix2 name artifact fixes. Package names identify Android applications. LMC 8.8 and 9.6 belong to separate branches, with their own configuration considerations.
Sizes and hashes have not been measured for every source-listed Hasli artifact. A hub date is not automatically the date of a later fix.