summaryrefslogtreecommitdiff
path: root/docs/html/sdk/api_diff/13/changes
diff options
context:
space:
mode:
authorSvetoslav Ganov <svetoslavganov@google.com>2013-05-03 01:13:05 -0700
committerSvetoslav Ganov <svetoslavganov@google.com>2013-05-03 01:20:56 -0700
commitbfa1bf020859a03668f1af1d59f035c53a97c7e8 (patch)
tree842fc4e10bdcfd9ecc91cf92f070460ef34ca469 /docs/html/sdk/api_diff/13/changes
parent245a3e1c1ed265a13d07000ef6e786ec321b85c4 (diff)
Multiple bindings to the same accessiblity serice if it dies.
1. When a service dies we clear its state and remove it from the bound services waiting for new onServiceConnected call in which to initialize and add the service. The problem is that after clearing and removing a dead service there is a call to onUserStateChangedLocked with will end up rebinding to the service, so we get multiple onServiceConnected calls as a result of which we add the service twice and it becomes a mess. Note that every time the service dies we end up being bound to it twice as many times - royal mess! onUserStateChangedLocked is not even needed since we cleare and remove the serivce and this method will be called when the service is recreated. 2. When a service dies and is recreated by the system we were not adding it properly since we regarded only services that we bond to and wait for the connecton. Now we are also regarding service which died and are recreated. bug:8796109 Change-Id: I5ec60c67bd3b057446bb8d90b48511c35d45289d
Diffstat (limited to 'docs/html/sdk/api_diff/13/changes')
0 files changed, 0 insertions, 0 deletions