# ✿ messing with ÄÖÜß on Android
**URL:** https://community.mp3tag.de/t/messing-with-aouss-on-android/68164
**Category:** Support
**Tags:** player
**Created:** [April 10, 2025, 8:42pm UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164 "2025-04-10T20:42:32Z")
**Posts on this page:** 19
**Page:** 1
### Author:  [@BlackFirePhenex](https://community.mp3tag.de/u/BlackFirePhenex)
#### Post date: [April 10, 2025, 8:42pm UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/1 "2025-04-10T20:42:32Z")
Hi,
how can i prevent this flower ✿ from messing up other parts of the same tag? This problem is only occuring on my Android phone (A54 5G). I tried a smiley instead of the flower, but that ended up in a line of question marks for the entire title. The umlauts `Ä Ö Ü ä ö ü` and `ß` can be displayed correctly but not with the flower in the same tag.
For some reason it only happens if it's a .mp3-file (red lines). When it's a flac-file the title gets displayed correctly (green lines).
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 10, 2025, 8:49pm UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/2 "2025-04-10T20:49:32Z")
What are the settings for MP3tag tags in the options?
Ctrl-O \>Tags\>Mpeg \> Id3V2-UTF16
should be the setting.
If it already is, press Ctrl-S to save the tags again.
---
### Author:  [@BlackFirePhenex](https://community.mp3tag.de/u/BlackFirePhenex)
#### Post date: [April 11, 2025, 4:18am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/3 "2025-04-11T04:18:45Z")
Wasn't entirely sure if it was on UTF-16, but it is.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 11, 2025, 4:41am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/4 "2025-04-11T04:41:51Z")
The screeshot from the android device looks like it shows the filename - and not the tag data. What does the filename look like in the windows environment?
---
### Author:  [@BlackFirePhenex](https://community.mp3tag.de/u/BlackFirePhenex)
#### Post date: [April 11, 2025, 6:05am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/5 "2025-04-11T06:05:23Z")
first, the bright white texts are the filename (with gray file-extensions). Below that in gray are the Tags:
`Artist` - `Album` - `Year` - `Genre`
`Track`. `Title`
Second,
The Filenames show up perfectly fine in windows.
This happens only on android and only with mp3-files for some reason.
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [April 11, 2025, 6:10am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/6 "2025-04-11T06:10:47Z")
If you try another player software (just for a test) on your Android phone, do you see the correct/expected characters?
(This would help to narrow down the source of the problem: Android as operating system or playing software.)
Or do we see the above screenshot from a file explorer software on your Android phone?
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 11, 2025, 6:18am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/7 "2025-04-11T06:18:33Z")
If MP3tag shows the tag data OK - but the player does not like it, there is not a lot that MP3tag can do.
A different andoid player would be worth a try.
---
### Author:  [@BlackFirePhenex](https://community.mp3tag.de/u/BlackFirePhenex)
#### Post date: [April 11, 2025, 9:22am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/8 "2025-04-11T09:22:37Z")
it shows up like that in my file explorer with wich i transfered the file first and my music player app. so it´s more likely an android or samsung thing, i think.
---
### Author:  [@BlackFirePhenex](https://community.mp3tag.de/u/BlackFirePhenex)
#### Post date: [April 11, 2025, 9:30am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/9 "2025-04-11T09:30:59Z")
The first image is from my phone, yes. It also shows up like that in my Musicplayer app "Musicolet". Everything gets displayed correctly in windows.
---
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [April 11, 2025, 11:25am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/10 "2025-04-11T11:25:17Z")
> [@BlackFirePhenex](#):
>
> For some reason it only happens if it's a .mp3-file (red lines). When it's a flac-file the title gets displayed correctly (green lines).
AFAIK Flac (Vorbis Comment) uses UTF-8 for character encoding.
Try out what happens if you save this mp3-file as ID3v2.4 UTF-8 in Mp3Tag.
---
### Author:  [@BlackFirePhenex](https://community.mp3tag.de/u/BlackFirePhenex)
#### Post date: [April 11, 2025, 8:57pm UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/11 "2025-04-11T20:57:10Z")
That worked!
But why? Isn't UTF-8 worse than -16?
---
### Author:  [@AreDigg](https://community.mp3tag.de/u/AreDigg)
#### Post date: [April 12, 2025, 1:55am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/12 "2025-04-12T01:55:48Z")
> [@BlackFirePhenex](#):
>
> Isn't UTF-8 worse than -16?
Bigger number doesn’t mean better. UTF-8 uses ASCII as a «base» and uses control characters for the additional symbols. The 8 only tells you that it uses 8 bit per character (and combines characters for non-ascii), and 16 means 16 bit per character. UTF-16 uses more space for «Latin» letters, and it also depends on endianess (so there are two versions of it).
---
### Author:  [@BlackFirePhenex](https://community.mp3tag.de/u/BlackFirePhenex)
#### Post date: [April 12, 2025, 2:53am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/13 "2025-04-12T02:53:02Z")
so technological terms a as coherent as ever and i forgot that. perfect.
well, thanks for the clarification.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 12, 2025, 6:18am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/14 "2025-04-12T06:18:19Z")
> [@BlackFirePhenex](#):
>
> Isn't UTF-8 worse than -16?
What is worse is the player's ignorance to standard compliant character encoding of the tag fields.
I would look for a different player rathern then resave my whole collection with ID3V2.4 tags.
---
### Author:  [@BlackFirePhenex](https://community.mp3tag.de/u/BlackFirePhenex)
#### Post date: [April 12, 2025, 7:03am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/15 "2025-04-12T07:03:31Z")
I really don't think it an issue with the player and more with android. I mean two completely unrelated apps showed the same issue. And the player is so far the best i ever had. For example it has built in (sync)lyric display and editor. This is the first problem i ever had with it.
Also i won't redo all my songs in -8. That would take me days. If i have problems in the future with it, i will change it on a "per-case-basis".
---
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [April 12, 2025, 10:16am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/16 "2025-04-12T10:16:35Z")
> [@BlackFirePhenex](#):
>
> Also i won't redo all my songs in -8. That would take me days.
You mean ID3v2 UTF-8?
Although ID3v2.4 has existed as a standard variant for more than 20 years, it hasn't yet widely prevailed over ID3v2.3, probably because it's difficult to replace a de facto standard with a new variant. Therefore, many people still use ID3v2.3 to be on the safe side in terms of compatibility.
In Mp3Tag, you can only get UTF-8 as the character encoding for MP3s if you select ID3v2.4.
However, as you write, saving all MP3s in this format with Mp3tag wouldn't really be a special effort. Instead of days, it would probably take a few minutes at most, depending on the number of files:
Change in Options -\> Tags -\> MPEG -\> Write to ID3v2.4 UTF-8
Load all music files
Filter by the MP3 suffix
Select all displayed files with CTRL-a
Click Save
---
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [April 12, 2025, 10:26am UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/17 "2025-04-12T10:26:22Z")
> [@BlackFirePhenex](#):
>
> I really don't think it an issue with the player and more with android.
Android has no problem with UTF-16.
UTF-16 is used more frequently in Android than UTF-8.
---
### Author:  [@phw](https://community.mp3tag.de/u/phw)
#### Post date: [April 12, 2025, 1:27pm UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/18 "2025-04-12T13:27:59Z")
I had been struggling with Android encoding issues with MP3 as well. I tried different encodings and switching between ID3 v2.3 and v2.4. It sometimes worked with some files, then other files with accents or umlauts broke again for no good reason.
I never figured out exactly what is happening, but it looks like Android is often doing some guesswork on the encoding, and sometimes getting it wrong. Which is a bit strange, because ID3 tags define the encoding quite clearly.
One solution is to use a player that does extract the tags itself instead of relying on the Android media library.
I personally got sick of dealing with the issue and switched to use Ogg Opus for all my files.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [May 12, 2025, 1:28pm UTC](https://community.mp3tag.de/t/messing-with-aouss-on-android/68164/19 "2025-05-12T13:28:23Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.