From: Florian Grandel <fgrandel@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Nexus 4 in BLE peripheral role with bluez stack
Date: Sat, 28 Mar 2015 00:51:05 +0100 [thread overview]
Message-ID: <5515ECE9.9080101@gmail.com> (raw)
Hi,
I recently built an autonomous bluetooth LE network (based on Nordic
nRF51822 central/nRF8001 peripheral µC) which I use for basic home
automation tasks.
To access this network from my Nexus 4 I need to put the phone in a
peripheral role so it can connect to the nRF51822 central.
As bluedroid won't support older Nexus phones in a peripheral role
anytime soon and is difficult to hack I was looking into bluez as an
alternative. I looked through the bluez source over the last few days,
watched your latest commits and list conversations, read up all kind of
README's and API docs.
I'm pleased to see that you're actively working on the kernel-side LE
advertising mgmt API and that you already implemented HAL stubs on the
Android side for the Lollipop 5.0 peripheral role enhancements.
It seems that the min requirement for peripheral role support in Android
would be at least 5 concurrent multi-advertising instances.
What is your schedule for the implementation of the multi-advertising
stubs in the Android bluetoothd HAL daemon? Is someone working on it
already? Would you welcome patches? (I never contributed to bluez,
though, and would require a bit of initial 1:1 support...)
Is there still something else missing on the kernel side or in userland
to make multi-advertisement work? Or is it all just about HAL support now?
Kind regards,
Florian
--
Florian Grandel
Freelance Software Developer
next reply other threads:[~2015-03-27 23:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 23:51 Florian Grandel [this message]
2015-03-28 0:01 ` Nexus 4 in BLE peripheral role with bluez stack Marcel Holtmann
2015-03-28 6:45 ` Multi-Advertising: implementation options, timing questions Florian Grandel
2015-03-28 6:57 ` Marcel Holtmann
2015-03-28 13:32 ` Florian Grandel
2015-03-28 20:18 ` Arman Uguray
2015-03-29 23:23 ` Florian Grandel
2015-03-30 0:48 ` Marcel Holtmann
2015-03-30 17:23 ` Jakub Pawlowski
2015-03-30 17:44 ` Arman Uguray
2015-03-30 18:04 ` Jakub Pawlowski
2015-03-30 21:57 ` Marcel Holtmann
2015-03-30 22:26 ` Jakub Pawlowski
2015-04-01 12:34 ` Florian Grandel
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=5515ECE9.9080101@gmail.com \
--to=fgrandel@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.