USB Audio Player PRO (UAPP): 24- and 32-bit playback, ubiquitous USB audio support for Android

[Brain Damage]

Hmmm, I may have just answered my own question but will share for feedback and in the event it is helpful to others. Solution was to select the "Use with Bluetooth output" checkbox:

Bear in mind that only LDAC will be able to decode 96kHz 24bit. AptX HD can only do 48kHz 24bit. So the BT codec your using will also determine the output you're listening too.
I have to go into Developer Options to change the default codec AptX to LDAC on both my LG V30 and V40.

 

[LoryWiv]

Bear in mind that only LDAC will be able to decode 96kHz 24bit. AptX HD can only do 48kHz 24bit. So the BT codec your using will also determine the output you're listening too.
I have to go into Developer Options to change the default codec AptX to LDAC on both my LG V30 and V40.

Thank you. Happily, HiBy RS6 transmits LDAC to my BTR5 receiver dongle without setting any developer options. I did have to enable LDAC codec on BTR5 using FiiO control app.

 

[MikeyFresh]

Hmmm...I just now tried a standard USB-C to USB-C cable (not OTG) connecting my Samsung Galaxy Tab S7+ to a Hidzs S9 Pro USB dongle DAC/HP amp, and it worked perfectly. No need for an "OTG" cable. So, there's that.

Perhaps OTG or host mode is now just baked into the Type C spec at this point? My CEntrance HIFI M8 v2 also works with a regular Type C cable, however others seems to report issues with the use of certain cables, and some cables even seem to retain the old directionality issue as well where it only works when connected in one direction and not the other.

Another curiosity would be the inclusion of a Type C OTG adapter in the box with certain phones, for example my Galaxy S10 came with one, why would they go to the expense of including that as an accessory if it were entirely unneeded?

If OTG is essentially baked into the Type C spec, then the proliferation of so-called OTG Type C cables is just marketing or semantics at this point.

 

[FlacFan]

I am thinking OTG configuration is needed as soon as one side is USB A, mini or micro. Both cable ends with C connector should be working right off the bat.

Cheers

 

[Chris Kaoss]

Almost. Yes.
Never had an issue with usb-c to usb-c.
But when it comes to usb-b, I've to use an OTG adapter, when the source is my smartphone.
For example connected with my desktop DAC.

 

[rozel]

I just wish that UAPP would work in TIDAL "Download" mode. Will this ever be possible? If not what's the issue?

 

[blotmouse]

I just wish that UAPP would work in TIDAL "Download" mode. Will this ever be possible? If not what's the issue?

Doubt it will ever be possible due mostly to complications around copywrite infringement and theft. Streaming services require certain safeguards when DL'ing software so you are less prone to just stealing the music and canceling your subscription (they do that inside their proprietary apps). They are usually downloaded in small broken data chunks to protected hidden directories and "stitched" together during playback, and then deleted automatically at a specified interval.
The companies would have to give the keys to their security model to a 3rd party vendor (UAPP). The same security model they use to convince/assure record companies of, that their content will be protected from rampant theft.

I don't know this is the exact reason, but that's my best assumption.

 

[Joe Bloggs]

I just wish that UAPP would work in TIDAL "Download" mode. Will this ever be possible? If not what's the issue?

We're not UAPP but I can confirm that we are prohibited from downloading TIDAL tracks in our apps pretty much for exactly the reasons blotmouse stated.

 

[DBaldock9]

Doubt it will ever be possible due mostly to complications around copywrite infringement and theft. Streaming services require certain safeguards when DL'ing software so you are less prone to just stealing the music and canceling your subscription (they do that inside their proprietary apps). They are usually downloaded in small broken data chunks to protected hidden directories and "stitched" together during playback, and then deleted automatically at a specified interval.
The companies would have to give the keys to their security model to a 3rd party vendor (UAPP). The same security model they use to convince/assure record companies of, that their content will be protected from rampant theft.

I don't know this is the exact reason, but that's my best assumption.

We're not UAPP but I can confirm that we are prohibited from downloading TIDAL tracks in our apps pretty much for exactly the reasons blotmouse stated.

In a similar situation - when the "Doctor Who" TV show came back on the air in 2005, it was available to be streamed from Amazon Prime Video. At the time, I was running SuSE Linux, but Amazon was using Microsoft specific DRM, which wasn't available in any Linux browser. So, I bought a Roku streamer which had an Amazon Prime app, that included the DRM key(s) to decode and display the show. Otherwise, I would have had to run Windows on my PC.

A year or two later, Amazon changed to some other type of DRM, which does work in Linux browsers - so Amazon Prime videos can be watched on my Linux PC.

 

[rozel]

Thing is I'm subscribing to TIDAL. If I use a DAC, attached to my phone in my car then I hear lovely sounds from TIDAL in download mode through the car's Aux-In. So what's the difference going through UAPP via USB? Makes no sense whatsoever - nothing to do with copyright imo

 

[Ferdinando1968]

With the allowed download, you have the binaries, containing the hi-res music tracks, inside your smartphone.
if you have a rooted smartphone, you can (in theory) have access to hi-res music tracks
(I think this is the potential copyright infringement).
I'm pretty sure the Tidal app doesn't work with rooted smartphone.
I believe instead that UAPP works, and could therefore allow access to audio tracks.

 

[MarkParity]

With the allowed download, you have the binaries, containing the hi-res music tracks, inside your smartphone.
if you have a rooted smartphone, you can (in theory) have access to hi-res music tracks
(I think this is the potential copyright infringement).
I'm pretty sure the Tidal app doesn't work with rooted smartphone.
I believe instead that UAPP works, and could therefore allow access to audio tracks.

But wouldn't the tracks be stored encrypted on your phone and then decrypted when played in Tidal, that's how I would do it anyway.

Perhaps the problem the music streaming providers have with allowing UAPP to download tracks for offline mode is trusting UAPP to accurately report the number of times a given track has been played while in offline mode, the artist would expect the 0.0000001p royalty for every time an offline track was played too.

 

[Ferdinando1968]

But wouldn't the tracks be stored encrypted on your phone and then decrypted when played in Tidal, that's how I would do it anyway.

Perhaps the problem the music streaming providers have with allowing UAPP to download tracks for offline mode is trusting UAPP to accurately report the number of times a given track has been played while in offline mode, the artist would expect the 0.0000001p royalty for every time an offline track was played too.

I also use UAPP on TIDAL, and (as far as I could tell) my listening stats are updated even if I use UAPP.
(besides, I see no theoretical difficulties in compiling statistics on the basis of what I request from the remote server, without needing a
specific player that keeps track of what I listen to).

Regarding the encryption of the tracks, I have no idea whether or not the official app encrypts the songs stored on the device.
(may not be necessary, as if you are not root, that part of the filesystem should not be accessible).

I can imagine 2 reasonable scenarios:
1) in which the stream is transmitted (and stored locally) encrypted.
The decryption would take place during play, using decryption keys that must be known only to the official app (otherwise it would be useless encryption).
And in this case the third-party app would have no way to decode the stream.

2) the stream is transmitted unencrypted, and encrypted by the app (official or third party) on a voluntary basis.
In this case you should trust that the third-party app does effective coding to avoid having the binaries exposed in the case of a rooted device.

This 'confidence' may not exist.

 

[dmagnan]

I have a problem with 24/96 and higher def music files: they aren't output by UAPP, only 16/44 files work. When I try to run hi def files UAPP then won't output anything until I restart it, then 16/44 only. I've tried everything I could think of in settings changes. Has anyone run into this? Any ideas?

 

[MarkParity]

I have a problem with 24/96 and higher def music files: they aren't output by UAPP, only 16/44 files work. When I try to run hi def files UAPP then won't output anything until I restart it, then 16/44 only. I've tried everything I could think of in settings changes. Has anyone run into this? Any ideas?

That sounds like a question you should send direct to UAPP support, @Davy Wentzler is usually very quick at replying in my experience.

Support would also need to know more about the specific devices you are using.