Bluetooth A2DP compliant headsets don't get recognized with my Samsung Galaxy Tab (T-Mobile) with Android 2.2. I'd like to make it work. The Samsung FAQ says that A2DP is supported. But I've had no luck getting the Tab to recognize these any BT headsets. Can you help?
The problem was that the Samsung Bluetooth API filtered out zero class bluetooth devices resulting in detection problems (or not finding some devices). Samsung has now fixed this problem so all you have to do is upgrade the firmware on your tablet (using Kies) and that should take care of your problem.
Related
When I press a button on a device that is connected to iOS or Android via Bluetooth, it should perform some task in an app(app installed on iOS or Android). I am not sure which Bluetooth profile will be best for my job. I think HID profile, but will it work with iOS ? Any suggestions or comments are welcome.
iOS devices can't use standard Bluetooth connection with Android. In this case you should use BLE (Bluetooth Low Energy). This means you should use GATT profile for Android. There is an important issue here: all iOS devices can BLE peripheral or central but for Android some devices only can peripheral.
I'm trying to implement Bluetooth Low Energy . The fact is, I can find some devices around me, so the scanning seems working, but there are some devices which I can't find ... such as a motorola, which has Android API 19, so since BLE is enabled since API 18, shouldn't it work ?
So my question is, are there some devices not compatible with BLE ? (I can found some devices but not all)
What do you mean by "device"? Motorola what? Phone? Watch? Light bulb?
If your phone can search for and find some ble enabled devices then it got both hw and sw support.
The other "device" must be ble advertising for your phone to hear it during scanning.
A Motorola phone with android api19 can only scan, not advertise. Some android 5 devices can do ble advertise, so they can be scanned by android api19 devices but not the other way round.
I'm wondering if Bluetooth 4.0 (low-energy) mobile phones could discover classic Bluetooth devices (3.0 and lower), and vice-versa. All I am interested in is discovering the "friendly names".
EDIT: As I have understood the replies of this post, Bluetooth 4.0 can discover classic Bluetooth devices but not the other way around. Then my follow-up question is, can a Bluetooth 4.0 device in LE mode discover classic Bluetooth devices?
The answer depends on if you mean Bluetooth v4.0 device, or BLE device, the two are not the same.
Bluetooth v4.0 = Classic Bluetooth + Bluetooth High Speed + Bluetooth Low Energy
Therefore, Bluetooth Low Energy is only a subset of Bluetooth v4.0. If your question is regarding Bluetooth v4.0 phones (generally phones are not BLE only), then the answer is Yes, Bluetooth v4.0 mobile phones can theoretically discover Bluetooth v3.0 devices and lower.
Hate to be blunt, but nope not possible (although it would be handy). 4.0 is 4.0 alone. Check out the Bluetooth Core Spec for more info
No a BLE can not discover a classic bluetooth device nor a classic bluetooth device can discover a BLE.
A device with BT V4 will discover both.
And A BT V4 will be discovered by BLE if it is advertising as BLE.
I also had same question, so I did little experiment.
I may contribute to this topic from my experiment that I did with old mobile(Nokia C5-00), New mobile(Samsung galaxy grand prime) and two bluegiga ble113 chips.
I swithched on bluetooth of all the devices and started scanning for near by devices I observed the following:
Observation1: Samsung galaxy grand prime (BT version 4 +Ble): It was showing both bluegiga ble113 chips, and Nokia C5-00 on the list.
Observation2: Nokia C5-00 (Earlier version of BT): It was showing only Samsung galaxy grand prime in the list.
Observation3: ble113: Out of the two ble113 chips one was in advertising mode and other in scanning mode at first the scanner chip was discovering only other BLE113 advertiser chip, but when I started advertising from Samsung galaxy grand prime phone using BLEBroadcast app the ble scanner chip started discovering the Samsung galaxy grand prime phone also.
Its perhaps late but just to clarify. The question in the title sounds like its asking about the interoperability of the two different Bluetooth modes, but the details of the question drift toward whether or not the mobile phone supports these two capabilities.
As far as the interoperability is concerned, as pointed out by VSingh, Classic Bluetooth discovery and Bluetooth Low Energy discovery work in opposite ways.
In classic, the endpoint [eg your Android] SEARCHING for devices TRANSMITS inquiry packets. Devices in discoverable mode, LISTEN for these packets and respond accordingly.
In Bluetooth Low energy, the endpoint [eg your Android] SEARCHING for devices LISTENS (scans) for advertisement packets. BTLE devices that are discoverable TRANSMIT these advertisement packets.
If the radio on your mobile device can do both of these things, then you can discover both classic and low energy devices.
is there a way of importing the most used Android devices (for example Galaxy family) to the Android Virtual Device Manager as by default there is only some Nexus stuff in there?
Or did you create the Galaxy family the manual way in terms of specifying screen size for each device, upload device frame etc.?
Thanx for your help,
Florian
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