If you're using LE v7.0.x (Jarvis) it should be identical to OE. If you're using LE 8.0 alpha builds (Krypton) Kodi devs removed the overlay screen that shows codec and other bits of info. It wasn't a popular move and should be partially added back before Kryton release.
First let's see if those are bits added back. If not, we can look at patches. Most of the LE team aren't fans of the way codec type info has been dumbed down in Estuary. We understand why it's been done, but.
I created an account just to state the very nearly same thing, however wrt video codec bitrate info. However, unlike you I can see NO valid reason for the dumbing down as even the rankest imbecile would be better served seeing bitrate and other info given that an imbecile would have no other recourse unlike me who can jump through hoops, i.e. grab notebook, etc., ssh, poke around, be annoyed by idiots trying to tell me what's best, etc.
[EDIT]
BTW I'm on the m004u asus chromebox bleeding edge builds and this still has NOT be reenabled... I'm really frightened by that...
[/EDIT]
[EDIT2]
At the very least I'd make this config file configureable, or realistically this should be the idiot -> someone with a clue setting like all of the other menu configs... i.e. basic(idiot) -> standard(imbecile) -> etc.
[/EDIT2]
You could bring it back by simply adding this below in your keymaps XML. This is actually what i have in my gen.xml file to bring the old "codecinfo" back, put which key you want to use where "61525" is.
<keymap><fullscreenvideo><keyboard><key id="61525">playerdebug</key></keyboard></fullscreenvideo></keymap>
PlayerDebug can be displayed using Ctrl-Shift-o on a keyboard.
PlayerDebug can be displayed using Ctrl-Shift-o on a keyboard.
Not everyone use a keyboard with LibreELEC, you can map it to a button on the remote, this is why i added the keymap.
Not everyone use a keyboard with LibreELEC, you can map it to a button on the remote, this is why i added the keymap.
I know 
I mapped it too on my remote (green button) and hardly use a keyboard myself.
But, as the OP specifically wrote about the "o" key, I figured my post could be useful to him at least.
