FM Transceiver in Android 2.2

by Dave » Tue, 25 May 2010 01:59:56 GMT

Sponsored Links
 Now that Android 2.2 has been released and Google has presumably
written drivers for the FM Transceiver included in the Bluetooth chip,
is there a way to access the FM Transceiver through the SDK or NDK?  I
am thinking about applications like FM Radio or FM streaming of audio
to a car stereo.

I am not seeing any changes to the SDK that seem to allow this.
Anyone know if apps like this will be possible?  If so, what am I


Other Threads

1. SensorManager misbehaving on emulator when app was taken to 1.5

Hi guys,

I am developing an app that relies heavily on sensors.

Last night I've installed the 1.5 SDK and the app that was running
fine on 1.1 is no longer doing so. Using logcat, I could spot that the
problem is when a new sensor manager instance is to be created. From
my working app, I isolated the call into this very simple Activity:


import android.content.Context;
import android.hardware.SensorManager;
import android.os.Bundle;
import android.util.Log;

public class Test3 extends Activity {
    private SensorManager mSensorManager;

        /** Called when the activity is first created. */
    public void onCreate(Bundle savedInstanceState) {

        Context ct = getBaseContext();
        Log.e("TEST","Before sensor manager");
        this.mSensorManager = (SensorManager)ct.getSystemService
        Log.e("TEST","After sensor manager");

Then observed the logs with DDMS's logcat:

I/ActivityManager(  567): Starting activity: Intent { flags=0x10000000
comp={} }
D/AndroidRuntime(  833): Shutting down VM
D/dalvikvm(  833): DestroyJavaVM waiting for non-daemon threads to
D/dalvikvm(  833): DestroyJavaVM shutting VM down
D/dalvikvm(  833): HeapWorker thread shutting down
D/dalvikvm(  833): HeapWorker thread has shut down
I/dalvikvm(  833): De{*filter*} has detached; object registry had 1
D/dalvikvm(  833): VM cleaning up
D/dalvikvm(  833): LinearAlloc 0x0 used 638076 of 4194304 (15%)
I/ActivityManager(  567): Start proc for activity pid=841 uid=10019 gids={}
E/TEST    (  841): Before sensor manager
D/qemud   (  546): fdhandler_accept_event: accepting on fd 10
D/qemud   (  546): created client 0xc088 listening on fd 14
D/qemud   (  546): client_fd_receive: attempting registration for
service 'sensors'
D/qemud   (  546): client_fd_receive:    -> received channel id 10
D/qemud   (  546): multiplexer_handle_control: unknown control message
(26 bytes): 'ko:connect:0a:service busy'
W/ActivityManager(  567): Launch timeout has expired, giving up wake
W/ActivityManager(  567): Activity idle timeout for HistoryRecord
{436aeee0 {}}
D/dalvikvm(  611): GC freed 644 objects / 34808 bytes in 305ms

At this point the app blacks out and eventually asks to be forcefully

As you can see, the execution never gets to the second log message.

Although having read that the sensor manager changed, I saw that the
way to instantiate it did not change at all.

Any help/clue much appreciated! This is driving me insane. :)



2. Sending touchevents in Android


Can we trigger touchevents (with X-Y coordinates as input) as we do
for keyevent using the commands
 "adb shell input keyevent <some keycode>"  and also
"adb -s emulator-5554 sendevent <type> <code> <value>"
in the emulator or the target.

I couldn,t find any information regarding this from the SDK

Any help in this will be really great.


3. conversion to dalvik format failed with error 1

4. ViewFlipper - showView(2) functionality rather than just showNext()

5. ViewFlipper - showView(2) functionality rather than just showNext()

6. ListView Entries

7. Fwd: wanted chart api for the android application..