Do not Lock on Registration and Config Query
ImsRegistration and ImsConfig interfaces do not
need to be locked on because they access a
TelephonyManager API independent of MmTelFeature
state.
Bug: 74119196
Test: Telephony Unit Tests
Merged-In: I48a554c509b61094dd65b3d8ac6195a891508a64
Change-Id: I458db42cd815f87f57eab6b13878532105297180
diff --git a/src/java/com/android/ims/MmTelFeatureConnection.java b/src/java/com/android/ims/MmTelFeatureConnection.java
index 276688c..5679591 100644
--- a/src/java/com/android/ims/MmTelFeatureConnection.java
+++ b/src/java/com/android/ims/MmTelFeatureConnection.java
@@ -484,22 +484,16 @@
}
public IImsConfig getConfigInterface() throws RemoteException {
- synchronized (mLock) {
- checkServiceIsReady();
- return getConfig();
- }
+ return getConfig();
}
public @ImsRegistrationImplBase.ImsRegistrationTech int getRegistrationTech()
- throws RemoteException {
- synchronized (mLock) {
- checkServiceIsReady();
- IImsRegistration registration = getRegistration();
- if (registration != null) {
+ throws RemoteException {
+ IImsRegistration registration = getRegistration();
+ if (registration != null) {
return registration.getRegistrationTechnology();
- } else {
- return ImsRegistrationImplBase.REGISTRATION_TECH_NONE;
- }
+ } else {
+ return ImsRegistrationImplBase.REGISTRATION_TECH_NONE;
}
}