Google's Carrier Services reports permissions aren't granted although they are

17 Views Asked by At

I've been trying to get Backup calling on my Tensor Pixel and it has worked, but it's been super weird. The main common factor for me is that location matters, it works in certain locations and doesn't. Right now I'm trying to diagnose why it doesn't work. I looked through adb logcat and I'm greeted with this message: E com.google.android.ims.: [32] fcu.u:18 [32] : (Sim): Permission is required for SubscriptionManager (P.S. That is the Carrier Services app, and has the icon of Google Play Services) I'm extremely confused on what it means as I have granted the app all it's permissions and it's not spitting out the reason why it refuses to connect.

I've attached the rest of the logcat below

02-28 18:58:22.310 2571 2957 D ImsEnablementTracker: [0][1]resetIms, component:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:22.311 2571 4143 D ImsEnablementTracker: [0]Enabled state:processMessage. msg.what=COMMAND_RESET_MSG,comp onent:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:22.311 2571 4143 D ImsEnablementTracker: [0]Resetting state:processMessage. msg.what=COMMAND_RESETTING_DO NE,component:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:22.427 3635 5333 I com.google.android.ims.: [32] fcw.c:11 [32] : SIM state event delay enabled: attempts 3, maxAttempts 3, delaySeconds 90 MSIM delayseconds 90, effective delay seconds 90 02-28 18:58:22.427 3635 5333 I com.google.android.ims.: [32] fcw.c:25 [32] : reached max delay attempts, do not reschedule 02-28 18:58:25.312 2571 4143 D ImsEnablementTracker: [0]PostResetting state:processMessage. msg.what=null,component:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:25.313 2571 4143 D ImsEnablementTracker: [0][1]sendEnableIms,componentName[ComponentInfo{com.google.andro id.ims/com.google.android.ims.services.CarrierServicesImsService}] 02-28 18:58:25.388 2571 2571 D ImsEnablementTracker: [0][1]enableIms, component:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:25.388 2571 4143 D ImsEnablementTracker: [0]Enabled state:processMessage. msg.what=COMMAND_ENABLE_MSG,com ponent:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:25.423 2571 2571 D ImsEnablementTracker: [0][1]enableIms, component:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:25.423 2571 4143 D ImsEnablementTracker: [0]Enabled state:processMessage. msg.what=COMMAND_ENABLE_MSG,com ponent:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:25.463 2571 2571 D ImsEnablementTracker: [0][1]enableIms, component:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:25.463 2571 4143 D ImsEnablementTracker: [0]Enabled state:processMessage. msg.what=COMMAND_ENABLE_MSG,com ponent:ComponentInfo{com.google.android.ims/com.google.android.ims.services.CarrierServicesImsService} 02-28 18:58:25.544 3635 5333 I com.google.android.ims.: [32] fcw.c:11 [32] : SIM state event delay enabled: attempts 3, maxAttempts 3, delaySeconds 90 MSIM delayseconds 90, effective delay seconds 90 02-28 18:58:25.544 3635 5333 I com.google.android.ims.: [32] fcw.c:25 [32] : reached max delay attempts, do not reschedule 02-28 18:58:46.299 3635 5333 I com.google.android.ims.: [32] fcv.run:2 [32] : delay time out, reset attempts 3 and process SIM event 02-28 18:58:46.304 3635 5333 W com.google.android.ims.: [32] fcu.a:1 [32] : (Sim): process intent: android.intent.action.SIM_STATE_CHANGED 02-28 18:58:46.313 3635 5333 E com.google.android.ims.: [32] fcu.u:18 [32] : (Sim): Permission is required for SubscriptionManager

I have tried to reset the phone multiple times, and have observed it briefly connected before disconnecting immediately with no reason. I have tried to get IMS registration restarted multiple times. I don't know how to express the amount of time I spent trying to get this working and this seems like the root cause I need to find as to why it's not working.

0

There are 0 best solutions below