I have read that Web Bluetooth API can connect to Bluetooth BLE devices. I understand that BLE is a part of Bluetooth V4, but will Web Bluetooth connect to a regular V4 device that is not BLE?
The version number in Bluetooth is mostly irrelevant. More optional features are added in every new version, but that's it. BLE was added in version 4. "Regular V4 devices" does not make sense. If you refer to "Bluetooth Classic" or BR/EDR devices, these are not BLE devices. However you will be able connect to these devices in Web Bluetooth if they run a GATT server, if the OS supports it, since GATT can also run over BR/EDR.
Related
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 want to scan and connect devices using Bluetooth in React-Native. I tried react-native-ble-manager and react-native-ble-plx plugins.
But I have a problem these plugins connected to special devices that have peripheral mode enabled. Look this answer.
Question:
How can I implement Bluetooth for all (at least all smartphones) devices in REACT-NATIVE?
Has anyone tried SPP service (RFCOMM) on Google glass? I couldn't find any documentation anywhere listing what kind of Bluetooth protocol or profile that Google glass supports.
I have run an OBEX service search on the glass, and it seemed like Google glass doesn't support OBEX. Other than OBEX, what other BT profile is known to work properly on the glass?
So for SPP service (RFCOMM) you can use the UUID "00001101-0000-1000-8000-00805F9B34FB" as you might already know, I'm using this and it works fine at 115.2K of baudrate.
Then in a separate thread you manage the connection, if you go to the developers portal of Android they have an explained example and good info of the protocol.
Using the Bluetooth APIs, an Android application can perform the following:
-Scan for other Bluetooth devices
-Query the local Bluetooth adapter for paired Bluetooth devices
-Establish RFCOMM channels
-Connect to other devices through service discovery
-Transfer data to and from other devices
-Manage multiple connections
Hope this helps!
Does Apple allow dual mode BLE connectivity in iOS? It seems that if BLE iOS apps could communicate to dual mode Bluetooth devices in BR/EDR mode, one wouldn't need to join the MFI program.
The CoreBluetooth library allows communication with a BLE peripheral using the GATT profile only.
The use of other profiles (aside from generic HFP/A2DP/AVRCP which is supported by AVFoundation and keyboards which have native HID support) requires going through the MFI program. So for example SPP.
And yes, iOS does not prevent using BLE for data communication while using an audio profile to the same device at the same time.
As of iOS 13 you can connect to both BLE and BR/EDR with CoreBluetooth, as introduced here.
Can a WindowsCE device connect so more than one BlueTooth device? The device needs to both serve as a BlueTooth hands-free speaker for a phone and connect to a third device via a serial BlueTooth connection.
Can an application do this without the need of a speciel driver?
You must understand that Windows CE is a modular OS and any specific platform capabilities are implemented by an OEM. An OEM can create a Windows CE device with absolutely no Bluetooth support or they might choose to implement just a Bluetooth client profile (say as a bluetooth audio device) or they may choose to implement a Bluetooth server so they can consume a Bluetooth serial device. They may also choose to implement both. Beyond what the OEM does in software, the hardware itself might allow only one or the other (or both or neither for that matter).
The short of this is that we can't actually answer your question becasue there is no generic answer that fits all devices. You have to ask the Device OEM what they support and if they can extend that support if they don't support what you need.