IssueTracker

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.

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

use vrecorder

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!

I couldn't figure out how to star... But I need to call records because of my
business..

Fix this google you lazy fucks

fix it to beat iphone

LOL! pls fix guys! come on

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.

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!!

[Comment deleted]

[Comment deleted]

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

It doesn't work in Android 2.1.

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.

Seems like this should be fixed.

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.

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

This issue started almost a year ago and still marked as New. Seems like ignored by developers..

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).

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.

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.

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.

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!

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..

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?

that's a good point, but the framework works fine with outgoing call.. Issue is with incoming call..

Please fix this bug. Still does not work in 2.x.

Please fix this bug urgent google developer team

Please fix this bug urgent google developer team

please do somthing about that bug.

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.

@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.

See http://code.google.com/p/android/issues/detail?id=8187#c14

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?

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.

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! :)

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

On what phone are you working?
I've also had success with Samsung Galaxy S2 running Android 2.3.3

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.

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

Fix it please.

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.

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.

It's very surprising that Android does not support to record the incoming call function.

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.

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.

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".

The silence says more than any words can.

[Comment deleted]

Please keep conversation relevant to the bug we are discussing, not law or politics.
Such discussion is not productive towards fixing this bug.

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..

MediaRecorder used to record media and save .It worked but failed in android 12. couldn't figure out issue

Is there a bluetooth headset that would record conversations to a micro SD card? That
would suffice but I have never seen one for sale.

Just one more off-topic message in order to answer the request of the previous post:
http://www.tradekey.com/product_view/id/276675.htm
http://utel.manufacturer.globalsources.com/si/6008820659699/pdtl/Bluetooth-
headset/1003179637/Bluetooth-Headset.htm

For clarification, the problem is that the hardware makes call recording impossible?
If so, that would be extremely disappointing. Especially, considering that my Palm
Centro does an amazing job of recording calls or just functioning as a voice recorder
in general -- and I've been under the assumption that my Centro is inferior to
Android phones.

@utkjamie,

Let's not be too dramatic, here.  If this is indeed a hardware limitation, it was
probably a simple oversight in the design of the Droid.  Declaring all Android
devices as inferior is incorrect.  The Android API seems to support it, so it's not
an Adroid "inferiority."

It's either,
1. A bug in the Android support (see the above post of the enumeration values
differing)
2. A hardware limitation of current devices,
3. A porting issue of Android to the current devices which isn't allowing the voice
link streams to be used.

Shawn,

I hope it is not too far off topic to discuss this, as it would be quite an effective
work-around and would allow me to go to Verizon to get my Droid back - it broke my
heart to return it. I looked over the bluetooth headsets on the page you mentioned
and the only headset with a recording option doesn't appear to have a mic, just
speakers. I had already been looking at this headset and almost bought six of them
when I realized there was no mention of a mic. If the headset did indeed have a mic,
it would be perfect. If you have knowledge of a bluetooth headset that records -and-
has a mic, please let me (and anyone else reading this that might be interested) know.

These Google People are Ash-oles.

If they don't reply this Thread. I will load Porn Pictures every day in this Thread
every day.

Will Google now pay Attention to this ?????????

Blackmail is not the best way to get Google to fix bugs. Just be patient. If the issue
is so important to you, vote with your dollars, not stupid pranks in a bug tracking
system.

We are aware of your concerns and we would love to be able to please every one of
you. However, we need to manage our priorities and unfortunately this particular
feature request is not a high priority right now.

We are open to discussions and if you are willing to help get this feature
implemented in the system, please come start a discussion on the appropriate mailing
list/group (see source.android.com for more information about the available lists.) A
very important issue with such a feature would be security concerns, please keep this
in mind when doing proposals for APIs and/or implementations.

Please keep this discussion civil.

@romain...@android.com

As much as I object comment 63's way of getting Google's attention I think that:

a. The lack of responses from Google to this and other discussions is a real shame.
Please note that responding does not equal resolving. Responding means letting the
users know what is going on and/or what should they expect in the future in regard to
the issue discussed.

b. You/Google (I assume you're responding for Google, please ignore the rest of this
paragraph if I'm wrong about it) don't have a say about the way this discussion is
evolving since you're clearly not part of it. It's just plain wrong to accuse someone
else for not being civil while you're doing just the same by systematically ignoring
all users's input. The only ones (as I see it) who can set standards to this
discussions are the ones who are part of it. As long as you're not a productive part
of it, quit being its cop.

c. All this (the users's whining and aggressiveness) wouldn't have happened if you
just responded. You (again, if you're responding in the name of Google. s/You/Google,
if you're not) are the only ones to blame for the current nature of discussions here.
BTW, other users (like me) are offended by this state only we are unable to respond
in the name of Google and just stop it, are we?
---

@mosltes...@yahoo.com

Please, don't. I'm sure that Google is doing their best behind the scenes. They are
just mute about it (which is very wrong but I think not wrong enough to justify
pornifying a tracker system).

This feature should be fixed. Our other corporate cell phones record with no
problem. Very useful when trying to get phone numbers, confirmation numbers, and
other important business info while a call is in progress. This would be more
business 'friendly' than having to find somewhere to write this info down and
interrupt the caller to repeat the info. I am very interested in the Droid and am
seriously considering replacing our corporate cell phones with the Droid. This would
be a serious insufficiency for a business user if this feature is not available on
this new Smartphone.

As per Latest Soure Code Review in Eclair Version ( Android 2.0) the Code have Little
Evolved to

  35 /* Do not change these values without updating their counterparts
  36  * in media/java/android/media/MediaRecorder.java!
  37  */
  38 enum audio_source {
  39     AUDIO_SOURCE_DEFAULT = 0,
  40     AUDIO_SOURCE_MIC = 1,
  41     AUDIO_SOURCE_VOICE_UPLINK = 2,
  42     AUDIO_SOURCE_VOICE_DOWNLINK = 3,
  43     AUDIO_SOURCE_VOICE_CALL = 4,
  44     AUDIO_SOURCE_CAMCORDER = 5,
  45     AUDIO_SOURCE_VOICE_RECOGNITION = 6,
  46     AUDIO_SOURCE_MAX = AUDIO_SOURCE_VOICE_RECOGNITION,
  47
  48     AUDIO_SOURCE_LIST_END  // must be last - used to validate audio source type
  49 };

But i am Still not sure Whether under lying core can Expose these Call Audio Stream
to Java Classes.

@     RomainGuy@Android.com, digit@google.com, jbq@google.com sop@google.com

If 114 Starred Issue is not Important then whats the Use. I this this Issue is in Top
20 List of Bugs. and Google is not even making any Comment or Progress Though the
Source Code is Modifying.

If Security is the Issue Make this Recording as per Country of SIM Inserted into it.
But that must not be the reason not to implement this Feature. i think there is very
Less effortes are need to Solve this Problem. Google is not Focusing on Customers
Demand rather

Google, your Legal department is hurting your business by just saying "No" instead of
finding a solution for you to be customer-focused and follow the law at the same
time.
Note that while you may not get as many responses on this issue as for some others,
the call-recording feature is bigger than you think because it is essential for many
business owners. Many people who put their comments in this thread (myself including)
are business owners and our decision of staying away from Android phones till that
issue is resolved should be taken by you with the factor of 10 or higher as we
represent not a single but a bulk purchase prospective customers.

romain...@android.com: seeing as Google always presents itself as a company
interested in listening to its customers and engaging its users in productive dialog,
I hope you wouldn't mind participating further, and perhaps answering a few questions
for us. Dismissing the entire thread as "uncivil" and refusing to participate would
be an outright insult to the majority of the posters, who have been courteous,
respectful and helpful to Google's efforts.

Now, for my questions:

- Why is this not a high priority issue? It is currently No. 30 in the Android issues
list, sorted by number of people who "starred" the issue. Is this not an indication
of the public demand? How exactly does Google prioritize its issues, if you don't
mind my asking?

- You state that security might be a concern. Please elaborate. Even now, any app can
access the voice stream from the microphone. How did you resolve the security
concerns related to that? How would that be different than the security concerns
related to the incoming stream?

- Google has demonstrated that it can address geographically-restricted legal issues
simply by releasing different firmwares for different localities. Case in point:
Droid has Google Maps nav and no multi-touch; with Milestone it's the other way
around. Simple problem - simple solution. No fuss. Why can't this be applied here?

- Who says that this is even a legal issue for Google, even in countries where all-
party consent is required for recording? When has a manufacturer of recording
equipment (or developer of recording software, for that matter) ever been held liable
for an illegal recording performed using its product?

Thank you in advance for your time and for your thoughtful response.

@romain...@android.com

I feel your pain of being the target to all the questions in this thread, but since you
are the only one that stuck his head out, here comes another one:

I am still puzzled if the lack of access to the audio signal of phone calls is a legal
issue alone or if it is a hardware limitation of today's handsets. Could you kindly
elaborate on this?

Thanks - Joachim Neumann

Its not a Hardware Limitation. HTC Diamond (and all Latest GSM - HSDPA) devices from
HTC can easily Record Calls in both way. and this Radio is Very Very Identical.

This is all Messed in Android Core Level APIs which dont exposes Audio Stream
Properly to Java Classes even though Proper enums is Provided its still buggy.

@romain: how can we raise the priority for this issue? how abt a bunch of developers
sign a petition? we need this!

@all: any ideas for a collaborative effort? a webpage? facebook page?

we are not asking Google to develop an call recording app for us... we are asking
google to fix the bug so that we can develop our own call recording app... even if
somebody/country going to sue for call recording they will sue the app developer not
google...

perhaps google team is holding up this an exclusive feature for their nexus phone...:P

we are not asking Google to develop an call recording app for us... we are asking
google to fix the bug so that we can develop our own call recording app... even if
somebody/country going to sue for call recording they will sue the app developer not
google...

perhaps google team is holding up this an exclusive feature for their nexus phone...:P

Today i just get into Google Voice, and it also allow use to Record Calls

even in Skype we can Record our Calls. they why not on Android. all Windows HTC phone
in USA allows it.

[Comment deleted]

Just to let you know that the call recording API in Android 1.6 does "work", I have
just tested it on HTC G1 successfully. My company (Portable Electronics Ltd) is
building this voice recoding apk with limited resources and will release it for free
when we finish, probably in a few months' time. I will be posting here to get testers
later-on before public release (I believe you won't mind?). (I don't get why all the
complains towards Google here when the API does work..)

Ericwongcm,

I may have misunderstood, but I thought there was no public API available.  This
makes it hard to distribute in any market except for rooted phones.

Would you mind sharing with me how you are using the call recording API?

Thanks and Regards,

Matt

Matt,

Sorry, can't help you on that because I don't write the software myself.
All I can say is the public API is available on Android 1.6 onwards, find it.

I already Reports Bugs and Errors on API 1.6 i am not sure that its may be patched in
1.6 R2?

Any Sample Demo

I have the Source Code too but its not Working though

Matthew, it seems to me that you should follow <a
href="http://developer.android.com/guide/topics/media/index.html#capture">this</a>
guide, using MediaRecorder.AudioSource.VOICE_CALL as the audioSource.

Eric - I'd be happy if you elaborate on how it works - is the sound quality any good?
Does it record silently or does it let the other party know it's being recorded (by
beeping and/or by playing a voice notification along the lines of "you are being
recorded" a la Google Voice)?

I see Google doesn't allow html within comments, so the link given above is corrupt.
Here it is again:
http://developer.android.com/guide/topics/media/index.html#capture

Even tough Setting Source as MediaRecorder.AudioSource.VOICE_CALL

It Just Records Sounds from MIC only!

Heta...@gmail.com: I never said it works correctly, but it IS the correct API to use. I
assume Google is using it as a placeholder until it is actually implemented. However,
Eric claims it does work, so I hope he will elaborate as I asked him to, and also tells
us exactly what firmware revision he is using, and whether they are using the API as
described in the link I provided.

Eric - is it possible that you just developed yet another app that records the call
from the mic, i.e. only captures both sides when on speakerphone?

If anyone at Google is reading this, I believe this issue's type should be changed to
bug, seeing as there is already an API for obtaining the call stream
(MediaRecorder.AudioSource.VOICE_CALL) but it does not work as expected (apparently
mirroring MediaRecorder.AudioSource.MIC instead).

So the issue type should be changed to "Bug", and the priority should be adjusted
accordingly.

Heta...@gmail.com: seems like you are right....the incoming voice is still very faint
but mine is too loud....regardless of settings. Anyone tried the API on Android 2.0?
Is it fixed there?

@ericwongcm: could it be that you are *not* directly recording the incoming call
signal but rather the speaker signal as it is picked up by the phones microphone?

Joachim

mianiumashmi,

I agree.  This should be a bug rather than an enhancement since it has been in the API
from Level 1.  That is a long time to leave a public-facing API hook unimplemented.

This is just speculation, but if Google's Nexus One phone has two microphones to
improve the sound quality *during phone calls*, the phones main CPU needs access to
both microphone signal. If we are lucky, we also get access to the incoming call
signal. Even more advanced would be a hardware design that drops the old fashioned
radio chip altogether. In this case all audio and radio signal processing would
happen in the main CPU (google for VOIP over white space).

Joachim

plz make this recording thing work

How can the CPU record incoming calls then?  Surely incoming and outgoing calls are
routed through the same RF encoder.

I'm extremely disappointed at how many things I was told the OS could do, but DOESN'T.

I need a resolution to this as well. I bought my android phone gambling that there
will be an app that will be able to do this feature. I would be using this app every
day since I run a small business and on the road a lot (Don't answer the phone when
driving, by on the road I mean when I'm out of the office). With millions of small
businesses I know it will be a very popular app. It's not a frill to have this
feature, but a necessity to have this functionality for both business and safety.

I have 15 sales people on the road for my company at any given time and I don't allow
any of them to buy blackberries for lack of this feature alone. Luckily this is the
first and only android phone in my organization. I hope it will be the first of many
future phones I buy.

Elevate this to BUG, HIGH, Today.

come on...its a API that does not work as specified...it is a BUG BUG BUG!

BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG
BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG
BUG BUG BUG

Make it High Priority

Useless Features like Animated Wall Papers are Introduced in 2.1, and Core Important
Features are Missing I hate android as Open Source Project

even thous Android 2.1 is running development is dont in Shadow and they earn money
from Device and then make it Open Source. is it a Open Source Project

7 Devices uses Android Kernel, DROID, DROID ERIS, Hero CDMA Monent, Click, Samsung
7500, Acer Liquid and all Model is violating Laws by not Releasing Kernel Soruce Codes.

Laws are Murders in Android System. I have to take this to Court of Law. IDK whats
this stupid Engineers are upto. but they are Sued they come on Knees.

I don't really give a damn about this bug anymore. I do give a damn about google
refusing to respond to their customers.

When you don't respond to customers who get from you some free email service is one
thing (a bad one, granted, but what are you going to do?). When you sell
phones/produce an OS sold in phones and you still don't respond to your customers is
much worse. Seems like Google is suffering from autism (either that or they employ
too much lawyers).

I won't return my phone but if this (google attitude) is not changed by the time I
need to buy another device you can forget about it being a google related one.

See i have activate participated in so many Bugs. It only to support Platform
Development and making the OS nice. But now i understood Google Implements the Thing
which the Manufacturer or Operator Want. Damn the Customer Attitude.

Palm Pre uses Same Gmail Sync and it have Birthday and Annivarsary in Contact which
sync fine with Gmail. and See Damn Android they dont know what Feature Gmail have and
still missing in Google Sync. Damn it !

Yea it's just a bug so fix it already.  And why even call it an open source project
if it isn't, if you're confused what open source is please visit this
http://www.kernel.org/pub/

and stop relating android to linux unless it is true open source, it's just a lie and
we aren't being fooled.

@phaze3131

Android is open source: http://source.android.com/

The problem is that many users don't have unlocked phones where they can install
modified builds of the source code. Also, many drivers for phone hardware is still
proprietary, so debugging those may be impossible.

Did we ever establish how the audio was getting routed through the phone? Is there a
way to route the audio through android so it can be recorded?

... http://android.git.kernel.org/

I agree this should be marked as a bug and not enhancement, but, I'm unstarring this
issue because of the immature turn the comments have made.

True good point but I just meant that comparatively I can install many forms of
linux/unix on my system that is not "locked"

There is just a logical difference, we only have one piece of hardware and it's
"locked" so we can't install any versions of the software or updates that we want.

Just stating the differences between a true open source project and one limited like
this one, but hey it's a totally new concept (on wireless phones) I'm not trying to
bash it, just trying to say I wish we had more control.

Good work developers :)

Agreed, this would be a great feauture.

Yeah, it's immature.

Still, I expect Google Inc. to communicate with it's users and I can't find another
way to ask them to do so. They are just unreachable.

Nevertheless I agree that this line of discussion is not appropriate here, so:
1. Sorry, I'll try to avoid it in the future.
2. I've opened a (immature) bug at
http://code.google.com/p/android/issues/detail?id=5883 so that people (like myself
sometimes) interested in bashing/criticizing Google Inc.'s behavior in this regard
can use it and not this one (which causes other people to un-star).

Does anyone know how fix the problem "ERROR/audio_input(31): unsupported parameter:
x-pvmf/media-input-node/cap-config-interface;valtype=key_specific_value" ?

The iPhone doesn't support call recording, even with all the hacking that is going on. I think it would be a
wise marketing decision to enable this feature in the android platform.
That would trully help headset manufacturerd build an iPhone killer. Imagine the droid with such
function...

Just a quick note: INAL, but providing a working API for recording an inbound call
stream shouldn't generate any legal culpability on Google's part, beyond what is
already induced by providing external routing of the inbound stream through the 3.5mm
jack/any bluetooth device that supports the HSP/HFP profile.

I know it is not a practical solution to the concern raised in this thread, but if I
were determined to preserve the inbound and outbound streams in a persistent storage
medium, I could simply use a male-to-male 3.5mm cable to connect the phone to an
audio recorder, then use the 3.5mm output from the recorder to earphones (so I could
monitor the conversation while recording it), and use vRecord or similar on the phone
to capture the outbound stream. After the conversation ended, I could transfer the
outbound capture file from the phone and inbound capture file from the recorder, onto
the computer, and then mix the two streams: the result would be a file containing the
entire conversation.

Granted this would be a pain to do, and is in no way a practical solution--but
AFAICT, the legal ramifications are the same as providing a (functional) API to do
this directly from the phone. Obviously, there are some fuzzy legal areas regarding
inhibition/enablement for breaking local laws, but I think (again, INAL) those could
be ironed out while still providing a working API. Am I missing something?

I get this java error while execute the record example on SDK 2.1 on Dream/G1
It works with SDK 1.6 but this errors occurs for Android 2.1.
Any ideas ?

W/System.err( 1724): java.io.FileNotFoundException: /data/local/tmp/record.3gpp
W/System.err( 1724):    at
org.apache.harmony.luni.platform.OSFileSystem.open(OSFileSystem.java:244)
W/System.err( 1724):    at java.io.FileOutputStream.<init>(FileOutputStream.java:97)
W/System.err( 1724):    at java.io.FileOutputStream.<init>(FileOutputStream.java:168)
W/System.err( 1724):    at java.io.FileOutputStream.<init>(FileOutputStream.java:147)
W/System.err( 1724):    at android.media.MediaRecorder.prepare(MediaRecorder.java:460)
W/System.err( 1724):    at
com.fmcc.callrecorder.CallRecorder$1.onClick(CallRecorder.java:94)
W/System.err( 1724):    at android.view.View.performClick(View.java:2364)
W/System.err( 1724):    at android.view.View.onKeyUp(View.java:3985)
W/System.err( 1724):    at android.widget.TextView.onKeyUp(TextView.java:4369)
W/System.err( 1724):    at android.view.KeyEvent.dispatch(KeyEvent.java:1061)
W/System.err( 1724):    at android.view.View.dispatchKeyEvent(View.java:3683)
W/System.err( 1724):    at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:747)
W/System.err( 1724):    at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:747)
W/System.err( 1724):    at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:747)
W/System.err( 1724):    at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:747)
W/System.err( 1724):    at
com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchKeyEvent(PhoneWindow.java:1655)
W/System.err( 1724):    at
com.android.internal.policy.impl.PhoneWindow.superDispatchKeyEvent(PhoneWindow.java:1102)
W/System.err( 1724):    at android.app.Activity.dispatchKeyEvent(Activity.java:2038)
W/System.err( 1724):    at
com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchKeyEvent(PhoneWindow.java:1631)
W/System.err( 1724):    at
android.view.ViewRoot.deliverKeyEventToViewHierarchy(ViewRoot.java:2368)
W/System.err( 1724):    at android.view.ViewRoot.handleFinishedEvent(ViewRoot.java:2338)
W/System.err( 1724):    at android.view.ViewRoot.handleMessage(ViewRoot.java:1641)
W/System.err( 1724):    at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err( 1724):    at android.os.Looper.loop(Looper.java:123)
W/System.err( 1724):    at android.app.ActivityThread.main(ActivityThread.java:4338)
W/System.err( 1724):    at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err( 1724):    at java.lang.reflect.Method.invoke(Method.java:521)
W/System.err( 1724):    at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
W/System.err( 1724):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
W/System.err( 1724):    at dalvik.system.NativeStart.main(Native Method)
E/MediaRecorder( 1724): start called in an invalid state: 4
D/AndroidRuntime( 1724): Shutting down VM
W/dalvikvm( 1724): threadid=3: thread exiting with uncaught exception (group=0x4001e170)
E/AndroidRuntime( 1724): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 1724): java.lang.IllegalStateException
E/AndroidRuntime( 1724):        at android.media.MediaRecorder.start(Native Method)
E/AndroidRuntime( 1724):        at
com.fmcc.callrecorder.CallRecorder$1.onClick(CallRecorder.java:102)
E/AndroidRuntime( 1724):        at android.view.View.performClick(View.java:2364)
E/AndroidRuntime( 1724):        at android.view.View.onKeyUp(View.java:3985)
E/AndroidRuntime( 1724):        at android.widget.TextView.onKeyUp(TextView.java:4369)
E/AndroidRuntime( 1724):        at android.view.KeyEvent.dispatch(KeyEvent.java:1061)
E/AndroidRuntime( 1724):        at android.view.View.dispatchKeyEvent(View.java:3683)
E/AndroidRuntime( 1724):        at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:747)
E/AndroidRuntime( 1724):        at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:747)
E/AndroidRuntime( 1724):        at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:747)
E/AndroidRuntime( 1724):        at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:747)
E/AndroidRuntime( 1724):        at
com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchKeyEvent(PhoneWindow.java:1655)
E/AndroidRuntime( 1724):        at
com.android.internal.policy.impl.PhoneWindow.superDispatchKeyEvent(PhoneWindow.java:1102)
E/AndroidRuntime( 1724):        at
android.app.Activity.dispatchKeyEvent(Activity.java:2038)
E/AndroidRuntime( 1724):        at
com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchKeyEvent(PhoneWindow.java:1631)
E/AndroidRuntime( 1724):        at
android.view.ViewRoot.deliverKeyEventToViewHierarchy(ViewRoot.java:2368)
E/AndroidRuntime( 1724):        at
android.view.ViewRoot.handleFinishedEvent(ViewRoot.java:2338)
E/AndroidRuntime( 1724):        at
android.view.ViewRoot.handleMessage(ViewRoot.java:1641)
E/AndroidRuntime( 1724):        at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1724):        at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1724):        at
android.app.ActivityThread.main(ActivityThread.java:4338)
E/AndroidRuntime( 1724):        at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1724):        at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1724):        at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 1724):        at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 1724):        at dalvik.system.NativeStart.main(Native Method)

In many locales, even within the US, it is perfectly legal to record a conversation
made over the phone.  Some states require one party to be aware of the recording (ie,
the recording party), others require all connected parties.

This isn't about spying, it's about the ability to audit business calls, as well as
keep a record of important data which may not be easily recorded while on-the-go.

Please provide this functionality via API.

Call recording is perfectly legal in Sweden as long as one of the participants are
aware of it.
Please implement this.

Yes, please implement.  As others have said - it can be limited based on geography.  
Best,
david

Call recording is perfectly legal in Denmark - so yes, please implement.

More to the point, even if call recording is illegal in a particular region
(with/without permission) that's not really an issue for the makers of the phone (no
more than the downloading of illegal content is for the makers of say a web-browser).
This would be an exceptionally useful tool to have on my phone and I can't see how the
legal ramifications of what I did with a recording I made are any issue to the Android
dev team.

this is such a basic feature...
only reason i dont move to the Nexus1

So let me get this right.....Google removed the feaature cause it's illegal to record
call conversations in certain states/countries???
For one, the maker does not get "in trouble" the end-user does and that's only if the
recording is used in the court of law.
Here in Chicago, it's illegal to register a gun, but the CHOICE to buy a gun is there.
Is this the same company that if i pop open a browser and type in Google search "How do
i make a bomb" i get About 51,700,000 results (0.31 seconds)
Where is the logic????

I need this function for business.  Can't buy a droid until it is available.

Thanks

My company choose between the iPhone and Android as a standard phone, depending on
which of those who first implements a real call recorder function like in s60.

Please come before the iPhone so that I do not have to buy an iPhone.

Hi. After some research, I'm convinced that it won't work because of a software
issue caused by some code inside Android itself. These 3 commands don't seem to work:

android.media.MediaRecorder.AudioSource.VOICE_CALL  ;
android.media.MediaRecorder.AudioSource.VOICE_DOWNLINK  ;
android.media.MediaRecorder.AudioSource.VOICE_UPLINK  ;

These are the commands needed to run a Call Recorder.

This is a bug. It should be fixed. But the Android team are busy with many things so
they will only take the time to fix it if people show that they will appreciate it.

So we need to vote to fix this bug. If they see that many people are voting and want
this, I'm sure they will pay attention to it.

Go to Android Issue 36909561:
http://code.google.com/p/android/issues/detail?id=4075

Go to the bottom of the page.
Vote by starring it (right above the comment box).

Please don't comment unless you can help in fixing it. It will just clutter the
place up. I haven't commented either.

I hope that if we can get 3000 stars, this will be made a top priority by the
Android team.

Get your friends to vote in on this too.
If you own a business, force your employees to vote too. *grin*

Thanks.

Probably won't do a bit of good, but I'll add my voice to this.

Of course it's upsetting that the API facility that supports application access to
the incoming audio stream is broken, and that Google apparently has refused to fix
it. It's upsetting because Android phones are expensive and this creates a natural
assumption that basic features will be supported. That comparatively ancient phones
can do basic things like call recording and bluetooth initiated dialing while my
Android phone is fundamentally incapable despite the availability of a broad
community of third party developers is shocking and disappointing, to say the least.

But I think what reflects so poorly upon Google is *not* necessarily their refusal to
fix these defects in their product. One could easily imagine design or production
situations in which the functionality is physically difficult or impractical to
provide, given specific component choices or design decisions that may have been
extremely compelling and understandable for other unrelated reasons.  No, the real
problem is Google's disrespectful and insulting refusal to simply *respond* to those
who are naturally expressing frustration about what is (seriously now) a baffling
limitation.

Is this an intractable problem? Are there extenuating circumstances? Was there a
disconnect in the design process that left the hardware platform missing some key
feature that makes it impractical or impossible to fix this defect?  Just tell us
what's going on, Google, and though you may get some flack for it up front,
ultimately a lot of this heat will disappear.

I have ordered Nexus One from Turkey, and get upset when discovered taht I can't
record calls. And I am not at States!!!
I have a Public relations agency and all the day long our customers decribe their
expectations. How I am supposed to overcome them if I can't record their explanatons
and needs.

One way... Sell my Nexus one and buy another phone.

It is a pity that I have given my ex telephone to my nephew...

I was shocked. Quite a show stopper.

I think google will support this feature very soon .

ya lets keep our fingers crossed

I am a Chinese. I started to be aware of the importance of call recording capacity,
when I was treated unfairly by a Chinese bank. Nowadays in China, many companies
(suce as banks, phone service carriers, etc) provide their costomers with services
through phone call, and they will record every conversations between the customer
and the company. The problem is when something goes wrong, or disbute arises, the
company won't let you hear the recording, even in my case, the bank company
presented to the law court, as an evidence, a note loaded with "text formate" of the
recording, in which a lot of messages was missing! They just manipulated the contents
(the conversation), because they could take the advantage of the situation that I
have no recording as an evidence to present.

I have been looking for a good phone with call recording capability, but
unfortunately I bought this Motorola Milestone!!! Here I strongly apeal Google to
fix this issue.

This seems to me to be a problem with individual phone models themselves. The API
support is there in the Android platform to record calls, and it is reported to be
working on certain handsets.

I've been playing around with trying to find out why call recording isn't working on
the Motorola Droid, and the /system/lib/libaudio.so file seems to be where the error
occurs. Since it is a [I think] proprietary Motorola library specific to their phone,
meaning the source is unavailable, there's not much more I can find out :-\

AudioHardwareMot: AudioMgr Error: Unsupported input path

This is a major hindrance!  Are there Google folks actually looking at these posts?  If
so please drop a line and simply let us know.  Also, I think there is a major gap in
people's knowledge of how to report frustration about such issues so I think that this
is not getting as much attention as it should (especially compared to the number of
folks that I know who are angry about this).  Is rallying people to post in this forum
the best way to expedite help for those of us who desperately need this function?

There is a new application in Andorid Market called AllCallRecorder. I think it would
help you.

@Rimidalv78 Have you actually tested that app? IT DOES NOT WORK!

Seriously! I mean SERIOUSLY! This day and age and we don't have reliable/stable/any
phone recording. unfrick'nReal. Had i known this 2 months ago i would _not be a new
owner of a Droid (nor have a wife with a new Eris).

Believe me when i say i'm doing what i can to to dissuade other new adopters. geeze

I'm with y'all!

Call recording is a must!

it am glad to see this feature come in android platform!

It's an important feature for me.

That is the only issue stopping me from buying a Nexus 1. Simply ridiculous that a
major function like this is not supported.

this is a bug and not enhancement, please fix it.

Driving while taking notes is EXTREMLY dangerous…. Recording to access later is the way
to go… This is the only thing I miss about my Windows CE based Glofiish M700

LiamJamesAlford, I have tested AllCallRecorder on my HTC Hero. It works.

Adding my voice to the long list of users who need this issue resolved.

heya,

Yeah, I'd have to voice this is a neat feature to have.

In most countries I believe it is legal (just often not legally admissible as
evidence - but I don't think that's why most of us want it). And even in the States,
it's only illegal in a few states.

I suspect it might just be laziness, as opposed to any legality issues.

Cheers,
Victor

heya,

I just noticed this:

http://www.androidzoom.com/android_applications/tools/allcallrecorder_frcn.html

Can anybody comment on whether this works for them? It doesn't do the dodgy record
via speakerphone, does it?

(I haven't actually bought my Nexus yet, that's why I can't test it - I'm actually
sitting on the fence until I can make sure that call recording will work - I dont'
want to buy the handset, then find out that the handset will never support it.).

Cheers,
Victor

I'd like this feature too.

heya,

I just noticed there's another program, called AirVoice, which is meant to do this:

http://www.androidzoom.com/android_applications/tools/airvoice_cjsj.html

It seems a lot of these apps don't work for the majority of people *sigh*. Can
anybody know if this is a limitation of the current generation of Android phones, or
an intentional omission by the Google Android team?

Cheers,
Victor

It seems Google implement fixes where their own products links up to the Android
OS/browser. I sense a conspiracy here, Google, I suspect, will not fix the call
recorder problem in the hope in migrating users to Google Voice. This would be a
great shame because it means the whole world apart from the United States will miss
out on call recording on their Android devices.

the phone application should support recording calls.  every corporation I call says
they are recording me, i should have the right to record them to defend myself.

As far as I know there is an API for call recording, but there were no devices with
hardware support. Did anyone already try one of the newer phone, like the droid,
legend, or nexus one? Over a year ago I developed something for the G1, but currently I
don't have the time and focus to install the environment again and try call recording
on the Nexus One, especially when I suspect that someone probably already tried this.

I am a journalist. I must have call recording to transcribe interviews. How, how, how
is it possible that this simple feature is not available on the Droid. It is easily
available on the iPhone.

For two months I haven't been getting any email notifications regarding this issue.
That seemed strange to me, in light of the fact that this is a VERY active thread and
people have posted dozens of comments during that time.

Then I noticed the following notice at the top of this page:
"Comments by non-members will not trigger notification emails to users who starred
this issue."

Interesting. It does not show up in any of the other Android issues I checked. Some
new type of Google censorship? Way to go, "do no evil" guys!

Anyway, for all of my fellow call recording enthusiasts who have given up on Android,
I would recommend buying Nokia S60 phones (S60v3 or S60v5), running Psiloc's
excellent Voxtrack Personal call recording app. Just go to Psiloc's product page and
make sure the model you intend to buy is compatible.

The only thing that kept me from buying an iphone was lack of a call recording feature.
The only thing that is very likely to keep me from buying an adroid os based phone is very likely
to be the lack of a call recording feature that even my wm 6.1-based phone or almost "free"
non-smart phones support.

I am not going to give specific rationale as to why I want a call recording feature since previous
postings have given strong enough business case for a life-saving call recording feature.

Come May, 2010, SKT, a South Korean carrier, will pound the South Korean market with almost
8 adroid models with more in the pipeline. In the absence of a call recording functionality,
Please, don't make me go for  HTC's HD2 when I can easily pick up an adroid-based phone if
this "simple" feature is supported.  

Let me tell what I think about these "bugs" in the API. They are there for a reason,
and the reason Google didn't respond to our votes is that they don't want to! Call
recording is totally illegal in some countries and on other it is illegal without
notification of the other party that he is being recorded. That's why the apps for
Symbian and WM have "beebs" during the call, that the other party hears.

Google is a company that loves the freedom of speech (remember the China situation
last month?), but it is also an international company that operates in many
countries and such a function may angry some governments and large companies. This
is the reason why iPhone also doesn't have it... Apple just don't want to be under
fire about this feature, just because of several hundred people that really need
this call recording. They just don't care about us, because we are a very, very...
very little part of their target market of multimedia, games, e-books and so on
shits, that actually sell todays smart-phones to the mass!

heya,

Mishoboss: You've basically ignored everything else anybody on this thread has said.

It's a valid feature, that more than "a few hundred" people probably want to use. Do
you really think everybody who wants this feature has posted in this forum? Heck, or
even knows about Google Code? Sorry, but you've got some serious sampling bias there,
my friend.

Also, it may be illegal in a couple of states in the US, but guess what, the world's
much bigger than that. Note that we're talking here about recording by one of the
participants in the call, as opposed to wiretapping.

In most of the Western democracies I'm aware of (Australia, Canada, UK, Finland
etc.), it's legal to record the call, for your own use, as long as one of the
participants is aware - and since it's you making the call, that's obviously the
case.

In countries like India, it's prohibited, and only the government is allowed to
record (whenver they want)...lol, but let's not go there. China, well, yeah, you can
pretty much do whatever you want.

Even in the US, only 12 states require notification of both parties (or all of them,
if there are multiple participants), whilst every other state requires only one
party's consent.

It's a useful feature that several people here have helpfully provided valid use
casese for. I suspect it's more a case of laziness, or other features taking
priority, on Googles part. I mean, really, look at the tomfoolery that Google's doing
with China, serving it out of HK? Or that website they created to expose governments
that are invading their citizen's privacy?
(http://www.google.com/governmentrequests/)

So I'm sorry, nothing personal, mishoboss, but your points are all pretty empty.

Cheers,
Victor

See:

http://www.citmedialaw.org/legal-guide/recording-phone-calls-and-conversations
http://www.rcfp.org/taping/
http://en.wikipedia.org/wiki/Telephone_recording_laws

Hi, Victor,
I don't think my points are all empty. Yes, I know the world is not USA (I'm from
Bulgaria ;)), but the large USA companies like Apple and Google always think first
of the USA mobile market and their carriers... But this is another story. The point
is that I really think the call recording is intentionally disallowed. The strange
thing here is that Google actually provides a way of call recording via their Google
Voice app, but that happens on a server and only for outgoing calls via the app.

Call recording is not only an Android issue. In fact this is a very, very old issue
from the first days of Windows Mobile for Smartphone. I always wanted to record my
calls and have a modern smartphone, and that always was a trouble (except in some
Symbian phones I had in the past years). On almost every Windows Mobile phone from
HTC there were a blocking in the firmware for getting the line data directly. Some
good guys in the XDA forums provided a custom hacked ROMs that made possible the
call recording without the stupid speaker turned on. Symbian and Nokia phones were
the only one that provided call recording without any problems, at least in the
first years. Then they decided to embed a beeping sound directly in the Symbian, but
of course there were also pretty guys that hacked it.

iPhone also doesn't have it, and probably never will, even on jailbroken phones.

But, lets get back to Android. The fact is that there were several apps that claimed
they make call recording (with the speaker turned on of course ;)) prior to version
2.0. Could you tell me ONE call recording app that works on Android 2.0 and 2.1?
Google just did their work ;)

So, I'm afraid that we will never see an official Android API for getting the line
stream. Don't get me wrong, this is the most important feature I need on my modern
big-ass, multi-touch, gigahertz, super, mega, 5G, "PHONE"... but I doubt I get it
official.

My hope is some pretty guy from XDA will break it and deliver to us a hacked ROM...
and I hope it will be soon! :)

Note that one can always put the phone near tape recorder and record anyway even
without any beep or any other warning. Further more, one can synthesize digitally any
recording these days, thus any legal use of such technology is very much doubtful.

If the API is provided then it would probably be possible to do voice encryption, and
this is were most governments would step in...

But it is indeed very much useful for personal record keeping.

Well, you're right, if someone wants to record his call, he will find a way. HTC (or/and Google) just don't
want to make it easy for anyone, because there will be many people that might use this for illegal
purporses... :(

On the earlier Windows Mobile versions Microsoft didn't block the line stream, but the HTC phones did it.
Because I wanted so much to have Windows phone, I end up with one Eten M700 phone, that worked
like a charm on recording my calls. So maybe the problem isn't just Google, but HTC too...  

even i am facing a same problem..my call recorder application which is built on
android 2.1 works fine on the emulator but the same does not work on motorola
milestone(called as droid in US).I have tried it by setting audio source to
default,mic,voice_uplink,voice_downlink,voice_call..still it doesnot works.Is there
any official announcement regarding this.I need to show it to my client.

Rseven has a call recording feature that works on 1.5 but not the 2.1 phones. Rseven on
Symbian & Windows Mobile have call recording & we want to have the same feature on
Android. We're still trying every avenue to make it work

I'm definately in great need of this. I'm running an HTC Desire and would like to add
my voice to those lobbying google for a change!

Someone said something about the HTC Diamond which was my previous phone and was
incapable of doing it without a speakerphone work around too. The software supported
it alright. Apparently the guys at XDA were saying it was hardware limitation :-/

I hope we're not going to hit that problem with android phones. And selfishly
speaking especially so with the Desire! :-)

I'm definately in great need of this. I'm running an HTC Desire and would like to add
my voice to those lobbying google for a change!

Someone said something about the HTC Diamond which was my previous phone and was
incapable of doing it without a speakerphone work around too. The software supported
it alright. Apparently the guys at XDA were saying it was hardware limitation :-/

I hope we're not going to hit that problem with android phones. And selfishly
speaking especially so with the Desire! :-)

I'm definately in great need of this. I'm running an HTC Desire and would like to add
my voice to those lobbying google for a change!

Someone said something about the HTC Diamond which was my previous phone and was
incapable of doing it without a speakerphone work around too. The software supported
it alright. Apparently the guys at XDA were saying it was hardware limitation :-/

I hope we're not going to hit that problem with android phones. And selfishly
speaking especially so with the Desire! :-)

If you can stand to use an older palm phone and the older operating system ( not the
latest) you can run Mvoice software on your phone. When you receive an incoming call
there is a prompt that allows you to record the call or not. The software works
flawlessly. My phone stores about 12 hours of recorded conversations and I just dump
them into my office computer as needed. You can then search by phone number and
retreive what you need to reveiw later. I have used these recordings to my benifit
in several recent lawsuits and several fraudsters may end up in jail eventually
because I was able to verify converstaions that normally would have just been
denied. In todays world you need to document as much as humanly possible. I feel
naked without call redcording software. Perhaps I just need to do business with a
better quality of people but I seem to be a magnate for the crooks.

There is a work-around for this issue (might have been mentioned before)...

I have successfuly recorded calls by using the HTC voice recorder app while putting
a call on speaker.  Not a great solution, but the recording is quite audible when
played back.  for better quality recording one could plug speakers into the headset
jack and put them in front of the mic.

This worked ok on my incredible (CDMA version of the desire), but is obviously not
the optimal solution.

Is this still broken in 2.2? I can think of lots of really cool apps that may be
possible with call recording, I will list a few here "just because":

1) Receive a phone number over an active call using DTMF tones. This should be built
in by default! You're on the phone to someone and they're about to tell you a phone
number, instead of getting a pen or going back and forth from ear to keypad, you just
ask them to key it in. Suck on that one iPhone!

2) Transcribe call. Use speech to text to save a phone call as text or email. Since
there's two channels you could assign both users a name so it looks like a script:
<me> Hello?
<marketeer> Hello, could I interest you in some spam?
<me> No.

3) Built-in programmable answerphone with unlimited offline storage. Why pay to
listen to your voicemail when your phone can act as an answering machine? Send
selected people to answerphone, have custom messages depending on the caller's group,
listen to them while they leave a message like with a real answering machine.

4) Echo chamber. Record, wait for pause, playback. Childish and irritating fun.

5) Lip reader for the deaf. A picture of a mouth which mimics the caller's mouth so
that deaf people can take calls.

6) WiFi call router. Route calls to your computer, include standard phone users in
partyline chats over Skype, MSN, Yahoo or Vent.

7) Remote voice command. Have android apps which can answer the phone and interact
with other devices on your command.

8) Voice changer. Put your friend's call on loudspeaker, but pitch shift him so he
sounds like a girl so all your friends can laugh at him.

9) Interview sync. Record a call in high quality at both ends, using a tone to sync
the start of the conversation, then join the two streams back together again. Useful
for interviews in podcasts.

10) Encrypted calls. Calls with a slight delay and simple encryption, speed up the
sound, break the last second into chunks and swap them around.

All cell phones I previously used (over 6) had built-in call recorders. The
illegality claim is bogus. It's up to the consumer to comply with laws. This is like
preventing people from speaking English because some country out there bans English
on cell phones.

Google: a call voice recorder is long overdue.