Play audio over an active phone call, so other end can hear it

by Marco Nelissen » Sat, 08 Aug 2009 02:24:56 GMT


Sponsored Links
 The hardware doesn't support it. The closest you can get is by playing
it over the speaker at full volume, so the microphone will pick it up.





--~--~---------~--~----~------------~-------~--~----~



Play audio over an active phone call, so other end can hear it

by Dianne Hackborn » Thu, 10 Sep 2009 11:38:39 GMT


 You can't do this on the G1 class hardware.  This audio routing is handled
by the baseband, which is a separate CPU running the radio and other related
things.









-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Proxy.getInvocationHandler(...) returns null

Hi there,

It seems that Proxy.getInvocationHandler(..) is broken since it always
returns null.

Background:
I'm porting a java application to Android which utilizes dynamic
proxies.
The application is working on a usual JDK 5.0.

Scenario:
1) I create a Proxy instance P via Proxy.newProxyInstance(Classloader,
Class[], InvocationHandler);
2) Proxy.isProxyClass(P.getClass()) is TRUE
3) ERROR: The value returned by Proxy.getInvocationHandler(P) is null!

BUT: The proxy instance P seems to work, The InvocationHandler gets
correctly called.

- Does anyone also encountered this Problem?
- Is there a solution?
- Can anyone help?

As workaround I now cache all InvocationHandlers in a static
Map<Object, InvocationHandler> and retrieve it from there. But this is
ugly and I would like to solve it in the usual way using
Proxy.getInvocationHandler(..).

Best regards,
Christian
--~--~---------~--~----~------------~-------~--~----~

2. HELP! Weird Activity lifecycle / thread issue

I have ActivityA, which invokes ActivityB using startSubActivity using
an explicit intent.

In ActivityB, I start a worker thread.

Case 1:
If I handle a click in ActivityB and setResult() and finish(), I go
through the lifecycle (onFreeze, onPause, onStop).  I put a call to
worker.interrupt() in onPause, which is called successfully.  I return
to ActivityA with a result code.

Case 2:
The worker thread runs into a condition which should automatically end
ActivityB.  When I hit that condition, the worker thread sends a
message to a handler in ActivityB.  The handler, then calls
setResult() and finish().  In this case, my onPause() is never called
(so my worker keeps working), however, ActivityB finishes correctly
with a result code returned to ActivityA.

Any ideas?  Am I misunderstanding the Activity lifecycle?  I'm about
to try to set up a bare-bones test case to see if I can repeat this.

Thanks
s6
--~--~---------~--~----~------------~-------~--~----~

3. Dialog generating NullPointerException

4. How can MapView display standard map menu options (like directions to location etc.) without extra code

5. applyAlpha?

6. menu item indicator

7. Adding browser supported types