Does RadiusNetwork's IBeacon Locate app supports Nexus 5 and Nexus 4 ?
Both of my devices are running stock android 4.4.2.
I am trying to detect an iBeacon, which is detectable from an iPhone.
I got "Unfortunately, Bluetooth Share has stopped." every time i'm running the App.
For Nexus 4, i turned off the Wifi before running the app.
Thanks!
As Chris Stratton suggested in his comment, this is a bug in Android bluetooth code.
In Chris' link, davidgyoung also provided a link to his blog about solution to this issue.
Thanks to both!
Related
I'm trying to connect my Android phone to Arduino board with USB Host Sheild in order to let Android to launch my app in accessory mode. Basically, it works perfectly well on older devices as Moto G (2015) - Android 6.0, Nexus 5 - Android 6.0.1 and ancient noname tablet with Android 4.4.2. But I noticed that on Android 7 and above the app doesn't get launched or no prompt accessory dialog is shown, I tried a few Huawei devices, Xiaomi all of them have Android 7 or above.
So, my question, is accessories API still available in Android 7+? Thanks in advance.
UPD. Seems I got pretty firm evidence that Accessory Mode is still available in Android. Basically, I tested my solution against Google Pixel 3XL with Android 10. Works well.
Thus my conclusion is, how well that mode supported is up to a manufacturer.
Is there any ideas how enable this mode, maybe by installing custom ROMs or using some unofficial tweaks. Thanks.
Of course it does - but these stock ROM might lack an application to deal with it. The problem rather seems to be that usbremotecontrol.com went down - and the one snapshot available on archive.org looks strange. Just see which application is used on these Android 6.0 devices.
I am developing an Android app based on the sample project BluetoothLeGatt provided by Google, that exchanges BLE data with another device.
Tests run on Android 4.3 (API 18 - Samsung Galaxy S3) worked fine, but when I tried it on Android 6.0 (API 23 - HTC One M8), I noticed significant performance issues: the BLE seems to slow down the application, which display haltingly the data received through notifications.
As I suppose that the HTC is more efficient, is it due to the BLE implementation on newer Android APIs? Or the sample project that is out of date?
Thanks in advance for your help
I finally found the solution. Actually the issue didn't came from the Android "Central role" side. It came from the "Peripheral role" side played by my TI SensorTag, which updates automatically the connection parameters after 6 seconds, to go under some kind of low power mode (with a longer connection interval).
6 months later... that's never too late!
we are developing an Android app which can connect to multiple heart rate sensors simultaneoulsy via Bluetooth Low Energy.
We have an implementation which is working quite well, so the code is not the problem.
What drives us crazy is the limitation of parallel BLE-connections which seems to be different from device to device.
We have a few test devices here: Motorola MotoE and MotoG, a Samsung Galaxy Tab A and an HTC Nexus 9. All of them are running Android 5 or 6, original vendor versions. None of them is able to connect to more than 7 BLE HR sensors simultaneously.
Then I have tested with my private Samsung Galaxy S4, which is rooted and has Cyanogen CM12 installed. With this device I can easily connect to 12 HR sensors simultaneously which is the number we want to achieve with our app.
I have tested this both with our own app implementation and with the Nordic Semiconductor nRF Master Control Panel which I think is a pretty good generic BLE app: https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=de
When I try to connect the app to a 7th BLE sensor on any of our devices, the ADB output prints the following error message:
E/BluetoothLeBasicConn: Connection state changing error: 133
I did some pretty intensive googling about that whole problem, but most of the results I've found were quite old. Some people said, that the limitation came from the Bluetooth Chipset itself, others said it was a software limitation through Android.
Could you help me to find out, where the limitation is coming from?
If it is the chipset, then I would like to know, which devices we should use for supporting as many parallel connections as possible. Sadly it is very hard to find out which Bluetooth chipset is built in the different devices. Hardly any of the hardware specs I found tell anything about this.
If the limitation comes from software side, can we change it somehow without rooting phones or install modded OS?
Thank you very much!
In case that you are still interested in it. The limit comes from
BTA_GATTC_CONN_MAX (hardcoded in android)
Which is set to:
4 on Android 4.3 and
7 on Android 4.4
There is by the way also a limit on the amount of characteristics for which you can activate notifications. (BTA_GATTC_NOTIF_REG_MAX)
which is:
4 on Android 4.3,
7 on Android 4.4 and
15 on Android 5.0
I'm trying to develop a bluetooth 4.0 app for S3. The problem is, the phone behaves like it doesn't even have bluetooth 4.0. It doesn't discover 4.0 devices, and isn't discoverable with 4.0 devices. I tried both in the settings of the phone and in an app, using the Broadcom-ble API. The Broadcom API doesn't have any extra functionality for finding/discovering 4.0 devices, rather it uses the regular BluetoothAdapter functionality and claims that it will be augmented in 4.0 phones to also discover 4.0 devices.
Has anybody tried using bluetooth 4.0 on the S3? Has anyone succeeded in using the Broadcom API?
Thanks in advance.
This is now a confirmed bug, that will be fixed "in future releases".
See this forum thread at Samsung.
A beta for Samsung BLE SDK has been released here. I am going to study this SDK and hopefully it solves some of my problems.
It has been reported by Andrew Dodd, a senior XDA developer, that the Galaxy S3 doesn't actually support Bluetooth Low Energy
The Galaxy S3 has been marketed as Bluetooth 4.0 Low Energy (aka Bluetooth Smart) since its release - but it is not actually BTLE capable -http://developer.samsung.com/forum/board/thread/view.do?boardName=GeneralB&messageId=157757 - Samsung is STILL advertising the device as BTLE capable when it is NOT, despite the fact that they have been aware of this false advertising for months.
Samsung have a page at:
http://developer.samsung.com/ble
where you can download a Bluetooth LE SDK and sample code (registration is required, but otherwise it's automatic).
For what it's worth, there's an HTC page at:
http://www.htcdev.com/devcenter/opensense-sdk/partner-apis/bluetooth-low-energy/
where you can request access to their 'Partner APIs'. This needs license agreements to be signed (which for me means lots of lawyering) so I've not actually got code from them yet..
Ian
Refer this link
http://e2e.ti.com/support/low_power_rf/f/538/p/240097/879328.aspx
http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/538/8880.S3-BLE.zip,
attachment package can run on Samsung S3, now it limit with discover BLE devices and pairing. Some recent days, i try to find out how to send/receive data. But still not any luck.
I hope it can help.
Update your phone to Jelly Bean, then download nRf Utility from the Play Store, it can scan BLE devices around you!
Huawei Ascend G300-U8818 comes with android 2.3.6 os version.
I had successfully compiled the source code of android ICS
Is it possible to port android ICS on Huawei G300-U8818?
If its possible to port then how device performance will be affected?
Official website of Huawei keeps silence about porting android ICS to Huawei G300-U8818.
How do I make sure that porting is possible or not?
Thanks.
g300 will update to android 4.0 on the 3rd season said by offical website
http://www.modaco.com/forum/650-huawei-ascend-g300-g300modacocom/
ics already out in china works fine in uk
U8815 and u8818 are the same device