Want something that runs in the background without lighting up the screen or showing notifications every two seconds. Needs to save recordings somewhere I can actually access them. Anyone have something that works properly on newer Android versions?
The short answer is that no single app works perfectly across all Android versions, and that is the honest starting point most threads skip over. On Android 9 and below, apps like Cube ACR and ACR Phone deliver solid two-sided recording. On Android 10 and above, Google tightened audio API access for third-party apps, which is why most standalone recorders now only capture one side of the call. The best performing options at this point are either OEM-native solutions built into certain phone dialers, or monitoring platforms designed from the ground up for background audio capture. Worth knowing before you spend time downloading five apps that all produce the same broken result. 
Mate, welcome to the most frustrating corner of the Android ecosystem 
I went through probably four apps before landing on one that actually recorded both people talking. Xnspy was the one that sorted it out for me. Runs quietly, logs everything to a dashboard you can check from any browser, no massive notification sitting there the whole time. If you want something that does not require a tech degree to set up, that is where I would start. Saves you the three hours of stuffing around I did first. 
Android Call Recording: API Restrictions and What Still Works
This is a topic that trips up a lot of users because the landscape changed significantly starting with Android 10 and has continued shifting with each update since.
Why the Problem Exists
Android uses a system called AudioRecord with different audio source constants. The one relevant here is MediaRecorder.AudioSource.VOICE_COMMUNICATION, which previously allowed apps to tap into both sides of a phone call.
What Google Changed
- From Android 10 onward, this audio source no longer grants access to the incoming earpiece stream for third-party apps
- Apps on Google Play are subject to additional policy review that flags call recording intent
- Background service restrictions introduced in Android 8 also limit how long apps can run silently
Approaches That Still Function in 2024
OEM Dialer Integration
- Xiaomi MIUI, OPPO ColorOS, and some Realme builds have native recording in the phone dialer
- These bypass third-party restrictions entirely because they operate at the system level
- Not available on stock Android, Pixel, or most Samsung models
Accessibility Service Method
- Some APK-distributed apps use the Accessibility API to stay active in background
- User must manually enable this under Accessibility settings
- Works on Android 11 and 12 with some reliability, patchier on 13 and 14
Monitoring Application Approach
- Apps built for device monitoring rather than standalone recording handle audio routing differently
- Cloud storage built in, so recordings are not lost if the device is wiped
- More consistent across Android versions compared to recorder-only apps
If you are on a non-MIUI device running Android 10 or above, the monitoring app route is where consistent results come from. 
What I keep thinking about with this whole topic is where call recording on Android is heading, not just where it is right now. Google has been narrowing the permission window for audio access with every major release. Apps that work today on Android 13 may break entirely on Android 15. The ones built around monitoring as a core function rather than recording as a side feature seem better positioned for that future. They are not trying to sneak through an API gap. They are designed for the use case from the base up, which tends to mean longer shelf life when OS updates roll out. Something worth factoring in beyond just which app works this week. 
Going to push back on the folk recommending Cube ACR as if it is still 2019. That app has serious issues on anything running Android 11 or above and the developer has been slow to address it. Half the five-star reviews on the Play Store are from users who tested on old handsets and never tried it on a current OS. If you are on a Pixel or a recent Samsung, your odds of getting two-sided audio from Cube ACR are not great. Check XDA Developers for your specific phone model before trusting any blanket recommendation. The results vary a lot by device and nobody here knows what phone you are actually running. 
Tested about eight apps over two months on a Samsung Galaxy A54 running Android 14. Here is the actual order of events. Downloaded Cube ACR first, one-sided recording only. Tried Boldbeast next, same result with slightly better audio quality on my own voice. Moved to an APK version of ACR Phone from the developer site, got inconsistent results depending on whether I was on WiFi calling or standard network. Switched to a monitoring app approach and that was the first time I consistently got both sides of the call recorded automatically with no manual steps each time. If you are starting fresh, skip the first three steps and go straight to the monitoring app category.
Call Recording App Comparison: Functional Analysis
Before selecting an application, it is worth mapping out the technical constraints against the available options. Most forum threads skip this and jump to recommendations without context.
Constraint Matrix by Android Version
Android 9 and Below
- Third-party apps can access VOICE_COMMUNICATION audio source
- Two-sided recording is achievable with standard microphone permissions
- Cube ACR, Boldbeast, and ACR Phone all function reliably here
Android 10 to 12
- API restriction limits incoming audio access for third-party apps
- Accessibility API workaround functions with user configuration
- Results are inconsistent and device-dependent
Android 13 and 14
- Background service restrictions tightened further
- Play Store distributed apps face additional compliance review
- APK-sideloaded apps have more flexibility but require manual installation and update management
Application Categories and Their Trade-offs
Local Recorders (Cube ACR, Boldbeast)
- Strength: Simple setup, no account required
- Weakness: Android version sensitivity, one-sided audio on newer OS
Monitoring Platforms
- Strength: Cloud storage, consistent background operation, cross-device access
- Weakness: Subscription cost, setup more involved than a standard app
OEM Native Solutions
- Strength: System-level access, best audio quality
- Weakness: Only available on select device brands
For users on Android 12 or above without an OEM dialer solution, monitoring platforms offer the most stable long-term performance. 
The framing of this question as an app problem is worth examining. What people are actually running into is an OS architecture problem that apps are trying to work around with varying success. Android moved toward a privacy-first audio model starting with version 10, and each subsequent release has closed more of the gaps that third-party recorders were using. The apps that still work well are not doing anything clever with audio APIs. They are either operating at a level the OS permits natively, like monitoring services with established background permissions, or they are on devices where the OEM left the door open through their own dialer code. Understanding that distinction explains why the same app gets completely different results depending on whose phone it is installed on. 
A friend of mine needed call recordings for a situation with a contractor who kept changing what was agreed verbally. She went through a few apps and kept hitting the same wall, only her own voice in the playback. What ended up working was switching to something built for ongoing monitoring rather than a one-off recorder. The recordings were stored to a cloud account automatically, so she could pull them up from her laptop whenever needed without having to dig through the phone. Not the most glamorous solution but it held up over several weeks and she had everything she needed when it mattered. Sometimes boring and reliable beats clever and flaky. 