Issue with upsampling to 48kHz on Roon ARC with Pixel 10 (ref#V60P0X)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Upsampling to 48kHz with USB Driver on Roon ARC on Android (Pixel 10)

Tell us about your home network

· Roon ARC

I use the Campfire Audio Axion on my Pixel 10 and the signal will be always converted (Sample rate conversion) from 44kHz to 48kHz. The Axion has an internal USB DAC and I have enabled the USB Driver on Roon ARC. I cannot change this behaviour and I do not understand why, In the past, this was working properly. My phone is the Google Pixel 10 running Android 16.

Did you change your phone, or has the beta driver previously worked on the phone?

No, I did not change my phone. It worked before on the same phone

Hey @Alex_Reusch,

Thanks for writing in and I’m sorry to hear about your playback issues in Arc!

We’re not currently seeing any devices with an active Arc install tied to your account which is odd. Could you please reproduce the issue and share a more specific track name?

If you perform a fresh install of Arc on your mobile device, do you run into the same issue?

Thank you!

I have uninstalled ARC and did a fresh install. Enabled the USB Driver. When I connect the Campfire Audio Axion, it sets the sampling rate to 48kHz. There is nothing I can do. It does not matter which song I play. Take for example: Till Tomorrow from the Album: Touch Yello.

I don’t think you mentioned that these are In-ear Monitors. This is the likely reason for setting 24-bit 48 kHz, i.e., it uses Android Audio for volume control and microphone.

As for why it worked before, I don’t know for sure, but I had a similar issue before, and it was the cable. You could also try restarting your phone to see if that enables the beta driver.

Well, restarting the phone is some of the very basic stuff that I assume to be done, before opening a support case. Why should the cable be an issue now? After it worked before? So why not check if it might be an issue with the USB Driver on Pixel 10 with latest Android release? Seems to be the more obvious issue here…

I plugged the Axion directly into the USB port on my Mac Mini where I do run Roon Desktop App. Configured the DAC in the midi setup of Mac OS and Roon is playing highres files 96kHz or 192kHz without any conversion. So the Axion works like a charm as it should. Which means it is not a cable issue, not an issue of the DAC inside the Axion.

In my experience, this needs to be done when selecting the beta driver and when connecting the DAC. For instance, when connecting my TANCHJIM Space just now, I had no volume control and gain until I restarted my Pixel 7 (Android 16.)

Not necessarily so, as not all cables are equal when it comes to Android (and iOS for that matter.) It may be worthwhile trying another.

The Campfire Audio Axion including the DAC works on the Mac?

See details Campfire Audio Axion

Also, the cable is a fixed part of the Axion, as it includes the DAC on and also the microphone and the control buttons for volume etc. The DAC is inside the USB-C Plug and therefore the cable attached to it should not have an impact on conversion. Can you rule out completely that it is not an issue with the USB driver on the latest Version of Android with service update of April 2026?

Any update? Again, it’s not a defective cable or DAC. It looks like an issue with the USB Driver on the Pixel 10 and with the latest Android update.

Roon support will respond to your ticket in due course.

Hello @Alex_Reusch

Thank you for the updates. I have tried to retrieve the diagnostic data from your account without success. Would you kindly provide us with the ADB logs during the connection of your DAC to the phone and playback startup using the guide below:

Connect your PC to Android phone and install ADB (instructions are here (all platforms)). Then:

  1. Type adb shell in terminal
  2. Type logcat v (ref: http://developer.android.com/tools/help/logcat.html)
  3. Reproduce the problem and let terminal print logs for 3-5 more seconds
  4. Select output from the moment you started the reproduction of the bug till the very end
  5. Upload the log here and let us know once you have done so:

https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external