[BUG]2.0.1/Taalojärvi auto ignoring incoming call

agreed. happens to me too.

Second that. Sometimes the display locks up, sometimes I can find the call muted and answer it. Telephone functions have been rock solid for a year now. Problems started immediately after upgrade.

I'm not sure if I'm having the same issue, but: Most calls, it seems, come through perfectly fine. There's one person I know of, though, who claimed he called me several times... but there was nothing. No ringing, no missed call notification, nothing in the call logs. This guy has my number stored on his cell phone since ages, so I rule out the possibility that he dialed a wrong number.

How is it with you guys? Do you find the missed calls in the call log? Do you see the LED blinking?

@ossi1967 yes, I can see this missed calls in call log. For me it's working likes after 1-2 sec of ringing it's stop ringing but i can still answer the phone call. It looks like press lock button during incoming call.

Happens to me, too.

I've seen this issue with two different callers so far - both in my address book. The ringtone plays for 1 second and then the call is automatically ignored.

I have a Insmat case for my Jolla phone and I've seen this behaviour with the cover closed and open. In both cases the phone has been display up.

Internally we are unable to reproduce the issue. Sent debugging instructions last week for couple of you. In case you see this and want to help comment here and I'll contact you.

I'll gladly help. Today I almost missed a call from the hospital due to this bug.

@Joona Petrell tell me how to help you.

Seems like voicecall-ui-jolla had gotten out of sync. The traditional remedy seems to have worked, i.e. pkcon install voicecall-ui-jolla. If this sounds unfamiliar, check out developer mode, ssu, pkcon.

I tried to install voicecall-ui-jolla and I get information there is no required version but after pkcon refresh it was possible to install voicecall-ui-jolla. So you right voicecall-ui-jolla had gotten out of sync.

Did you have any problems during the system update, and did you update the normal way or from commandline?

I updated system the normal way. Didn't have any problems.

Unfortunately updating voicecall-ui-jolla didn't solve problem. @Keto@Joona Petrell Do you want any logs before I'll go back to previous version?

@atlochowsky I thought I had sent you email already. Could you send me an email on my jolla.com account so I can obtain your email address?

@ierikho Sent you mail.

@Joona Petrell I have not noticed mail from you. Give couple days to reproduce this issue.

I believe updating voicecall-ui-jolla solved the problem for me.

@ierikho didn't solve the problem for me. I send logs to Joona Petrell and I hope he will find out the reason why this happening.

somehow missed this bug report but suffering from it too - but not every call shows this behaviour- missed many important calls already:-(

@all maybe it is stupid what i tell you, maybe could help you by searching on reproducibility on it.
try your tests with different ambiences. I remark by myself some strange things happened with the sound depends on which ambience is selected...

Maybe some of you have already done next things, if not, you could try to stop different "nice to have" interfaces and let just a minimal survival one.
Come back to 2G calls, no bl, no wifi, no gps, etc...
If it's better, then you can one after one (with in between check) to reactivate it.

other stupid question... who has the app "situations" installed and on working?

@cemoi71. That's a very good point. I do have Situations installed and the calls are ignored while my phone is in "Silent mode" because I'm at work (decision factor is the Cell-ID). Anyhow at home, when I put the phone manually on silent mode, calls are not autoignored.

@cemoi71 nope - no Situations installed but ignored calls ...

@elastic thx for answering

@all with the bug, an other stupid question. if you have openrepos patch/app what's happened if you put them away for some little amount of days

@cemoi71 actually it's not bad idea. I'll turn off patches and will see what happen .

@atlochowski ;-) i'm really curious to know how if it works by you then...
If (only) the problem disappear, you can try then step per step bring back each one (just one after one), to identify the bad-one. (hope that we will find the problem).
If problem still persist, then we could try some other things.
Are you able to tell if by jolla on their side could reproduce this problem?
If not then, that will really complicated...

@atlochowski i have just a simple question... with which ambience are you currently ?
By me i note sometimes something strange with the "intense" one. like not expected sound level programmed with "situations" app. And i'm not sure because too rare, i passed one or 2 calls on the month (about 20). But couldn't really understand what happens, if it is because of my inattention or other things.

@cemoi71 I don't know if Jolla have problems with reproducing this issue but for sure needed logs. So I sent them logs from my phone.

Already know I can't live without "Disable wake up lockscreen animation" patch and "Upcoming event's on lockscreen".

@atlochowski "I don't know if Jolla have problems with reproducing this issue but for sure needed logs. So I sent them logs from my phone." Seems for me that they don't have the problem by home. That make the the issue more complicated. Ideally is to find someone by jolla who could make his device in the nearer condition than you.

"Already know I can't live without "Disable wake up lockscreen animation" patch and "Upcoming event's on lockscreen"."
interesting is to know if all those who have the same problem as you, have the same patches. I ask me how could we ask them for it...
the action is just to eliminate if the problem comes from patches or not. From ambience or not.
What i would suggest you is give a list of your patches on your above thread and convince all the other who have the same problem to make the same, with argument that has maybe nothing to do with it, but to eliminate it to the suspected-list.
According to me (you could make this list longer) the things which could make problem are:

• the openrepos patches
• Third part apps which could works in underground like "situations"
• Other interfaces from system which could as early access interfere with it (BL, wifi, buteo etc..). but for these could jolla have a better overview.

please tell me if you don't understand what i'm telling, i try my best to have a clear discussion in English. but sometimes could be difficult (things from experiences and culture).

I had the same problem even before I had any patches or any other ambiences than the stock ones. All this after installing the early taalojärvi.

Happens here sometimes (1 out of 10 calls) on two different phones.

I have the problem as well with no patches and no Situations app. The problem pops up also with my custom picture ambience.

I thought so far, that it is about the call ignoring by turning the phone around, gyroscope is quite crappy other times as well.

@William interesting report... did you tried to turn the automatic orientation to off?
otherwise may i ask you which kind of other communication interfaces do you have on working? bluetooth, wifi, 2g, 3g 4g? gps (not a communication interface but could maybe interfere)...

@all as an idea which spontaneously come to me, on the list of things that could interfere may be an android part (an app or a part of the lib interface). You could try to cut the android support to see if it comes from there...

Great feature, I don't get bothered anymore :-D ....

We have discovered one issue which can cause automatic incoming call silencing. I'll send test RPM for testing shortly.

@cemoi71 I turned now auto orientation off, let's see. I only use 4G (no bt, no wifi, no gps), data doesn't even switch to 3g or 2g.

@Joona Petrell is it possible to know which parts or functions are engaged? Which one should we stop or start for having to test and confirm your suspicions? please.. thx in advance for answer..

@cemoi71 Auto orientation setting does not effect the issue, it happens wheter on or off.

@William was too easy to be a serious candidate. i'm curious what Joona could deliver from informations (if you saw his above comment).

It might not be related but I changed my display shield yesterday - the old one was really scratched and not clear any more - today not a single call was ignored ... I'm wondering if Jolla changes the sensor to a more sensible setting so it recognises dim light (or a scratched display shield) as turning the phone upside down to ignore the call ... just a suggestion ...

@elastic if you still have your scratched shield, you can try it again... maybe it could happen something with the parameters of chip sensitivity ...

@cemoi71 no sorry, went straight in the bin and out in the morning :-(

I saw it happening only once while checked several times. I get then a message that says incoming call is active and the incoming phone call tone gets muted.

as every call was set to ignored after one ringing today it seems not be related to the old screen protector - would have been to easy :-( - what I can say for shure is that it always happens when the phone is in my pocket or laying on the display or in dim light - so it might be somehow related to the sensor ...

@elastic first try to have the whole phone under a paper sheet or anything which cover it. and make a call.
then maybe if you know where is the sensor, to put your thumb on it.

Ok I figured something out: during an incoming call you can ignore (silence) the call by flipping the phone - now it seems that it don't have to put on a table to silence it it is enough to just flip it (test it - no need to lay it on the display) - and since 2.0.1.x it now seems that the phone is recognising even smaller movements (like walking with the phone in the pocket) as flipping and that maybe is why calls are ignored every now and then - test it - call your Jolla and and just move it a bit in your hand - mine starts to ignore the call very soon then :-(

@elastic maybe you right. For me it's usually happen when I'm trying to pull out my phone from the pocket or when phone is in pocket and i walk. Maybe flip to silence is to sensitive. @Joona Petrell what you think about that?

@elastic yes i know for the small flipping case, but i didn't knew that was not so sensible before. interesting what you tell. But i don't understand why it would be really sensible by your phone and jolla devs didn't saw it. And that is touch not all devices... that's really strange. do you think that it is more the problem with the acceleration sensor than the one for the light? do we need a pocket detector?
do you know if there is an app which analyse all the phone sensor, and make graphic to observe the sensibility? that would be practical for a lots of people who want to check the feature of their devices...

@cemoi71 - only thing I can say is that it never happened before the update ... For shure it isn't the light sensor as silence by flipping even works when you're holding the phone in the air - I never used that feature so I didn't know how it works before I did some tests on my phone today - if there would be a switch to turn off that feature we would know more but it's a fixed feature (why ever) - so everything here is just wild guess ;-) @atlochowski thanks for the info @joona-petrell anything?

@elastic that's right, it would be a strange relationship between light-sensor and the call-function. it make more sense with the accelerator.
Interesting would be to know if all early access have this issue.
Because currently it seems that not all have it...

someone knows where is the option to activate deactivate the silence function of a call by flipping?

just by the way do you have already given a look at this ? https://together.jolla.com/question/129794/possible-bug2017connection-problems/
just to be sure that is an other theme...

For me this problem started a couple of days ago (and couple of weeks after update). I've got also problems with Situations app. At first it didn't switch wifi and cell connections, then it worked for couple of weeks and after I discovered the ignored calls problem I made a restart and now Situations doesn't switch networks again. I tested now this call ignoring problem. At first I thought that the screen must be covered (I covered sensors with no result), then I thought that the phone has to lay face down but only flipping the phone got the ignoring result every time.

@atlochowski do you know how far is jolla on the bug? seems that the status above changed to "in release"... Did they found something concrete? thx in advance

@cemoi71 I don't know anything,

@atlochowski hi, you told in an other thread that jolladevs are still active on this bug. How do you see it? Did you have get further Updates? (I'm not an early access member thus, i don't know exactly how works an early access process until its end)

They sending me packages by mail and I'm testing if their solution works or not. Of course I'm talking only about finding solution for ignoring incoming calls.

@atlochowski binary files...am i right? like chris adams told me some things about possibilities for early access people support... how interesting!

@cemoi71 It depends. Some part of sailfish is open source. So if it's about changing something in xml files they can send pure code.

@atlochowski yes i understand something like that. As i know (correct me if i'm wrong) the whole gui interface is closed (i think it is the silica interface), and a big piece of other parts of the os are open.
As i understand buteo (i think that should be the synchronisation interface) has something that should be closed too.
I have an issue (like a big part of other members) with the caldav and carddav interface.

And after some discussion with chris adams, for this part, that is not so easy as non-early-access to get a binary file for his fix, because the code is closed at this part of the system...

Still no updates on this bug? It's really annoying.

@atlochowski how does it work on your side? is it green? yellow? or red?
May i ask you an other question? this "bug" does it appears when you use the internet through mobile network? Do you have wlan on too?
would it happens if your device get internet from any interface? or no internet from anything?

seems to be really complicated. A kind of combination of different unwanted behaviours...

It's now been over 2 months since Taalojärvi went into Early Access, and this bug still seems to remain unfixed. Got no problem with the fact that some bugs are tricky to deal, but are we likely to get any official comment from Jolla on the delay and anticipated timelines for the public release of Taalojärvi? The silence at the moment is a shame

@strongm please don't use hard words so quick. that's annoy you more or less deeply, is understandable. but "shame" is strongly negative, especially when you have no idea on what's happened....

I'm guessing English isn't your first language, since 'it's a shame' is a lightweight idiomatic expression that simply means "that's disappointing", as in "What a shame that you couldn't go to the ​party". That's how I meant it.

@strongm hmmm if i use the French translated version of shame, that is really strong. But i notice that some French (not really usually) colleagues use it so freely without to think what reaction it could produced. Then it explode naturally.
And on this experience, i ask me if this phenomenon is possible in English too.
Is there a word stronger than shame?

This isn't really the place to go into it - but there is a (often significant) difference between an colloquialism/idiomatic expression and the individual words it consists of.

ahah i know what you mean. shame may have different interpretation and impact, depends on the use of it, the combination with other words. but here how it is used, that is clearly used with a strong sense "The silence at the moment is a shame" i can turn the idiomatic expression of it in every different levels and sense, it has an explicit and clear meaning...
Whatever. no comment....

cemoi71: crois-moi, c'est toi qui interprète mal. En anglais, "it's a shame" veut vraiment dire "c'est dommage". Ce n'est pas intuitif, mais le français a des exemples similaires comme dire "sans doute" pour dire que justement il y a des doutes.

@strongm i see now what you mean. sorry i need currently a lots of time to step back, and sometimes some internet searching give wrong founds especially if it is quick done... this word shame is for me really particular, especially currently with the issues that we know....

@jbruggem oui tu as raison en ce qui concerne le litige. mais le cas de sans doute n'est pas comparable. ca exprime une éventualité qui tend sur l’absence de doutes. Et en ajoutant le mot aucun on obtient une accentuation. ce n’est pas un faux ami. enfin bref, on dévie du sujet principal. bonne continuation

It seems like there is no solution in sight. So I'm quite unsure what to do: Wait until there is finally a solution delivered or make a Factory-Reset and go to the last stable Version, which means a lot of work until my setup is like it is at the moment.

This bug is really annoying, because it applies to the heart of a phone.

I opted out from early adopters program and got a new "update" for Saimaa. I don't know if that is recommended way to downgrade but it seems to work for me.

Really, that sounds great. I'll give it a try. How long did it take to show you the "update" after your opt out?

I give that answer, just that this doesn't get lost in all the comments:

If you like to downgrade you can do that, by opting out of the early adopters program. I had to wait for around three hours, than an "upgrade" to Saimaa was shown. I disabled all my patches, downloaded and installed Saimaa. All went pretty well.

This information came from @Janssoni. Thank you very much for that. Hopefully the ignored calls are now history.