Infinity Pure

Part 01What “Infinity Pure” actually does

Infinity Pure is a single toggle inside Anantar Ultimate. Tap it on, reboot once, and Infinity Player becomes the only process the DAP's audio device will accept. The Android audio server — which normally mediates every sound on every Android device — leaves the path, and the bits from your file reach the FPGA untouched.

With Infinity Pure on, your DAP stops behaving like a phone running a music app and acts as a dedicated CD transport — one job, one process, one path. The volume slider drives analogue attenuation in the DAC instead of nudging digital samples. Notification dings disappear. The audio subsystem becomes a single-purpose tunnel from file to ear.

As a user, you don't need to know how the swap is implemented. You flip a switch in Anantar Ultimate, the device reboots, and on the next boot Infinity Player owns the audio device. Flip it back off, reboot again, and the device returns to ordinary Android behaviour — everything else (apps, library, accounts, settings) is untouched either way.

iBasso's own MangoOS, the stripped-down second OS on DX-series players, works on the same principle: with Android out of the path, the music app alone owns the audio device end-to-end. But you reboot into it, losing streaming apps, browsers and system services. Infinity Pure gets the same direct path without leaving Android — apps, accounts and streaming stay.

Infinity Pure is not just an “exclusive mode” flag inside the player. It is a system-level handover of the audio device — the same idea as MangoOS, applied inside Android instead of replacing it. That is why it requires a reboot, and why no Android music app on the market — Neutron included — can produce the same result from userspace.

Part 02Why the Android audio server matters — even when it doesn't resample

A common misconception is that the headline Android-audio problem is sample-rate conversion. On a modern DAP it is not: the DAP's standard HAL already passes the file's native rate through — 44.1 to 384 kHz — with no resampling. So if Infinity Pure doesn't escape something Android was doing wrong with the rate, what does it actually do?

It removes audioserver (AudioFlinger) from the path. Even without resampling, the audio server still has four effects on what the DAC sees:

• Software volume. AudioFlinger multiplies every sample by the stream-volume scalar. At reduced volumes, the lowest-significance bits are gone before the DAC ever sees them.
• Buffer chain. App buffer → mixer buffer → HAL buffer → ALSA — four links, each adding latency. Infinity Pure has one.
• Cross-process IPC. Frames hop between processes before reaching the kernel. Each hop is a context switch the scheduler can delay; small but not deterministic.
• Shared device. The audio server keeps the stream alive for any notification or system click that might want to mix in. Infinity Pure switches the device to exclusive.

Part 03How playback reaches the DAC — before and after Infinity Pure

The clearest way to see what Infinity Pure changes is to draw both paths next to each other. First, how every Android music app on DX340 — Neutron, UAPP, Hiby, Tidal, the stock player — reaches the DAC today:

Neutron and UAPP do everything an app can do inside the Android sandbox — high-priority audio thread, native-rate request, codec-gain writes in “Direct” mode. But every frame still passes through audioserver on its way to the kernel. The mixer thread, the software gain stage, the four-deep buffer chain, the IPC hop — they don't go away from inside the sandbox.

Now flip Infinity Pure ON and reboot. The same chain collapses into this:

Three things change in a way the user can feel:

• One owner, one path. The kernel holds the audio device exclusively for Infinity Player — no notifications, no keyboard click, no other app can write a sample.
• Native rate, single buffer. Same 44.1–384 kHz the standard HAL already preserves, but through one buffer instead of four — less latency, less jitter.
• Bit-perfect volume. The slider writes directly to codec_volume — analogue attenuation in the DAC, no software multiplier eating bits.

Part 04What we can prove — on-device diagnostics

Audio claims should be testable. We won't pretend Infinity Pure scores better on a 1 kHz sine at the DAC pins: iBasso's standard Android HAL already measures excellently, and the analogue output looks similar in both modes. Infinity Pure can prove what no meter shows: who owns the audio device, and whether the path is what we say it is.

The two snapshots below come from a real DX340 running the same FLAC file in two different scenarios. The commands are ps (which app is alive), lsof /dev/snd/pcmC0D0p (which process holds the audio device), and cat /proc/asound/card0/pcm0p/sub0/status (what state the kernel device is in). They are reproducible on any unit.

The two snapshots put the whole argument on one screen. Same output sample rate (96 kHz), same DAC chip, very similar meter readings at the headphone jack. What differs is structural — and structurally provable: the kernel reports the audio server as device owner in scenario A, the music app itself in scenario B. This is not subjective, and no sandboxed Android player can produce it, however clever its code.

In other words: Infinity Pure's value is not “measurably louder/quieter/cleaner at the jack”. Its value is determinism — you can prove, on demand, that nothing else is in the path. And once you have that proof, every other claim built on top of it (bit-perfect volume, lowest latency, no system-sound interruption) becomes verifiable rather than promised.

Part 05Side-by-side: Infinity Pure vs Neutron / UAPP / typical Android player

How the path compares with a normal Android music app — Neutron and UAPP included. Those are excellent players; the difference is not skill, it is what an app is allowed to touch.

In one sentence: an app can only be as clean as the Android sandbox allows; Infinity Pure sets the sandbox aside and lets the player own the audio device directly.

Part 06Streaming use case — Tidal & Qobuz under Infinity Pure

A common question: if Infinity Pure owns the audio device exclusively, can I still stream Tidal or Qobuz? Yes — that is the point. Streaming runs inside Infinity Player, not as separate apps: the Tidal and Qobuz browsers, library, playlists and player are one process. When Infinity Pure hands Infinity Player the audio device, hi-res streaming comes with it.

This is what MangoOS cannot do. On MangoOS you reboot into a stripped Linux that has no Tidal app, no Qobuz app, no network streaming stack — just local files. Infinity Pure keeps you on Android, so the WiFi stack, the streaming SDKs, and your accounts are all still alive while the audio path stays single-owner.

• Native rate end-to-end. A 24-bit / 192 kHz Qobuz stream stays 24-bit / 192 kHz from the CDN to the DAC. No transcoding, no resampling, no software-volume scaling on top.
• Gapless streaming. Infinity Player pre-resolves the next track's CDN URL ~5 seconds before the current one ends, so album-mode Qobuz/Tidal listening crosses tracks without the usual streaming gap.
• Exclusive device, even while streaming. WiFi can interrupt, the network can stutter, but no other process on the device can write a sample — the kernel still reports Infinity Player as the sole owner of /dev/snd/pcmC0D0p.
• Same volume rules apply. The slider drives codec_volume directly — analogue attenuation in the DAC. Streaming hi-res at low volume is not bit-reduced.

In short: Infinity Pure + streaming is the scenario MangoOS was never designed for, and the one ordinary Android players can't cleanly deliver. It is the reason this approach exists inside Android instead of on a separate OS.

Infinity Pure is one of two features in this product that genuinely cannot be reproduced by an Android app — the other is direct FPGA harmonic tuning. Both depend on owning a layer of the operating system that ordinary apps cannot reach. That is the difference between a player on a DAP and a player that is the DAP.