Andreas Shimokawa 6125594703 Various changes related to INITIALZED device state ... Due to a bug in DeviceCommunicationService.isConnected(), devices using the INITIALIZED state only worked when they had useAutoConnect set to true (Mi Band) Now setting devices to INITIALIZED state to allow any action send to DeviceCommunicationService is mandatory. As an exception only REQUEST_VERSIONINFO will be also be allowed for CONNECTED state. This also fixes a problem when notifications came in on the Pebble with 3.x FW before we actually knew it was FW 3.x (INITZALIZED state on the Pebble now implies that we know the FW version)		2015-08-07 13:24:54 +02:00
..
bt	More refactoring: new service/devices package and service/bt package	2015-08-03 23:51:53 +02:00
btle	Initial support for transaction-local GattCallbacks (not used yet)	2015-08-05 23:26:09 +02:00
devices	Various changes related to INITIALZED device state	2015-08-07 13:24:54 +02:00
receivers	Big refactoring: move classes and packages around to get a better structure	2015-08-03 23:09:49 +02:00
AbstractDeviceSupport.java	Big refactoring: move classes and packages around to get a better structure	2015-08-03 23:09:49 +02:00
DeviceCommunicationService.java	Various changes related to INITIALZED device state	2015-08-07 13:24:54 +02:00
DeviceSupport.java	Last refactoring for now: BluetoothCommunicationService	2015-08-04 01:01:14 +02:00
DeviceSupportFactory.java	Last refactoring for now: BluetoothCommunicationService	2015-08-04 01:01:14 +02:00
ServiceDeviceSupport.java	Big refactoring: move classes and packages around to get a better structure	2015-08-03 23:09:49 +02:00