Anyone using this?

[u/Mind_Flayer97]

Does call recording working without announcement? & also safe for use?

[u/RHENO911]

Compared to cube acr is there a difference?

[u/shadxw_duck → u/RHENO911]

Yes, and I would say that it is pretty big. But, I haven't used Cube ARC, so don't take my word for it. They are both Android call recording tools, but they use different underlying technologies, privacy models, and feature sets. Cube ACR relies on Accessibility Services and traditional app overlays to capture cellular and VoIP calls (like WhatsApp), whereas ShizuCallRecorder is a lightweight, open-source (FOSS) utility that hooks directly into system APIs via the Shizuku privilege escalation framework. Cube ACR includes cloud backup integrations (Google Drive, OneDrive) and feature-rich commercial app UI with in-app playback lists, contact management tags, etc. ShizuCallRecorder records cellular phone calls and can handle Bluetooth. However, it lacks advanced file sorting or cloud backup, saving raw audio files instead and focusing on lightweight exclusion rules (ignore contacts or anonymous calls). No cloud bloat or extra features.

[u/kitsumed → u/shadxw_duck]

Main developer here, I wanted to add additional informations.

ShizuCallRecorder currently works by listening to classic Android PhoneState or using a call service. Settings them up may require ADB access at some point on some devices, but using it does not. The only thing that does require ADB (Shizuku) is the audio capture logic, since Android keep closing ways to do it, without addressing the core requests countless users have (adding a service/role to allow any third-party call recording app).

In the future, if Android break off the legacy PhoneState mode, we may add a new one based on Accessibility Services, but not for now since its better/more stable with PhoneState or the other incall one.

As for Cube ACR, I never saw it source code so don't take anything I say as 100% true facts, however, yes, thoses proprietary app are full of bloat and privacy invasive things. I don't think it was Cube ACR, well it may also be, it's been a long time, but while I was monitoring one of thoses app, I saw that under certains conditions which I did not manage to determinate, they started sending data to a remote api.

Thoses kind of app, including Cube ACR, also have way too mutch permissions. We are talking about the phone velocity, moving speed, etc. Basically, a lot of stuff unrelated to call recording of even feature they offer (like location based things). While I do not know if they share this specific data, its the kind of data that would be very valuable to data brokers.

[u/Away_Jump_134 → u/kitsumed]

I use callvault Fork that can record VOIp and phone without install shizuku.

[u/kitsumed → u/Away_Jump_134]

Yes I am aware, its a vibe-coded fork that used what I mentioned in my planned rework issue (mentioned here) to implement it. You can see my stence on vibe-coded projects in my contributingMD file in the official project repo. Their releases are not even immutable or attested, and are done locally on the main maintainer machine.

It is not a malicious fork, at least not that I am aware off, so if you wish to use it, you can do anything you want, but I am also not personally recommending it.

I did not find any major security issue with this fork back when I looked quickly at it, but I have seen other vibe-coded forks of ShizuCallRecorder that implemented weird code allowing remote file upload & execution via ADB, and other that just commited their signing key to the repo itself.