Could you please describe the 2 ways that you reference?
On Dec 11, 9:40 am, Mr Pinguin pinguint...@googlemail.com wrote:
Is it possible to record only
VOICE_DOWNLINK Voice call downlink (Rx) audio source
?
It doesn't work for me. it records only 2 ways.
On 4 Dez., 08:00, hongki park
Is it possible to record only
VOICE_DOWNLINKVoice call downlink (Rx) audio source
?
It doesn't work for me. it records only 2 ways.
On 4 Dez., 08:00, hongki park parkhongki.spr...@gmail.com wrote:
^^ what are you talking about ???
2009/12/4 Hetal Patel heta...@gmail.com
Will anybody
^^ what are you talking about ???
2009/12/4 Hetal Patel heta...@gmail.com
Will anybody reply ever
Android us Useless as far as Bugs is Concerened Nobody ever Bother to
rely of Patch
This is another Exmaple of Google Which Never Comes out of BETA
I hate Android
On Nov 19, 1:32 pm, Hetal
Will anybody reply ever
Android us Useless as far as Bugs is Concerened Nobody ever Bother to
rely of Patch
This is another Exmaple of Google Which Never Comes out of BETA
I hate Android
On Nov 19, 1:32 pm, Hetal Patel heta...@gmail.com wrote:
Here is what I see.
In AudioRecord.h and in the
In Package
android.media
Classes MediaRecorder.MediaSource now after API Level 4 ( Android
1.6 ) Includes
4 VOICE_CALLVoice call uplink + downlink audio source
3 VOICE_DOWNLINKVoice call downlink (Rx) audio source
2 VOICE_UPLINK Voice call uplink (Tx) audio source
See the
I'm deseperately trying to use the VOICE_CALL parameter, in order to
record both
the in and out audio streams during a phone call. When using
VOICE_UPLINK or
VOICE_DOWNLINK or MIC, it works fine, however.
At runtime, in the DDMS log, I get:
09-30 15:35:09.812: ERROR/AudioFlinger(51): invalid
Understood, I thought that this was straightforward.
When attempting to record a phone conversation on Android v1.6 (by
using the
MediaRecorder.AudioSource.VOICE_CALL audio source parameter), at
runtime an
exception is thrown unexpectedly. The test is performed on the HTC ADP
with firmware 1.6.
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
Hi Roman and Nick,
Looks like I have to exercise some patience with my plans to implement
a software hearing aid in a mobile phone.
Thanks a lot for your explanations and the helpful link to embedded.com
Joachim
--
You received this message because you are subscribed to the Google
Groups
At a high level, this description is correct, and is how the majority of
mobile architectures operate. The applications CPU that Android runs on is
not usually in the data path for in-call audio.
Nick
On Tue, Nov 10, 2009 at 10:17 AM, Joachim Neumann jogineum...@gmail.comwrote:
Hi Dianne,
I
Hi Joachim,
That's kind of correct. The so called baseband processor (which runs
the cellular low level stuff, RF, modem functionality, ...), has to
expose whatever would be needed from higher level. You might be able
to get some additional radio property information using AT commands
but getting
Here is a pretty good link which talks about the intercommunication of
baseband and AP
http://www.embedded.com/columns/technicalinsights/187203124?_requestid=22
--
Roman Baumgaertner
Sr. SW Engineer-OSDC
·T· · ·Mobile· stick together
The views, opinions and statements in this email are those of
Hi Dianne,
I am also struggling with this issue and would like to understand the
limitations in current Android hardware.
My present understanding is that in on current Android phones there is
a GSM/3G chip that
1. receives the *analogue* GSM/3G antenna signal
2. receives modem-like AT commands
The current Android hardware I know of does not support this.
On Sat, Aug 22, 2009 at 7:11 AM, slenzi sle...@gmail.com wrote:
Is it possible to get a handle on the outgoing data (voice) stream
during a call? I'd like to be able to intercept the outgoing data,
alter it slightly, then write it
14 matches
Mail list logo
