I would like try to connect two devices via BLE classes and i found the following Website for reference
Bluetooth
And before i am starting with programming the classes i wanted to know if ist even possible to connect a Bluetooth 4.2 and a Bluetooth 4.0 device together?
Because of i have a MCU with Bluetooth 4.2 and a Tablet with 4.0 and i am trying to write an app to connect those two devices.
I've already tried to connect an Iphone with Bluetooth 4.2 to my MCU and this is working but with my Tablet i get the message "Connect has been declined by the other device" (i still try it outside of my app and only on the android System under Settings).
Maybe this is the totally wrong community but i've just wanted to give it a try maybe somebody has an answer for that
Related
I just randomly found a Bluegiga BLED112 Bluetooth dongle and I tried to connect it to my Debian 10 laptop as a basic dongle for Bluetooth audio outs.
Unfortunately I wasn't able to solve all the issues I had, starting from the fact that the device is not fully listed once used lsusb and just a mere ID number - namely ID 2458:0001 - pops out and bluetooth or bluez helps weren't successful either.
This given, I tried to follow several of the guides you can find online, also by running available scripts, but again nothing worked.
So if it's possible, what should I do in order to run such a dongle for the basic use I mentioned above - i.e. just for connecting my stereo speakers to my computer?
Thanks
The BlueGiga BLED112 is not a regular Bluetooth USB dongle. It gives you a virtual com port that can be used to access an API that in turn acts as a BLE device.
It is ment to be used for development of IOT solutions.
Also it does not support Bluetooth Classic, it only supports Bluetooth Low Energy.
What I was wondering is if there were any type of handshake process that happens when two Bluetooth devices connect that both tell each other what version of Bluetooth they support and just use the lowest available version that they both support. And if that negotiated version is stored anywhere for API use?
Android device: Bluetooth 4.2
IOT device: Bluetooth 4.0
Negotiated: Bluetooth 4.0
So from the example above the two devices have decided on using Bluetooth 4.0, now do system Bluetooth API's have access to viewing the negotiated version or does the Bluetooth chip just handle everything without offering that information?
I have an Asus USB-BT400 Bluetooth Dongle, it works with BLE devices. I also have an TI Sensortag, i installed the drivers and software and I can connect my PC to the sensortag (using windows 7 or windows 8.1 in VM, both works).
Windows doesn't find drivers for the sensors (I think 8 in total) so I would like to know how I can communicate to them. I already exposed a COM port for the bluetooth device (that's possible via Bluetooth settings). I tried the BLE device monitor, where the COM port shows up, but it gives an error (no response from BLE host at port COM3). I also tried the windows Desktop app (win8), which doesn't work either.
I would be glad for any solutions, resources and hints which do not require me to buy the Dongle from TI website for ~50$.
Thank you!
I don't believe it works under anything less than Win 8.1 as the OS must have the BLE Profile drivers.
Running VM is not going to help, as you need those drivers at the base OS level.
I would like to run and test P2P connectivity over Bluetooth via Game Center (GKPeerPickerController). I own an iPod Touch with OS 4.1 installed and am trying to connect it to the iPhone Simulator running on my Mac via Bluetooth, however they are not seeing one another. Bluetooth is on for the iPod and the Mac. Is this even possible? If so, what am I missing?
I dont think it is possible, since bluetooth networking is currently not supported in the simulator.
check this for more detail..
http://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/GameKit_Guide/GameKitConcepts/GameKitConcepts.html%23//apple_ref/doc/uid/TP40008304-CH100-SW1
I want to know if the developer team which made the emulator have some information to make bluetooth work in the Android emulator, indicate some links about it, if they have some date for release or if they'll make it works in the future.
as far as I know there is no support in the emulator for bluetooth. And I will have to teach android and bluetooth in some classes. And the students will need to code stuff and test (guess it) in the android emulator.
So I came up with a bare-bone reimplementation of the android bluetooth API on top of tcp. You can find it on here on github.
Basically, you run a tcp-server on your machine, and the emulators will connect through it.
Instead of using the classes in the package android.bluetooth, you just need to use the classes in the package dk.itu.android.bluetooth (and other 2 little modifies).
As for now it supports:
switch on/off the "radio"
discovery devices (only other android emulators)
creating bluetooth services
connecting to bluetooth services
It's not much, but until we got some more from the android guys, I guess there is nothing else around.
Hope it'll be useful, cheers!
The documented bluetooth limitation appears inconsistent with the qemu -bt option. So, how is bluetooth enabled in the emulator so the -bt options can be used, or at least to know that bluetooth is supported?
The target/board/.../BoardConfig.mk having "BOARD_HAVE_BLUETOOTH := true" doesn't provide a bluetooth icon or enable bluetooth. So, how do we turn on bluetooth on the android qemu emulator?
What does it mean that bluetooth is not supported given the -bt option for emulating USB devices that were provided in 2008? The post and limitations are outdated.
The functional limitations of the emulator include:
No support for placing or receiving actual phone calls. You can simulate phone calls (placed and received) through the emulator console, however.
No support for USB connections
No support for device-attached headphones
No support for determining network connected state
No support for determining battery charge level and AC charging state
No support for determining SD card insert/eject
No support for Bluetooth
http://developer.android.com/tools/devices/emulator.html#limitations