Feature description
A toggle for a simplified explicit tag. Just a simple bracketed E, “[E]”, as an alternative to 🅴.
Problem solved
Under “Playback settings” → “Advanced settings” the current toggle for “Explicit symbols in media session” uses the E in a box character (🅴). This does not render on some devices when casting or playing via bluetooth.
My test are limited to my vehicles: a 2017 Buick Enclave (no particular surprise that 🅴 doesn’t render) and a 2023 Kia Carnival (which has much more extensive font compatibility). Both vehicles display the missing glyph sybol (□) rather than the 🅴.
Brought benefits
Provides an easily-rendered alternative symbol to quickly determine the “cleanliness” of a song that will work on pretty much any device.
Device type
Phone
I searched existing feature requests
on
Sorry way too specific, most people do not enable this option anyway as it breaks scrobbling.
“too specific” and “most people do not enable” don’t really make sense. You and symfonium already support loads of advanced features that most users do not enable. You may have the metrics, but I’d argue that most users do not use scrobbling. “Most users” will do the minimum required and never delve deeper than that. But “most users” and “most forum” posters are different subsets.
Anyhow, if it is true that “most people do not enable” the option, then wouldn’t it make more sense for the option to work “properly” in one of the most common use cases (ie. bluetooth casting in a vehicle) for those users that do enable it? You don’t even have to break the current implementation, it would just be another toggle that most people can ignore.
Excuse the C++ style psudocode, but:
string displayedTitle = songTitle;
if (dispExpl) displayedTitle = "\uD83C\uDD74 " + displayedTitle;
if (dispSimpleExpl) displayedTitle = "[E] " + displayedTitle;
Something like the first “if” already must exist. Then you’d just need the few lines in the advanced settings code to enable a new toggle.
Of course, that is all just my opinion and you are surely inundated with many such on a daily basis. Thanks for all the work you do. Symfonium really is fantastic already!
Ask yourself why it’s even an option and why it’s off by default 
Sure
Q1. Why is it an option?
A1.1. So users can quickly identify explicit tracks (particularly useful when children, or otherwise “sensitive” individuals, are present).
A1.2: Someone requested the feature 
Q2. Why is it off by default?
A2. Not everyone wants it.
My proposed solution more fully resolves Q1 in a manner that is universally compatible with any device to which the music is being cast. It provides the greatest fulfillment of A1.1, while at the same time completely preserving the behavior for the folks of A2. And as an additional advanced toggle, the current “E in a box” can also preserved for anyone that prefers it.
