All the above seems in line with my own findings: battery drain is around 7-10% per hour when connected to my desktop (usb 3.1 gen 2, usb-c to usb-c). Same happens when connecting it to my MacBook (usb 2.0, usb-a to usb-c).
@Paul - iBasso Is the drain on purpose, are you aware of this?
Unfortunately, even though I replied earlier to you that this didn't happen on the version of TIDAL I was using back then in combination with my DX150, the exact same problem happened to me today.
The player was 'choking' / 'stuttering'. When not using the "Master" option, no problems are there.
(WiFi is connected to 5 GHz / DX150 is on the latest official firmware, no modifications / TIDAL version: 2.12.0.905.8)
@Paul - iBasso does this behavior have something to do with Androids samplerate conversion? I believe (not sure) I read that on the DX220 you, as a company, figured out how to bypass this limitation for other apps than the Mango player, without the app adressing specific hardware of the player / or needing specific drivers. (like UAPP or Neutron Player do at the moment)
If this is true, is it possible to bring this functionality to the DX150 aswell?
edit:
source:
http://ibasso.com/cp_xq_dy.php?id=8401#page10
If I did read or interpreted that
incorrectly (which is more likely ), could you maybe explain the stuttering when using TIDAL with Master quality enabled from iBasso's point of view? (hardware or Android wise: what's actually happening with / on the device that causes this annoying behavior?)
Besides that, does it even make sense to use this option in TIDAL, at the moment, or will it be down-converted anyways with the current firmware / audio-system of the DX150 / Android?
...If samplerate conversion has nothing to do with this, could you look into this problem? I know that some similar stuttering problems, that were discussed on the FiiO forums, were solved by using the crossfade setting in TIDAL and setting it to 1 sec. However that option is gone, which limits my options on the client side.
However I'm not sure if it even is related and if this problem isn't caused by the TIDAL app itself, which makes it a lot harder to solve since we need to deal with TIDAL-support...
(To be fair: I noticed the same behavior on my previous device, FiiO X5 III, also when using TIDAL in combination with the Master setting, so no 'blame' to iBasso, it's probably an Android or TIDAL issue in the first place )