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.
Related
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
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'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.
I am doing multicast in my android apps and I have some troubles like most of people ;-)
I have created an android application which listens for multicast.
It works fine on 2 phones and one tablet (Samsung S2 & S3 and Motorola). The problem is with an Asus tablet. When I launch the application only on this device, I can receive data via multicast but when I launch the app on another device I cannot receive anymore data on the Asus but it works on the other.
I read somewhere that some tablets don't support completly multicast but I don't really understand the meaning of "not completely".
Can anyone help me on this issue?
I will perform several test with another asus and an acer tablet next week to see if it works.
Thanks.
Anthony