After the update, when I make or receive a call, the screen goes white then has a popup that says “Phone keeps stopping”, “Call keeps stopping”, or “CallBGprovider keeps stopping.”

I was able to install the google phone app, so I can make and receive calls now, but I would like to use the samsung one. Anyone know of an easy fix. I already cleared the cache of Phone, Calls, and CallBGprovider and it didn’t fix it.

  • grizchicago@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Having the same issue. I refuse to do a factory reset, but as others have said, downloading and using the Google phone app has worked for me as well.

  • Massive-Pineapple929@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Let’s perform Reset Settings on your phone. This will reset your settings. You can do that from Settings> General management> Reset> Reset all Settings. A settings reset will return the device’s settings to the factory default settings without deleting data. Any customizations you have made to your device, such as ringtone, will be discarded.

    -Samsung Chat

    Worked for me surprisingly.

  • iameffex@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Seems like they pulled the update? My AT&T S22U says no updates available. Guess I’m lucky after reading this. Didn’t they beta test phone calls? Seems very odd…

  • iameffex@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Seems like they pulled the update? My AT&T S22U says no updates available. Guess I’m lucky after reading this. Didn’t they beta test phone calls? Seems very odd…

  • lscraig1968@alien.top
    cake
    B
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I had to reset my phone back to factory then restore from the last backup to get the phone to stop crashing. Huge PITA!

    I only lost 12 hours of texting. Will have to reload my music. 🤬

    S22 regular

  • lscraig1968@alien.top
    cake
    B
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I had to reset my phone back to factory then restore from the last backup to get the phone to stop crashing. Huge PITA!

    I only lost 12 hours of texting. Will have to reload my music. 🤬

    S22 regular

  • kcnetter@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I’ve been following along and trying everything mentioned short of full factory reset. In the Samsung community thread, someone just posted a bit ago about the “Secure Folder” app. Disabling the “Secure Folder” app seems to have actually worked. I have an S22 on AT&T. There was not initially an option to disable the app when I first looked, but somewhere from the settings/apps list I was able to find a way to disable it (I cleared cache/date, etc. too). I took out the sim turned off the phone, replaced sim and turned on and now it works. I have taken the sim out several other times trying other suggested fixes too, so not sure this added anything. I have previously removed ATT Call Protect, cleared cache from the boot menu, etc. 

  • jawsx99@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    It’s Samsung’s phone app. Download the “Phone by Google” app and make it default. Should fix the issue

    • ElmoTeHAzN@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      IT’S NOT THE POINT HERE. I SHOULDN’T HAVE TO DOWNLOAD ANOTHER APP AND MAKE IT DEFAULT TO MAKE A PHONE CALL AND ALSO GUESS WHAT THIS STILL BRINGS UP THE PHONE APP. WHEN YOU GET A CALL

  • Terizent@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I tried uninstalling Secure Folder and it fixed the problem for a couple hours. Then the problem came back!

    • kcnetter@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      After I “uninstalled” the app it still showed up, but I was then able to disable it. Did you make sure it didn’t still show up, or if so to disable it? My issue hasn’t come back…yet anyway. I did also uninstall Call Protect.