Ask / Submit
205

[bug] Trying to answer a call: Pulley menu cannot be pulled down.

asked 2014-02-12 17:58:07 +0300

fivepointsquare gravatar image

updated 2015-07-21 12:32:15 +0300

heubergen gravatar image

Sometimes when I get an incoming call the slide down to answer / up to reject/silence/etc simply does not respond to any kind of touching on the screen.

Fortunately this happens quite rarely (1/10 times at a rough estimate) but is still quite a serious issue.

Addition: The "end call" button is affected as well (no response), as reported further down in the answers, and as I have experienced myself.

edit retag flag offensive close delete

Comments

4

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 )edit
1

I 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 )edit

PS: 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 )edit

I'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 )edit

its 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

11 Answers

Sort by » oldest newest most voted
36

answered 2015-05-18 16:47:08 +0300

AkiBerlin gravatar image

Occurred to me too in 1.1.4.29

edit flag offensive delete publish link more

Comments

Same here, at least three times. Battery was not particulary drained since I use to keep the phone charging whenever I am at home or work.

Giacomo Di Giacomo ( 2015-05-18 18:58:21 +0300 )edit

Same here.

hoschi ( 2015-05-19 14:11:46 +0300 )edit

Me too. One time.

Makeclick ( 2015-05-19 20:42:22 +0300 )edit

Same here.

M.Bln. ( 2015-05-19 21:21:19 +0300 )edit

Same here.

tomoshokas ( 2015-05-19 21:37:57 +0300 )edit
16

answered 2015-05-19 11:45:33 +0300

updated 2015-05-19 11:46:20 +0300

I never dealt with it before the last update - 1.1.4.29. Now confirm this bug - when incoming call the slide does not respond, only buttons work (volume up/down, power for ingnore call). Have this behavior only when getting incoming, not often, 1/10 as topicstarter. Battery 21%

edit flag offensive delete publish link more

Comments

i also had it once last week, but it occured couple of times not during incoming call but just on every level of UI in every app in every screen - no.pulley menus no buttons response

Dragomir ( 2015-05-19 19:21:10 +0300 )edit
2

@Dragomir: Maybe you run into the same input focus problem than I did several times.

axaq ( 2015-05-20 03:24:14 +0300 )edit

@axaq: yes this sounds just like my problem, but i also had one with the incoming call too

Dragomir ( 2015-05-20 10:29:12 +0300 )edit
1

This happened to me again recently. How about a fix Jolla?

unruly ( 2015-05-20 11:22:27 +0300 )edit
1

Same, several times on 1.1.4.29 and never before

SergeiStPete ( 2015-05-23 00:53:30 +0300 )edit
11

answered 2014-02-25 20:51:18 +0300

unruly gravatar image

I had this happen today. Jolla was fully charged when I received a call but was unable to answer it as the pulley system would not respond. No response either up or down - 'answer' or 'reject'.

edit flag offensive delete publish link more

Comments

4

Happens to me sometimes also. To answer the call I am able to stroke from the side and go the main screen, then go into the phone app again (the call is not rejected while I do this, but alert sound is muted) and the the pulley menu works again. If I am quick enough, I can still answer the call.

Macilaci457 ( 2014-04-16 16:08:09 +0300 )edit

Encountered this once with Paarlampi. Next (incoming) call had no audio (might be unrelated, caller [called later back] was in car so hands-free at other end might be problem there), then I turned phone off for moment and all was good again. Also, two times now after answering (pulley to answer worked) phone has completely hung when connecting - as in "take battery out" hung. Black screen and nothing else, power button does nothing. (not sure if both of either of these were with Paarlampi or previous release)

ToniR ( 2014-04-19 20:42:20 +0300 )edit

Happened again today! Phone fully charged.

unruly ( 2015-05-22 13:18:17 +0300 )edit
2

@unruly - This is not an answer, it's a comment. Please stick to commenting if you are not responding with a solution.

Edz ( 2015-06-06 13:57:28 +0300 )edit
11

answered 2015-06-06 14:05:56 +0300

Edz gravatar image

updated 2015-06-06 14:14:03 +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,

edit flag offensive delete publish link more

Comments

1

Unfortunately the pkcon install voicecall-ui-jolla didn't solve the problem for me. Never had the problem before Äijänpäivänjärvi update. On the other hand the phone got also an update & full reset in service just before Äijänpäivänjärvi.

tw ( 2015-06-07 18:18:12 +0300 )edit
2

@Jolla: any progress in localizing the problem and in finding a solution? As already written this is a serious issue! Please fix this as soon as possible. Many thanks.

M.Bln. ( 2015-06-12 23:03:47 +0300 )edit

it didnt help here, either

mettska ( 2015-06-26 22:43:08 +0300 )edit

occured to me twice now since update to 1.1.6... so like once in a week

pawel ( 2015-07-11 11:26:40 +0300 )edit

Perhaps the buc is triggered by multiple causes, but this fix worked for me.

jollakin_on ( 2015-09-02 12:35:45 +0300 )edit
10

answered 2015-06-26 10:07:39 +0300

meneer gravatar image

This doesn't happen often, but when it does, for me this works:

  • Swipe right or left to leave phone screen.
  • Then select phone cover from lockscreen.
  • Pull up or down again to accept call.

It may look like you declined the call, but pull down to re-confirm call.

edit flag offensive delete publish link more

Comments

2

1.1.6.27 and still having the problem

tw ( 2015-06-26 22:46:39 +0300 )edit

Just a small comment - had this before, but the issue disappeared on 1.1.6.27 with full reset before the upgrade which i make for some other reasons. Currently android support and many apps were installed previously are off.

SergeiStPete ( 2015-07-03 14:51:39 +0300 )edit

It happens to me too :(

carmenfdezb ( 2015-07-03 17:38:35 +0300 )edit

I just had this problem for the first time, running 1.1.6.27.

reinob ( 2015-07-27 09:56:17 +0300 )edit

Yeah, workaround works usually but is quite a hassle just to answer to call.

aispof ( 2015-08-10 19:51:54 +0300 )edit
8

answered 2015-05-22 21:20:17 +0300

M.Bln. gravatar image

It happened to me today too. So it's the 2nd time for me..

BUT in this second case I could NOT END my call, instead of declining or answering an incoming call. So this seems to be more an issue about the phone-app at all than just about reacting to incoming calls.

@Jolla: plz fix this - this is a serious issue!

edit flag offensive delete publish link more

Comments

I have also encountered this issue for a no. of times. The workaround as suggested above to lock the phone from the lock key and then go to the phone app works but this needs to be fixed asap.

dillihifi ( 2015-05-24 10:54:52 +0300 )edit
7

answered 2015-07-03 13:50:28 +0300

ozzi gravatar image

Please fix this. It's still happening. This is a real big pain point, so many missed calls...

edit flag offensive delete publish link more

Comments

Agree, with 1.1.7.24 that bug happens to me more often then before. This is annoying - please fix this.

tomorrow ( 2015-07-25 10:04:24 +0300 )edit
4

answered 2015-06-26 04:36:16 +0300

Occurred to me again in 1.1.6.27. pkcon install voicecall-ui-jolla didn't solve the problem

edit flag offensive delete publish link more

Comments

Did you reboot as one solution suggests?

raketti ( 2015-06-26 08:40:56 +0300 )edit

Reboot after pkcon install voicecall-ui-jolla ? Yes, of course, many times.

Maybe I must repeat pkkon after upgrade to 1.1.6.27?

zaharov.andrei ( 2015-06-26 09:02:52 +0300 )edit

To be honest, I have no idea, but you could try that. I haven't had this issue and I don't know my way around that well to help, sorry.

raketti ( 2015-06-26 09:49:12 +0300 )edit

I had the same problem with latest update.

meldolion ( 2015-06-26 19:48:29 +0300 )edit

I've experienced the issue with 1.1.6.27.

Rigoberto ( 2015-07-03 14:56:31 +0300 )edit
3

answered 2015-07-21 11:09:14 +0300

Unfortunately this problem has not been resolved yet. I experieced this issue a few minutes ago, I'm running early access release 1.1.7.24, my battery is at 75%. In the meantime I'll use meneer's 'work arround' from june 26 '15

Jun 26 '15 meneer 3233 ●24 ●45 ●40
This doesn't happen often, but when it does, for me this works: Swipe right or left to leave phone screen. Then select phone cover from lockscreen. Pull up or down again to accept call. It may look like you declined the call, but pull down to re-confirm call.

edit flag offensive delete publish link more
1

answered 2015-07-03 18:02:38 +0300

rferrazz gravatar image

I think that is something related to Android apps, try to start an android application and lock the screen with the lock button, then call your jolla, here something nasty happens every time. I'm experiencing issues even when i get an incoming call while I'm using an Android app.

edit flag offensive delete publish link more

Comments

I have no Android on my Jolla but have had this problem for well over a year.

unruly ( 2015-07-04 14:11:06 +0300 )edit

For me this happens if I'm using another app (Jolla or android) when the call comes. Only Phone app does not respond to screen gestures. My guess is application focus-layer problem.

Manwe ( 2015-09-01 17:16:55 +0300 )edit
Login/Signup to Answer

Question tools

Follow
24 followers

Stats

Asked: 2014-02-12 17:58:07 +0300

Seen: 3,197 times

Last updated: Oct 02 '15