From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: bill dr <bilel.dr@gmail.com>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: BLE for Android
Date: Fri, 3 Jan 2014 13:55:20 +0200 [thread overview]
Message-ID: <20140103115518.GC9809@aemeltch-MOBL1> (raw)
In-Reply-To: <CAHTi60E1Qo1XNM+hyaMo9zWbVpNoKYqD8L4MtdbqPEZ43yJWuA@mail.gmail.com>
Hi Bilel,
On Fri, Jan 03, 2014 at 12:39:04PM +0100, bill dr wrote:
> Hi all,
> Thank you Luiz and Andrei for your responses.
>
> @Andrei : I am aware that the latest android version supports "as best
> as it can" BLE. But I have a constaint to use 4.1 Android only.
>
>
> That lead us to my second question : what should I do to add such support ?
>
> If I have understood correctly the HAL Bluetooth (in Bluez package) is
> different from Android HAL.
There is no Bluetooth HAL in Android 4.1, HAL appeared when Android moved
to Bluedroid stack in version 4.2.
> so to have BLE support in Android 4.1 I have to:
>
> 1- Adding the last Bluez package and compile it.
> 2- make changes to Android Bluetooth HAL or just add a JNI interface
> wrapping the Bluetooth HAL one ?
> 3- make changes to system service to support BLE.
> 4- make changes to Android SDK to export these changes to developpers.
Looks too much work for nothing.
> Is it correct ? is there more straightforward way ?
> especially about the second point and the confusion between Bluetooth
> HAL and Android HAL.
Forget about HAL, hack JNI ....
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2014-01-03 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 11:47 BLE for Android bill dr
2013-12-31 12:02 ` Luiz Augusto von Dentz
2014-01-03 11:02 ` Andrei Emeltchenko
2014-01-03 11:39 ` bill dr
2014-01-03 11:55 ` Andrei Emeltchenko [this message]
2014-01-03 12:02 ` bill dr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140103115518.GC9809@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=bilel.dr@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox