.

[KthugS]

.

[Peke]

These two options still don't work at all with Wi-Fi Sync.

Force Mask do not work with WiFi sync as it was remove by design, Enforcing masks over WiFI sync impose high strain on device, battery drain and was removed for the time being. Resync on other side works (I just tested it), are you sure it is not an test error.

If I modify some of the original file tags and run Wi-Fi Sync, MMA always shows "Updated"
This means that only the database on my MMA will be updated, not the files on my device.
In special cases, such as when I re-encode a FLAC file on my PC to a new version, MMA will say "Downloaded" and the file on my device's SD card will be identical to the PC file.

That is normal behavior and it was made to evade non needed sync. FLAC files are lossless and only difference on re encoding would be metadata, so not needed to resync.

When synchronizing directly from MMW after connecting via USB without using MMA Wi-Fi Sync
The options below will be activated after scanning.
Image

After scanning, a confirmation dialog box will pop up and copies such as filename_1.ext on the device will be displayed in the deletion list.
When I accept the delete and start syncing, the options in MMW that weren't working work.
In other words, once synchronization is complete, the files on the device's SD card will be identical to the original source.
Since all duplicate files created with filename_1.ext have been deleted, the number of sync target files and the number of files on the device are also the same.

I am not sure I completely understand these Can you elaborate what you tested and what was end result.

In conclusion, I would like to maintain the files on the device's SD card the same as the files on the PC, but this is not possible with Wi-Fi sync.
MMW sync settings work with USB connection, but not with MMA Wi-Fi sync.

In My tests i have found that files on device are same, are you sure that you did not changed some settings in Tagging profile settings that can influence metadata.

Also I noticed that you removed all conversation rules in which case default one can be applied in some cases.