answered
2015-06-06 14:05:56 +0300
Aside all the non-answers and comments, here is a real answer, one that actually fixes this problem. I have answered this on several iterations of this very question, but with your help, we can start getting rid of and slowing the amount of duplicate questions, particularly on this subject.
If you haven't already, you will need to activate Developer Mode. You will need to set a password to use Developer Mode, YOU choose the password. To do this, tap on Remote Connection inside the developer mode settings, enter your chosen password and remember it! (if you get an authentication error, you will need to sign in, using devel-su and the password you set earlier - in some cases you won't need to, it seems to depend on whether or not you have enabled developer mode and set a password previously).
Once you have enabled Developer Mode and set your own password, open Terminal from the launcher icon and type in this command; pkcon install voicecall-ui-jolla once done, reboot your phone. This should fix the problem we are encountering.
I agree that this problem appears to be a bug, but I also wonder if it is the installation and/or the removal of another app that is causing the problem - just a thought.
@jolla - I think the team need to look into this, this is fast becoming a frequent problem for many of your users.
Regards,
Is this completely random or does it maybe occur only when battery level is low? It's a known problem that there are complete UI-freezes (for more than a few seconds) when the battery is low. For me it starts at roughly 10%. This would correspond to your estimate of one of 10 times. So maybe it's not a bug in the telephony UI, but just another aspect of the known low-battery-UI-freeze?
ossi1967 ( 2014-02-12 22:21:06 +0300 )editI had this a couple of hours ago, now there are still 21% charge on the battery.Only Clock and Settings were active on home screen.
It could be related to the phone waking up and doing lots of things simultaneously: I had not yet used the phone today, briefly after the call has been missed (due to being unable to "Answer" it), I received an e-mail notification.
Related may be https://together.jolla.com/question/14717/lock-screen-does-not-respond-to-swipe/. There it is suggested, to place the handset horizontally on a flat surface (upside down?, a relation to the proximity sensor is assumed there). Unfortunately, this is not really a solution if you are short on time until the call is diverted or stopped due to other reasons.
jgr ( 2014-02-24 11:29:18 +0300 )editPS: I am quite sure that I did not cover the proximity sensor as is suggested in question https://together.jolla.com/question/6096/double-tap-occasionally-fails-to-wake-device/, which may be related regarding the cause of the problem.
jgr ( 2014-02-24 11:54:43 +0300 )editI'm getting the same issue and it's started to affect the daily use quite a bit. Approximately 1/3 times I'm unable to answer a call in time, and it seems not to be connected to the battery state. Sometimes it fails even though battery is full, and sometimes it works even if battery is almost empty. I hope the next release will fix this, since otherwise removal of the beta label is too soon.
matrixx ( 2014-02-24 12:34:26 +0300 )editits maybe connected to this issue that complete phone is freezed when its looking for the correct network, that issue took place some how often
meldolion ( 2014-02-24 23:36:19 +0300 )edit