[Brain Damage]

If that's the only reason, try the high impedance adapter trick. You'll need 3.5mm extender along with it.

1. It's going to be like this first:
V30 -> 3.5mm extender -> high impedance adapter -> planar IEM
2. The high impedance mode will be enabled.
3. Remove the impedance adapter
4. Connect planar IEM to 3.5mm extender.
V30 -> 3.5mm extender -> planar IEM

I used to use this trick with FAAEAL 80 ohm 3.5mm impedance adapter from Amazon & KZ PR2.

Thanks. I have impedance adapters and have been aware of this trick, it's just a bit fidgety and was interested to hear about being able to check the DAC settings with this software approach

 

[Brain Damage]

Thanks. I have impedance adapters and have been aware of this trick, it's just a bit fidgety and was interested to hear about being able to check the DAC settings with this software approach

I believe with the extender plugged in, the quad DAC on the V30 enters auxiliary mode as opposed to the high impedance mode (experienced when a high impedance iem/headphone is directly plugged into the jack of the V30). At least this is my experience.

 

[keibee]

Thanks. I have impedance adapters and have been aware of this trick, it's just a bit fidgety and was interested to hear about being able to check the DAC settings with this software approach

Yes, I was told that the true high impedance mode can be enabled in a hardware level only. Software tricks are just boosting the volumes up and may give you some distortions at the higher volume.

 

[Veroxious]

Does LineageOS break DSD support? And UAPP doesn't seem to work at all, either. Neutron can play music but not DSD files.

 

[nhockon]

LG music app can active Quad Dac on 16/44.1, android 8?

My device : v40, stock Android 8. Im using Poweramp with hires setting (force 24 bit, 44.1Khz)

 

[nhockon]

Why UAPP just display "16 bit", Quad DAC works?

(v40, Android 8.1, UAPP)

In Neutron, it upscale to 32 bit.

 

[Chris Kaoss]

Uapp doesn't show the "internal" upscale process.
So the displayed sample rate is correct, if bit perfect is applied in the settings.
The internal upscaling in Uapp is for bypassing the android mixer mainly.

You can force Uapp to automatically output with 24 bit/ 32 bit, but that doesn't make sense. (via HighRes driver settings)
It'll still show the source bit rate.

 

[nhockon]

Uapp doesn't show the "internal" upscale process.
So the displayed sample rate is correct, if bit perfect is applied in the settings.
The internal upscaling in Uapp is for bypassing the android mixer mainly.

You can force Uapp to automatically output with 24 bit/ 32 bit, but that doesn't make sense. (via HighRes driver settings)
It'll still show the source bit rate.

Thank you. My Bit Perfect is OFF, because i hear someone say "parametric EQ >>> bit perfect".

 

[Chris Kaoss]

Can't comment on that statement bc I don't use EQ in my systems, except a tiny boost on the Mojo 2.

If done right, (parametric)EQ is able to sound better to yourself, but that doesn't mean better sound quality.
It just sounds more/better to your likings, and/ or can correct different flaws of the headphone used. ( but only from your pov, not others )

Anyway, Uapp convert every 16 bit stream to 24 bit internally for the purpose of bypassing android mixer, which generally resamples all streams to 48kHz, instead of 44.1kHz (and it's multiples)

If you don't have to correct your headphone(s) in their presentation (bc they sound right to you stock), I'd always go with bit perfect on.

p.s.
Uapp has it advantage in the possibility to play streams from SD-card, Tidal, Quboz and all associated sources bit perfect and bypassing android mixer.
Besides some additional in app features like tone booster, morph it or xfeed, for example.

 

[nhockon]

@Chris Kaoss this is wall of text about bit perfect...

In the audio world "bitperfect" essentially just means the digital end of your dac is getting the file's datastream 1:1 without any resampling or effects etc. Making sure you have bitperfect is usually not an issue and virtually no one would be able to tell the difference between bitperfect vs non-perfect in most circumstances unless the imperfection is really egregious, such as a really lossy transcode, very low sample/bitrate, or an operating system applying it's own effects and EQ on top of a signal which changes the response of what you hear. Also note I said "digital end" of the DAC, if the DAC is made poorly or is busted or can't output a properly reconstructed signal from 20hz-20khz whether or not the signal is bitperfect becomes less relevant anyway. Not something that is an issue with modern dacs usually, especially highly rated ones you'd find on here. I don't know how well the Android SRC behaves but usually with modern resampling, the typical result even if somewhat "flawed" is still usually "audibly transparent" as far as human hearing is concerned- what you'd encounter even with a less than perfect SRC is maybe some artefacts many decibels (typically over -100 dB) down. So, not anything you'd realistically be able to hear, and definitely not after it's masked by the audio signal itself in music. I don't believe vanilla android does anything strange to the signal other than resample and maybe adding some effects of lowering and raising the volume of playing media when you have an incoming call or notification. There could very well have some sort of "audio enhancements" from certain manufacturer's android builds or device-exclusive software that do stuff like bass boosting or volume limiting, maybe specific EQs if you're using a phone's speakers vs using another audio source like the headphone jack or a USB dac, but I'm sure in some cases audio enhancements could be turned off in settings and ignored completely by using the DAC in exclusive mode with software like UAPP. Shifts in a response on the other hand is something that is clearly audible in a multitude of circumstances and may be a product of dac, amp, and loudspeaker(+room)/headphone functioning so this is why the the FR takes higher precedence here over the simple virtue of a signal being "digitally untouched". By buying good dacs/amps we eliminate their contribution to FR so now we only have to worry about the speaker or headphone which is what EQ aims to correct. We were not in the minds of the artists during the production process as @IAtaman touched on, but what we do know is that the artist+producers likely produced/finalised/listened to the file you are listening to in or approximating certain conditions, and the response in said conditions is probably the best representation of what they wanted you to hear, so the most effective way to achieve "as the artist intended" generally speaking is to also approximate those conditions: a flat in-room response generally produced by high-quality studio monitors or other flat loudspeakers in controlled or semi-reflective conditions. Unsurprisingly, research also says this is what humans prefer to listen to. In the case of headphones, the harman research serves as a proxy for these findings so the appropriate target would be something closer to harman-like. If your setup cannot achieve near those responses on their own (few can), EQ is what is used to get closer to enhance the sound which obviously involves losing the "bit perfection". And if you don't like that sound you can always just EQ to another preferred target or use various targets for different conditions. That being said, "bitperfect" is more or less a technical concern/diagnostic tool to ensure your source-to-dac interaction is perfect, and perfection does not necessarily mean it will sound any different to you, let alone better. As I mentioned already, good modern sample rate conversion is virtually transparent and if I were to bet on it I'm sure the android one functions fine. Bitperfection has more relevance in music production when working with digital files and processes than it does with listening/reproduction. So to put it simply: choosing bitperfection over EQ will sound worse 99.9% of the time unless there is some other underlying problem with the source.

(Source: MrNice13)