Obsolete
Status Update
No update yet.
Comments
he...@gmail.com
Here is what I see.
In AudioRecord.h and in the MediaRecorder.AudioSource, the enum values differ.
In native code (AudioRecord.h), the values are ..
44 enum input_source {
45 DEFAULT_INPUT =-1,
46 MIC_INPUT = 0,
47 VOICE_UPLINK_INPUT = 1,
48 VOICE_DOWNLINK_INPUT = 2,
49 VOICE_CALL_INPUT = 3,
50 NUM_INPUT_SOURCES
51 };
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=include/media/AudioRecord.h;h=13e51eea1eb478517f677df0642b4d2221571192;hb=donut#l38
In Java MediaRecorder AudioSource, the values are ..
120 public final class AudioSource {
121 /* Do not change these values without updating their counterparts
122 * in include/media/mediarecorder.h!
123 */
124 private AudioSource() {}
125 public static final int DEFAULT = 0;
126 /** Microphone audio source */
127 public static final int MIC = 1;
128
129 /** Voice call uplink (Tx) audio source */
130 public static final int VOICE_UPLINK = 2;
131
132 /** Voice call downlink (Rx) audio source */
133 public static final int VOICE_DOWNLINK = 3;
134
135 /** Voice call uplink + downlink audio source */
136 public static final int VOICE_CALL = 4;
137 }
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=media/java/android/media/MediaRecorder.java;h=be4b489eb08683750fc2149184ab073e8528e6d4;hb=donut#l120
Now, if you look at AudioFlinger, any input source, whose value of stream type is >=
NUM_INPUT_SOURCES (i.e., 4), we will get an "invalid stream type". Because of the
mismatch of the enums, the Java API sets the value of VOICE_CALL stream type as 4.
So, the check fails and we get the failure.
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=libs/audioflinger/AudioFlinger.cpp;h=da7cc8a6aa62a9d66097a6d9c7c184d132df7c3d;hb=donut#l2245
Fix:
Set the values of the stream types to be the same in the Java and c++ code.
Hope this helps.
In AudioRecord.h and in the MediaRecorder.AudioSource, the enum values differ.
In native code (AudioRecord.h), the values are ..
44 enum input_source {
45 DEFAULT_INPUT =-1,
46 MIC_INPUT = 0,
47 VOICE_UPLINK_INPUT = 1,
48 VOICE_DOWNLINK_INPUT = 2,
49 VOICE_CALL_INPUT = 3,
50 NUM_INPUT_SOURCES
51 };
In Java MediaRecorder AudioSource, the values are ..
120 public final class AudioSource {
121 /* Do not change these values without updating their counterparts
122 * in include/media/mediarecorder.h!
123 */
124 private AudioSource() {}
125 public static final int DEFAULT = 0;
126 /** Microphone audio source */
127 public static final int MIC = 1;
128
129 /** Voice call uplink (Tx) audio source */
130 public static final int VOICE_UPLINK = 2;
131
132 /** Voice call downlink (Rx) audio source */
133 public static final int VOICE_DOWNLINK = 3;
134
135 /** Voice call uplink + downlink audio source */
136 public static final int VOICE_CALL = 4;
137 }
Now, if you look at AudioFlinger, any input source, whose value of stream type is >=
NUM_INPUT_SOURCES (i.e., 4), we will get an "invalid stream type". Because of the
mismatch of the enums, the Java API sets the value of VOICE_CALL stream type as 4.
So, the check fails and we get the failure.
Fix:
Set the values of the stream types to be the same in the Java and c++ code.
Hope this helps.
he...@gmail.com
i have Put in Manual Settings for Call Recorder Source as 0,1,2 and 3 All these
Settings only Records Voice Stream from MIC only there is no Such VoiceCall,
VoiceCall Incomming and Outgoing.
I think Google have missed some file to Support it Actual
Settings only Records Voice Stream from MIC only there is no Such VoiceCall,
VoiceCall Incomming and Outgoing.
I think Google have missed some file to Support it Actual
mi...@gmail.com
use vrecorder
ch...@gmail.com
android.media.MediaRecorder.AudioSource.VOICE_DOWNLINK ;
android.media.MediaRecorder.AudioSource.VOICE_UPLINK ;
These two option do not work!
Whatever I set it to VOICE_DOWNLINK,VOICE_UPLINK or VOICE_CALL, the resault is the
same as VOICE_CALL!
Please fix!
Thanks!
android.media.MediaRecorder.AudioSource.VOICE_UPLINK ;
These two option do not work!
Whatever I set it to VOICE_DOWNLINK,VOICE_UPLINK or VOICE_CALL, the resault is the
same as VOICE_CALL!
Please fix!
Thanks!
[Deleted User] <[Deleted User]>
I couldn't figure out how to star... But I need to call records because of my
business..
business..
su...@gmail.com
Fix this google you lazy fucks
al...@gmail.com
fix it to beat iphone
ba...@gmail.com
LOL! pls fix guys! come on
lo...@gmail.com
The issues related to this bug started over a year ago. Google's inability to fix
this bug presents a great opportunity for competitors to show the inferiority of
Google's support and community help.
this bug presents a great opportunity for competitors to show the inferiority of
Google's support and community help.
li...@gmail.com
Pls fix. I work in service for homeowners. This would help out for me to remember
appts and also to prove to them they had appointments set. PLSSSSSSS fix!!
appts and also to prove to them they had appointments set. PLSSSSSSS fix!!
jo...@gmail.com
[Comment deleted]
jo...@gmail.com
[Comment deleted]
[Deleted User] <[Deleted User]>
This is such an important feature. I have been receiving several threats and if this worked then i would be able to get a restraining order, however its broke so i cant. I use a Motorola Droid
as...@gmail.com
It doesn't work in Android 2.1.
te...@gmail.com
Eric Raymond has been doing a good job of selling the Android (Nexus1, etc) But this is an essential feature. Without it, I might as well use Symbian S60; they are Open Source now too. I'll hold out a little while longer for this, but not much.
ld...@gmail.com
Seems like this should be fixed.
ne...@gmail.com
Something new in Android 2.2 , are there 3 options work now ?
gu...@gmail.com
Tried in Froyo (2.2) and the VOICE_DOWNLINK option still records from the MIC, even when you are on a phone call. So it still does not work, and there seems to be no way to record the voice stream during a call.
jl...@gmail.com
I hate to admit it but android is starting to disappoint me. :-(
Maybe I must swallow my pride and become a iphone user since I see this as a requirement for a phone
Maybe I must swallow my pride and become a iphone user since I see this as a requirement for a phone
tp...@gmail.com
This issue started almost a year ago and still marked as New. Seems like ignored by developers..
mi...@gmail.com
Yes the issue should be fixed but I have to say... it's not directly just android related.
To get this to work the hardware vendors would need to include the correct libraries in there builds.
I think that this is why no googlers did any task on this, but they could at least have said this.
As AUDIO calls wont go directly trough the system (only the notifications) someone would need to write hardware drivers for the corresponding phones.
The audio is directly routed from the GSM chips to the audio in/out chips and to actually get hold of this streams it would need some driver that intercepts this or reroute it trough the phone (rerouting could cause problem with delays but outputing to two different places could be a solution).
My best bet is that some skilled coder (sorry Im not that skilled and dont have the time to digg that deep for it) could write a driver missusing the BT stack (the same as the FM Radio driver on Nexus/Desire does with the FM signal where the audio gets decoded on the chip and sent to the speaker but I dont know exactly if this goes trough the system or if they also bypass android because I havent seen any FM recording app until now (or dont know of one).
To get this to work the hardware vendors would need to include the correct libraries in there builds.
I think that this is why no googlers did any task on this, but they could at least have said this.
As AUDIO calls wont go directly trough the system (only the notifications) someone would need to write hardware drivers for the corresponding phones.
The audio is directly routed from the GSM chips to the audio in/out chips and to actually get hold of this streams it would need some driver that intercepts this or reroute it trough the phone (rerouting could cause problem with delays but outputing to two different places could be a solution).
My best bet is that some skilled coder (sorry Im not that skilled and dont have the time to digg that deep for it) could write a driver missusing the BT stack (the same as the FM Radio driver on Nexus/Desire does with the FM signal where the audio gets decoded on the chip and sent to the speaker but I dont know exactly if this goes trough the system or if they also bypass android because I havent seen any FM recording app until now (or dont know of one).
wi...@gmail.com
It would be useful if there was an API that indicated which AudioSources were supported on a device. Something like:
/**
* Returns those audio sources supported by the device.
*/
public int[] AudioManager#getSupportedAudioSources()
Not only would this allow developers to gracefully handle devices that don't conform, but it would also highlight to device manufacturers where they are deficient and provides a point of competition between them.
I think this may have been the intention of MediaRecorder#getAudioSourceMax but the contract is not clear whether it is the maximum source supported by the device or just the maximum value supported by the current build of the platform. And in any case it assumes all sources up to any including that source are supported which is a very linear view.
NB AudoManager would eb the right place for this method IMHO because it could be used from any input mechanism eg MediaRecorder, AudioRecord.
/**
* Returns those audio sources supported by the device.
*/
public int[] AudioManager#getSupportedAudioSources()
Not only would this allow developers to gracefully handle devices that don't conform, but it would also highlight to device manufacturers where they are deficient and provides a point of competition between them.
I think this may have been the intention of MediaRecorder#getAudioSourceMax but the contract is not clear whether it is the maximum source supported by the device or just the maximum value supported by the current build of the platform. And in any case it assumes all sources up to any including that source are supported which is a very linear view.
NB AudoManager would eb the right place for this method IMHO because it could be used from any input mechanism eg MediaRecorder, AudioRecord.
td...@gmail.com
Isn't there some kind of conformance test devices have to pass in order to get the Android Market? If so it apparently isn't very thorough.
wi...@gmail.com
Yes there is, but that test is only as good as the contract defined for it. And it also needs to cater for all types of devices, not just mobile phones.
This is why I like the idea of adding an explicit API mechanism to determine the functionality. It makes it clear to the device developer what they need to aim for. It makes it clear to any platform testers whther a device is suitable for its target environment/market. And it makes it clear to application developers at runtime whether the device is capable.
This is why I like the idea of adding an explicit API mechanism to determine the functionality. It makes it clear to the device developer what they need to aim for. It makes it clear to any platform testers whther a device is suitable for its target environment/market. And it makes it clear to application developers at runtime whether the device is capable.
co...@gmail.com
Please developers fix this and don't ignore this request! Android LACKS of the ability to record the voice of the caller and this is a SHAME!
em...@gmail.com
i did record both party audio streams from outgoing call for 30sec, but for incoming call it goes wrong..
So, its not the logic which was wrong but the device itself doesn't support..
Developers, please fix this..
So, its not the logic which was wrong but the device itself doesn't support..
Developers, please fix this..
mb...@gmail.com
i think it is all android(google) related, because even their own phones (nexus one and etc) have this issue.
Why we have such options in framework if they don't work on any device?
Why we have such options in framework if they don't work on any device?
em...@gmail.com
that's a good point, but the framework works fine with outgoing call.. Issue is with incoming call..
ch...@gmail.com
Please fix this bug. Still does not work in 2.x.
dh...@gmail.com
Please fix this bug urgent google developer team
sz...@gmail.com
Please fix this bug urgent google developer team
pe...@gmail.com
please do somthing about that bug.
va...@gmail.com
I thought Android was open and easy to work with. I own an iPhone but was thinking to change to HTC Desire just to be able to record calls but i guess there is little point to do so.
Google please pull out the finger and get this working. Its embarrassing that a company as big as this can not make a basic feature that was offered many years ago by Symbian or even WM to work properly.
Google please pull out the finger and get this working. Its embarrassing that a company as big as this can not make a basic feature that was offered many years ago by Symbian or even WM to work properly.
ke...@gmail.com
@vampyren
You _might_ be able to record entire calls, i.e., incoming and outgoing audio. I can do so on the HTC Incredible. I don't know for sure whether the Desire supports it.
Seehttp://code.google.com/p/android/issues/detail?id=8187#c14
You _might_ be able to record entire calls, i.e., incoming and outgoing audio. I can do so on the HTC Incredible. I don't know for sure whether the Desire supports it.
See
va...@gmail.com
Thanks for the reply but since this thread is open i assume it is not solved or is that wrong to assume?
Just to be sure what application do you use?
And what version of Android? (seems 2.1/2.2 is where the problem is at)
Also i been searching 3hours for an application today and everyone say the same thing, it is only possible to record your own voice.
Check here for some comments:
http://forum.xda-developers.com/showthread.php?t=654132&page=4
On Page5 someone tipped on this page actually :)
If anyone owns a Desire or even better Desire HD can you please confirm if
"Total Recall" or "Ultimate Voice Recorder" or any other software can record the in/outgoing calls?
Just to be sure what application do you use?
And what version of Android? (seems 2.1/2.2 is where the problem is at)
Also i been searching 3hours for an application today and everyone say the same thing, it is only possible to record your own voice.
Check here for some comments:
On Page5 someone tipped on this page actually :)
If anyone owns a Desire or even better Desire HD can you please confirm if
"Total Recall" or "Ultimate Voice Recorder" or any other software can record the in/outgoing calls?
to...@gmail.com
This is pathetic. Unless you write the most basic apps in terms of input/output functionality, you have no idea what you might come up against on a given handset. And, for Google to just ignore this issue (even if hardware manufacturers share in the blame) is unacceptable. They have said they think Android can make them $1 Billion in a year, but think how much more it could make them if developers had the tools they need to write leading-edge apps. Shameful.
dj...@djodjo.org
this is unbelievable! and the priority is medium! and the type enhancement!
it is a necessity and it is urgent!
I have htc desire and have the smae issues I can record the conversation but cannot split the up/downlink stream on the top i tried to mute a stream and all the streams except one (setStreamMute/setStreamSolo) I tried with the volume and all I get is ether
1) have all streams
2) have no streams at all recorded
3) app crashes
I have delved into that for the whole day today and couldn't believe that android can leave it for such a long time unresolved.
I will work on that on a lower level to see where the problem is.
if anybody has a solution please share! :)
it is a necessity and it is urgent!
I have htc desire and have the smae issues I can record the conversation but cannot split the up/downlink stream on the top i tried to mute a stream and all the streams except one (setStreamMute/setStreamSolo) I tried with the volume and all I get is ether
1) have all streams
2) have no streams at all recorded
3) app crashes
I have delved into that for the whole day today and couldn't believe that android can leave it for such a long time unresolved.
I will work on that on a lower level to see where the problem is.
if anybody has a solution please share! :)
al...@gmail.com
I don't know you guys has fixed this issue or not. But I am working on an app need to record the call voice. I used the source MediaRecorder.AudioSource.VOICE_CALL and its working fine.
Here is the sample code from my application.
fodler = this.getFilesDir().toString();
String fname = "";
try
{
android.media.MediaRecorder mr = new MediaRecorder();
mr.setAudioSource(MediaRecorder.AudioSource.VOICE_CALL);
mr.setOutputFormat(MediaRecorder.OutputFormat.MPEG_4);
mr.setAudioEncoder(MediaRecorder.AudioEncoder.AMR_NB);
fname = fodler+ "/aa"+System.currentTimeMillis()+".mp4";
mr.setOutputFile(fname);
mr.prepare();
mr.start();
///////////////////////////////////////////////////////////////////////////////////////////////
/////////////////////////////// hold here and make call then release the execution. I tested by debug and add the bread point here.
Thread.sleep(1000);
///////////////////////////////////////////////////////////////////////////////////////////////
mr.stop();
mr.reset();
mr.release();
MediaPlayer player = new MediaPlayer();
FileInputStream fis = new FileInputStream(fname);
FileDescriptor fd = fis.getFD();
player.setDataSource(fd);
player.prepare();
player.start();
}
catch(Exception ee)
{
Log.d(Utils.Tag_Log, ee.toString());
}
Let me know if any problem.
Ali
Here is the sample code from my application.
fodler = this.getFilesDir().toString();
String fname = "";
try
{
android.media.MediaRecorder mr = new MediaRecorder();
mr.setAudioSource(MediaRecorder.AudioSource.VOICE_CALL);
mr.setOutputFormat(MediaRecorder.OutputFormat.MPEG_4);
mr.setAudioEncoder(MediaRecorder.AudioEncoder.AMR_NB);
fname = fodler+ "/aa"+System.currentTimeMillis()+".mp4";
mr.setOutputFile(fname);
mr.prepare();
mr.start();
///////////////////////////////////////////////////////////////////////////////////////////////
/////////////////////////////// hold here and make call then release the execution. I tested by debug and add the bread point here.
Thread.sleep(1000);
///////////////////////////////////////////////////////////////////////////////////////////////
mr.stop();
mr.reset();
mr.release();
MediaPlayer player = new MediaPlayer();
FileInputStream fis = new FileInputStream(fname);
FileDescriptor fd = fis.getFD();
player.setDataSource(fd);
player.prepare();
player.start();
}
catch(Exception ee)
{
Log.d(Utils.Tag_Log, ee.toString());
}
Let me know if any problem.
Ali
mi...@gmail.com
On what phone are you working?
I've also had success with Samsung Galaxy S2 running Android 2.3.3
I've also had success with Samsung Galaxy S2 running Android 2.3.3
ke...@gmail.com
It's entirely device-dependent. For example, VOICE_CALL works on the HTC Incredible, but VOICE_DOWNLINK and VOICE_UPLINK don't work (it's worse actually; they are treated exactly the same as VOICE_CALL).
Unfortunately, there are no exceptions thrown when VOICE_CALL, etc. are used but are not supported by the device, and there is no way to check if the device supports them. What generally happens in the case of a non-supporting device is that silence is recorded instead of the desired audio source.
So, I wouldn't count on your app actually working on a wide range of devices if you're using this part of the API.
Unfortunately, there are no exceptions thrown when VOICE_CALL, etc. are used but are not supported by the device, and there is no way to check if the device supports them. What generally happens in the case of a non-supporting device is that silence is recorded instead of the desired audio source.
So, I wouldn't count on your app actually working on a wide range of devices if you're using this part of the API.
nc...@gmail.com
I agree with the last comment. It seems completely device dependent. However the mismatch between the Java files and AudioRecord.h would be nice to have fixed. I have had limited success with the voice recording and as I am dealing directly with the manufacturer we are now working on this issue together. Hopefully we can find a resolution to this issue ourselves as this is a critical feature for me and my 10 000 clients.
Google please just fix the header files and Java files so we can really see if it works
Google please just fix the header files and Java files so we can really see if it works
zx...@gmail.com
Fix it please.
lu...@gmail.com
Many of the newer phones now support call recording. You can look at Total Recall recorder on the android market. All the phones they say that they support are worth buying if call recording is important to you. There are many budget android phones on the list as well if you don't want to spend too much.
If you currently have an older phone that doesn't support it, there's a very low chance that it will be supported in the future. I suggest you just change phones.
If you currently have an older phone that doesn't support it, there's a very low chance that it will be supported in the future. I suggest you just change phones.
ke...@gmail.com
Then Google should close the bug as WontFix and add a caveat to the documentation on the API that it doesn't work on all devices so that every individual developer doesn't have to painstakingly discover that.
ul...@gmail.com
It's very surprising that Android does not support to record the incoming call function.
nc...@gmail.com
Android supports this however the device you use might not support it. I am working with a Chinese manufacturer at the moment and we have had great success with this. However Korean and US model does not work or sort of works. The problem is that you can't query the device to determine if it supports the API or not.
jo...@gmail.com
I have an app Call + Voice recorder which is able to record call audio (up/down) on some devices using the MediaRecorder.AudioSource.MIC audio source.
Call recording works on most Xperia devices, but at this time does not work on Samsung Galaxy S2. It's hard to believe how such an important issue can remain unattended to by Google for so long.
Call recording works on most Xperia devices, but at this time does not work on Samsung Galaxy S2. It's hard to believe how such an important issue can remain unattended to by Google for so long.
al...@gmail.com
Would like to have at least something happen on this bug. Even if it's just some text from a developer saying "we don't care".
ru...@gmail.com
The silence says more than any words can.
jb...@android.com
[Comment deleted]
en...@google.com
na...@gmail.com
Voice call recording using MediaRecorder required capture_audio_output permission @ run time on 6.0.1 but fail continuously not granted this permission. used Moto g4, samsung on5, samsung on7
using Audio source MIC only capture mic audio not receiver audio..
anybody to solve this, need help..
using Audio source MIC only capture mic audio not receiver audio..
anybody to solve this, need help..
vi...@gmail.com
MediaRecorder used to record media and save .It worked but failed in android 12. couldn't figure out issue
Description
but in new SDK 1.6 i have seen following sources added too.
But all Three New Sources is Buggy and Not Working
android.media.MediaRecorder.AudioSource.VOICE_CALL ;
android.media.MediaRecorder.AudioSource.VOICE_DOWNLINK ;
android.media.MediaRecorder.AudioSource.VOICE_UPLINK ;
<<<<<First Source - Just Gives Error>>>>>
10-01 15:36:01.666: ERROR/AudioFlinger(556): invalid stream type
10-01 15:36:01.666: ERROR/AudioRecord(556): AudioFlinger could not create
record track, status: -22
10-01 15:36:01.676: ERROR/MediaRecorder(779): start failed: -2147483648
10-01 15:36:01.688: DEBUG/AndroidRuntime(779): Shutting down VM
10-01 15:36:01.688: WARN/dalvikvm(779): threadid=3: thread exiting with
uncaught exception (group=0x4001aa28)
10-01 15:36:01.688: ERROR/AndroidRuntime(779): Uncaught handler: thread
main exiting due to uncaught exception
10-01 15:36:01.697: DEBUG/CallNotifier(637): stopRing()... (OFFHOOK state)
10-01 15:36:01.697: DEBUG/Ringer(637): stopRing()...
10-01 15:36:01.707: DEBUG/Ringer(637): - stopRing: null mRingHandler!
10-01 15:36:01.717: ERROR/AndroidRuntime(779): java.lang.RuntimeException:
start failed.
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
android.media.MediaRecorder.start(Native Method)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
com.its.CallRecorder.CallStateListener.Recorder_Prepare(CallStateListener.java:75)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
com.its.CallRecorder.CallStateListener.onCallStateChanged(CallStateListener.java:50)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
android.telephony.PhoneStateListener$2.handleMessage(PhoneStateListener.java:298)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
android.os.Handler.dispatchMessage(Handler.java:99)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
android.os.Looper.loop(Looper.java:123)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
android.app.ActivityThread.main(ActivityThread.java:4203)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
java.lang.reflect.Method.invokeNative(Native Method)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
java.lang.reflect.Method.invoke(Method.java:521)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
10-01 15:36:01.717: ERROR/AndroidRuntime(779): at
dalvik.system.NativeStart.main(Native Method)
<<<<< Second and Third Source >>>>>
Work Properly but only Records Audio from Mic of may be Uplink Channel Data