CameraService: Link to client binder death at end of connect
If, within a binder Looper thread, a Binder object death notifier is
registered, and then a nested Binder transaction is begun, that
transaction may process a death notification callback for the
just-registered object, if it was dead at the time of registration.
This can lead to an unexpected nested call into the service, and cause
deadlock.
To avoid this, move the death notifier registration to the end of
handling the connect transaction.
Also remove one extra bit of disconnect logging.
Bug: 23525545
Change-Id: If01cbaf42704f55134118afefc9a8f7bdb014e09
2 files changed
