Describe the Bug/Crash
I am experiencing an encoding issue when editing audio metadata using SimpleTag Audio.
After saving tags that contain Turkish characters, they appear corrupted. For example:
- "Altın Kafes" becomes "Altın Kafes"
- "Ş" becomes "ÅŸ"
- "Ö" becomes "Ö"
This looks like a UTF-8 text being interpreted as ISO-8859-1 (or similar encoding mismatch).
Steps to reproduce:
- Open an MP3 file
- Edit metadata (Title, Artist, etc.) using Turkish characters
- Save the tags
- Reopen the file or check in another music player
The issue is reproducible consistently.
I have attached screenshots showing the problem.
Describe the intended behavior
Turkish characters should be saved and displayed correctly.
For example:
- "Altın Kafes" should remain unchanged
- Special characters like "ş", "ı", "ö", "ü" should not be corrupted
Tags should be written using a proper encoding such as UTF-16 or UTF-8 in ID3v2.
What android version do you use?
Android 16
What device model do you use?
Redmi Note 14 4G (HyperOS 3 Android 16)
Windows Subsystem for Android (WSA Android 13)
Bug report
This seems to be related to how ID3 tags are written.
Possibly:
- Tags are being saved using ISO-8859-1 instead of UTF-8/UTF-16
- Or UTF-8 text is written but read/interpreted incorrectly
The corruption persists across different music players, which suggests the issue is in the written metadata itself rather than just display.
It may help to explicitly set ID3v2 encoding (e.g. UTF-16) when writing tags.
Duplicates
Describe the Bug/Crash
I am experiencing an encoding issue when editing audio metadata using SimpleTag Audio.
After saving tags that contain Turkish characters, they appear corrupted. For example:
This looks like a UTF-8 text being interpreted as ISO-8859-1 (or similar encoding mismatch).
Steps to reproduce:
The issue is reproducible consistently.
I have attached screenshots showing the problem.
Describe the intended behavior
Turkish characters should be saved and displayed correctly.
For example:
Tags should be written using a proper encoding such as UTF-16 or UTF-8 in ID3v2.
What android version do you use?
Android 16
What device model do you use?
Redmi Note 14 4G (HyperOS 3 Android 16)
Windows Subsystem for Android (WSA Android 13)
Bug report
This seems to be related to how ID3 tags are written.
Possibly:
The corruption persists across different music players, which suggests the issue is in the written metadata itself rather than just display.
It may help to explicitly set ID3v2 encoding (e.g. UTF-16) when writing tags.
Duplicates