cameraserver: Reduce Camera2ClientBase destructor log confusion.

We log disconnect in CameraService::BasicClient::disconnect() and also
in ~Camera2ClientBase(). Since ~Camera2ClientBase() can often run a few
seconds after BasicClient::disconnect(depending on when we get another
binder call), the disconnect logs from the Camera2ClientBase destructor
can be confusing to look at on quick inspection.

Bug: 235352466

Test: Inspect logs

Change-Id: I3fbaa0bde2c21c3b13d5d86f7691eb49f9eb53a2
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
diff --git a/services/camera/libcameraservice/common/Camera2ClientBase.cpp b/services/camera/libcameraservice/common/Camera2ClientBase.cpp
index ae22717..e54813f 100644
--- a/services/camera/libcameraservice/common/Camera2ClientBase.cpp
+++ b/services/camera/libcameraservice/common/Camera2ClientBase.cpp
@@ -168,8 +168,8 @@
         mCameraServiceWatchdog.clear();
     }
 
-    ALOGI("Closed Camera %s. Client was: %s (PID %d, UID %u)",
-            TClientBase::mCameraIdStr.string(),
+    ALOGI("%s: Client object's dtor for Camera Id %s completed. Client was: %s (PID %d, UID %u)",
+            __FUNCTION__, TClientBase::mCameraIdStr.string(),
             String8(TClientBase::mClientPackageName).string(),
             mInitialClientPid, TClientBase::mClientUid);
 }