安卓端的开源通话录音工具,能把通话双方的声音一起录下来,不需要 root,也不用连电脑。通话录音本身需要 shell 级权限,项目给了两条路:默认用内置 ADB 在手机本地配对一次;已经装 Shizuku 的人直接选它,省掉配对环节。两种方式在设置向导里随时切换。录完还能转写、生成摘要,方便事后翻查通话重点,处理全程留在设备端,无广告、无账号,除非手动打开 Drive 备份,音频不出手机。代码以 GPL-3.0 发布,项目从 ShizuCallRecorder 分叉,重新架构后用嵌入的 ADB 自包含运行,不再硬依赖 Shizuku。想留通话存证、又不想折腾刷机的 Android 用户适合从这里开始。
Recording call audio needs shell-level privilege. CallVault gets it one of two ways — pick either in the setup wizard, and switch whenever you like:
| Built-in (default) | Shizuku |
|---|---|
| Pairs once, on the phone itself. No other app, no PC. | Already run Shizuku? Nothing to pair — choose it and go. |
CallVault is a fork of ShizuCallRecorder (Copyright © kitsumed (Med)), re-architected to run self-contained over embedded ADB, so it no longer needs Shizuku — and still runs through it, as a second mode, if you prefer. It is a modified, independent version — not endorsed by or affiliated with the original author. See NOTICE.md.
Recordings are Opus in an .ogg file at 24 kbps by default (AAC/.m4a also available, 8–128 kbps), saved to a folder you pick and can open in any other app. CallVault can also write BCR's metadata file beside each recording — off by default — so tools built for BCR, such as bcr-gui, can read your calls' details.
[!NOTE] App-call capture depends on your phone's audio stack and on each app's own build. Verified so far on OnePlus 12 (OxygenOS 16) and Galaxy S24 FE (One UI 8.5) — reports welcome. Carrier Wi-Fi calling (VoWiFi/VoLTE) is not covered, and an app call that starts before CallVault is ready is lost rather than recorded late — the routing is fixed the moment the call begins. Bluetooth headsets are fine, including AirPods; only LE Audio is untested.
|
|
|
|
| Search | Transcripts settings | Recordings settings |
|:---:|:---:|:---:|
|
|
|
|
Both run on the phone, on the CPU, with no account and no network.
Transcription uses whisper.cpp. Two models — 190 MB, or 574 MB for better quality — downloaded once over Wi-Fi.
Summaries use llama.cpp with Google's Gemma. It is a 2.6 GB download and needs a similar amount of memory to run, so it wants a recent phone; CallVault states the cost before it downloads anything.
Speaker labels come from the call's own two channels, not from a voice model, so they cost nothing extra. One tap tells CallVault which side is you, and it renames every past phone call too. App calls stay as Speaker A and Speaker B.
[!NOTE] Pick your language rather than leaving it on auto-detect — detection is unreliable and can transcribe a language phonetically into the wrong alphabet. A long call is transcribed in passes and takes a while, but it is not refused.
| Leaves the phone? | |
|---|---|
| Recordings | Only if you turn on Google Drive backup |
| Transcripts, summaries, notes | Never |
| Speaker names, contacts, call log | Never |
| Analytics, telemetry, crash reports | None exist |
CallVault reaches the network in three places, and nowhere else: GitHub, to check for a new release (on by default, roughly daily); Hugging Face, to download a model you asked for; and your local network during pairing, to find the phone's own debugging service. Drive backup goes through Android's own file picker using the Drive app already on your phone — there is no login in CallVault, and it never talks to Google's servers itself.
arm64-v8a). On Android 11 the screen must stay unlocked during a call.[!IMPORTANT] CallVault leans on hidden Android APIs, so behaviour varies by OEM and can break on a new Android release. On phones that aggressively kill background apps (OxygenOS, MIUI, One UI), allow it in Auto-launch and exclude it from battery optimisation — see dontkillmyapp.com.
On OPPO, OnePlus and Realme phones there is one extra switch to flip before anything works — see below.
Built-in mode is CallVault's own, and the default. It pairs once, on the phone, and needs no second app at all. It is the default because it can do more, not because Shizuku is an afterthought.
Already running Shizuku? CallVault supports it directly. Choose Shizuku mode and there is nothing to pair, no wireless debugging to switch on, and CallVault starts no debugging of its own — it borrows the privilege Shizuku already holds. Phone calls record, and everything that happens afterwards — transcripts, summaries, search, tags, playback and export — is identical. What differs is capture-side only.
Switch whenever you like; any setting a mode couldn't honour comes back when you switch away. The table is the honest difference between the two.
| Built-in mode | Shizuku mode | |
|---|---|---|
| In both modes | ||
| Phone calls, both sides | ✅ | ✅ |
| Transcripts, summaries, search, tags, playback and export | ✅ | ✅ |
| Where they differ | ||
| Works without installing another app | ✅ | ❌ |
| Nothing to pair, and no wireless debugging of CallVault's own | ❌ | ✅ |
| After a reboot, recording starts again by itself once the phone is on Wi-Fi | ✅ | Only with Shizuku's own auto-start (Android 13+, trusted Wi-Fi) |
| App calls (opt-in, Android 14+) | ✅ | ✅ |
| Speaker labels | ✅ | ✅ |
| Keeps recording if Android kills the background process (opt-in) | ✅ | ✅ |
| Recording away from Wi-Fi (opt-in) | ✅ | ❌ |
| Full bug-report export | ✅ | ❌ |
[!IMPORTANT] After every reboot, the phone has to be on Wi-Fi once before CallVault can record — in either mode. Android clears the debugging access CallVault starts from on every reboot, and it can only be set up again over Wi-Fi. Any network will do, for a few seconds, with no internet needed — your home Wi-Fi joining automatically, or another phone's hotspot. There is no one-time setup that removes this without root. CallVault tells you when it is waiting, so a missed call is not how you find out.
[!NOTE] Recording away from Wi-Fi needs USB debugging switched on — see the two debugging switches. It is armed over your network, and a reboot clears it. It comes back as soon as the phone joins any Wi-Fi network for a few seconds — it needs no internet, and a café or a hotspot will do. CallVault says when that is needed, so a missed call is not how you find out.
Download CallVault.apk from Releases, or add the repo to Obtainium for automatic updates.
[!IMPORTANT] Recording calls is regulated, and the rules differ sharply between countries and states — often every party must consent. This is your responsibility, not the app's. Where it helps, you can turn recording off for individual apps, or have CallVault ask each time rather than record automatically. Read the disclaimer before you use it.
CallVault can't be on Google Play — Play bans both call recording and the privilege mechanism it depends on. F-Droid is planned.
Then open it and follow the setup wizard: accept the disclaimer, grant permissions, pair once (or pick Shizuku), and choose where recordings are saved.
If a recording stops when you lock the screen, set Default USB configuration to Charging only. CallVault offers this during setup and from Settings.
[!WARNING] Not while you are using Shizuku, and not during a call. Changing the Default USB configuration restarts Android's debugging service. Shizuku's server is hosted by it and stops too, so you would have to start Shizuku again before anything could be recorded — and doing it mid-call ends the recording in progress. CallVault now declines the change while a recording is live.
[!WARNING] Keep the pairing: uninstalling CallVault wipes it and there is no way to restore it — you pair again from scratch.
Both live in Developer options, and they do different jobs. You don't need both on all the time.
| Your setup | On Wi-Fi | Away from Wi-Fi |
|---|---|---|
| USB debugging on + Recording away from Wi-Fi on (recommended) | ✅ | ✅ |
| USB debugging on | ✅ | ✅ until the recorder has to restart, then it waits for Wi-Fi |
| USB debugging off, Wireless debugging on | ✅ | ❌ |
| Both off | ❌ | ❌ |
[!WARNING] Turning USB debugging off stops the recorder, even with Wireless debugging on — Android restarts its debugging service when the USB setting changes. On Wi-Fi, CallVault starts it again within a few seconds. Away from Wi-Fi it can't, and the notification says so.
If you switch Wireless debugging off yourself, CallVault leaves it off. The notification says recording is paused and has a button to turn it back on. If you'd rather CallVault switch it back on for you, turn on Keep Wireless debugging on for recording in the Recordings page's settings, under Connection (classic layout: Settings ▸ General ▸ Experimental; you're also asked during setup).
In Shizuku mode, Shizuku runs inside the same debugging service, so anything that restarts it stops Shizuku: turning USB debugging off, or arming recording away from Wi-Fi in built-in mode. Start Shizuku again from its app — CallVault tells you when that's needed and reconnects on its own once Shizuku is back. Shizuku started after USB debugging is already off keeps running.
ColorOS, OxygenOS and Realme UI refuse ADB permission grants out of the box. CallVault pairs, and then the privilege it needs is quietly denied — so recordings never start. This affects Shizuku mode too; Shizuku reports it as "the permission of adb is limited".
One switch fixes it, and it is not in an obvious place:
Can't see it? It is hidden in some translations, which is why people conclude their update removed it. Set the phone's language to English, turn the switch on, then set the language back — it stays on.
Flip it before pairing. If you already paired, restart CallVault afterwards: a session that started earlier keeps the permissions it had at the time.
Join the CallVault group on Telegram — the quickest way to ask a question, report something odd, or hear about a new build. Bug reports are still welcome as GitHub issues, which is the better place for anything that needs a log attached.
git clone --recursive https://github.com/madkongo/CallVault.git
cd CallVault
./gradlew assembleRelease
Needs JDK 17, the Android NDK (27.2.12479018) and CMake — the transcription and summary engines are built from source. Without a keystore at signing/callvault-signing.keystore the release APK builds unsigned; sign it yourself before installing.
Code shrinking stays off: the privileged recorder is launched out-of-process by app_process from a class named in a string, so R8 cannot see it as reachable and strips it.
CallVault is a modified fork of ShizuCallRecorder by kitsumed (Med); the original project's name, trademarks, and logos are the property of their owner and are used here only for this required attribution. The ADB pairing/mDNS code is adapted from RikkaApps/Shizuku (Apache-2.0).
Built on the work of:
Licensed under the GNU General Public License v3.0. ⚠️ Additional Terms under GPLv3 Section 7 apply (at the end of the license file), including trademark protection and the mandatory fork-attribution requirements that this project complies with.
CallVault is not affiliated with, endorsed by, or supported by kitsumed/ShizuCallRecorder, Shizuku, scrcpy, or Google/Android. "Android" is a trademark of Google LLC.
Recording phone calls may be subject to complex and varying laws in different countries and jurisdictions. You may need consent from all parties before recording. The developers and contributors are not responsible for any misuse or legal consequences. Learn more: Telephone call recording laws. This is not legal advice — consult a legal professional for your situation. It is your responsibility to verify that CallVault's behavior on your device complies with your local laws, and to stop immediately any activity that would constitute a legal infraction.
| 日期 | 榜单 | 排名 | 周期新增 | 总 STAR |
|---|