3
[CLOSED]Calling Issues after Update to December Security Patch

Thread Status:
Not open for further replies.
  1. I1517135236469
    Donut Jan 16, 2020

    I1517135236469 , Jan 16, 2020 :
    There remains a dial showing the call you made recently even after one has disconnected the call.

    This is the new issue that I have been facing after I have updated OnePlus 5T to December 2019 Security Patch.

    Could there be any way to avoid such issue?
     

    #1
  2. U1526230639669
    Cupcake Jan 18, 2020

    U1526230639669 , Jan 18, 2020 :
    After the recent 9.0.10 update on my OnePlus 5T, the call timer runs for about 5 seconds after the call is disconnected. The notification shows that a call is active for the same period whereas the call does disconnect on time.
    Can this issue be fixed asap. Without testing they just roll-out feature ?
     

    #2
    maqsood2k7 likes this.
  3. Waveform Modifier
    Marshmallow Jan 18, 2020

    Waveform Modifier , Jan 18, 2020 :
    This is a user community forum and not tech support page. Please report bugs to the proper place. See the pinned Official OTA thread.
     

    #3
  4. shaikmohammedari
    Donut Jan 18, 2020

  5. samnadar
    Cupcake Jan 28, 2020

    samnadar , Jan 28, 2020 :
    SOLVED!!


    I was facing this issue since the last update of OxygenOS 9.0.10

    It was really annoying and got scared if my mobile was hacked, did lots of research and followed the instruction I googled for and finally it was solved.

    It’s just a bug and OnePlus will soon address this issue.

    Follow this steps to get rid of it.


    Step 1:

    Click the CALL button


    Step 2:

    Click on the 3 dots on top right of the screen.


    Step 3:

    Click SETTINGS from the dropdown


    Step 4:

    Turn off the NOISE CANCELLATION.

    That's it..


    It worked for me hope it works for you too..

    Cheers,
    Sam Nadar
     

    #5
    I1517135236469 likes this.
  6. SoniaB
    Nougat Senior Moderator Jan 28, 2020

    SoniaB , Jan 28, 2020 :
    This is a known bug issue and has been reported several times on the forum.
    All you can do is wait for the next update with a fix.

    I will close this thread
     

    #6
    I1517135236469 likes this.