IssueTracker

[Comment deleted]

Here is the log

4-12 22:46:25.855 5651-5651/? I/InCall: InCallUISystemDB - getSuppService: 0
04-12 22:46:25.855 5651-5651/? I/InCall: InCallUISystemDB - getTtySetting, setting: 0
04-12 22:46:25.865 550-550/CallRecorderService: mRecorder starting
04-12 22:46:25.865 5651-5651/? I/InCall: SecVoiceCallCardFragment -  - needToShowMenu
04-12 22:46:25.865 5651-5651/? I/InCall: SecVoiceCallCardFragment -  - showMenu: false
04-12 22:46:25.865 3158-15622/? I/APM::AudioPolicyManager: getInputForAttr() source 4, samplingRate 8000, format 1, channelMask 10,session 838, flags 0
04-12 22:46:25.865 3158-15622/? V/audio_hw_primary: adev_open_input_stream: request sample_rate:8000
04-12 22:46:25.865 3158-15622/? V/audio_hw_primary: in->requested_rate:8000, pcm_config_in.rate:48000 in->config.channels=2
04-12 22:46:25.865 3158-15622/? D/audio_hw_primary: adev_open_input_stream: call echoReference_init(12)
04-12 22:46:25.875 3158-15622/? V/echo_reference_processing: echoReference_init +
04-12 22:46:25.875 3158-15622/? I/audio_hw_primary: adev_open_input_stream: input is null, set new input stream
04-12 22:46:25.875 3158-5815/? I/AudioFlinger: AudioFlinger's thread 0xe9b80000 ready to run
04-12 22:46:25.885 3158-15622/? W/ServiceManager: Permission failure: android.permission.CAPTURE_AUDIO_OUTPUT from uid=10209 pid=550
04-12 22:46:25.885 3158-15622/? D/PermissionCache: checking android.permission.CAPTURE_AUDIO_OUTPUT for uid=10209 => denied (666 us)
                                                   
                                                   [ 04-12 22:46:25.895  3158:15622 E/         ]
                                                   Request requires android.permission.CAPTURE_AUDIO_OUTPUT
04-12 22:46:25.895 3158-15622/? E/AudioPolicyIntefaceImpl: getInputForAttr() permission denied: capture not allowed
04-12 22:46:25.895 3158-15622/? V/audio_hw_primary: stop_voice_note_recording
04-12 22:46:25.895 3158-15622/? E/audio_hw_primary: adev_close_input_stream, set jack_in to null
04-12 22:46:25.905 3158-15622/? E/AudioRecord: Could not get audio input for record source 4, sample rate 8000, format 1, channel mask 0x10, session 838, flags 0
04-12 22:46:25.905 3158-15622/? E/StagefrightRecorder: audio source is not initialized
04-12 22:46:25.905 550-550/MediaRecorder: start failed: -2147483648

Issue seem to be same with
VOICE_UPLINK
VOICE_DOWNLINK

But, does not affect
VOICE_COMMUNICATION
VOICE_RECOGNITION

Anyone? It seems this has gone unnoticed

No updates?

This change was intentional in M.
RECORD_AUDIO permission was too easy to acquire considering the privacy risk involved in allowing capture of voice call audio.
Also note that capturing from VOICE_CALL source is not supported consistently across the Android ecosystem and not mandated by the Android CDD.
The SDK documentation should be updated accordingly.

This essentially stops call recording for legitimate apps like mine and 200+ others.

There seems to be no other permission to acquire access to voice_call audio source. Are there any alternative permissions or plans?

Although it is not mandated, many manufacturers including Samsung, Sony, HTC, LG supported it.

I agree with  nihan...@gmail.com.

Call recording is a major feature for; lawyers, reporters, doctors...

The security aspect should be dealt with using the same methodology implemented for the location services.

I've just bumped into this inability to use the VOICE_CALL audio source on a new Android 6.0 device (DEXP Ixion E240 Strike 2). The MediaRecorder throws an exception when I try to start it during a call.

However, if I set the audio source to MediaRecorder.AudioSource.MIC instead of MediaRecorder.AudioSource.VOICE_CALL, it then works as it should. I guess that in countries where phone call recording is not welcome (such as Russia) this MIC mode can be used as a fairly good substitute to the VOICE_CALL mode. You'll hear your own voice clearly on the recording, and will still hear the other party's voice, but not as good as in the VOICE_CALL mode, however. But I guess this can be used as a workaround for now.

In fact, on the device that I mentioned (a cheap $50 phone), phone calls recorded with MIC are even better than those recorded with VOICE_CALL on $250 phones. So, the original idea to address privacy issues is not quite working anyway.

If necessary, create a separate, more specific permission than CAPTURE_AUDIO_OUTPUT, such as CAPTURE_VOICE_CALL to make it clearer to the users and the app developers.

It is sad to see this gone. A quick search on the Play Store reveals that there ware over 100 million combined downloads of call recording apps.

This shows people use it. Some times for safety, sometimes for not keeping, sometimes to keep memories of loved ones.

As #11 suggested, a new permission would solve privacy concerns

This change is done since Android 6.0, which is to prevent malicious 3rd party apps from recording voice calls, and we consider it's a benefit to user's security. This is also considered a good opportunity to OEM's business, because OEMs can only provide such voice call recording apps now.

Capturing from VOICE_CALL source requires the CAPTURE_AUDIO_OUTPUT permission. This permission is reserved for use by system components and is not available to third-party applications.

OEM's are also kind of third party between android os and users, and there is as i know no malicious apps in splay store and they could not be, and since android 6.0 users can disable any provided permissions and are aware twice of permissions they grant.

If the idea is to carve out business for OEMs so that third party app makers can't participate, that seems very unusual for Google and a dismaying change.

In the meanwhile, does any OEM provide call recording? The overwhelming answer looks to be no. Users have been resorting to rooting their phones, which opens up bigger security problems. A dialog that plainly asks if the user wishes to grant permission to a particular app to record calls would be much better.

Ironically, according to https://code.google.com/p/android/issues/detail?id=227947 , Google is one of the few OEMs to not undo this restriction. So the argument from within Google is that OEMs will provide call recording, yet Google itself doesn't provide this, and other OEMs are kicking it back to 3rd parties.

Meanwhile, the OEMs that are undoing it leave the user with a dialog that doesn't make it as explicit as possible that the recording permissions they are granting extend to phone calls.

What a stupid idea to limit CAPTURE_AUDIO_OUTPUT to system apps only... ;/

I am going to develop a new app for call recording, and this is a major issue. Waiting for google for help..

We're currently developing an internal recording app for our sales teams and this issue just pulled us back. Sad! :(

Cutting functionality for 3rd party developers is always a bad idea. Asking permission is there for a REASON. This should be no different than any other permission request to the user.

Absolutely, I am a regular person who sometimes need to verify what was said in a phone conversation. I feel that I should have that option and that Google should not disallow app makers from offering this option.

I don't think it's Google's place to restrict this permission for third-party developers. There are illegal uses related to this permission, but there are also many legitimate uses related to this permission. Google should not be making the decision that because there are a few possible illegal uses, everybody should be denied. In the case of recording received audio from a phone call If you are so inclined to do this illegally, all you need to do is tape a microphone next to the phone audio receiver. The illegal use is the responsibility of the developer and user not the toolset.

It seems few applications are able to stream voice_call into mic by using native code...

So this is either:

- a bug to have CAPTURE_AUDIO_OUTPUT only for system application

OR

- a SECURITY issue that native code can by-pass the permissions

This should be reopened

I have a Google Pixel and since Google is OEM in this case I would like Google to provide an app that I can use to record my calls. Currently such app doesn't exist and third party apps cannot record calls.

What is even more absurd is that current apps can request permission for MIC and record me during my phone calls - they just cannot record other party of the conversation. So "SECURITY" is clearly not a concern here - apps still can record things. Current situation just makes things not usable for legit apps.

Same problem as #25 above here with a Google Nexus 6P.

The problem still exists on Android O - Google, any update on this?
This has been clearly dragging for too long!

I suspect the problem can be worked around by using Oreo's new ConnectionService API, which seems to permit joining calls into virtual conference calls, where one side of the call could possibly be a call recording app.

It'd be nice if the intended interface worked, though.

Hello,
I remember my old Nokia n900 which natively recorded calls with very good quality. Today with Android it is not possible ... the technology is behind us 🤔

As usual, Google won't give two hoots unless it causes bad press or affects their bottom line enough.
Heil Google!

Heil Google!

it is stupid. it is just less security.

谷歌是个愚蠢的胆小鬼，根本就不存在的官司都让你紧张成这样。难道你真的以为靠这个就能阻止他们违法录音么？这样做导致的后果你们不知道？为我们着想？正常人会赞成这个么？逗我吗？

The workaround is you buy two phones and connect the speaker output of one of them to the micro of the another, and reciprocally :-D

I actually trust some 3rd side with my privacy more than any OEM, but as it stands would be great if Google would make an app by itself.
Many people want the abilty to record calls to have a record to not forget stuff, Google if you are taking are power to develop do it for us.

Google if you are taking *our* power to develop do it for us.

it is not only to record calls, it is the ability to have automated
answering systems

2018-02-04 17:05 GMT+01:00 <buganizer-system@google.com>:

--
from my gmail account

Is it true that  it is system wide permision, so i can sign the app bundeled with repo before build then compile ? Will this work?

I've won 2 court cases thanks to being able to record my calls and having the proof for the court that the otherside had lied to the court.
In the UK it is legally allowed to record a call without telling the other party. There is no telecommunications law against it. The only law there is comes under data protection laws, so that means I can't put it on the internet for everyone to listen to (without the other party's consent) but I can use it as evidence like I did in a court, or to give to the police as evidence, which I did to prove that my then landlord was threatenng & harassing me because I had complained about them not doing the repairs.
I've still got my first android phone that I keep as a backup in case of emergencies in case my daily phone breaks and needs repair/replacement. It's a Google Nexus 5 and it has NEVER been able to record both sides of a call unless I put it onto the speaker so it can (only just) record the other party.
I don't know if this is due to it being Google made or LG made, but it has prevented me from ever buying another Google or LG phone, and I'd really like to buy the new V30/30s/35ThinQ or V40/45 that is rumoured for later in the year.
I tried over a dozen different call recorders on it and none would do it except via the way mentioned.
6 months afterI bought a Sony Xperia Z1 Compact and that is perfect! It even has its own built-in answer machine in case you miss a call and don't want to use your telecom's voice mail service, for whatever reason. Mine at that time used to have a 25p charge every time you called the voice mail. So if I wasn't in cell range my phone couldn't get the call so it automatically went to voicemail so having the ability to record the voicemail was perfect when someone had left a number for me to call them on. I could play the recording and save an extra 25p (plus call allowance minutes) by not having to replay the msg or call it again later when I had a pen at hand.
I also had the compact Z3/Z5 and they also worked perfectly like the Z1C. My wife had the Z3C when I got the Z5C and I (sadly) sold the Z5C prior to the newer version coming out. Unfortunately the newer model wasn't a top spec device like the others so I didn't buy it, I went back to the Z1C and it's still my daily driver!
The newest versions of the call recorder app I use no longer work so I deleted them and I copied the older version app from my Nexus 5 and now it works perfectly again. I've also just found today (that's why I know about this thread) APKPure and it has the last 10 versions of the app so I'm going to go and do some testing.
The dev' wasn't bothered about helping and never mentioned anything about these problems so I don't know if he's got it to work on the newer OS but s/he only uses Samsung's phone to test the app on.
So I agree with the other comments above, Google should make a new permission so users can agree to a call being recorded because it's a necessity in this day and age when there's so many corrupt companies with corrupt staff/practices for us to be able to prove when they tell lies!

wow, this and especially the closure as a won't fix by " am...@google.com" makes me seriously consider dropping android, which I've been using for years...

I think we might have good news about Android P :
https://www.neowin.net/news/android-p-could-officially-support-call-recording
https://www.androidpit.com/android-p-news-release-features

Meaning we might have a feature of a built in call recording.
Already made some requests about it and related to it :
https://issuetracker.google.com/issues/110436314
https://issuetracker.google.com/issues/110433612
https://issuetracker.google.com/issues/73132010
https://issuetracker.google.com/issues/110374382

Samsung note 8 (android 7.1) - records only my voice.
Huawei p20 pro (android 8.1) -  records only my voice.
Samsung a9000 (android 6) - all good.
I have tried all audio sources in settings.

Can help to investigate with android studio

@42 Maybe try here:
https://stackoverflow.com/q/50970915/878126

This doesn't appear to work for the reasons mentioned above: https://f-droid.org/en/packages/com.github.axet.callrecorder/

wow this is garbage

We have a Wileyfox Swift (1st Gen). Before it was migrated to plain Android (from CyanogenMod) it recorded calls without issue. Now it appears we are caught by this problem too.
We understand this thread is really intended to address a development goal/this particular issue but we are desperate and have to ask: does anyone know of a potential solution we can try that doesn't involve rooting? If the solution is to switch to a custom ROM e,g, Lineage, which one would help us in this aim?
Thanks.

Lineage OS is Cyanogen (without Mod).

Switched to omnirom treskmod with my one plus 5t and I confirm the bug! With the oone plus original rom it was working fine 😥

Google, please enable native internal audio recording. I, like other users & devs are getting angry with Google's flippant banning or limiting of legitimate apps (i.e. Tasker fiasco), especially with little to no communication. ...Part of Android's popularity was and is it's open and universal nature. While perhaps not fully open, it provided many more possibilities than iOS. Unfortunately, in that regard, Android's policy changes seem to take their cues from Apple, deciding for users what is best for them. I do not like this practice, as it has lead to the end of some very useful and legal apps (Taker being a great example, along with Another Call Recorder). It disadvantages users who have legitimate uses for apps they paid for, and it cheats developers out of their hard work, with no recourse. Android's actions are harming future interest in app development. I do not believe privacy/security is the primary concern here. While I have suspicions on the real reason (legal pressure, OEM pressure, etc.), I expect Android to go back to their roots of open choice. If you close something off, users who drive Google's add revenue and Android popularity deserve to know why and deserve to have a real dialogue. Otherwise, iOS or another future OS development may throw you to the wayside.

I support this.

I do Support this Please look into it. Enable call recording in Android 9 .  "Google, please enable native internal audio recording. I, like other users & devs are getting angry with Google's flippant banning or limiting of legitimate apps (i.e. Tasker fiasco), especially with little to no communication. ...Part of Android's popularity was and is it's open and universal nature. While perhaps not fully open, it provided many more possibilities than iOS. Unfortunately, in that regard, Android's policy changes seem to take their cues from Apple, deciding for users what is best for them. I do not like this practice, as it has lead to the end of some very useful and legal apps (Taker being a great example, along with Another Call Recorder). It disadvantages users who have legitimate uses for apps they paid for, and it cheats developers out of their hard work, with no recourse. Android's actions are harming future interest in app development. I do not believe privacy/security is the primary concern here. While I have suspicions on the real reason (legal pressure, OEM pressure, etc.), I expect Android to go back to their roots of open choice. If you close something off, users who drive Google's add revenue and Android popularity deserve to know why and deserve to have a real dialogue. Otherwise, iOS or another future OS development may throw you to the wayside."

Why is Google taking control of every one.  Who authorized Google to do so...  Since Google is pre installing their apps into mobile,  we are forced to use it....  Google you are nothing but a spy.....  You are a third party platform....  I love yahoo,  Duck duck go.... I don't have any issues......  Fuck Google.....  Get out of peoples lifes.....  U need fuckin permission for everything....  Why u mother fuckin Google shit....  I sincerely request anybody out there to make a new mobile without fuckin Google apps in it....  Iam not a developer.  . If I was I would be creating something against Google. Fuckin US shit.....   Google has contributed more like terrorism,  crimes,  political ass licking jobs....  What else have u contributed...  Making peoples lifes misery.....  Everything was fine till 10 to 15 years back until this mother fuckin Google company came into existence......

You use gmail bro

It's up to the user to choose if an app can have a permission. Many OEMs aren't trustworthy, including Huawei, which sends sensitive information to the Chinese government!

There seems to be a new API in Android Q to record internal audio: https://android-developers.googleblog.com/2019/07/capturing-audio-in-android-q.html?m=1

>There seems to be a new API in Android Q to record internal audio: https://android-developers.googleblog.com/2019/07/capturing-audio-in-android-q.html?m=1

works great with e.g. youtube, but doesn't capture audio from calls, unfortunately.

Still no update? It's so bad this simple feature is prevented by the system

In Norway and many other countries, it is legal to record every conversation you yourself are a part of, including telephone conversations. It is not allowed to publish the recordings without the permission of everyone who took part in the conversation, but most people record telephone conversations for evidence purposes. It has happened several times that I have spoken to e.g. customer service where there has subsequently been a disagreement about what was said and when I have asked them to send the recording of the conversation they refuse. "It is for internal use only". Then a situation arises where the amount of evidence is asymmetric simply because Google refuses to let people use their Android phones to legally record phone calls.

New pixel phone user and I cannot record any of my calls now. This is disgusting that Google is not allowing me to do what is perfectly legal in Canada.

I believe this is just legal everywere at this point and Google is just taking away power from people to be able to record possible frauds due to them being a part of several ones.
This is detestable.

Supporting the topic to get this issue resolved.

This is required for more security

Google is supporting people who wish to make up a fictional record of events whenever the evidence cannot be found to disprove it. They give strength to the devil by doing so, as the devil is the father of lies. They are the enemy of all righteous persons because a righteous person is justified by the truth. There is no righteous justification for Google to prevent a person from creating a record of the truth for evidentiary purposes. What will happen to them?