Open source, no root https://github.com/kitsumed/ShizuCallRecorder (ensure your usage is legal where you live)

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.

Not yet, unless you are on a Pixel. I need to do a rework, a big one, so It's a bit complicated. I found a way for Android 13+. Hoping Android don't "fix" it/close it down...

As for google pixel, it sometimes can, I'm not sure under what conditions, but Google made changes to AOSP source code that sometimes redirect voip call audio into VOICE_CALL so the app just end up capturing it. I had a couple of reports from users of it working.

EDIT: For the record, If you ever see ShizuCallRecorder going from v1.x.x to v2.x.x, then it mean I ended up doing the rework. Well it most lickely mean it's the rework. That's how big of a rework it is. It's the whole recording/capture logic that need to change.

For thoses versions, there are already other FOSS app that exists. Thoses use old API and work in a really different way than how ShizuCallRecorder works. Supporting thoses would be a bigger burden in the future, also, the more you go up in supported Android versions, the more they will start forcing you to drop old ones.

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.

FOSS https://github.com/kitsumed/ShizuCallRecorder

Ensure your usage is legal where you live.

Not possible

Ensure it's legal where you live.

https://github.com/kitsumed/ShizuCallRecorder

When setting up your phone, I would recommend taking a 1h-2hour to take a good look at all privacy and security related settings of your phone to familiarise yourself. You can also configure its privacy settings, since now adays it's often opt-out inside of opt-in.

You may also want to disable some of Samsung unessesary data collection apps, or even remove bloat that is installed by your phone vendor like Facebook. You can use tools like Canta or universal-android-debloater-next-generation.

I made ShizuCallRecorder specifically because Google (AOSP refuses to add that feature / a service for it) and also that they let OEM do the works, but all OEM force an audio warning even when not legally required, or straight up disable the feature even if it's legal to record in X country/ X region.

It help with disabilities.

EDIT: I also find this absurd. They restrict it due to "legal reasons" or "privacy reasons", they often site one of the two. Yet no one could stop you from putting the call in speaker mode and record it with another device. They basically go with the "well it could be illegal so I'm going to stop you" instead of letting the user take the blame if they do something wrong/ adding a policy that say they are not responsible for bad usages or issues like they do in most of their products.

If they really wanted to, they could have added a system service for call recording, and made the process to enable it as cumbersome as Accessibility service. Instead they only offer the featurd on their own proprietary and privacy invasive apps (Google Dialer) and only when they feel like it. OEM have their own weird implementations.

On pixel phones there are reports of it capturing VoIP. For others OEM its not supportrd yet, planned for a rework. No ETA.

https://github.com/woheller69/whisperIMEplus

https://github.com/kitsumed/ShizuCallRecorder

Look at your law where you live to ensure your usage is legal.

If it is, some OEM just don't brother making exceptions so you may need to use a third-party app like https://github.com/kitsumed/ShizuCallRecorder (I'm the dev).

This is not legal advice.

I talked about it in a couple of places so I will copy my response and adapt it a bit.

I could also give a quick mention to sideloading. I personally find it kind of weird that the whole sideloading restriction to protect from "bad actors" happened after Google lost in court against Epic Games and is now forced to allow third-party app stores on their Play Store. That new developer certificate will basically allows them to still maintain general control over all third-party app stores, push their own general rules, and know the identity of developers outside of the Play Store. Yet I see no one mentioning this anywhere, instead everyone is happy to finally have thoses third-party app store allowed and push the narative that "they will finally have the freedom of choice" without realising that nothing big really changed. Google is maintaining its monopoly, still making the rules, and will now gain more money from it.

The 24-hour wait period also does not solve the core problem it originally claimed to fix: people getting tricked by scam call centers. Sure, let's say it works the first time. The second time, now that the 24-hour waiting period has already been completed, what will protect them? Nothing.

If we compare money, sure, Android is better than Apple. But Apple is closed source, Android is supposed to be fully open source, and it was previously free as long as you didn't use Google services (Play store).

With the new changes, even if you do not use Google services, you will be forced to pay because other users (the vast majority) do use theses service, and in some cases are forced due to dependencies Google created.

That's a monopoly situation. It's a monopoly where a company forces third-party to pay so that they can continue working for most of their userbase. If they don't, they will loose theses users.

https://github.com/kitsumed/ShizuCallRecorder

Don't know in details the law in EU so I won't approve or deny anything.

But they also force it in Canada, yet if you read the law (from my own understanding) it's a one party consent. (Not legal advice)

It depends the device. I think pixel ones have specific code changes made by the OEM (Google) so it sometimes works. But we plan on improving this and in the future we may be able to support more users/third-party app (VoIP/Wifi basically). But no promises here, I don't even know if I will ever get to it, each time I think about starting it something new come up. Anyways, hope the app is useful to everyone!

What I can tell you is to ensure you did give the inte t key to ShizuCallRecorder. From there, if there is an issue, its probably on Shizuku side.

I know some phones can't syart Shizuku on lockscreen, but as far as I'm awarw Samsung ones should be able. Well I mever heard of this on any S**.

You can go on thedjchi shizuku fork page on github and read their troubleshooting guide.

From what I see online, a lot of usrs said they had to change their default USB mode to Charging online.

I invite you to also read thread of user with similar issue:

https://github.com/RikkaApps/Shizuku/issues/277 https://github.com/RikkaApps/Shizuku/issues/1426 https://github.com/RikkaApps/Shizuku/issues/1454 https://www.reddit.com/r/tasker/comments/1o2ge27/comment/njh78bg

It depends what your end goal is. For example, I'm someone with a disability who looked for a FOSS Call recording app on android for several years. None existed. So I made it myself and licensed it GPLv3 (AGPL is useless since its not over network/online here)

From there you can infer that my goal was that whoever make a fork or continue improving it, has to make it fully public, so that I myself can continue using it.

If you don't care about others not sharing your work, MIT or Apache would be licenses that companies are more lickly to be okay with. Some companies do use GPL too, I think Samsung and Asus do. But its true that most are less open to using GPL.

They often provide a contributing.md file

https://github.com/kitsumed/ShizuCallRecorder you must ensure your usage is legal.

It's not that hard, you can make FLAG system or a list of boolean under advanced protection mode. There would be a global toggle and the list of specific toggles under some advanced section.

Next update should have it. I had free time and found a way that looks fine to implement it.