This could be bug in one of the following software/firmware, but I am incline to think it might be an mp3tag issue:
I have a Samsung YP-P3 media player and an Android phone (HTC Hero) which reads the embed art of mp3 files. With mp3tag, these are read correctly by the software of the player/phone when it's saved as id3v2.3.
When it is saved a id3v2.4, both device cannot read the embed art. If I re-save the tag with easytag, another tagging program, without modifying any information/embedded file, the devices mentioned above will read them correctly with id3v2.4 tag.
mp3tag remains my favorite tagger by far with all the customized scripts, so I have no intention of switching to easytag. Can this be a bug in the way mp3tag handles the embedded art?
I'm using also a Hero smartphone which is unable to read the covers as Mathieu mentioned it.
I have experienced that the covers are not correctly readed by AIMP software (MP3 file reader) for example (and other devices).
Using this software, the cover is badly displayed (it seems the file encoding is wrong).
As I'm not familiar with the different tag version, I'm wondering if this problem is linked with tag version (2.3 to 2.4) or if the file encoding used by MP3Tag could be enhanced to enable the "sensitive" devices or software to work with.