ibeacon-android

All beacons are not shown in Android using altBeacon library

こ雲淡風輕ζ 提交于 2019-11-30 17:26:08
问题 I am using the AltBEacon Android library for developing an iBeacon app for Android devices . I am scanning for beacons, however, only two out of four beacons are found (sometimes 1/4). I increase mBeaconManager.setForegroundScanPeriod(5000l); to 5 seconds, but still same result. I am not sure if the CustomAdapter I use for binding details to view is wrong or the issue is do with the mobile device (I am using Galaxy Note II - Android 4.4.2 (KitKat))? Can anyone locate my mistake? Another issue

Radius Networks' ibeacon ranging fluctuation

六月ゝ 毕业季﹏ 提交于 2019-11-30 05:27:16
I'm fairly new to iBeacon but I have spent the day trying to get informations and a working Android application with iBeacon. I have stumbled upon Android iBeacon Library samples and gave it a try. I used the latest aar file (0.7.3) and basically copy/paste their examples in a new project. I have created a beacon using an iPad with AirLocate (compiled from Apple's code from the Dev Center) and launch the code. My problem is the range fluctuating all the time with no logic. For example, the phone (in this case a Nexus 5, original rom, no modification) placed half a meter away from the iPad

Decreased BLE startScan detected devices on Android 5.0 Lollipop

徘徊边缘 提交于 2019-11-30 01:47:31
Short version: In my tests with Android 5.0 Lollipop I have noticed android.bluetooth.le.BluetoothLeScanner detects BLE devices less frequently than Android 4.4 KitKat. Why is this and is there an alternative? Long version: I am developing an Android application, specifically for the Nexus 7 tablet, that focuses on detecting Bluetooth Low Energy (BLE) devices. The app is mainly interested in the RSSI value of the beacons, to determine their proximity to the tablet. This means I won't need to connect to the BLE device, since the RSSI value is passed to the scan callback when the device is

onServicesDiscovered not be called on BluetoothGattCallback

╄→尐↘猪︶ㄣ 提交于 2019-11-29 12:55:28
I start working with ibeacon and android. But there are some problem need for your helps. On blutoothGatCallback I implement onConnectionStateChange and call discoverServices(). Althougth, discoverServices() return true but there is not any callback execute, I hope onServicesDiscovered being called, but not. @Override public void onConnectionStateChange(BluetoothGatt gatt, int status, int newState) { Log.i(TAG, "onConnectionStateChange : " + status + " newState : " + newState); if (newState == BluetoothProfile.STATE_CONNECTED) { boolean isdiscover= mBluetoothGatt.discoverServices(); if

What is the correct BeaconLayout for Estimote and Gimbal beacons

不羁岁月 提交于 2019-11-29 09:32:13
问题 I would like the 2.0 release of the Android Beacon Library to be able to properly detect both old style Estimote beacons (pre-2013 models that did not support iBeacon technology) and Gimbal beacons. I know that Gimbal beacons have encrypted identifiers, so these cannot be read directly. But I would at least like to share code that can detect that one is around. Here is what I have: Code to detect a Gimbal beacon (without reading encrypted identifiers): BeaconManager beaconManager =

Radius Networks' ibeacon ranging fluctuation

為{幸葍}努か 提交于 2019-11-29 03:53:36
问题 I'm fairly new to iBeacon but I have spent the day trying to get informations and a working Android application with iBeacon. I have stumbled upon Android iBeacon Library samples and gave it a try. I used the latest aar file (0.7.3) and basically copy/paste their examples in a new project. I have created a beacon using an iPad with AirLocate (compiled from Apple's code from the Dev Center) and launch the code. My problem is the range fluctuating all the time with no logic. For example, the

Decreased BLE startScan detected devices on Android 5.0 Lollipop

寵の児 提交于 2019-11-28 22:35:30
问题 Short version: In my tests with Android 5.0 Lollipop I have noticed android.bluetooth.le.BluetoothLeScanner detects BLE devices less frequently than Android 4.4 KitKat. Why is this and is there an alternative? Long version: I am developing an Android application, specifically for the Nexus 7 tablet, that focuses on detecting Bluetooth Low Energy (BLE) devices. The app is mainly interested in the RSSI value of the beacons, to determine their proximity to the tablet. This means I won't need to

Android 5 static bluetooth MAC address for BLE advertising

谁都会走 提交于 2019-11-27 23:43:38
Android 5 introduces BLE MAC address rotating for increased privacy. Every time when calling BluetoothLeAdvertiser.startAdvertising(), the MAC-address is changed. Is it possible to disable address rotating, and just use the same MAC address during the entire lifetime of BluetoothLeAdvertiser? The MAC Address is a physical address and does not change. In BLE terminology, it is the Public Device Address or BD_ADDR for BR/EDR. I haven't tried it, but reading it with readAddress() should return the same value each time. What the Android's BLE framework does is NOT use that address when advertising

Android 5 static bluetooth MAC address for BLE advertising

我怕爱的太早我们不能终老 提交于 2019-11-26 23:21:02
问题 Android 5 introduces BLE MAC address rotating for increased privacy. Every time when calling BluetoothLeAdvertiser.startAdvertising(), the MAC-address is changed. Is it possible to disable address rotating, and just use the same MAC address during the entire lifetime of BluetoothLeAdvertiser? 回答1: The MAC Address is a physical address and does not change. In BLE terminology, it is the Public Device Address or BD_ADDR for BR/EDR. I haven't tried it, but reading it with readAddress() should

Does BluetoothLeAdvertiser work on a Nexus 5 with Android 5.0?

自古美人都是妖i 提交于 2019-11-26 19:37:10
问题 After flashing my Nexus 5 to the Android 5.0 preview release hammerhead-lpx13d, the OS reports that it no longer supports Bluetooth LE advertising. If you call: ((BluetoothManager) this.getSystemService(Context.BLUETOOTH_SERVICE)) .getAdapter().getBluetoothLeAdvertiser() always returns null. In addition, the new method: ((BluetoothManager) this.getSystemService(Context.BLUETOOTH_SERVICE)) .getAdapter().isMultipleAdvertisementSupported() always returns false The first method used to return a