I tried running Bluetooth low energy sample code from android on two different android phone that has Android Lollipop installed and it supports BLE 4.0 too. but when i run the app and try to scan it , i am not able to get the name of other device in a list.
i am running this sample on Micromax android one.i am pretty new to BLE , so i am not sure i can see other BLE supported mobile phones in a list not just the peripherals.
i am running bluetoothlegatt sample from android only.
Related
I want to know if we can detect android phones as well with BLE Scan. I am trying to develop an android app which can scan nearby Bluetooth Android devices.
I checked both android devices are compatible with BLE with this app: https://play.google.com/store/apps/details?id=com.myan.michaelyanyoga.bluetoothchecker
Note: I am using this code to develop my scanner app: https://github.com/kaviles/BLE_Tutorials. I am able to see my laptop Bluetooth on this list but not other android phones(which supports BLE).
To detect Android phones using BLE, the other device needs to:-
Have Bluetooth turned on.
Be advertising
Unfortunately, most devices are not doing this by default, which means you may not be able to use BLE for your intended purposes. You can test this by doing the following:-
Download the nRF Connect Android app.
Go to ADVERTISER from the top menu.
Toggle the "Test" advertiser.
After this you should begin to see your Android device via Bluetooth.
I hope this helps.
I'm working on a BLE application for both ios and Android devices.
The application is written utilizing ionic and cordova.
On my Samsung Galaxy S6, Android version 6.0.1, my application will not populate the scan list even though I know I have devices advertising. Other generic applications like BlueScan and Bluetooth LE Scanner run on this phone do populate the scan list as I believe they should.
I also have access to two other Android devices--Motorola MotoG and Samsung Galaxy Tab 4. Both of these two devices will populate the scan list as desired running my application.
ios phones also populate the scan list appropriately.
Has anyone else run into such a problem with a Samsung Galaxy S6? If so, were you able to determine if there was a modification required to the app's source code or some setting needing adjusting on the phone itself?
An updated version to the BLE plugin we were using proved to have a fix for this issue.
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'm using the RFDuinoTest app to test the module, but it is not getting detected by any of the android devices.
Two of the devices I've tried this on are:
-Samsung Galaxy Grand 2
-Nexus 7 Tablet
I've also tested the module with iphone 5 and it works fine. There aren't any issues in programming it either, and I've tried both with Windows and Mac.
Is there a chance that this is because of some problem with the android devices and not with the module? Or should I just assume that the module is damaged?
To simply test the ability to connect and interact with the rfduino from your mobile device, use a BLE smart device scanner. Try BLE Scanner for Android.
I found myself in the same predicament when attempting to use the RFdunioTest app for Arduino. I do not know why that app does not pick up surrounding rfduinos.
Followed Android Wear GUIDE.
People noted this :
The Android Wear Preview app is compatible with Android 4.3 and higher and is not available for the Android emulator.
This thing may be indicated that it will use Bluetooth Low Energy - BLE, to establish connection between Android Wear device - Wrist Watch, and Android mobile devices since BLE technology only be available on Android 4.3 or higher, and not available on Android Emulator. But I am not sure.
Currently I know this to connect Android Wear Emulator with Android Phone device :
Connect your device to your development machine over USB.
But I wonder that when Wrist Watch device with real Android Wear SDK was released,
It will be used what's thing to connect to Android Mobile device?
Please tell me,
Thanks,
p/s : If I am right, it also means the Android Mobile devices can connect to Wrist Watch will be limited since not most of Android Mobile devices always support BLE technology.
Long story short: No-one knows for sure.
Long story long: Your observations point to BLE, and looking at the emulator we can also find pieces of information pointing to a bluetooth-based connection.
But until Google releases more information on how things are going to be, we cannot say anything for sure yet.