I also didn’t quite understand what is exactly the case here.
Did the phone failed (or refused) to call an emergency service number? If so, which one, from which country/operator?
Or did the phone fail to allow calling in a emergency situation, e.g. while it was locked ?
I agree that’s a serious fault so its preconditions should be properly tracked.
My 5 cents! Reboot your phones continuously, and I can almost guarantee that you will avoid such problems.
4 Likes
While any device can fail anytime -and by murphy’s law it always at the wrong time and when you need it the most- this is not a nice “solution” or workaround.
First and foremost a phone (regardless of OS) should be as reliable as possible. Piece of mind for the user, convenience and reliability brings you money.
2 Likes
On xperia 10 ii,
I have this problem sometimes that calling a number (from wherever you can: ui, contacs or sms) doesnt bring up the call ui.
The call keeps going on in the background, but until the receiving end picks up its impossible to stop it cause the ui is, well, not there.
1 Like
This might cause confusion for some people - I’d say daily.
4 Likes
Or at least every second/third day, depending on how much you use it. But daily is good.
They should give us an option to automate stuff like that if it’s needed. Samsung has auto restart for years as an option for example.
1 Like
Then please, make a feature request.
1 Like
Moved to the category “Bug reports”. Set as “Tracked”.
3 Likes
We will try to reproduce the problem but it will be a tough job as the call problem is rare.
If you happen to run into this issue again, please try to collect some logs from your phone and describe, as precisely as possible, how the whole sequence of events went.
To get the logs, you need to enable the Developer mode.
The bare minimum would be to get the journal log with the command:
devel-su journalctl -a -b --no-tail --no-pager > journal.txt
If the oFono Logger app were installed on the phone (before the incident) then we would get more detailed telephony-related logs. The instructions for this are in this document.
If you do not want to publish your log(s) here in the Forum, please file a ticket in the Customer Care and attach the log files to the ticket.
10 Likes
I am really sorry for what happened to you. I can feel how it’s frustrating. I hope our community can help improving the SW (and also HW performances) to face with more effectiveness emergency situations where the connection is a life-saver.
Unfortunately I understand what you feel: I got the very same incident with Iphone 7 from my wife.
I would say never. On some systems the SW itself asks for a reboot every few hours or when automatic operations (updates or others) are done. On Android the reboot is a must-do because of the java and kotlin garbage collector very bad handling.
We shall distinguish: On a system where I am in control of what happens I don’t need reboot and I don’t expect someone tells me it’s needed a reboot. If I don’t know what’s happening inside my device the reboot is highly reccomended.
On recent versions of SFOS, I know of at least two situations where dialing was not possible wo reboot (XA2). So, it looks to not be so rare…
I suspect I’ve had this happen once or twice during a year with my Xperia 10 III.
During a call, I could see a top bar with the ongoing call time displayed, but i wasn’t able to interact with it. I also wasn’t able to bring up the call screen from the running apps selection or the Phone-app. I believe re-entering the app just displayed the app as if I opened it normally without being in a call.
I didn’t pay enough attention to give a detailed description but I thought I’d just +1 this.
1 Like
Just happened on an XA2 (H4113, only one SIM in + SDcard) with 4.5.0.24 triggered while 2 calls came in at quite the same time, one was rejected with a message, the other one “disappeared”.
After that, it wasn’t possible to place a call. Flight mode on → off, Voice-UI restart didn’t help.
Rebooted…
2 Likes
Are you people observing in these cases, that the “telephone” app if opened on the app cover indicates as if a call is ongoing but can not be ended at all - even if there is no more call ongoing? I experience that quit often.
1 Like
As you mention it: it occurred to me that handling two incoming calls once ended in an Ofono nirvana and required a reboot … (Xperia 10 ii or iii - i do not recall)
The root cause for this could be the same as in Audible tone after ignoring call .
Release notes for 4.6.0.11 EA state that they could not reproduce it any more, so, is this happening on 4.6 too?
Edit: So, not the same root cause, as it seems…
2 Likes
Indeed, I had today on 4.6 this exact behaviour. One call ended, but was stuck in the phone application. Visible on the cover. The action button was not doing anything. Then, later on, I noticed that I was not able to call anymore.
systemctl --user restart voicecall-manager
restored a correct behaviour.
3 Likes
If restarting voicecall-manager solves the issue, would it make sense to restart it when the voicecall-ui is restarted?
1 Like