Ask / Submit
105

Call ended but phone is still processing the ending

asked 2014-04-24 23:05:25 +0300

BonoNL gravatar image

updated 2017-04-28 22:40:54 +0300

PLEASE SEND LOGS TO JOLLA(care@jolla.zendesk.com You can refer to issue #28354). See below how to create and send logs.

**Present since 2014**

UPDATE 06-04-2017 Still present in 2.1.0.11 on AquaFish/JollaC

UPDATE 03-03-2017 Still present in 2.1.0.9 on JollaC

UPDATE 22-08-2016 Problem still present, even with JollaC

UPDATE 01-12-2016 STILL HASN'T BEEN FIXED Send many logs but still no solution.

Since the update to 1.0.5.16 the following is happening when ending a call.

Me or the other side is ending the conversation by pressing end call or something like that. The connection is interrupted/closed as it should be, but the screen that says call ended stays on for a while. Normal behavior was, and should be, returning to the phone/call application so one can call another contact.

At this moment it even happened that after a call, I lock the phone immediately and when I received a call about 20 minutes later it was handled as a "call waiting" because the previous call still wasn't handled by the phone.

I've tried a couple of things myself off course, also because nobody else seems to mention having this bug.

  • I've rebooted the phone
  • I've removed the battery for about 30 minutes and rebooted the phone afterwards.
  • I've set the phone back to factory defaults

Even when I've set the phone back to factory defaults it seems to appear, even when I didn't installed my backup back on the phone.

WILL JOLLA EVER FIX THIS BUG? At this moment I've switched back to my beloved N9 because the bug had made working with the Jolla for business not pleasant. The Jolla is unusable at this moment!

edit retag flag offensive close delete

Comments

1

I have had this behavior once or twice , can not reproduce this, it seems random

teun ( 2014-04-25 08:24:18 +0300 )edit
1

It's happening to me every call and the phone is useless to me at this point. I'm restoring it to factory defaults once again and hope that it will be fixed in the next update, if not I will return the phone to Jolla.

I will also try to film the behavior with my N9 so the problem can be visually experienced, maybe it will come more clear then.

BonoNL ( 2014-05-03 01:18:47 +0300 )edit
1

Not sure if we're describing the same behavior, but it seems like I currently have one call on hold all the time. With each incoming call, I only get a slight beep for an alert and have to drop the non-existent call to answer.

ZZB ( 2014-05-05 15:17:15 +0300 )edit
1

The persons who're suffering this issue, which provider do they use?

RobNas ( 2014-05-05 15:42:19 +0300 )edit

I'm having the same problem since the last update. What's annoying is that the phone is still processing the last ended call. So when receiving a new call, it doesn't ring, it behaves like during call waiting.... Therefore I'm not hearing further calls and thus missing many received calls!!! It also uses more power from the battery...

mer2os ( 2014-05-05 17:37:53 +0300 )edit

9 Answers

Sort by » oldest newest most voted
6

answered 2016-12-02 10:17:52 +0300

taran gravatar image

Problem.still there..

edit flag offensive delete publish link more

Comments

same here. especially when i make the calls.

tortoisedoc ( 2016-12-02 18:17:34 +0300 )edit
5

answered 2017-06-28 23:18:11 +0300

BonoNL gravatar image

updated 2017-07-01 11:44:01 +0300

There is a potential fix on the way.

Jolla contacted me and I manually installed some updated packages. Now it's working as intended.

For the people interested in the fix here are the packages but use on your own risk.

These are the instructions that i got from Jolla:

http://joona.net/debug/

Instructions:

  1. Enable developer mode under Settings -> System -> Developer mode -> Remote connection -> Set password.
  2. Open Terminal, call devel-su and provide password.
  3. Install following call libraries with debugs enabled (tested to work on 2.1.0): http://joona.net/debug/

scp .rpm nemo@mydeviceip rpm -Uvh --force voicecallrpm --nodeps

  1. After you see the issue mark down the repro time somewhere and gather traces using terminal.

journalctl -a > journal.log scp nemo@mydeviceip:journal.log .

  1. Clean up: Next OS update will remove the debug packages. Also you can remove cellular debug logging by removing the environment file.

version --dup rm /var/lib/environment/ofono/debug.conf

edit flag offensive delete publish link more

Comments

1

It is good to hear the progress on this!

martonmiklos ( 2017-06-29 01:07:41 +0300 )edit
3

I believe that the formatting went wrong there. It should be something like that:

scp *.rpm nemo@mydeviceip
rpm -Uvh --force voicecall*rpm --nodeps

Thanks for posting anyway!!!

cuh7b5 ( 2017-06-29 11:16:22 +0300 )edit
1

Hope to see this fix to be included in the next OS update. Thanks for sharing. I will wait for the OS update.

Mohit ( 2017-07-05 14:53:17 +0300 )edit
4

answered 2016-08-23 18:25:44 +0300

Im on 2.0.24 and still the problem is present

edit flag offensive delete publish link more

Comments

2

2.0.3.24?

vattuvarg ( 2016-08-23 19:21:31 +0300 )edit

yes that one

tortoisedoc ( 2016-08-23 22:07:51 +0300 )edit
1

Everybody who got this problem,

Please do the following to provide Jolla some logs:

Go to terminal,

Enter devel-su

enter your password.

and then:

journalctl -a > /home/nemo/call.log

Mail those loggings to Jolla(care@jolla.zendesk.com) together with the following questions answered:

Could you describe the steps to reproduce in detail:

  1. Does it happen always or randomly?
  2. What kind of network are you useing?
  3. What is your operator?
  4. Do you use multiple SIM cards?
  5. In which slot is the SIM card inserted?
  6. Do you dial orreceive a call when this happens?
  7. Which side disconnects the call?
  8. How is the call disconnected?
  9. How many and what apps you have running when the issue reproduces (check next time it occurs)?

You can refer to issue #28354.

BonoNL ( 2016-09-05 20:59:31 +0300 )edit
3

answered 2016-09-06 07:53:21 +0300

updated 2016-09-06 07:53:47 +0300

My case:

Does it happen always or randomly? - yes

What kind of network are you useing? - 3/4g
What is your operator? - sonera
Do you use multiple SIM cards? no
In which slot is the SIM card inserted? - in the left one, on jolla c
Do you dial orreceive a call when this happens? - dial
Which side disconnects the call? - I usually do
How is the call disconnected? - b pressing the button on the ui
How many and what apps you have running when the issue reproduces (check next time it occurs)? - it varies, the end result is still the same

Issue #28354.

edit flag offensive delete publish link more

Comments

Did you mail it to Jolla and provided logs with it?

care@jolla.zendesk.com

BonoNL ( 2016-09-06 23:05:37 +0300 )edit

no and no.

tortoisedoc ( 2016-09-07 08:33:16 +0300 )edit

Please do.

BonoNL ( 2016-09-09 21:46:04 +0300 )edit
2

answered 2015-06-29 22:09:31 +0300

murali gravatar image

i am facing the issue i habe 1.1.6.27 version in my mobile.

edit flag offensive delete publish link more

Comments

same here.

MohammadR ( 2015-08-15 14:50:00 +0300 )edit

I'm having this issue with almost every call, 1.1.7.28

goldenm ( 2015-09-01 21:31:44 +0300 )edit
1

Me also, I will make another Youtube movie of it and send a bug report to Jolla.

Also please up vote this newer thread about: https://together.jolla.com/question/98984/bug-unable-to-place-a-call-straight-after-latest-one/

Also send a bug report towards Jolla Zendesk it will help them clear the bug faster.

BonoNL ( 2015-09-14 22:46:39 +0300 )edit

I just realized this problem happened to me with update 1.0.5.16, then it was fixed. I commented here in May 2014. Now it's happening again with update 1.1.6.27 and 1.1.7.28 I reset my phone many times, even without recovery the phone still acts like this after update 1.1.6!!

mer2os ( 2015-09-15 10:58:10 +0300 )edit
1

Also we should report to them the network problem issue, that has been existing since early updates: https://together.jolla.com/question/18417/no-network-coverage-direct-after-call/ Which I didn't really notice until I read about it. So if you actually look at your phone after closing a call, you will notice that you lose the network for a few seconds. These two issues might not be related, but still it has to do with the phone app, so it should be taken into consideration as well!!!

mer2os ( 2015-09-15 11:03:58 +0300 )edit
1

answered 2017-04-11 08:55:24 +0300

I'm also facing this issue. I'm on Intex Aqua Fish 2.0.5.6

When I press "end call", screen returns to the call log but I'm unable to dial other numbers until I got a small notification-kind-of-thing in the topmost area that "call ended". This is very frustrating given the fact that this problem persists for minimum 2-3 minutes sometimes.

I'll generate and send the logs later.

edit flag offensive delete publish link more

Comments

Yes please send logs!!

BonoNL ( 2017-04-11 22:23:38 +0300 )edit
1

answered 2017-05-03 12:12:36 +0300

247 gravatar image

updated 2017-06-28 23:11:22 +0300

BonoNL gravatar image

can confirm i have this error on the J1 even with 2.1...

edit flag offensive delete publish link more
0

answered 2017-04-12 09:07:11 +0300

deloptes gravatar image

updated 2017-04-12 09:08:06 +0300

In the gmain mail thread "lock JP01 on 4G, is it possible?" it was stated, that perhaps LTE/4G/3G switching is related to not being able to call or being called. Can this be related to this issue?

in the past I used the Radio Switch app (on warehouse) to lock my JP01 on 4G network (it seems that if 3G signal is low sailfish doesn't search for 4G networks, but in my area 3g is 2100MHz and 4g on 800MHz, so it penetrates the building walls way better), but a while ago the 4G mode stopped working because the bash command use was no longer working.

I'm writing to know if it's still possible with a new bash command to lock the phone in 4G only mode, and if so how.

I do know there is the "more network modes" patch but I would like to avoid to use patches.

The dialog in System Settings should be enough, it should be noted though that LTE did not usually support voice calls so when you are making the call the phone always needs to switch back to UMTS (things may have changed).

edit flag offensive delete publish link more

Comments

Well I tried to go for 3g only for a while, but it didn't solved this problem.

BonoNL ( 2017-04-12 22:45:49 +0300 )edit
1

Strange, I think we had this issue one time here. I mean, I am not at 100% sure, but it sounds like this issue. My wife is using AquaFish with Bob from A1 - Telecom in Austria. This is how I came to the thread and subscribed. Since then it never happened again. So most likely there are other factors and its hard to reproduce. In our case I was not able to dial the number - I was always deverted to the voice mail. She did not notice after ending the last call, unless I called at the fixed line at home and told her to reboot.

deloptes ( 2017-04-13 13:04:12 +0300 )edit
0

answered 2017-07-16 21:21:39 +0300

fyodorov gravatar image

Я даже не хочу себя утруждать писать по английски, как jolla не хочет себя утруждать сделать что бы при нажатие кнопки "Завершить вызов" вызов все таки завершался... Проблеме больше года, не надо забывать что основная функция телефона - звонить. 2.1.0.11 в Jolla C и в Jolla проблема одинаковая, замена сим карт, операторов, возврат к заводским настройкам, отказ от CS-Fallback выбором 3G only - проблему не решают.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
16 followers

Stats

Asked: 2014-04-24 23:05:25 +0300

Seen: 3,688 times

Last updated: Jul 16