As with other discussions surrounding how Samsung has chosen to implement call recording... I'm not sure why it's such a taboo feature from a manufacturer standpoint: default the announcement to ON, agree to terms when disabling it.
In a one party state like Oregon for call recording, it's definitely a two party state for recording someone in person... But there's no announcement on the voice recorder app or other limitations. Same thing with video recording...
Even if Samsung utilized their AI to engage about the differences in state laws (like a tutorial) before being able to accept the terms, I think it could be done well.
This is an issue from Google not Samsung. There is a way around it. You can download the APK file for truephone dialer, then allow it under accessibility features. There is more to it than this. You'll have to find instructions online. Be forewarned: downloading an APK from a non-reputable site could introduce malware to your phone.
I'm interested to know if you have this working on the beta? Specifically for a non-rooted US Samsung phone. After messing with it and reading the xda forums for 30-40 pages on this topic/app, here are my observations:
This app is very versatile and will allow dropping down into the system dialer to initiate call recording, but doesn't seem able to initiate the recording itself. Therefore, the recording prompt is still there.
Sounds like it may be possible to initiate it with a magisk module, but that requires root.
You can use recording in true phone itself, but without root you're only going to get one end of the conversation (not the person on the other line) unless you use speaker phone, just like the other apps that don't have access.
What Samsung is doing is at the system level and I don't think there's an actual work around (that produces the same quality) without root.
It's surprising to me that this is a Google problem if Samsung can do it in other countries, Samsung phones can be imported that allow for it, etc. GrapheneOS has it baked in, no audible recording notification. I don't know if OnePlus does in the US or not... Or other oems running Android. If it's baked in at the system level (even with the recording notification as it is in this beta), it's hard to believe Google expects to shoulder the liability if Samsung doesn't put a voice notification at the beginning. What I mean is that I don't think it should matter to Google what Samsung does.... But maybe there's a licensing agreement? It's possible.
So I think it's each oem's problem from what I'm seeing. I'm intrigued to hear your thoughts on why it's Google.
I think true phone is a way around the voice notification, but much is sacrificed. Happy to be wrong about this too though:)
Thank you for sharing your observations and detailed thoughts on this topic! You've clearly done a deep dive into the issue, and we appreciate the effort you've put into testing and researching.
To address your points:
Compatibility with Non-Rooted US Samsung Phones: You're right that recording functionality on non-rooted devices is quite limited due to restrictions at the system level. It aligns with what we've seenāwithout root, apps often can only capture one side of the conversation unless using speakerphone, which impacts quality.
Samsung's System-Level Integration: Itās interesting that Samsung allows full call recording in other regions but restricts it in the US. This disparity could indeed stem from regional legal requirements or agreements, but the fact that imported Samsung phones or GrapheneOS offer such features suggests this isn't solely a Google restriction. It could be a combination of factors, including OEM licensing agreements and regional compliance.
Google's Role: We agree with your point about it being hard to believe Google would take on liability for Samsung's implementations, especially if Samsung omits audible notifications in certain regions. This does raise questions about how much of this is controlled by OEMs versus Android's broader policies. It might also reflect Google's conservative approach to liability and ensuring compliance with global legal standards.
Workarounds and Compromises: As you mentioned, apps like True Phone provide some alternatives but at the cost of quality and user experience. The limitations youāve pointed out, such as needing to use speakerphone or relying on root for full functionality, are a tradeoff for avoiding the built-in restrictions.
Magisk Modules and Rooting: While rooting provides more flexibility, itās not a practical solution for most users due to the associated risks (voiding warranties, potential security issues). Itās frustrating for users who just want seamless functionality without jumping through hoops.
Your insight about OEMs being the key players in implementing these features is compelling. Samsung and other manufacturers seem to have the capability, but their choices might be influenced by regional policies or their agreements with Google.
You're right that recording functionality on non-rooted devices is quite limited due to restrictions at the system level. It aligns with what we've seenāwithout root, apps often can only capture one side of the conversation unless using speakerphone, which impacts quality.
I'm glad to inform you that you are wrong, at least if you're using truephone instead of the stock Android dialer. I'm in the U.S. with the S24 Ultra that is NOT rooted. I am able to record both sides of the conversation without using the speaker phone and without giving a warning that the call is being recorded. There is no compromise other than having to trust truephone, the site where you download the APK and you do have to give it control of your phone in the accessibility settings. Also of note, the first time you try to set it in assessibility settings you will not be able to do so. You have to go to Apps and make exceptions for truephone B4 you can go back to assessibility and allow truephone there. It's a royal pain, required hours of research and quite a bit of time fiddling with it on the phone. Also of note, I did have it working B4 I installed the beta and didn't have to make any changes once the beta was installed. It just worked. I don't see why it wouldn't work if you start from the beta. I hope this helps! Good luck!
