It has been a while since my last SP4000 update, which covered build 0.65.3. Since then, AKCFW has changed considerably—not only through new features, but through discovering and correcting several deeply buried A&K and Android behaviors.
The current milestone is AKCFW 0.77.6, now sealed as a Classic Audio Engineering Candidate for controlled testing. It is not yet a public Release Candidate, and Pure Audio remains a later phase.
What has changed?
A cleaner, more DAP-focused operating system
SP4000 is built on a general Android/Qualcomm platform containing many components intended for phones rather than music players.
AKCFW now removes or suppresses a coordinated collection of unused phone, SIM, carrier, SMS, IMS and cellular components. Additional unused camera, NFC, wireless-display, sensor-calibration and diagnostic services have also been addressed where testing proved it safe.
This work had to be approached carefully. Some apparently useless cellular services shared dependencies with Wi-Fi or caused Android to wait indefinitely when removed individually. The final design preserves the Qualcomm infrastructure actually required by the player while removing the unnecessary user-facing and background phone stack.
The old Tencent/Treasure app store residue is also gone.
Revised CPU and audio-process management
This became one of the largest areas of development.
AKCFW now identifies the active music application and places its work on the performance CPU cluster while maintaining a separate policy for the fixed Android audio stack. It supports:
AKMusic
Apple Music
Qobuz
Qobuz Connect & Roon Ready endpoints
DAC mode
Other compatible Android audio applications
The controller follows playback start, pause, resume and application handoffs. It also periodically verifies its own state and repairs placement if Android moves a process unexpectedly.
Playback clocks return to the normal idle policy when music stops. The system is no longer intended to remain unnecessarily elevated simply because an application is open.
Testing has covered native PCM (including FLOAT), DAR Max PCM, DAR Max DSD, streaming applications, deliberate placement disruption, recovery, reboot and unplugged standby.
Improved diagnostics with lower overhead
The Diagnostics section introduced in 0.65.3 has received considerable refinement.
AKCFW can retain useful boot, device-state, crash and optional usage information without constantly enumerating everything Android exposes. Device Usage Log and Verbose Kernel Log remain user-controlled, while internal state collection is more bounded and predictable.
Unnecessary Qualcomm Wi-Fi diagnostic activity such as continuous cnss_diag operation has also been suppressed without disabling normal Wi-Fi.
Boot Slots and component information
Settings → System Information now includes proper information for both physical boot slots.
Each slot can report:
Active or inactive state
Boot result
Installed AKCFW version
Firmware build
Audio profile
Versions of the modified AKCFW components
This also helped expose an important A/B Android behavior: both slots share /data, including package and compiler state. Several earlier approaches that appeared correct on one slot could break Settings after switching firmware.
That entire package transition was reworked. AKCFW now preserves stock APK naming and performs narrowly controlled cache handling, allowing clean movement between AKCFW and official firmware without requiring users to understand Android recovery internals.
Stronger recovery tools
Android Recovery now includes an AKCFW Recovery Tools section with:
Boot Rescue
Boot-diagnostic export
Direct recovery-log viewing
Persistent recovery ADB access
Boot diagnostics can be exported to compatible removable storage, including FAT and exFAT cards.
The recovery screens were also cleaned up so their spacing, wording and structure feel deliberate rather than like engineering controls bolted onto the stock menu.
Factory-reset resilience
Factory reset exposed several dependencies that ordinary upgrade testing could not reveal.
One build passed broad testing but failed after /data was erased because a required permission relationship had existed only in previously retained user data. That build was withdrawn, the clean-data contract was corrected, and onboarding was subsequently tested from an empty /data.
These failures are precisely why intermediate build numbers are not public releases. A failed build remains rejected rather than being quietly rebuilt under the same version.
Modernized AK File Drop
AK File Drop has been revised with more robust lifecycle and connection handling, safer file operations, and access to both internal and removable storage.
It now provides friendlier storage roots while retaining strict path containment and protection for areas that should never be exposed through the file-transfer service.
What does it mean to you? You can finally upload music over Wi-Fi directly to your SD Card, bypassing sending it to internal storage first.
Reliable Sleep Timer and Auto Power Off
The original A&K timer implementation contained several overlapping state paths and inconsistent exceptions.
AKCFW now uses one clearer implementation:
Sleep Timer stops active music at the selected time.
Auto Power Off shuts the player down only after the required inactivity conditions are satisfied.
Both controls cancel and restore their state cleanly.
Actual playback stopping and a real ten-minute physical power-off were tested on the player.
New user-facing controls
Settings → Extras has continued to grow while retaining the SP4000 design language.
Current additions include:
Android Auto enable/disable
Aurora Store installation control (great if you choose not to sign in to Google Services with your account)
TIDAL enable/disable
SD-card notification control
180° screen rotation
Playback Format Indicator
The power menu now provides Power off, Restart, and Close current app instead of offering shutdown alone.
The Playback Format Indicator follows native PCM and DAR output, including the correct final PCM or DSD presentation.
Protection against unwanted official updates
AKCFW no longer permits the online A&K updater to silently offer and stage a firmware version incompatible with the current CFW base.
Local firmware installation remains available. This is important now that official SP4000 firmware 1.05 exists while AKCFW is still intentionally developed from the known 1.04 foundation.
I have inspected 1.05. It contains some welcome changes, including manual-scanning code, but that feature is disabled by default (by A&K) and its exposed interface remains quite unfinished (sadly).
A future 1.05 rebase is recorded, but it will be treated as a separate migration after the current AKCFW feature set is complete—not rushed into the middle of development.
Current status
AKCFW 0.77.6 Classic Audio is the current sealed Engineering Candidate.
It has passed controlled testing with AKMusic, Apple Music, Roon, Qobuz and Qobuz Connect, including CPU placement, playback clocks, pause/resume handling, DAR modes, recovery behavior, deliberate state disruption, reboot and bounded unplugged standby.
A recent exploratory USB DAC test also passed 44.1, 176.4 and 192 kHz PCM operation without audio underruns or crashes. One visual quirk was found: the on-screen Playback Format Indicator can remain visible after USB DAC mode is closed even though the hardware has returned to its normal state. That correction is already tracked for 0.78.0 and is identified as purely cosmetic.
There is still work ahead: further resilience testing, the eventual Classic/Pure split, Companion integration and, later, evaluation of a clean official-1.05 rebase.
Still, compared with 0.65.3, the project is considerably more complete, more resilient and far better understood. Many of the hardest improvements were not glamorous new buttons—they were eliminating stock assumptions, hidden dependencies and failure cases that only appear during slot changes, factory resets, firmware rollback or prolonged real-device testing.
That is exactly what this engineering phase is for.
Support AKCFW ❤️
Project donations are always completely optional, but deeply appreciated. Every contribution helps support continued research, development, case studies and gives me more freedom to keep improving AKCFW and building better solutions for your devices.
-Adam