According to Nick ... on porting newer BT stacks on android ..
http://osdir.com/ml/android-platform/2009-02/msg00442.html
On Fri, Jun 11, 2010 at 12:20 PM, Pavan Savoy wrote:
> Well it's not just BlueZ API is it ?
> Your stack also need to put up the DBUS interface similar to what
> Android JNI e
Well it's not just BlueZ API is it ?
Your stack also need to put up the DBUS interface similar to what
Android JNI expects or sort of re-write the JNI not to use DBUS and
link to your stack.
On Fri, Jun 11, 2010 at 12:16 PM, Surendra Ippagunta
wrote:
> Yes, if your stack has same BlueZ API. You c
Yes, if your stack has same BlueZ API. You can replace BlueZ source
code with yours.
Regards
Surendra
On Fri, Jun 11, 2010 at 9:39 AM, Ajith Kamath wrote:
> Since my present code base was originally derived from bluez(but now uses
> other stack) If I remove/modify the #ifdef codes(of my own sta
Since my present code base was originally derived from bluez(but now uses
other stack) If I remove/modify the #ifdef codes(of my own stack) in
BluezWrapper will my project end up using just Bluez?
Regards,
Ajith
On Thu, Jun 10, 2010 at 12:05 AM, Surendra Ippagunta
wrote:
> Hi Ajith,
>
> Android
Hi Ajith,
Android Java Classes use JNI framework to invoke the native C code.
There is JNI wrapper for BlueZ stack and I think you should insert
your stack here.
http://www.netmite.com/android/mydroid/1.6/frameworks/base/core/jni/android_bluetooth_RfcommSocket.cpp
Regards
Surendra
www.onchipte
On Wed, Jun 9, 2010 at 11:55 AM, Ajith Kamath wrote:
> Ya I know all makefiles from External are called but I need to trace the
> calls of make files from build script.
> Atleast that of Bluez makefile.
>
Yes this is sort of an eternal question ... we have the whole of
build/core directory to und
Ya I know all makefiles from External are called but I need to trace the
calls of make files from build script.
Atleast that of Bluez makefile.
Also BOARD_HAVE_BLUETOOH param is in Boardconfig.mk file right?
Regards
Ajith
On Wed, Jun 9, 2010 at 11:40 AM, Pavan Savoy wrote:
> i guess all android
i guess all android makefiles under external/<...>/ directory are called ...
the only way you could prevent bluez from building is making
BOARD_HAVE_BLUETOOH false ? (or atleast that's what i think ..)
On Wed, Jun 9, 2010 at 9:22 AM, Ajith wrote:
> Hi all,
>
> Our current solution does not use B
Hi all,
Our current solution does not use Bluez stack in Android , but source
of Bluez is included in the Project Source code
What I need to know is from where is the Make files of Bluez called
Android Eclair code.
ie, Android.mk file exists in \externals\bluetooth\bluez , and I need
to know wher
