Cannot call or receive calls after upgrade to 4.5.0.19

Bug Reports
#1

After upgrading to 4.5.0.19 I cannot make phone calls or receive calls.

REPRODUCIBILITY: systematic
OS VERSION: 4.5.0.1
HARDWARE: xperia 10 II-dual xqau52
UI LANGUAGE: French
REGRESSION: yes - worked on previous OS
ISP : freemobile

DESCRIPTION:

Phone calls cannot be made
callers get a busy tone even I am not on the phone

PRECONDITIONS:

STEPS TO REPRODUCE:

To reproduce, either

  • use contacts
  • select a contact
  • press phone number
    or
  • open phone app
  • select a number
  • press the number
    or
  • open phone app
  • select keyboard
  • type a number
  • press call

What happens : Nothing
Expected : the call is made

reciprocally:

  • someone calls me

What happens:

  • he gets a busy tone

Expected :

  • they get a ring
  • if I pick up , we have a phone call

MODIFICATIONS:

use openrepos
use chum (amazfit + some games)
using in development crypto sdcard in cooperation with Olf

ADDITIONAL INFORMATION:

I noted that

  • voicecall-manager.service is failed, using SailorD
    the service calls /usr/bin/invoker -o --type=qt5 /usr/bin/voicecall-manager
    If I do it directly, I have

[root@Xperia10II-DualSIM defaultuser]# /usr/bin/invoker -o --type=qt5 /usr/bin/voicecall-manager
invoker: error: XDG_RUNTIME_DIR is not defined.
invoker: error: XDG_RUNTIME_DIR is not defined.
invoker: warning: Also fallback boosters failed, launch without boosting.
invoker: warning: Connection with launcher process is broken.
invoker: error: Start application /usr/bin/voicecall-manager as a binary executable without launcher…
Illegal instruction (core dumped)
[root@Xperia10II-DualSIM defaultuser]#

Calling /usr/bin/voiceall-manager results also in Illegal instruction

similarly, the vibration on screen touch is not working either

SFOS 4.5 feedback thread
#2

Which version did you have before the upgrade to 4.5.0.19?
How did you upgrade? Via the UI or using the command line?

Please collect the logs as in here: Collect Basic Logs | Sailfish OS Documentation

#3

I updated via command line , using : sfos-upgrade 4.5.0.19

I think I had 4.5.0.18
Collected basic logs - how to transmit them ?
Is a core dump useful ?

#4

I can confirm this issue, this already exists since 4.5.0.16. I upgraded using the standard procedure via settings.
I did not find the time to post a bug report or provide some reproduction steps, I will try to do so later after I am able to verify those.

Some further details on my experience:

What does not recover the device from this issue:

  • Toggling airplane mode
  • Restarting network services via settings utilities
  • Toggling network settings

What does recover the device from the issue:

  • Reboot
  • systemctl restart ofono command

Bug specifics:

  • Any phone functionality is broken (this is actually a very critical issue, due to broken emergency calls!)
  • The Phone app cover displays an ongoing call even though no call is active
  • After executing systemctl restart ofono command the “Phone call ended/terminated” dialog is displayed even though there was no active phone call
2 Likes
#5

Thanks for the logs!

#6

Hi

In my case, restarting ofono does not resolve the issue,
what I did : as devel-su : systemctl restart ofono
what happens:

  • I try and open a call through phone app/keyboard/typing a number/Cicking call
  • what happens first time : it says no available network (in french “pas de couverture rĂ©seau”) and fails
  • subsequent times : as in my first description : nothing visible happens
#7

Internal bug report created

1 Like
#8

Hi,
can we create a bug report against poor testing?
I am complaining since a long time that things are getting worse with each release.
When will Jolla start testing better before releasing?
Why is there the EA and what is it good for when so many critical bugs are being reported after release?
I’m surely not touching the phone when reading so many bug reports after 4.5.0.16
This is serious! I once wrote that some of the former Nokia employees know very well how they did Harmattan 1.2.
I can swallow some minor bugs, but this one … confirmed by multiple users …

please post at least what is the expected release date for the fix.

2 Likes
#9

We have received some logs from @ddelamarre (thank you). It is not yet clear why phone calls have stopped working on his and on a few other users’ phones while they keep working fine on the phones of the vast majority.

We did not observe this problem on any of the phones on which 4.5.0.19 was tested prior to the rollout.

It is impossible to estimate a release date when the culprit of the reported issue is not clear.

Apologies for the problems caused.

2 Likes
#10

I can understand that it is not possible to cover all variations. Forgive me my harsh remarks, but from my user perspective it is just making me nervous when reading these reports.
Especially after having experienced similar problems in the past.
I wish there were LTS version that I could stay on for a longer period of time, or an easy way to downgrade or rollback. For example at the moment with 4.4.0.72 I do not need to upgrade except for security reasons.
I do not recall if LTS was discussed or available.
I understand the complexity, but I think may be a wider circle of beta testers should be used before release.

#11

[root@Xperia10II-DualSIM defaultuser]# /usr/bin/invoker -o --type=qt5 /usr/bin/voicecall-manager

This should be run as user and as root it’s not expected to work. But as root you could try “systemctl --user restart voicecall-manager” and check what gets printed on the journal.

#12

I install Sailfish on my new Xperia … And no way to call or receive a call. I found this ticket and it is EXACTLY the same problem BUT I have one more information …

This happen ONLY with my Free sim card. I have another sim ( Bouygues for professional matters) and it works correctly !!! I made a log collect. Do you want me to furnish to you ? It depend on the operator use … Strange
Thanks to find a solution … It is a real pb a phone … which can make a phone call !

#13

Well, neither your nor the original reporter mentions whether this is with VoLTE or not.
Some operators have been know to mess up legacy calling (or specifically the falling back from 4G to something that can support classic CS calls) for VoLTE-capable phones. Does it work if you manually select 2G or 3G?

#14

Of course, for us … It is clearly a black box :stuck_out_tongue: And I am not able to speak about VoLTE as I don’t know aynything of this technology.
What I can tell you, I use an Xperia 10 plus … With 2G only, It works !!!
I will be a workaround until the correction … When I select “prefers 3G” … I have no network !! I tried twice, back to 4G and back to 3G … No able to catch network with 3G… Now, Free operator was not very old and as far I am remembered, they built only 4G antenna … Maybe, there is no 3G antenna around. I will try tommorow somewhere else …
If you need any other data … I would be please to anwser to your question :stuck_out_tongue: Regards

#15

I said my SIM2 is working … BUT … I discover this morning after many tries that Sim2 is not working anymore because … it was my data sim selected !!! There is clearly a link with data mobile. The sim selected for data mobile need to be in 2G to be able to make a call … The other does not have any problem to work. Hope it helps …