My knowledge on bluetooth is about zero. The Android audio system is used anyway when using BT. UAPP will just send audio in 32-bit floating point format with the sample rate according to the 'Android sample rate' selection in the app's settings. I don't expect the HiRes driver using a real HiRes direct path to the BT system.
Thanks Davy,
I changed the Android sample rate in UAPP from 44100 to variable, but there is no difference.
It´s really difficult to find technical discussion about aptX on Android.
Davy--FYI, since FiiO updated the X5 3rd gen to firmware 1.21 I have had a smooth playing experience with UAPP (4.3xx) and Tidal when listening through my Meridian Explorer2 USB DAC. This latest firmware claims to have added USB Audio to the X5. Plays Tidal HiFi and MQA just fine.
Previous firmwares I got dropouts and flickering lights but it looks like they really did something this time. I had had some minor errors when streaming Tidal with the new firmware (which could have been simply router proximity or other streaming issues) but I clicked on USB Tweak 2 in UAPP and it seems to have helped and have left it in place. Loving my X5 and UAPP with the DAC when I want to do the Tidal MQA thing;otherwise I prefer the UAPP Hi Res driver on the FiiO for non-MQA. Thanks again for a great app.
Davy--FYI, since FiiO updated the X5 3rd gen to firmware 1.21 I have had a smooth playing experience with UAPP (4.3xx) and Tidal when listening through my Meridian Explorer2 USB DAC. This latest firmware claims to have added USB Audio to the X5. Plays Tidal HiFi and MQA just fine.
Previous firmwares I got dropouts and flickering lights but it looks like they really did something this time. I had had some minor errors when streaming Tidal with the new firmware (which could have been simply router proximity or other streaming issues) but I clicked on USB Tweak 2 in UAPP and it seems to have helped and have left it in place. Loving my X5 and UAPP with the DAC when I want to do the Tidal MQA thing;otherwise I prefer the UAPP Hi Res driver on the FiiO for non-MQA. Thanks again for a great app.
The only true verification is capturing the audio output and doing frequency analysis. The next release of UAPP has support for the
Samsung S9+ (Qualcomm Snapdragon 845). If you have this variant and not the Exynos, all it should take is enabling the 'Direct' flag (and not any others) in the HiRes driver flags.
The hardware buttons on my Fiio X5III don't seem to be working despite the option being enabled. I know it worked a few versions ago, so I was wondering if anyone else if having this issue or is it just me?
I have just investigated the S9 Exynos version and the good news is that it will definitely play at 192kHz (proven by frequency analysis with RMAA and a sine sweep). However, there is no sign of a Direct mode being active and when you use the Android driver in 'Variable sample rate' mode, it also plays 192kHz (without resampling down and up). So I'm disappointed as well for it not having a direct mode. The Samsung music app shows the same behavior.
I have just investigated the S9 Exynos version and the good news is that it will definitely play at 192kHz (proven by frequency analysis with RMAA and a sine sweep). However, there is no sign of a Direct mode being active and when you use the Android driver in 'Variable sample rate' mode, it also plays 192kHz (without resampling down and up). So I'm disappointed as well for it not having a direct mode. The Samsung music app shows the same behavior.
May I ask if DSD64 native DSD / DSD over DoP support will be added.
Right now I am getting:
Output thread 0xe5105000 type 1 (DIRECT):
Thread name: AudioOut_85
I/O handle: 133
TID: 13054
Standby: no
Sample rate: 176400 Hz
HAL frame count: 7072
HAL format: 0x6 (pcm24)
I guess it means it converts the DSD64 to 176400Hz x 24 bit PCM?
May I ask if DSD64 native DSD / DSD over DoP support will be added.
Right now I am getting:
Output thread 0xe5105000 type 1 (DIRECT):
Thread name: AudioOut_85
I/O handle: 133
TID: 13054
Standby: no
Sample rate: 176400 Hz
HAL frame count: 7072
HAL format: 0x6 (pcm24)
I guess it means it converts the DSD64 to 176400Hz x 24 bit PCM?
Two more questions:
1. How do I know from adb output that the PCM is offloading to snapdragon DAC it internal ESS DAC? Thanks!
2. Sometimes I use USB 2.0 external DAC. May I ask what is the best setting for that in the USB tweak section?
Ex:
Tweak for devices with root access on/off
USB tweak 2 on/off
Buffer size
Bus speed
Also, what does tweak for root access do? If I uncheck it, will it reverts to the original system config? Thanks
Depends on your external DAC. Each behaves differently
My rule of thumb is, if it works don't touch anything
When using an external DAC, in my case I make sure that the audio driver is Android (to avoid conflict w/ internal DAC). Under USB tweaks I ticked "Use USB DAC", increase buffer to 16384. And under USB Audio, I make sure its Bitperfect (I like it).
I recommend to start w/out options and then experiment one by one and later combine.
Two more questions:
1. How do I know from adb output that the PCM is offloading to snapdragon DAC it internal ESS DAC? Thanks!
2. Sometimes I use USB 2.0 external DAC. May I ask what is the best setting for that in the USB tweak section?
Ex:
Tweak for devices with root access on/off
USB tweak 2 on/off
Buffer size
Bus speed
Also, what does tweak for root access do? If I uncheck it, will it reverts to the original system config? Thanks
1) I don't know. Perhaps some ALSA expert can explain
2) Like mickey says, if it works don't touch anything. However, you should enable USB tweak 2 for USB2 DACs.
Depends on your external DAC. Each behaves differently
My rule of thumb is, if it works don't touch anything
When using an external DAC, in my case I make sure that the audio driver is Android (to avoid conflict w/ internal DAC). Under USB tweaks I ticked "Use USB DAC", increase buffer to 16384. And under USB Audio, I make sure its Bitperfect (I like it).
I recommend to start w/out options and then experiment one by one and later combine.
Depends on your external DAC. Each behaves differently
My rule of thumb is, if it works don't touch anything
When using an external DAC, in my case I make sure that the audio driver is Android (to avoid conflict w/ internal DAC). Under USB tweaks I ticked "Use USB DAC", increase buffer to 16384. And under USB Audio, I make sure its Bitperfect (I like it).
I recommend to start w/out options and then experiment one by one and later combine.
Can you tell me which conflict there is? The internal driver setting should have no influence whatsoever on the use of a USB DAC with UAPP's own driver at least. You are also free to choose whatever buffer size you like of course, but please note that fixed frames values do not scale with sample rate. So 16384 is very safe for 44100Hz material (371 milliseconds), but if you are playing 192000Hz files it becomes 85 milliseconds which is on the low side. That's why the millisecond settng is preferred.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.