[LG V30 Guides, News, & Discussion] Ashtrix:
Done, Working on my V30S ! Thanks to all :D

Initial impressions

First the total volume output is raised which can be immediately observed. Which is great ! Because due to my hearing loss or the way how LG played safe game lol with this High End DAC which powers some Astell and Kern and Desktop Audiophile DACs, I always needed to be at 70 ish but now the 60-66 level is fine, and 70 is like 75+, So to my ears it's easily 6+ step increase and this is with Normal Mode (HiFi Status App) and my IEMs which are just 10 Ohms ( I personally believe the Tavil xml files force the Quad DAC and causes some not so good tuning output from the jack and the headphone/IEM impedance - Simply I could say, I cannot increase the volume with HIM forced, I hear disturbance even with 1-2 steps maybe because of High Sensitivity or not. So I leave it at factory mode. However that's me may / may not be applied to others.)

Second the Music Player and tonal difference - With this mode the EQ option is gone from LG Music Player along with the icon, that icon is now replaced the hifi icon in music player. New option only shows pitch speed with that new button on the right bottom (previously I use the Pure Surround and Bass Boost, Pure Surround artifacts sometimes with a few tracks and mix and match with digital filters, Short for example adds more spacious sound as it says + Pure Surround takes it to next level) And the DTS X : Surround option sounds a lot different to the Pure Surround and is on a whole another dimension..

"Wide" mode cuts off Treble/High End with quite some degree (I welcome this because my IEMs, triple driver have 2 TWFK Balanced Armature drivers and V-Shape causing peaky treble) along with midrange too and adds that Massive Bass/Low end emphasis, can be said "smooth sound"

"Side to Side" puts its opposite, more on the High End and Mid range (again the Dynamic Driver in my IEM, takes a step back, also I feel in this mode the volume is piercing due to the nature of my IEMs being hot at top)

"Front" mode as it puts a natural way and not so distant vs "Wide" mode plus more layered presentation, with better vocals as well and not excess low end and mind you all modes make the soundstage spacious and may even effect volume levels perception. BUT the biggest advantage is

no artifacts vs Pure Surround EQ mode, which makes this DTS X 3D cleaner and best option

, I Love this change. Also as you can notice if you enable the DTS : X 3D Surround mode, the sound preset options aren't available. Looks like they had tuned the ESS9218P to some libraries and couldn't get all in one shot, anyways I found the Preset options too aggressive and high delta with sound signature, to each their own.

Finally as you can see in the Screenshots, the UI is changed and the

only piece missing is the "EQ option"

like here in the V40 ThinkQ explains why the Music Player lost that mode everything looks same like that one from V40. I presume the EQ option is lost somewhere, if we can enable that it'd be endgame, as it has solid presets and nice custom tuning. Fingers crossed, since they borked this, LG fixes their mess with next update. Also no idea what's that Normalize switch is doing :confused:

One last note, I don't know if the DTS effect changed the sound signature a bit even when off, as Head-Fi users mentioned on V40, I cannot confirm this, would be great if anyone shares about this.

Also quite surprising how a simple line can change a LOT. Hope if any of that helps..:good:

Enjoy the DTS X guys, love how LG is enabling this on their prev gen devices. It's fun if you dig it :)

Edit: Without this, your LG Music player "HiFi button" won't work, tapping on that doesn't do anything, manually going to the HiFi DAC settings is needed. But "EQ button" works. AND I have Liveboot by Chainfire installed and it works flawelessly. I guess if I disable the mod at the end of the booting, livelogcat I see some lines in red color with "mixer paths" "headphones" perhaps errors or warnings, hard to get a proper read since it's a splitsecond...this could be entirely unrelated, but just sharing my observation.