Preamble: The information below is a collective effort from several headfi members. I'd like to acknowledge contributions from @kundica, @chillaxing, @mlknez, @ra990, @Left Channel, @scottm18, @oddluck, @james444, @dragion and others I've obviously forgotten. I'd also like to acknowledge the developers of Neutron and UAPP for many useful communications. If you see a typo, an egregious error worthy of a class-action lawsuit, something you mildly disagree with, or if I've forgotten something important, please pm me and I'll update this post. Important disclaimer: I am not affiliated with any Android app dev team. If you prefer the sound of some other third party music app not mentioned here - even though it re-samples everything to 48/16 PCM - you're free to use it. The following information is intended only to help new V30 users. -- The LG V30 is an awesome phone for music. Actually it's an awesome phone, but that's a review for another day; this post is strictly about the V30's audio. The V30 has a 3.5 mm headphone socket with quad ESS 9218P DAC and an amplifier that automatically adjusts output power to match your headphones. The V30 has an output impedance of approximately 1 Ohm, which is very good (using the typical rule of 8, it should do no harm to the frequency response of any headphone ~8+ Ohm impedance). Most people will be able to simply plug in their favorite headphones and enjoy surprisingly high-quality sound without needing to carry around a separate DAC/amp. Most of you won't need to worry about this thread. You can simply stop reading here and go and enjoy your V30, and/or hang out on the main V30 thread: https://www.head-fi.org/threads/lg-v30.858933/ Still reading? Cool. There may be some extra goodness you can squeeze from the sound quality of your V30. There are several little rabbit holes to go down here. Make your choice below, or simply take a shortcut to the recommended music apps at the bottom: Spoiler: Tricking the V30 Amp into Giving More Output Power The V30 has three gain modes: Regular device mode, Aux (external device) mode and High-impedance device mode. Currently, there's no known way of manually setting the gain mode on the V30 - it's set automatically by the V30 as a function of the attached device impedance. On your headphone's TRS connections, the V30 checks the resistance across T & S each time you plug in your headphones (T & S is the left channel - T & R aren't checked). If it detects < 50 Ohm, it switches to "Normal device mode"; between 50 Ohm and ~ 750 Ohm, it switches to "High impedance mode"; above ~ 750 Ohm, it switches to "External device mode". For most people, this is totally sufficient. But there are headphones (e.g., planar magnetic headphones) that are simultaneously low impedance and low sensitivity. Some may prefer more power to drive such headphones to louder volumes or create more headroom. There have been several suggestions on the main V30 thread for this. The idea is to first plug in an adapter which will trigger aux or high-impedance mode, and then plug in your headphones to the adapter. There are variants to this trick: for example, if your headphones have removable cables, removing them first, and re-attaching only after you've plugged in the 3.5mm plug to the V30, you will trigger aux mode. I generally don't recommend permanently leaving an impedance adapter in series just to trigger high-impedance mode; this isn't only taking one step forward to take one step backward, but it's also changing your headphone's frequency response. Here is a passive adapter I've tested (so I know it works in triggering aux mode, which has been sufficient for me): https://www.amazon.com/gp/product/B00GZQWI6C If you need even more power than that from aux mode, check out the following tip posted by @ra990: https://imgur.com/a/53lKd Note that not all V30 firmwares tell you which mode is currently active. If your V30 doesn't report this, @dragion found this app on the Playstore that you can use: https://play.google.com/store/apps/details?id=com.apptrio.hi_fi_status&hl=en P.S. The output impedance can be measured using the third method in the video below (you need method 3, because checking the voltage drop across an infinite impedance load will trigger the V30 to switch to "external device mode"): From two resistance loads, R1 and R2, you can then determine the output impedance from: R0 = (R1-R1*V1/V2)/(V1/V2-R1/R2) In all three modes, the V30 output impedance measures ~ 1.3 Ohm. The key point here is that the output impedance does not change with the amp's output mode - it does no harm to the quality of the audio output to trigger "external device" or "high-impedance device" mode. Spoiler: The Sampling Rate Issue In an ideal world, your music player would play back all your native file formats directly, without going through any further digital processing or conversion. You most likely need to do a bit of extra work to achieve this. Wait? Does sample rate really matter?? It depends what we're talking about. The difference between 44/16 and hi-res FLAC formats (96/24, 192/24, etc.) is a heated flame war for another day. The discussion here is simply about the ability of the V30 to output, natively, through its quad ESS DAC, the exact same sample rate you have in your music file. Why? Because re-sampling creates artifacts as a result of interpolation error, especially when the up-sampled frequency is not a simple multiple of the original. It's perhaps not surprising to discover that most music apps available in the Google Play Store do not support hi-res PCM and DSD via the quad DAC. (But some do - more details below...) However, the unpleasant surprise is that LG made a staggeringly bizarre oversight in the implementation of the V30's DAC, which cannot natively support 44 kHz, 16 bit files. Why is this such a bizarre oversight? Because the overwhelming majority of all digital music available today is in 44/16 format, and this will get up-sampled to 48/16 on most music apps, including the native LG music app. Sensitive IEMs need less power and can expose audible errors in the 16-bit integer representation of gain interpolated as a result of the up-sampling at low volume. These artifacts were first pointed out by @kundica on the main V30 thread (to hear this effect, listen on sensitive IEMs to the opening of Pink Floyd's Dark Side Of The Moon at volume level at or below ~15 via the native LG music app). Luckily, there is a solution to this. The Neutron and UAPP Android apps are capable of playing back all PCM files at their original sample rate - including 44/16 format files. They do this by bit-padding 44/16 files to 44/24 (a process that creates no audible artifacts), which the ESS DAC then processes natively without up-sampling. Neutron's interface can be confusing for new users - it has an awful lot of features and options - but it's able to play back all PCM (44, 48, 96, 192, 384 kHz) at native sample rate, has an awesome parametric EQ and is under intense active development. Support for native playback for 44 kHz and hi-res PCM files is also now available in UAPP (USB Audio Player Pro). This is significant because UAPP also allows streaming via Tidal and the official Tidal Android app will not play back 44/16 files without up-sampling. Both UAPP and Neutron are able to export bit-perfect data via USB-out, for those that want to use external DAC/amps. Spoiler: DSD A very brief background... PCM = pulse code modulation, which is the most common digital audio representation. It simply stores an amplitude value (usually represented as a 16- or 24-bit integer) over a series of discrete points in time, the gap between which defines the sampling frequency, f=1/dt. DSD = direct stream digital, which uses pulse density modulation. Instead of representing amplitude as a function of time, in PDM the amplitude is represented by the density of the pulses. Not everybody is a fan of DSD these days. For example: https://forums.linn.co.uk/bb/showthread.php?tid=23096 The following is a verbatim quote from Rob Watts that addresses some of the technical limitations (as he sees them) of DSD: I'm not here to bash DSD - I have some outstanding DSD recordings, but I suspect the key is just that I have some outstanding DSD recordings. In other words, the recordings themselves are what's most important and it seems that in many hi-res or DSD albums, a little more care was taken with the recording/mixing/mastering process. Moving on from the controversy over the format itself - if you have those files, you still want to be able to play them... DSD files with the .dsf extension can be played back via the stock LG music app or Neutron. Both these apps can play back DSD64 and DSD128 via DoP (DSD over PCM - which is a brilliant little trick that is audibly equivalent to native DSD playback). The latest UAPP update now allows it to do the same. Neutron can even playback DSD256 files (through some software trickery), which the stock LG music app simply refuses to play. Neutron and UAPP can also output bit-perfect DSD over USB to an external DAC. For iso files ripped from SACD, things are a bit more complicated. I know some users have been looking for an app that can handle these files. Neutron can't play iso files directly. Many thanks to @zenmastering for pointing out that UAPP does have some iso file support. A few of us have been testing this. I've not had much luck so far, but YMMV. You may get lucky with UAPP. Other apps like Kamerton are able to play iso files, but convert the audio to 48 kHz PCM. I'll keep updating this section if this situation changes. Spoiler: Bluetooth on the V30 Would you really buy a phone with a 3.5 mm socket, a high-quality DAC and amp, and then by-pass all of this using Bluetooth? If so, you're on the wrong thread. You probably want an iPhone. They're magical. Apparently. And Apple's removal of the headphone socket vastly improves the audio quality and the user experience. According to Jony Ive. In case you hadn't guessed, I'm not a fan of Bluetooth. I do own several Bluetooth headsets - some of them actually sound pretty good, and I understand the convenience factor. However, there's no Bluetooth codec yet developed that can losslessly transmit the files discussed in this post - not even AptX or AptX HD. And even if your headphones and transmitter both support a particular codec, what you'll actually get is the lowest common denominator of each, given the prevailing connection quality; and this could easily drop back to SBC and you'd never know, given the poor audio quality you'd be expecting anyway via Bluetooth. Bluetooth requires you to keep your headphones charged, but still run the risk of them failing at a crucial moment - not just because of the batteries running flat - the headphones can simply become unpaired when connections drop, which is a 100% guarantee at some point; dropouts are a regular occurrence with Bluetooth. BT headphones' built-in DACs tend to be poor, their built-in amps tend to be cheap, the quality of the headphone drivers themselves tends to be sub-par. Bluetooth sound quality is simply no match for the best wired headphones. I'm sure it will be one day, but that's many years in the future. Don't believe Apple's lies. They dropped the headphone jack for one reason only. Money. They want to make more money by selling your their own BT headsets, and they want to make even more money by charging a license fee every time you connect a wired headphone or external DAC, since the only wired connection to the outside world is now Apple MFi proprietary. If you're a V30 owner, you have a really high quality DAC and amp if you simply plug in a good pair of wired headphones P.S Thanks to @VI001101106 for the following tip for BT users: If you have an aptX-HD capable headset, you can 'force' an HD connection in the BT settings once they're paired to the phone. Spoiler: MQA The jury's still out for me on Merdian's Master Quality Authenticated format (MQA). There are several parts to Meridian's technology (https://en.m.wikipedia.org/wiki/Master_Quality_Authenticated) and whether or not you think it makes an audible difference, there is some fascinating technology behind it. Let's get the obvious point out of the way first. Many very smart people do not believe in hi-res anything: https://people.xiph.org/~xiphmont/demo/neil-young.html I think it's also worth mentioning @SomeGuyDude's emphatic and decisive take-down of hi-res recordings. I'm quoting the first part of his post (https://www.head-fi.org/threads/lg-v30.858933/page-126#post-13930854) here verbatim - no syllables changed for effect: "PFfffhhahahahahahaahahah" As you can see, not everybody's convinced by hi-res and MQA only expands on this hi-res revolution/controversy/snakeoil (choose whichever word you want there). From Stereophile: "MQA is a flawed solution to an increasingly archaic problem (compression). Supporting MQA in any way undermines superior non-proprietary technology, and paying for MQA is like hiring someone to rob you." You can find the full article below: http://flip.it/mRmeJv Could MQA have anything to offer? It looks like Meridian are trying to do something in their DACs, but oddly, their treatment of an impulse-response doesn't actually seem to require an MQA file: http://flip.it/vgA24u There are some theoretical outlier arguments for hi-res w.r.t. noise floor on recordings that might be made in the future with much greater precision than anything used currently, played back using TOTL equipment and gain riding, plus the timing of sharp attack transients, but for the most part, it's questionable if even your dog will appreciate hi-res audio, as every part of the chain - including amps, speakers/headphones have to be capable of extending that far and responding to ultra-fast transients. I spoke to Bob Stuart of Meridian about all this a while ago and he gave me a reference to a paper citing a meta-analysis where it was claimed ~52% of people could hear the difference with hi-res music. That's not very compelling. (FYI, 52% is about the same success rate one could have achieved in identifying the hi-res file by simply flipping a coin.) But the tech is interesting, so let's press on... Even if you're a hi-res believer, MQA isn't lossless - it sacrifices noise floor for sample rate in order to be able to fit the hi-res audio into a container not much larger than that of a regular 44/16 CD file. Something has to give with that level of compression. MQA applies lossy compression to data representing frequencies above those of redbook CD (44 kHz). So even if you're a hi-res believer, you're not getting a perfect delivery via MQA. Furthermore, there are some that question the ethics behind MQA - suggesting that it might not benefit any of us (other than Bob Stuart) in the long run: https://www.linn.co.uk/blog/mqa-is-bad-for-music The following is a more recent look at MQA, with many technical references for those interested in reading further: https://www.computeraudiophile.com/...-of-controversies-concerns-and-cautions-r701/ If you've read this far but are still wanting MQA directly on your V30, the official word from Tidal is that their Android app doesn't support it. (Update: 3/1/2018 - it does now.) But this particular rabbit hole goes a bit deeper... Firstly, you can actually play MQA files via the stock LG music app. The USB tool audio_flinger doesn't correctly report MQA output, but a real-time analysis from REW, recording V30 output directly, shows that the LG music app's MQA output does indeed create high-frequency output, beyond that of 44 kHz CD files. (Note that MQA files are designed to play back at 44 kHz when MQA decoding is unavailable in hardware or software, so this makes it difficult - some would argue impossible- to know whether MQA is actually working properly on your device.) The other issue with Tidal is that even though they don't properly curate material in their Android app, it does appear that the entire catalogue is there and accessible - it's just that you can't easily and directly identify which files are MQA via the Tidal app (thanks to @Left Channel for pointing this out). One suggestion has been to bookmark (i.e., add to your playlists) MQA files from the desktop app, and then play them back from the Tidal app. 44/24 FLAC files from Tidal do play back properly (no up-sampling) on the V30 quad DAC, so yes, MQA will sound better What about higher-sampling rates? One major problem with MQA - and all hi-res formats - is the surprising lack of hi-res (> 44kHz) content in most hi-res tracks. Check out this site: http://www.2l.no/hires/ All but one of the recordings listed in the above site have no content at all over 22 kHz. Some have no content over 11 kHz. So it's obviously not a coincidence that the corresponding MQA files are almost the same size as those of redbook CD. This situation isn't uncommon - there are many vendors offering for sale hi-res albums that actually aren't. See for example: https://www.head-fi.org/threads/bandcamp-promotion-thread.648932/page-2#post-13283024 Still feel like handing over large sums of money to re-purchase or stream all your music in hi-res?!? If so, you're actually in luck. Correct Tidal playback of all PCM and MQA files through the V30 DAC is now available via the UAPP app. (This update dropped 4/25/2018.) The official Tidal app also now correctly support hi-res (24-bit and higher sample-rate MQA) through the V30 DAC, if you can find those tracks. However, the Tidal app still does NOT correctly handle 44/16 PCM, which is still a large proportion of Tidal's catalogue. This up-sampling problem is far more significant than MQA, so UAPP is the best choice for Tidal streaming. On the other hand, UAPP doesn't (yet) provide offline storage for Tidal. Spoiler: Some Thoughts on the V40 I got lucky a few weeks back, through having a friend who decided his V40 was a "PoS" (his choice of verbiage) and so I got a second-hand V40 cheap. It turns out this particular buddy of mine just didn't know how to use Android. The V40 is not a PoS. The good news is, everything in this thread applies to the V40 The bad news is, everything in this thread applies to the V40 In other words, LG have still not figured out how to make 44/16 PCM play through the DAC without re-sampling via the Android mixer. But the current (as of 12/5/2018) versions of UAPP and Neutron are working perfectly for me, just as they do on my V30. I'd read a couple of comments on headfi about how the V40 just didn't sound as good as the V30. I'm afraid I was massively skeptical of those claims. Apologies to those folks who made those posts, because sure enough, my initial listening impressions were exactly the same - noticeably muddier and less resolving. But that was using the LG Music app. I've since gone back and done various SPL-matched A/Bs with the V30/V40 using the current version of the UAPP app and I honestly can't tell the difference. Both measure ruler flat: which begs the question, did LG really pay Meridian for this "tuning"?!? I could have sold them a Z-weighted file full of zeros for much less. I know I should probably have tested with the LG Music app too, but honestly if LG don't care about their music app (enough to make sure it correctly plays back the most popular digital music formats in existence), then I don't care about it either. I never use the LG Music app on my V30. I have no plans to ever use it on my V40. You shouldn't either (for the reasons discussed at the bottom of this post). As with the V30, THD and THD+N measure the same (at the same SPLs), regardless of mode (normal device, aux or high-impedance). The V40's volume steps aren't the same as those on the V30. LG chose to offer more fine-grained control at lower volumes (a good thing, IMHO). But SPL-matched, I can see absolutely no difference in THD(+N) between the two phones. A quick aside: Somebody had asked on one of the threads recently about how to match the volume levels, i.e., is there a formula to figure out what number to set the volume to (at a give mode) in order to match SPLs. Sorry for not replying to that question earlier. Unfortunately, the answer requires someone smarter than me. The sensitivity of every headphone is different, and every track can be mastered differently, so I don't know any easy starting point for this task. The only reliable way I know of closely matching SPLs is with a coupler, mic and SPL meter or a multimeter and a headphone with a precisely-known sensitivity. Here are my overall impressions of the V40: Pros: 1) More cameras. I guess more is better. ¯\_(ツ)_/¯ The zoom-lens might be handy. 2) The "boombox" feature. I don't think I'd use it very often, but if you forget your headphones and your BT speaker, the V40 does play louder (and digs into the lower frequencies slightly better) than the V30 through its speaker. You can actually feel the back of the case vibrating. It's not stellar audio quality by any means, but it's quite cool. 3) Speed. I've never felt my V30 was slow, but the response of the V40 is really snappy. Definitely a step up. 4) The display quality is far superior to that of my original V30. To my eyes, the V40 display looks perfect. (However, you don't need to go to a V40 to get that better display. LG seemed to have fixed this problem by the V35 and even later runs of the V30. I now also have a later model V30 that has an equivalently-perfect display to that on the V40). Cons: 1) It's too big (for me). I can just about reach everywhere on the V30's screen with one hand. I can't do that with the V40. And it's not like the display is really bigger in any meaningful way - width is the same as the V30, it's just longer. It looks like it's been made longer just to accommodate the notch. I'm neutral on the notch itself, but I wish the phone weren't so long. 2) The V40 has two additional hardware buttons that are totally unnecessary. Why can't the back fingerprint button still be the power button? And "Hey/Ok Google" brings me to the Google assistant, so why do I also need a button for that? Those two buttons just introduce additional weaknesses and potential failure points into the structure. Check out what happened to my friend's V40, and notice where it happened: My verdict on the V40: it's an excellent phone. For audio, the V40 is pretty much a wash with the V30, but the V40's speed and responsiveness is notably better. If it weren't for its size, the V40 would have already become my primary phone. Spoiler: Useful Miscellaneous Apps I've assembled a few suggestions here from our awesome headfi community that can make your V30 experience even better. Many thanks to @seanc6441 (a fellow earbud enthusiast!) for the suggestion on the Button-Mapper App: https://www.head-fi.org/threads/mus...s-for-the-lg-v30.868978/page-31#post-14726846 https://play.google.com/store/apps/details?id=flar2.homebutton&hl=en_US This allows you to set options such as long-press or double-press on the volume buttons to effectively give you hardware controls for previous/next tracks and play/pause. Many thanks to @archy121 for the tip on the Precise Volume app: https://play.google.com/store/apps/details?id=com.phascinate.precisevolume&hl=en_US This allows you to set different volume presets to control increments, default and maximum levels, plus it also has EQ capabilities and (very usefully!) allows you to lock the volume control to media by default (instead of controlling ringer volume). More info here from @archy121: https://www.head-fi.org/threads/mus...s-for-the-lg-v30.868978/page-36#post-14765207 Many thanks to @dragion for the link to LG's HiFi Status app, that tells you what output mode the V30 is in: https://play.google.com/store/apps/details?id=com.apptrio.hi_fi_status&hl=en And many thanks to me ( ) for this one... Tasker Tasker is one of the best reasons to use Android. It allows you to create actions or Tasks, that can be automated to make your life easier and happier. Even without root, you can customize your Android phone to do all sorts of useful things. Two quick examples below: Automatically Reset the V30's Volume Level when Plugging in Your Headphones The V30, at maximum volume, in high-impedance mode, driving sensitive IEMs, could probably damage your hearing in seconds. Why risk it? The following tasker profile and action automatically lowers the volume each time you plug in your headphones: 1) Open up Tasker and go to the "Tasks" tab. 2) Click "+" (bottom right) to add a new task. Let's call it "Volume Down!". 3) Now click "+" again to add an action. Choose "Audio", then "Media Volume". I selected level 4 (out of Android's usual 15 - but don't worry, this will scale to 4/15*100% of your HiFi DACs volume). 4) Now go to the Profiles tab and click "+" to add a new profile and select "State", then "Hardware", then "Headset Plugged". 5) When the "New Task" menu pops up, select the one we just created: "Volume Down!". Now every time your headphones get plugged in, your V30 will reset itself to a reasonable volume. Automatically SMS Your Current GPS Location to Your V30 Whenever You Park Somewhere Unfamiliar This one's a bit more involved, because I don't want an SMS trigger every time I park. (It quickly gets annoying if you get pinged with a GPS location every time you park at work, home, or any other familiar place that you regularly visit. 1) In the Tasks tab, we're going to create four new tasks (using the "+" button) called "AwayFromHome", "AwayFromWork", "AtHome" and "AtWork". For each one, we want the action selected to be "Variables"->"Variable Set". This is how you want to set each one: AwayFromHome: Variable name: %AtHome, Set To: 0. AtHome: Variable name: %AtHome, Set To: 1. AwayFromWork: Variable name: %AtWork, Set To: 0. AtWork: Variable name: %AtWork, Set To: 1. 2) Next, we want to create another task called "Park", for which we're going to add several actions in this sequence: Get Location: Source GPS, Timeout 60 s. Variable Set: Variable name: CarLoc, Set To: %LOC Wait 30 seconds (The reason you need this is your phone has to have enough time to decide if you're really inside or outside of the geofence(s) we'll set up in a minute - to save battery, it doesn't constantly check for this. Go to Preferences in Tasker using the upper-right hamburger menu, then click on the "Monitor" tab and scroll down and activate the option that says "Use Motion Detection". You need to do this to make sure the location updates more rapidly when you're actually moving - obviously it doesn't need to check as often when you're not.) If %AtHome neq 1 & %AtWork neq 1 Send SMS: Number: Your mobile/cell number, message: "Car: http/maps.google/com/maps?q=%CarLoc" (Don't use the quotes in the message.) Endif Tip: If you get stuck finding any of the above functions in the menus, Tasker has an awesome search function. 3) In the Profiles tab, we need to describe the scenarios that will trigger these actions. You'll first want to create two profiles called "AtHome" and "AtWork", which have an action for both the event (entering the geolocation zone) and the exit event (leaving it). You don't need high-precision for this, so cell tower-based location is perfectly adequate and doesn't add the possible battery drain from constant GPS queries. Both these are "Location" profiles. You'll want to set your new locations for your home and work and/or wherever else you park regularly and where you don't want to be pinged with GPS alerts. You have the choice to select NET or GPS. I recommend a generous (0.5 mile) radius with NET only and put the pins on your relevant location(s). The task you'll select for your home will be "AtHome". You then want to touch and hold on the green arrow pointing to that selected task and choose "Add Exit Task", then select "AwayFromHome". Do the same thing for your other location(s), e.g., work, making sure to match the appropriate locations and tasks. Now when you move in and out of your selected geofences, the variables we chose above will get set appropriately. Now create one last Profile called "BTConnect". You want this to trigger on a State - in this case "Net"->"BT Connected". You should provide the name of your car so that you don't trigger this each time you disconnect from your BT headphones. Then add whatever tasks you want when connecting to your car's bluetooth, e.g., I often use this one: Media Volume 14 Send Intent: Action: au.com.shiftyjelly.pocketcasts.action.PLAY (which starts playing my podcast app) You can adjust this to play whatever you'd like, or just do nothing by adding a dummy task, like waiting for 1 s. The important part here is you're now going to add an exit task. Once you've set the main task, hold on the green arrow until you get prompted to add an exit task. Then choose "Park". Done! 4) It will also be useful (when trying to find your car after parking in an unfamiliar location) to go back and add one more Task called "FindCar", which will do the following: System->Send Intent. Action: android.intent.VIEW, Data: google.navigation:q=%CarLoc&mode=w If you want to get fancy, you can even add a little icon to this and then pin it as a widget to your home screen. Now, if you're in an unfamiliar place and can't find your car, just press the "Find Car" icon and google maps will open up in pedestrian (walking) mode and immediately start navigating you back to your car. Cool huh? Good luck getting this level of customization from an iPhone - even jailbroken with Cydia installed! P.S. The SMS-send was just for fun - I like to have the GPS coordinates sent to my phone and watch as a text message just as an extra backup. You don't need to do this if you're sure you're never going to lose your phone as well as your car Note that none of the above Tasker actions require root. Of course, if you have root, there are more things you can do with Tasker... Spoiler: Rooting the V30 Would you buy a laptop or PC if the shop owner refused to give you the root password? That's the odd situation we're in these days, where Google, Apple, and many other smartphone manufacturers decide we need protection from ourselves (?) because we can't be trusted with root. In fairness, the situation is complicated by the higher security risks associated with easy root access (if it's easy for you to get root, it's easier for others too, and unscrupulous individuals could do nefarious things to your phone). Some folks on this thread have rightly expressed concerns about privacy in this digital age. One thing you can be sure of - there are people out there that you don't know, who know way more about you than you could possibly imagine. Your smartphone carries a lot of your personal information, so OEMs can use this as an excuse to lock you behind their own walled gardens. @Dannemand mentioned another cynical reason for OEMs not wanting you to root or jailbreak - it can extend the life of your device. (Apple regularly introduces new software tweaks exclusively to their latest models, when older devices could easily support those same software changes.) I'm sort of on the fence here, because one major concern I have about LG is that its smartphone division has been making huge losses for years. What if they decide to call it quits? Anyway, personal irrelevant rant over... Why root? Because at that point, you can basically do anything you want with the device you paid for. Some useful examples are giving Tasker the ability to do pretty much anything, Greenify (stop processes you're not interested in from chewing up your CPU and battery), Xposed framework (customise look and functionality of your phone), audio customisations (e.g., force high-impedance mode without a dongle). For example, my rooted V30 has the DTS:X 3D stereo option, which is normally only available on the V40. Root access also allows you to remove bloatware from your device - for example, rather than simply disabling nonsense like Facebook, you can experience the joy of completely deleting it A Word of Warning: Root at your own risk. I've personally never bricked a device from jailbreaking or rooting, but in theory it's possible (at least with the T-Mobile variant of the V30). If you don't know what you're doing there is a possibility that you might get your phone into a state where you don't have the knowledge to fix it. You may get obvious symptoms like boot loops, or more subtle issues like your modem firmware no longer supporting your usual LTE bands, etc. Before you even consider rooting, it's worth reading up on the necessary steps and technical verbiage. Many thanks to headfi's Android-rooting expert, @Dannemand, for the information below: https://www.head-fi.org/threads/lg-v30.858933/page-325#post-14743077 Most people tend to stay current with security patches and software updates, so what you'll almost certainly need to do is the following: 1) Downgrade to a previous firmware with a known vulnerability in the bootloader. 2) Unlock the bootloader with the beautifully-named "What" hack. 3) Flash TWRP onto your device 4) Configure in TWRP, then flash Magisk, and other useful utilities (such as disabling root-check). You'll need access to a Windows machine (or a virtual machine running Windows), as many of the tools needed are Windows-only. The procedures are described in detail on the XDA forums: https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193 I strongly recommend you take their advice when they say to re-read the instructions multiple times before starting, because it only takes one small oversight to potentially cause you a world of pain. (Also, be careful to choose the correct firmware for the What bootloader-unlock, because the link that ChazzMatt gives includes multiple patched firmwares.) T-Mobile customers please read those instructions even more carefully than others. I take no responsibility if anybody gets into trouble or destroys their device trying this. Edit. One important addition suggested by @Dannemand: Even if you choose not to root your V30 right now, if you have any possible plans to do so at some point in the future, you might want to hold off installing any system updates unless and until it's been confirmed that those updates don't prevent your ability to roll back your firmware (as this would prevent you from rooting, unless another exploit were discovered later). You can alway upgrade (by flashing a patched firmware) at a later stage, after you've rooted the device. The Bottom Line: Recommended Music Apps for the LG V30 1. Neutron - for all on-device storage playback, other than MQA. Why? It correctly plays DSD via DoP (up to DSD128 directly and DSD256 with some software trickery) and PCM files (up to 352 kHz) at original sample rate through the internal DAC or via the USB digital-out. Recommended settings: Under the "Audio Hardware" menu, select "Generic Driver" ON,. (which also has a sub-menu: Generic Driver -> Hi-Res Codec = ON, Generic Driver -> Hi-Res Speaker = ON), "Direct USB Driver", "DSD over PCM (DoP)" and "Follow Source Frequency" options. Note that the "Direct USB Driver" option is just for USB output. Using the latest update under Oreo (Android 8), these settings don't need to change. A great tip from @james444 - by default the V30 only has a brightness slider in the pull-down notification shade, but you can configure it to add a volume slider too, by pulling that shade all the way down, selecting "Edit", tapping the top-right hamburger menu, and toggling on "Volume". This is useful, because Neutron doesn't (yet) give you access to the fine-grained volume control when the quad DAC is active. By configuring the shade to have a volume slider, you don't need to leave the Neutron app in order to recover that fine-grained volume control. 2. UAPP - for all on-device storage playback, Google Play music and Tidal streaming. Why? The latest UAPP update now properly supports the V30 DAC for all PCM formats and MQA. USB digital-out works properly for all formats. More information is available here: http://extreamsd.com/index.php/hires-audio-driver Recommended Settings: Under "Settings"->"Internal audio driver", select "HiRes Direct Driver". Under "Settings"->"HiRes Audio"->"HiRes driver flags", toggle on "Direct PCM" and "MQA". N.B. If your V30 is running Oreo or Pie (Android 8 or 9), you only need to turn on the "MQA" option here. Under "Settings"->"HiRes driver audio format", leave this option as "Auto". Under "Settings"->"HiRes Audio"->"Buffer Size", I recommend using a 600 millisecond buffer length. USB digital-out has a little bug right now in UAPP, which requires you to disable the "HiRes Direct Driver" option to work properly. (Many thanks to @yklee118 for this tip!) The developer is aware of the issue and it will hopefully be fixed in a future release. (Update - this issue is now fixed in the later UAPP updates. One recommendation though - when using UAPP to drive an external DAC, you might need to increase the buffer size in "Settings->USB Audio Tweaks" beyond the default. I find 8192 frames works well.) 3. Poweramp - for all on-device storage playback, other than MQA. Why: Thanks to a tip from @ctheanh, we have now discovered a third app that can play 44 kHz/16-bit PCM without re-sampling! Poweramp has a very nice UI and also works with Android Auto for local device-storage playback. Recommended Settings: Audio->Output->Hi-Res Output->Wired Headset On. Settings (to the right of this): Enable: On. Sample Rate: Unfortunately, as far as I can tell, you need to set this manually. 4. The stock LG Music app: At this point, there's really no reason to use LG's music app, other than for MQA files stored on-device, which is probably a rare scenario. Why? It cannot play back 44/16 PCM without up-sampling, and this causes artifacts that are easily audible with sensitive IEMs. It also cannot push anything out via USB that isn't re-sampled to 48/16 PCM. Update 6/2019: On Android 9 (Pie), the stock LG music app now seems to be much less aggressive in grabbing the hardware DAC and as a result, I'm now seeing all forms of redbook and hi-res PCM being intermittently re-sampled through the Android mixer. I've logged this issue with LG, but I wouldn't hold out any hope of them fixing anything. 5. Your favorite 3rd party music app: You probably want to give this a miss. Why? If it's not listed above, it's probably safe to assume your app does NOT work properly with the V30 DAC. Audio will still route through the V30's DAC and amp, but all 44 kHz, 16-bit PCM files will be re-sampled to 48 kHz. If you're not sure, feel free to post here and if we find another app that does play bit-perfectly through the V30 DAC, I'll update this post. Happy listening P.S. Another update warning! Just when we'd ironed out the bugs and glitches from Android 8 (Oreo), we now have a new set of problems being caused by Android 9 (Pie). Other than UAPP (v 5.2.0 and newer), most music apps (including Neutron and LG's own music app) are not consistently using Direct mode in Android Pie. Poweramp is another option that is working correctly in Android Pie, but you need to set the sample rate manually (see above).