title: Android Bluetooth Low Energy (BLE) API Not Ready for Prime Time
body: <p>I am working on a fitness app that is to supports two BLE sensors (heart rate, stride).  I ended up with two bounded services (one for each sensor) called and bounded by my main activity.  This is running on Nexus 7 II, with KitKat.  I have spent days trying to get the app to stable state.   The Gatt connections, and notifications work perfectly right after a clean reboot. The problem I am having is getting things back to a working state after one or both of the devices get disconnected and needs to be reconnected.  Since similar issues have been reported by others, I have developed and tested various scenarios which included keeping the service and the connections going when the activity is restarted, closing the connections and the server and then starting fresh, closing only and not disconnecting, waiting before reconnecting, etc.  Currently, with one sensor, I can get the app to reconnect most of the time.  With two sensors,  the connections do not get re-established most of the time.  It is such a shame that android BLE API is so fragile considering that there are many new BLE devices every week.  I am wondering if anyone else has had much luck with multiple BLE sensors and if they would share their approach to get it working.</p>