New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLOSED] Support for bluez bluetooth low energy #9
Comments
Comment by fibasile Hi, I've compiled the bluez 5 and it works fine. It's quite big package and many files must be removed to fit into flash. I think I can send a pull request during the weekend.
|
Comment by dragom Great!!! |
Comment by fibasile While I find the time for a full pull request, please find attached the Makefile i'm using for the bluez package. Just create a bluez folder into the trunk/feeds/packages/utils/ and compile it.
|
Comment by dragom Great! Will try. I'm just struggling to make basic build work. Will let you know when I am able to test it. No additional patch, config files? Just Makefile? |
Comment by fibasile Yes, you need only this with the flags provided it compiles.
|
Comment by dragom Thnx again. Will let you know how it goes. Do you have any experience using bleno,noble on Yun? |
Comment by dragom It works! I am able to use Yun as ble beacon with this one |
Comment by tigoe Any luck getting BT Audio to work? I didn't have much luck with that. t. On Jan 11, 2014, at 3:53 PM, Dragoslav Mlakar notifications@github.com wrote:
|
Comment by fibasile Personally I didn't try with audio. Anyway, to compile audio support you need to edit bluez Makefile removing the --disable-audio flag. No idea if it compiles without errors. |
Comment by dragom @fibasile
So I manually activate when dongle is plugged in with: root@DrYun: @tigoe Will try to compile with removing --disable-audio and version of bluez 5.13, publish ipk so you can try |
Comment by fibasile @dragom thx. I used a CSR 4.0 dongle and another unbranded one, both work fine on the detection phase. But none of them shows up as iBeacon. I was using the raspberry pi tutorial from radius network for that. |
Comment by dragom @tigoe |
Comment by fibasile Great, I can confirm iBeacon is now working using your latest ipk build and the adafruit tutorial linked above. The dongle is an IOGear bluetooth 4.0 adapter (http://www.iogear.com/product/GBU521/) |
Comment by dragom @fibasile |
Comment by fibasile I just installed kmod-bluetooth ipk and plugged the device. Modprobe stuff 2014/1/12 Dragoslav Mlakar notifications@github.com
Fiore Basile |
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
This required - a bluez-* upgrade to 5.13 (thanks fibasile and dragom arduino/openwrt-yun#9 (comment)) - a glib2 upgrade to 2.28.8 (required by bluez) - patching cwiid as it was using deprecated hci_remote_name() function from bluez-libs
Issue by dragom
Wednesday Jan 08, 2014 at 19:54 GMT
Originally opened as arduino/linino#21
Is it possible to upgrade bluez libraries to latest one to have support for LE?
Current one looks that don't have le functions.
The text was updated successfully, but these errors were encountered: