Ask / Submit
74

[bug] Jolla C, could not receive sms/phone call

Tracked by Jolla

asked 2016-09-17 02:10:41 +0200

Whippler gravatar image

updated 2017-09-30 13:21:24 +0200

BonoNL gravatar image

So earlier today i was supposed to get couple sms messages that the item i ordered is ready for pick up, but never received them and had to rely on the email notifications. And later on i missed a call that never ringed or showed up on the phone.

So i asked a friend to call me. It booped normally on his end as if waiting for answering the call. But on my end nothing happened, Jolla C never ringed.

after rebooting the device i got the sms messages. and calls started working, pretty serious bug, missed my pizza too :/

sonera in finland, data on 4G, sometimes dropping to 3g.

Update 26/4/2017: Still not fixed in 2.1.0.11

Update: 16/7/2017: I did play around with two aqua fishes and find-my-jolla app. did send the magic word from both devices to the other. While i was able to send sms and the other one did receive, mine did not receive a single one untill reboot.

Update 30-09-2017 In my case it was fixed with the 2.1.1.26 update. Can we confirm that it has been fixed so we can close this question?

edit retag flag offensive close delete

Comments

Country, carrier, technology (3G, 4G?)

ossi1967 ( 2016-09-17 08:09:34 +0200 )edit
8

I have the exact same issue with my Jolla C, though I have observed it only with calls and not messages. I have at least three confirmed cases where the other party tried to call me and it looked like it was ringing on its side, but nothing showed up on my phone. Not even a missed call notification, it's like the call never happened. I was reluctant to report it until now because I wanted to eliminate the chance of an app or a patch etc. interfering... I have removed scumstopper app and removed all network change settings from Situations app to see if it would help, but the problem with this bug is you cannot reliably reproduce it or be sure it has gone away. Please Jolla, pay attention to this issue because it certainly is a showstopper....

thisisme ( 2016-09-17 15:14:56 +0200 )edit
1

I have the same on Aqua Fish, both on 2.0.2.48 and 51 versions

x1f ( 2016-09-19 13:48:54 +0200 )edit
1

It did happen for me with 2.0.5.6 on a Jolla C. I only noticed, when my Mom called me on the landline at home, asking me if I was okee and why I would neither answer to calls or SMS text messages.

The Jolla C had an uptime of ~10 days by then and I think I at least disabled SIM card 2 in that period.

I'm using Swisscom (4G enabled) in SIM1 and SIM2 is 3AT card, but only enabled when I go to Austria.

Venty ( 2016-12-12 15:01:15 +0200 )edit
2

I can't understand how this is not treated as a release showstopper by Jolla...

thisisme ( 2016-12-12 19:01:27 +0200 )edit

26 Answers

Sort by » oldest newest most voted
0

answered 2017-11-02 19:25:14 +0200

DarkStarSword gravatar image

updated 2017-11-10 02:04:43 +0200

Edit: Since this issue seems to be a little different, I've moved it to a new bug report:
https://together.jolla.com/question/173276/bug-unable-to-receive-sms-phone-calls-xperia-x-dual-sim-intex-aqua-fish/

This (or perhaps something very similar to it*) is still happening to me on 2.1.2.3 with an Intex Aqua Fish - after some amount of time I stop being able to receive calls or SMSs, but the phone still appears to be connected - the only way I find out is when someone complains that they couldn't get through to me, or I try to call myself or log into a service using my phone for 2FA and don't get the SMS.

My first SIM card for calls and SMS is on TPG in Australia, which is a reseller of the Vodaphone network. My second SIM card is also on the Vodaphone network (directly, not a reseller like TPG) for data. Both of these are connected to the "Vodaphone AU" network (I can also sometimes see "Vofaphone AU R", but I get "problem with connection" if I try to use it).

Notably, this issue only started for me when I moved from Sydney to Melbourne, which suggests to me that this is more than just carrier specific, perhaps depending on the specific network gear in use in the local towers. I can see two cellphone towers in the park right next to my place - I don't know if either of those are used by Vodaphone, but my signal strength is pretty much always shown as maximum, at least on SIM 1.

Nothing I've tried will work around it - tried all combinations of prefer 2G/3G/4G, disabling data, manual/automatic network selection, etc. Switching flight mode on and off or rebooting are the only workarounds, but that is not acceptable. I did try to gather some logs, but the problem refused to occur while I was doing that. ~~I am going to try with SIM2 completely disabled over the next week or so to see if that does anything.~~ Edit: Xperia X arrived sooner than expected, so probably not going to do this test.

  • One notable difference I can identify from the OP is that when people try to call me they get a message that my phone is switched off or unavailable, rather than ringing out. I have gone out of my way to disable all redirect, voicemail, etc services from my carrier.

Update 2017-11-05: My Xperia X (dual SIM model) arrived sooner than expected, and after two days of use a similar, but different issue is showing up on it where it loses connection to the network, but it actually shows that on the display: https://together.jolla.com/question/170394/xperia-x-loss-of-mobile-network/

Update 2017-11-10: This same issue just occurred on my Dual SIM Xperia X running 2.1.3.7 as well, where the phone indicated it was still connected but a TFA SMS did not arrive and when I tried to call it from my landline I was told it was unavailable. The phone indicated it was connected to 4G at the time, and was connected to WiFi, so was not using a mobile data connection. I had rebooted the phone only a few hours earlier, which makes this instance the fastest occurrence of this issue that I'm aware of. Since this is a dual SIM Xperia, I am going to try disabling the second SIM over the next few weeks to see if it reoccurs.

Moved to a new bug report

edit flag offensive delete publish link more

Comments

1

Yours seems to be a different issue, in the original issue described in this question it appears as normal ringing to the calling party. Also, Jolla have released a workaround and the phone prompts you to reboot when this issue occurs, you would have got this warning if you had the same issue. It happened to me again the other day, Jolla C on 2.1.2.3....

thisisme ( 2017-11-03 10:14:38 +0200 )edit

This same issue just occurred on my Dual SIM Xperia X running 2.1.3.7 as well, where the phone indicated it was still connected but a TFA SMS did not arrive and when I tried to call it from my landline I was told it was unavailable. I had rebooted the phone only a few hours earlier, which makes this instance the fastest occurrence of this issue that I'm aware of. The phone indicated it was connected to 4G at the time, and was connected to WiFi, so was not using a mobile data connection. Since this is a dual SIM Xperia, I am going to try disabling the second SIM over the next few weeks to see if it reoccurs.

DarkStarSword ( 2017-11-10 01:19:22 +0200 )edit

Since this issue seems to be a little different from the OP, I've moved it to a new bug report:
https://together.jolla.com/question/173276/bug-unable-to-receive-sms-phone-calls-xperia-x-dual-sim-intex-aqua-fish/

DarkStarSword ( 2017-11-10 02:03:46 +0200 )edit
0

answered 2017-10-05 10:13:10 +0200

'Update 30-09-2017 In my case it was fixed with the 2.1.1.26 update. Can we confirm that it has been fixed so we can close this question?'

Jupp, in my case i can confirm that the issue is fixed.

edit flag offensive delete publish link more

Comments

1

How can you confirm it is fixed? It can take days or even a month before it happens again, at least in my case.

thisisme ( 2017-10-06 18:47:11 +0200 )edit

Because since the update from the end of September I haven't had the issue once and I got the please rebot message(work around) twice.

Before I had this issue multiple times a day.

So I can say the update has worked for me.

BonoNL ( 2017-10-10 21:26:53 +0200 )edit

I will say it's better now, i have sometimes a warning that i have to reboot my phone to restore calls and sms...

It happens most likely at the end of a phone call. loooks like network hangs.. Now i'm with 2.1.2.3 since 2 days and no problem so far...

mvdm ( 2017-10-17 11:22:55 +0200 )edit

@thisisme in my case the issue happen like every week, and because i have to receive a lot of calls during my workdays, so the bug was very annoying.

And until now, everything is nice and shiny.

BlaeX ( 2017-10-17 12:38:51 +0200 )edit

It's great for you guys that it doesn't occur that often anymore but if it had really been fixed it would surely be stated so by Jolla ;)

thisisme ( 2017-10-18 18:27:35 +0200 )edit
0

answered 2017-08-29 12:46:58 +0200

mvdm gravatar image

Can we have a workaround from jolla for this

please

edit flag offensive delete publish link more

Comments

This is not an answer above

OT:

The problem seems to be fixed with 2.1.1.26 for me, can we confirm this?

BonoNL ( 2017-09-12 22:28:52 +0200 )edit

Thanks for this information. I'll upgrade the aquafish to 2.1.1 - as it happens here for now only once / year, we may wait a bit to see if it was fixed indeed

deloptes ( 2017-09-30 01:39:29 +0200 )edit
3

answered 2017-07-24 19:25:55 +0200

ghling gravatar image

updated 2017-07-24 19:27:48 +0200

Does anyone know if this is fixed with 2.1.1 or at least the promised work-around was included which tells you when the bug occurred and you have to restart your phone? I haven't found anything about it in the release notes, yet it is one of the major issues currently for me.

Edit: I may just answer my own question: From the changelog for droid-config-l500d:

[l500d] Ask user to reboot device after rild restart.

edit flag offensive delete publish link more

Comments

So is it fixed or not in 2.1.1.24?

louisbob ( 2017-08-19 13:40:37 +0200 )edit

+ 1 for this - a big show stopper. Considering to pay 300+ € for Xperia ... if the bug is there, it will be a pitty

Can someone provide an answer please?

deloptes ( 2017-09-30 01:33:17 +0200 )edit

I didn't experience the issue at least since upgrading to 2.1.1.26. Nevertheless, at least the phone seems to notify you when you need to reboot it because the rild service failed. I've seen the notification a few times as false-negative directly after a reboot, so at least it seems to work.

ghling ( 2017-09-30 16:36:59 +0200 )edit

Thank you once again. Very important to know! I need to read more about rild - no idea what it was. Some background: I bought Intex AquaFish and tested it for some time, but my wife broke her phone and "confiscated" the AquaFish - so cool color and size etc :) She became a beta tester and for the past >1y the issue appeared twice. (Yesterday the second time) I need a business reliability. So my plan is to upgrade the AquaFish to 2.1 and buy the Sony Xperia. I'll test the Xperia X during the weekend, when risk is low and I am also not sure that it offers full range of services required for the replacement of my Nokia N9.

Anyway thank you very much and kind regards

deloptes ( 2017-09-30 17:41:29 +0200 )edit
0

answered 2017-07-20 11:26:40 +0200

updated 2017-07-20 11:26:59 +0200

Just a question to whom who have the problem:

If calls are not mentioned by the phone, do this occur to every caller, who tries to reach you, or do only some of them go down the drain?

E.g. is there a difference in provider of the caller, or are only calls from mobile networks are lost?

[In my case, i have the strong assumption, that are only callers from D2/Vodafone, a German network provider here, are affected.]

edit flag offensive delete publish link more

Comments

It happens with different networks, a reboot fixes it for some time...

This is what happens with my phone also. I am using a OnePlus X and thought the port was badly done but I was wrong, this bug exists in the original Sailfish system it seems. This bug has been affecting the phone for more than a month now or maybe more before I discovered it.

I don't know about the calls but I am sure about the SMS messages as I gave it a try this morning. I wanted to create a login on a website and use the SMS login function but I never received the said SMS and asked someone to send me an SMS and the phone did not receive it at first. I had to reboot the phone for it to popup but the login SMS from the website never came through.

This is a serious bug and I hope Jolla can do something about it.

Maximilian1st ( 2017-07-20 14:04:39 +0200 )edit
2

This bug is believed to be present on the Jolla C/Aqua Fish only. Are you sure it's the same bug on the OnePlus X?

Giacomo Di Giacomo ( 2017-07-20 15:11:09 +0200 )edit
1

I'm sure it does not depend on the provider. When it happes to me, I cannot receive any calls or SMS as well as I cannot send any SMS or make calls. Device: Jolla C

SagaciousT ( 2017-07-27 10:23:31 +0200 )edit

thats interesting, although i don't receive calls, i can make them (and send SMS) without problems. ...

BlaeX ( 2017-07-28 09:32:59 +0200 )edit
0

answered 2017-05-24 12:52:27 +0200

thisisme gravatar image

This bug hit me again yesterday. I only found out today when I got a complaint from my friend that I didn't answer her call...

Here is my ril_log.gz

Although I am not sure it's of any use since all the timestamps in there are 1970-01-01...

edit flag offensive delete publish link more
2

answered 2017-03-08 10:13:39 +0200

cuh7b5 gravatar image

Still no joy. Jolla C, "Prefer 3G", manual network selection, Telekom Hungary. Ril log and journal log:

ril_log_3G.txt, journal_3G.txt

Jolla, please do something!!!

edit flag offensive delete publish link more
1

answered 2017-02-14 06:03:01 +0200

zepher gravatar image

updated 2017-03-04 10:28:37 +0200

I have also had this bug,

Australia, TPG (3G) Intex Alpha Fish (with Jolla C packages installed)

I had it on Prefer 3G (SIM1) and automatic network selection. Now testing with manual network selection

[EDIT] - works with manual network selection for TPG

edit flag offensive delete publish link more

Comments

1

I don't know if this is of any interest. I still have these problems on Aqua Fish set to 2.1.0 early access. I tried to call somebody. On my phone the UI still showed the contact list and for me nothing happened. In background the phone called the selected number. After waiting a while the phone plays the network unreachable sound and shows that the call is cancelled. But the phone on the other side keeps ringing until it's picked up. I cannot cancel the call which is made in background because I don't even recognize there is a call. It's like the UI loses connection to the phone module.

EDIT: Manual network selection does not prevent my bug. Selected contact to call. The UI keeps showing the contacts overview. A Message like "network failure" was shown. Then I heard the other person and before I could talk the phone ended the call because of the failure. This is a very strange behaviour. The phone dials the number correctly but thinks there is something wrong. I don't know how to reproduce. It just happens from time to time. I have to reboot for a new try then.

Hensch ( 2017-02-28 09:19:09 +0200 )edit

Just a note, with manual network selection it works fine for me.

zepher ( 2017-03-04 10:27:49 +0200 )edit

Problem still occurs with manual network selection and "Prefer 3G" options on Jolla C.

cuh7b5 ( 2017-03-06 10:17:03 +0200 )edit
0

answered 2017-02-11 12:39:25 +0200

t0mps0 gravatar image

this. cant believe such serious bug exists...

however a while ago i noticed that after tethering i had to reboot my jolla-c to be able to use it again. but i cant remember was the error in receiving phone calls or using the internet. so this might be an option to try to re-produce the bug. i really dont have time, just wished for a good working phone, in which jolla-c fails rather badly....

edit flag offensive delete publish link more

Comments

If you can't believe it look at this call bug which is already present for 3 years!!!

BonoNL ( 2017-03-09 12:25:47 +0200 )edit

I have the same problem. Fortunately I only get this very rarely, but still even one not recieved call is too much. I get this usually when I travel between Estonia and Finland and there is a network cap for 15-20 minutes between the ride.

Peeter ( 2017-04-05 19:04:56 +0200 )edit

I have it when making 5/10 calls ongoing. But I don't know if Jolla is taking action on this bug.

BonoNL ( 2017-04-07 21:53:53 +0200 )edit
0

answered 2017-02-10 14:06:42 +0200

Marco gravatar image

Installed 2.1.0.9 two days ago and set network mode to Prefer 4G. Today exactly the same issue occurred as before, so the issue hasn't been fixed. Going back to 3G...

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
25 followers

Stats

Asked: 2016-09-17 02:10:41 +0200

Seen: 4,949 times

Last updated: Nov 10