[bug] Phone application seems not to react when starting a call

Tracked by Jolla (In progress)

asked 2017-04-24 11:02:01 +0300

Hensch gravatar image

updated 2017-04-24 11:02:30 +0300

Sometimes, while starting a phone call, on the Aqua Fish (2.1.0.11 from Jolla C) the UI seems not to react. I select the contact to call and nothing seems to happen. After some time (approximately 10s) the UI is showing a failure and the call ended screen together with the call not available sound (3 tones). What it really does is calling the person in background without me knowing about it. Even after the error message it is keeping up the call with the other person hearing me but I can't hear anything. The only solution is a reboot to be sure the call is ended.

In combination with https://together.jolla.com/question/41985/move-end-call-and-call-again-buttons/ this is very unpleasant. I think this can be reproduced by quickly calling and hanging up. This is the case if I accicentally selected the wrong person to call.

edit retag flag offensive close delete

Comments

The same as:

https://together.jolla.com/question/145376/bug-20251and-2056-jolla-c-could-not-receive-smsphone-call/

If you set it to 3G only the problem will be solved in most of the cases.

BonoNL ( 2017-04-24 21:09:11 +0300 )edit

I cannot do this as this would make me unreachable for 50% of the time. On the coutryside we have a few areas where only 2G is available.

Hensch ( 2017-04-26 15:30:42 +0300 )edit
1

They are not always easy to reproduce, but we are currently trying to investigate many of these call issues.

Joona Petrell ( 2017-04-27 12:50:45 +0300 )edit

We have found a potential fix, but need community's help to test. If you are seeing issues with phone calls and have time to help, comment here and I'll contact you.

Joona Petrell ( 2017-05-05 16:47:57 +0300 )edit

As you wrote, this is very difficult to reproduce but I will see how I can help you. I will try to find a way to reproduce this evening.

EDIT: I tried to quickly call and hangup many times with WLAN or 3G data on. The bug didn't reappear. Seems that I cannot reproduce it.

Hensch ( 2017-05-05 20:26:30 +0300 )edit