android-4.3-jelly-bean

I'm currently developping an Android app using Android Studio. Currently, the app is launching perfectly on Lollipop devices, but crashes at launch due to a ClassNotFoundException on pre-lollipop devices (i've tested on ICS and it fail). The missing class is always from an external librairies at runtime. Here's the gradle file : buildscript { repositories { maven { url 'https://maven.fabric.io/public' } } dependencies { classpath 'io.fabric.tools:gradle:1.+' } } apply plugin: 'com.android.application' apply plugin: 'io.fabric' android { compileSdkVersion 23 buildToolsVersion '23.0.0'

I am developing an application where I have to connect to Bluetooth device on Android 4.3. And I want to get the battery level by using Battery_Service and Battery_Level . public class BluetoothLeService extends Service { private static final UUID Battery_Service_UUID = UUID.fromString("0000180F-0000-1000-8000-00805f9b34fb"); private static final UUID Battery_Level_UUID = UUID.fromString("00002a19-0000-1000-8000-00805f9b34fb"); public void getbattery() { BluetoothGattService batteryService = mBluetoothGatt.getService(Battery_Service_UUID); if(batteryService == null) { Log.d(TAG, "Battery

I've got a working app using CoreBluetooth to communicate between an iPad (central) and iPhone (peripheral). I have one service that has two characteristics. I have a Nexus 7 running the latest Android 4.3 with BTLE support. Android is a bit late to jump on the BTLE bandwagon but it appears they are approaching it similarly to how iOS did, where initially they only support acting as a central with the peripheral mode coming in a later version. I can load the sample Android BTLE app and browse for nearby peripherals. With my iPhone advertising as a peripheral I can see the value from

Ever since I upgraded my Samsung Galaxy S3 to android 4.3 (from 4.1.2) I am unable to use Chrome's remote debugging for android (more details here ). I have the developer options and USB debugging enabled on my phone, and this worked perfectly fine on android 4.1.2. Now, when I connect my phone to my PC, it simply connects as a media storage device and is not discovered as a USB device by chrome. I am ruling out any problems with chrome as I could USB debug with a Google Nexus4, also, looking at some other thread (here and elsewhere) it seems to be a problem with Samsung's 4.3 upgrade. Any

I remember reading in the "Guide and Hint" -doc to the Samsung BLE API (archived page) : One of the most important concepts of the Samsung F/W and stack is its synchronous nature . That is, if we call for example, writeCharacteristic for a particular characteristic, if it returns true , the next call to any BluetoothGatt or BluetoothGattServer method should be done after the onCharacteristicRead callback is received. This is because the stack is designed to support and process only one GATT call at a time, and if, for example, you call writeCharacteristic or readCharacteristic on any

Device used for testing: Nexus 4, Android 4.3 Connection is working fine but the onCharacteristicChanged Method of my callback is never called. However I am registering for notifications using setCharacteristicNotification(char, true) inside onServicesDiscovered and that function even returns true. Device log (there are actually no messages at all when notifications should appear / are sent via the Bluetooth device): 07-28 18:15:06.936 16777-16809/de.ffuf.leica.sketch D/BluetoothGatt: setCharacteristicNotification() - uuid: 3ab10101-f831-4395-b29d-570977d5bf94 enable: true 07-28 18:15:06.936

I am having trouble using startLeScan( new UUID[]{ MY_DESIRED_128_BIT_SERVICE_UUID }, callback ) on the new introduced BLE API of Android 4.3 on my Nexus 4. The callback just doesn't get called. I still can see incoming packages in the log: 08-02 15:48:57.985: I/bt-hci(1051): btu_ble_process_adv_pkt 08-02 15:48:58.636: I/bt-hci(1051): BLE HCI(id=62) event = 0x02) If I don't use the parameter to filter for UUIDs it works. We are using a manufacturer specific 128bit UUID for device of our company. Now, our device offers more services than I am providing in the array. But that shouldn't be the