Can't make calls, phone app crashes

[GiSS88]

Already tried clearing cache and force stopping. Every time I try to open the app, it just closes right away. Any thoughts on the issue?

 

[apascual89]

Already tried clearing cache and force stopping. Every time I try to open the app, it just closes right away. Any thoughts on the issue?

Try going to Settings /apps press the settings icon and check to see if you have the phone app set as default

 

[GiSS88]

Try going to Settings /apps press the settings icon and check to see if you have the phone app set as default

It was. Weird thing happened, I apparently had a voicemail--once I listened to and deleted that, the app started opening again. Really strange.

 

[eddymonti]

Is it stock? If you flashed something, like a ROM or an app, it is probably that and you need to (clean?) re-flash the ROM. Happened to me before on another phone when I flashed, and a re-flash fixed it. NVM, seems you have it working now.

 

[bond_]

It was. Weird thing happened, I apparently had a voicemail--once I listened to and deleted that, the app started opening again. Really strange.

I had the same issue seems like the phone app can't handle voicemail. I turned off visual voicemail to see if I can isolate the issue. Let's see what happens. BTW does anyone know if the source code of phone app is opensource or not?

EDIT: I think I know what the issue is, the voicemail I received was from a private number (VOIP). Looks like visual voicemail was unable to determine the caller number and died (I did not look into the logs but I am fairly certain about it).

 

[nathanielwilliam]

installing tmobile visual voicemail and deleting my voicemails fixed my issue. hope this helps someone.

I had the same issue seems like the phone app can't handle voicemail. I turned off visual voicemail to see if I can isolate the issue. Let's see what happens. BTW does anyone know if the source code of phone app is opensource or not?

EDIT: I think I know what the issue is, the voicemail I received was from a private number (VOIP). Looks like visual voicemail was unable to determine the caller number and died (I did not look into the logs but I am fairly certain about it).

 

[bond_]

installing tmobile visual voicemail and deleting my voicemails fixed my issue. hope this helps someone.

Thanks I did a similar thing. I dialed my Voicemail from Truecaller and deleted them. So from what I have tested the default dialer app was not able to handle visual voicemail from Private/Unknown number. Looks like someone overlooked a null pointer error.

 

[ykandel1]

null/segv kind crash

Thanks I did a similar thing. I dialed my Voicemail from Truecaller and deleted them. So from what I have tested the default dialer app was not able to handle visual voicemail from Private/Unknown number. Looks like someone overlooked a null pointer error.

I had the same issue. It turns out that I had a voicemail that was not deleted from an "unknown" number (t-mobile usa). The phone app was not able to handle it and crashed. I am assuming the phone number field was empty and whatever data that was there in its place from next field simply corrupted its memory or caused it to segv. I think this is just a bug in their phone app. In order to replicate the issue, just have someone block and send the voicemail to them and try opening the app, it crashes without any incident. Is there a way to see any exception thrown? or is that not on the consumer build?

 

[kunal1540]

I had the same issue. It turns out that I had a voicemail that was not deleted from an "unknown" number (t-mobile usa). The phone app was not able to handle it and crashed. I am assuming the phone number field was empty and whatever data that was there in its place from next field simply corrupted its memory or caused it to segv. I think this is just a bug in their phone app. In order to replicate the issue, just have someone block and send the voicemail to them and try opening the app, it crashes without any incident. Is there a way to see any exception thrown? or is that not on the consumer build?

You can use the user feedback app installed on the latest stock rom
Open it and recreate your crash and submit report to oneplus
If possible they will rectify in the next update