Bluetooth profile support in cupcake

by bmannix » Thu, 26 Feb 2009 11:18:29 GMT


Sponsored Links
 The roadmap for cupcake states that it now supports the Bluetooth A2DP
& AVRCP profiles.  Since the Bluetooth API was ripped out of 1.0 does
that mean that these are the only profiles supported?  Or are there
any other profiles currently supported?


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



Bluetooth profile support in cupcake

by Amir » Thu, 12 Mar 2009 10:19:19 GMT


 Have you heard anything about this?




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


Sponsored Links


Bluetooth profile support in cupcake

by Nick Pelly » Fri, 13 Mar 2009 01:26:04 GMT


  http://source.android.com/projects/bluetooth-faq 





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



Other Threads

1. passing intents

how do you pass an intent from a service to a new activity launched
from a main activity ?

there's a passextra( intent src ); but i dont think thats what im
looking for ?



activity main > start service( intent wuteverserviceintent );

activity main > start activity( intent newactivityintent );

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

2. Design choices for SensorManager and apps using SensorManager

Hi,

application to poll sensor data while the SensorService in system
server controls the sensor.

I have 2 questions:
1. Why Android designs the SensorManager and SensorService in this
way? Most of time in Android, XxxManager usually is an easy-to-use
wrapper for a XxxService and the service interfaces with HAL. Please
kindly share the thoughts behind the design. Thanks.

(My wild guess is that sensor can be very demanding of CPU, if it were
read from system server, it would slow down the system).

2. I would like to develop some fancy algorithm on sensor. And I would
like to let a number of applications to use the outcome of my
algorithm. Now I faces 2 design choices:

1) I can put the class for the algorithm in the framework, and let
each application to call SensorManager to listen to the SensorEvent
and pump the SensorEvent into my algorithm. When my algorithm outputs
something, each application can do its specific actions upon it. Or

2) I can create an apk which contains a service and my algorithm
class. The service will be started on demand and it invokes
SensorManager and pumps SensorEvent into the algorithm. When the
algorithm outputs something, it will broadcast an Intent and each
application can receive this Intent and do its specific action.

Please kindly help share your thoughts on the 2 design choices. Thank
you very much.

Sam

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

3. Google Streetview Data Format

4. where's android.telephony.TelephonyProperties moved to?

5. catching a trackball event

6. Problem with onChange of ContentObserver

7. Trouble with Chronometer object