I am a person who is developing an Android application using BLE.
In order to communicate with the device(peripheral) through BLE communication( GATT )
Galaxy Note 9, a terminal that was used for testing, suddenly started to not connect to GATT.
So I tested it with the Galaxy Tab (sm-t510) and it works fine. I build it on the same code, but I wonder why the Note 9 gets dirty as soon as it is connected to GATT and breaks really immediately.
In contrast, the tabs are doing very well.
I searched on the wiki, the tab is bluetooth 5.0 and the Galaxy Note 9 is bluetooth 5.0 + LE.
The device(peripheral) identifies the Bluetooth 4.1 device.
If you have any doubts about it, please help me
Related
We have a custom hardware product that uses bluetooth to communicate with an Android application.
Recently we have been getting reports of issues by users that use LG Velvet phones (LM-G900EM). We bought a Velvet and tested it ourselves. The phone will connect to the device, do a service discovery and then disconnect with an error. Usually codes 133(0x85) or 8(0x8).
To verify the issue we connected using the Nordic NRF Connect app instead of our own code. The behaviour is exactly the same.
Attempting the exact same actions on other phones all work perfectly, including other phones running the same version of Android (10) and the same Bluetooth version (5.1) as well as iPhones.
I'm not sure where to even begin addressing this issue. Does anyone have any insight?
This also seems to be an issue on some of the newer ThinQ series phones from LG though we do not have one to verify.
The issue turned out to be the Bluetooth firmware on our hardware. We use Microchip Technology microcontrollers and Bluetooth chips. Upgrading to version 1.4.1 of their firmware fixed the issue.
Apparently this issue also affected certain Xiaomi phones.
I'm currently looking into an issue where my companys app have some trouble establishing searches and connection to a cadence BLE peripheral.
We're developing using nativescript#6.1.2 {N}6 and for the past long while we've used the nativescript-bluetooth#1.3.1 plugin with no issue. It's been used primarily on tablets with bluetooth 4.x.
Problem started when we tried our app on Samsung Galaxy tab A7 with bluetooth v5.0. The app wouldn't start a search or connect with the usual peripheral Wahoo cadence sensor.
What I can do is see the Wahoo sensor in the Android Bluetooth Manager as well as nRF connect and Wahoo's Fitness app. But using the usual plugin doesn't seem to be able to do anything.
I'm still fairly new to the BLE programming game, so if anybody have any advice as to why the Samsung Galaxy tab A7 with bluetooth 5.0 won't connect, I'd be happy to receive some.
So nativescript-bluetooth 1.3.1 is no longer valid in Android versions 10+. I have to migrate my app to nativescript 7 as well. I'm having trouble with migrating, and if you have any suggestions for some of my questions, I would greatly appreciate it!
I developed an Android app to scan and connect to a BLE device. I tested it in Micromax Tab and some other devices, it was working fine.
But recently I tested in ASUS tab (C 7.0), most of the time it fails to scan the BLE devices (Sometimes its working fine).
Currently I faced this issue only in ASUS tab, rest of the Mobiles and Tabs are working fine.
Can anyone suggest what might be the issue?
I'm not even getting any warnings and errors.
I have discovered that the devices having Intel processor is having problems in BLE communication.
The devices having Mediatek, Qualcomm processor is better for BLE communication.
I'm trying to communicate two smartphones with Android 5.x through BLE.
First of all, I've installed the sample app from Google (https://github.com/googlesamples/android-BluetoothLeGatt) to test if the devices are correctly y scanned, but tablets and smartphones are not detected (the bluetooth is visible and enabled in both cases).
In the list only appears bracelets like Xiaomi MiBand, Fitbit... and some Macbooks, but nothing else.
I've read this report: https://code.google.com/p/android/issues/detail?id=82293
and this post (with Android 6.0 must be enable the location): Bluetooth Low Energy startScan on Android 6.0 does not find devices
I've tested with multiple scan apps from the Play Store, but all of them show the same result... I'm going crazy.
Scanning from Settings -> Bluetooth the result is correct (smartphones and tablets are detected).
Any idea about this problem? Why this devices are not appearing on the BLE scan?
Smartphones and tablets used to test:
Samsung Galaxy S5
Xiaomi Redmi Note 2
BQ Edison 2
iPhone 5
If device has BLE it does not mean that it will be visible (broadcast) any data by default. In order to achieve communication between two smart phones you need to have (install or write your own) application that uses BLE to create proper BLE service that will be exposed to other devices.
Some BLE capable devices such is iPhone for example broadcasts BAS (Battery Service) or similar, but I don't think that Android does.
So, don't expect to find any device on scan that you have described, and if you still need
to communicate two smartphones with Android 5.x through BLE
try to read Bluetooth Low Energy documentation and be ready to understand UUID, GATT, Characteristic...
I am currently working on an Android project that requires Bluetooth Low Energy Peripheral mode. As of now, just targeting the Galaxy S4 with 4.2.2 on it Samsung BLE SDK at http://developer.samsung.com/ble
I followed their API docs and programming guide very closely, however broadcasting characteristics or services over Bluetooth Low Energy just doesn't seem to work. Has anyone else had any luck with getting this to work yet? If so, any help would be greatly appreciated!
Thanks a lot.
Because Samsung BLE SDK only supports the central role, “advertising” a service as a central server means sitting their quietly, only revealing (or “advertising”) its service characteristics to another device in peripheral mode after a connection is already established. This connection establishment requires another device to do the actual radio advertising first. Samsung’s SDK isn’t going to do it.
What we need is an Android BLE API that allows creation of a peripheral server. Lots of folks were hoping that peripheral role support would be added in 4.4, but it wasn’t. Maybe we can hope for its addition in Android 4.5 or 5.0. There is a feature request asking for this. Add your name to the list!
Source
I am having the exact same issue. I can discover BLE devices and get their rssi values, but when I try to discover services or connect, I never receive a callback. I am using a Verizon Galaxy S4 running 4.2.2. I am using the Samsung BLE SDK 2.0. Apparently some heart rate monitors are working, but I get nothing using my ez430-rf256x TI development kit. I've tried the Keyfob demo and Heart Rate Profile demo in the Bluetopia v1.3 sdk.
Phones/tablets/pc's support(usually) Bluetooth dual mode chip. According to Bluetooth specification dual mode devices can't be a peripheral, but single mode devices do.