GitHub PushEvent at 2014-12-01 13:27:31
Repository: qtconnectivity
Actor: qtprojectmirrorbot
Payload: {"shas":[["78954716c7dfb5334386ba28d09363468a7fead2","429ec4e831e8320529ddfedc4983cef56f3f7ae1@theqtcompany.com","Android: Add characteristic indication support\n\nAt this point in time characteristic indication is very much under-\ndocumented. We have to make some guesses along the way notifications work.\n\nAlso, it turns out the code already supported indications but was not\nvery future proof. If the ClientCharacteristicConfiguration is expanded\nby future Bluetooth specifications the notifications could have been\nenabled despite the two relevant bits not being set. All that was\nrequired was to write {0xFC FF} and the notifications would have been\nenabled. This was due to assumption that only the byte array {0x00 0xFF}\nbeing the disabling data set.\n\nChange-Id: I6c54d557f51977418f91baf658b62e1121785029\nReviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>\nReviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>","Alex Blasche",true],["b82007fd2425bf7cae13dd525087bf390047a8cd","2b2da7ee70058494f2830a2dd496cfc458ab949b@digia.com","QLowEnergyController - concurrent characteristic writes\n\nQt's API assumes that several write operations must be\nserialized (this is not guaranteed with Core Bluetooth AFAIK).\nI can enqueu only write with response operations, otherwise\nI never know when to do the next write.\n\nChange-Id: Iaa83514748358437e2c39335ab142d084ff197e3\nReviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>","Timur Pocheptsov",true]],"size":2,"ref":"refs/heads/dev","head":"b82007fd2425bf7cae13dd525087bf390047a8cd"}