[Bug] Mobile data connection dies (since 2.0.1.X)

Question

76

[Bug] Mobile data connection dies (since 2.0.1.X)

Tracked by Jolla

asked 2016-01-30 00:11:37 +0200

pfbach

1211 ●11 ●18 ●20

updated 2016-08-31 16:49:27 +0200

nodevel

9595 ●94 ●124 ●122

Has anyone else experienced that the mobile data connection suddenly dies in the new version? I have to use WLAN, Restart Network Connections or reboot to make it work again. Has happened to me atleast 3 times. Never experienced this in prior versions.

EDIT: Still present in 2.0.1.11. As it was introduced in 2.0.1.7, let's hope it won't make it into the final release, as it makes 4G completely unusable (and 2G/3G problematic).

EDIT 31.8.2016:

Still present in 2.0.2.51 Early Release on Jolla C. It's a shame, since this release was supposed to fix 4G/LTE problems. 4G internet still not working.

edit retag flag offensive close delete

Comments

Never, I have always used to kill it myself after usage. BTW could the problem be somehow related to this one?

lakutalo ( 2016-01-30 12:05:35 +0200 )edit

Yes, I have this bug too. I posted a message about that here: https://together.jolla.com/question/126892/release-notes-201taalojarvi-early-access/?answer=128213#post-id-128213

Renault ( 2016-01-31 17:12:14 +0200 )edit

1

Yes, this has been the biggest issue for me on v2.0.1.7 (and now 2.0.1.11) which I have observed independently on two devices, on different providers (Czech, German) and on different locations (countries). So it seems that this bug should be provider or device independent.

As a workaround, I switch to use 3G only, as it happens on 4G all the time. Switching to 3G doesn't solve the problem (it still happens occasionally), but minimizes the occurrence significantly.

nodevel ( 2016-04-01 10:51:06 +0200 )edit

That was seriously fast testing. Too bad the bug is still there.

raketti ( 2016-04-28 16:38:52 +0200 )edit

4

And posting bugs into the release notes is a bad habit of people. No-one can track that properly.

chemist ( 2016-04-28 17:30:24 +0200 )edit

Never, I have always used to kill it myself after usage. BTW could the problem be somehow related to this one?
lakutalo ( 2016-01-30 12:05:35 +0200 )edit
Yes, I have this bug too. I posted a message about that here: https://together.jolla.com/question/126892/release-notes-201taalojarvi-early-access/?answer=128213#post-id-128213
Renault ( 2016-01-31 17:12:14 +0200 )edit
Yes, this has been the biggest issue for me on v2.0.1.7 (and now 2.0.1.11) which I have observed independently on two devices, on different providers (Czech, German) and on different locations (countries). So it seems that this bug should be provider or device independent.
As a workaround, I switch to use 3G only, as it happens on 4G all the time. Switching to 3G doesn't solve the problem (it still happens occasionally), but minimizes the occurrence significantly.
nodevel ( 2016-04-01 10:51:06 +0200 )edit
That was seriously fast testing. Too bad the bug is still there.
raketti ( 2016-04-28 16:38:52 +0200 )edit
And posting bugs into the release notes is a bad habit of people. No-one can track that properly.
chemist ( 2016-04-28 17:30:24 +0200 )edit

Answer 1

7

answered 2016-09-02 15:32:04 +0200

Ta_das
291 ●11 ●19 ●23

updated 2016-09-07 00:35:33 +0200

The same for JollaC with factory OS version (2.0.2.43). I live in a reinforced concrete building, in the ground floor, so the cellular signal is not always strong, varies over the time and in different places of the apartment. With my previous phone, Nokia 603, when it used to lose the 3G signal, it switched to 2G after couple of seconds. Now, when JollaC loses 4G, while checking emails or using web browser, it often loses all GSM connection, even 2G, in spite it is sufficient everywhere. Only phone restart helps. I am not always aware of this connection issue, so I have missed important calls and sms messages.

I do not know is this particularly the same issue as in the topic of this post, but I tried to avoid duplicate posts, so I wrote here. At the moment I have no time to trace debugging information, as I am not so much skilled in Linux command line, so it will take considerable amount of time to do it.

I consider this a big flaw of a phone, which should be fluently working on daily tasks, without paying much attention to the working internals. I like the Sailfish interface a lot, and small missing usability things which would be great if implemented - do not bother me. But the unreliable connection is a serious flaw, and I start considering about choosing a different phone, no matter how much I apreciate the Sailfish OS idea, as I use only one phone device, and to opt for two - one for daily tasks and other for leisure hobby is nor for me.

EDIT. While this issue happens I do not use WLAN, only mobile data connection. And, checked just now – enabling and disabling flight mode also restores connection, no need to restart the phone.

EDIT.2. Just to add, while the issue happened and phone missed calls and messages, the phone was not completely out of cellular network coverage, it must had remained partially visible to network provider, as the persons who had called me, said later, that to them my phone was giving usual sound of phone being called, but I never heard the call, neither my phone registered missed calls. Allso the messages which weren't received – they dissapeared, but were not kept at provider to be delivered later, as it usually happens, when the phone is turned off.

edit flag offensive delete publish link

Answer 2

5

answered 2016-05-10 19:41:03 +0200

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2016-05-10 19:54:43 +0200

Mr.Pancake
513 ●11 ●17 ●19

My mobile connection is dead on 2.0.1.11 It just says "Sorry. Could not connect to selected network". Sometimes WLAN can't be reached as well.

I could use some help debugging it to find the problem. Otherwise I'll have to reset the device, I'm not very fond of that idea.

Toggling flight mode, rebooting, using Sailfish Utilities has no effect whatsoever.

P.S had to bump this.

edit flag offensive delete publish link

Comments

3

We have internal bugs to track various connectivity issues: JB#33640, JB#33473, JB#35066

Can you please try the following to see if it helps:

dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0/context1 org.ofono.ConnectionContext.SetProperty string:Active variant:boolean:true

If that does make it connect, then I suspect that this is a connman+ofono interaction issue.

chris.adams ( 2016-05-11 05:04:44 +0200 )edit

yes, too. need to restart network services every 2/3 days

pawel ( 2016-05-11 20:58:03 +0200 )edit

1

@chris.adams the first run resulted in: Error org.ofono.Error.Failed: Operation failed, while on the second execution the reply was method return sender=:1.8 -> dest=:1.614 reply_serial=2

Mobile data connection now works. I hope it helped.

Mr.Pancake ( 2016-05-11 21:19:10 +0200 )edit

Thanks, this is sounding like JB#33473 - I will ping the appropriate developer.

chris.adams ( 2016-05-13 10:46:00 +0200 )edit

4

If you can, the following instructions will get more debug information for when it occurs:

It would be useful if you could create these two files:

/etc/tracing/connman/connman.tracing

containing this line

TRACING="-d '*ofono*'"

and

/var/lib/environment/ofono/debug.conf

containing this line

OFONO_DEBUG="-d drivers/ril/ril_plugin.c,drivers/ril/ril_data.c,drivers/ril/ril_network.c,drivers/ril/ril_sim_card.c,drivers/ril/ril_modem.c,drivers/ril/ril_radio.c,ril_plugin,ril_trace,grilio"

wait for the problem to happen again, and send the log (devel-su journalctl -a > log.txt) to chris dot adams at jolla dot com after redacting personal information from it.

If anyone can help by doing that, I'd greatly appreciate it :-)

chris.adams ( 2016-05-13 10:47:54 +0200 )edit

Answer 3

5

answered 2018-06-06 18:10:24 +0200

teleshoes
231 ●3 ●12 ●10

just saying, 2 years later, still have this HORRIBLE BUG on sailfish X, official build, latest version. cellular connectivity silently fails, for hours at a time, and then suddenly re-awakens (15 new texts, 12 voicemails, blah blah blah). this seems to occur MORE frequently when WIFI+GPRS are on in one place for a long time, BUT it still occasionally happens with wifi turned off.

this is more or less the worst possible bug a phone can have, and it seems crazy to me that it could last for years and multiple hardware ports.

p.s.: i also have this similar-but-separate bug mentioned in this thread: android loses connectivity while the rest of the phone keeps it. killing the app (google-drive), turning on/off airplane mode, and restarting the app fixes it. restarting aliendalvik fixes it too.

edit flag offensive delete publish link

Comments

I think i experience the same sometimes. #sailfishxc

edgar ( 2018-08-07 21:23:31 +0200 )edit

I am experiencing the same problems on my Sailfish X. In a few cases, I could have missed an important appointment because of this, but so far, I've gotten lucky. Unacceptable bug, since this is the very basic functionality of the phone. I sincerely hope Jolla is working on fixing this.

nforss ( 2018-09-11 07:54:38 +0200 )edit

a jolla developer suggests this may or may not help: https://git.merproject.org/mer-core/ofono/commit/076e2f0

if i understand the dev correctly, despite this commit being authored so recently, it is apparently part of the ofono thats in the official release of nurmonjoki

teleshoes ( 2018-09-14 19:11:31 +0200 )edit

STILL BROKEN. THREE YEARS, SIX MONTHS LATER. STILL MISS CALLS EVERY SINGLE DAY.

teleshoes ( 2019-06-06 07:20:37 +0200 )edit

Answer 4

4

answered 2016-08-31 19:01:05 +0200

Pikku-Y
486 ●8 ●18 ●18

In my case the phone disconnects from data connection often. No matter if its 3g or wifi.. but more on 3g. I just notice it when phone says "connected" message while using.. like its been disconnected and connects again

edit flag offensive delete publish link

Comments

This happens to me too, but only Android apps lose WiFi, SailfishOS apps aren't affected.

rfa ( 2018-03-23 19:07:21 +0200 )edit

Answer 5

4

answered 2019-10-10 08:38:16 +0200

teleshoes
231 ●3 ●12 ●10

still happens every day.

affects X, X Compact, and XA2, all SFOS versions (community, official, and official+g7 for xc), up to 3.1.0.11 (current latest official release at time of writing).

bug is never present in android (AOSP or Sony) on the same phones, which i test every once in awhile for a few days.

bug causes missed calls/texts/voicemails, while indicating good connectivity. bug lasts more than half an hour, and using wifi or apps doesnt affect it. airplane mode on/off toggle fixes the bug, though it takes a full 30s or so to re-establish connection, at which point all missed texts suddenly show up.

bug seems to only happen when in the same spot for several hours like, say, your home or office

edit flag offensive delete publish link

Answer 6

3

answered 2018-03-12 18:06:22 +0200

Nekron
3162 ●47 ●60 ●62

updated 2019-12-27 13:15:34 +0200

Sebix
1199 ●22 ●48 ●45

I push this bug upwards because a slightly different kind of bug is present since the first release of Sailfish X until today.

I have determined that keeping WLAN and mobile data connection online while beeing routed via WLAN will stop GPRS after 24 - 48 hours if your phone is keept on the same place. The 3G text beneath signal strength icon will disappear if this bug occurs and switching from WLAN to GPRS is no longer possible. This is quite annoying if you leave home and the automatic WLAN to GPRS handover done by the OS will not work and you will end up being offline until you recognize the failure.

I am not sure if some provides will kill GPRS connection if there is no traffic send for some time, however ofono/connman should detect the GPRS disconnected state and reconnect immediately if this happens.

Sending the command line as @chris.adams suggested will print "Error org.ofono.Error.NotAttached: GPRS is not attached".

dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0/context1 org.ofono.ConnectionContext.SetProperty string:Active variant:boolean:true

I captured some ofono.log to show what happends if my provider disconnects mobile data connection after 12 - 24 hs:

2018-03-18 09:26:12.575 RIL1> OEM_HOOK_RAW  
2018-03-18 09:26:12.575 RIL1> 0000: 01 00 00 00 04 04 00 00  11 00 00 00 51 4f 45 4d    ........ ....QOEM  
2018-03-18 09:26:12.575 RIL1  0010: 48 4f 4f 4b fa 03 08 00  01 00 00 00 00 00 00 00    HOOK.... ........  
2018-03-18 09:26:12.579 RIL1> SIGNAL_STRENGTH  
2018-03-18 09:26:12.579 RIL1> 0000: 01 00 00 00 f1 03 00 00  0b 00 00 00 00 00 00 00    ........ ........  
2018-03-18 09:26:12.579 RIL1  0010: ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff    ........ ........  
2018-03-18 09:26:12.579 RIL1  0020: ff ff ff ff 63 00 00 00  ff ff ff 7f ff ff ff 7f    ....c... ........  
2018-03-18 09:26:12.579 RIL1  0030: ff ff ff 7f ff ff ff 7f  ff ff ff 7f                ........ ....  
2018-03-18 09:26:12.579 drivers/ril/ril_netreg.c: ril_netreg_get_signal_strength() gw: 11, cdma: -1, evdo: -1, lte: 99  
2018-03-18 09:26:12.579 drivers/ril/ril_netreg.c: ril_netreg_strength_notify() 35  
2018-03-18 09:26:12.580 RIL1> RESPONSE_VOICE_NETWORK_STATE_CHANGED  
2018-03-18 09:26:12.580 RIL1> 0000: 01 00 00 00 ea 03 00 00                             ........  
2018-03-18 09:26:12.580 drivers/ril/ril_network.c: ril_network_state_changed_cb()   
2018-03-18 09:26:12.580 drivers/ril/ril_network.c: ril_network_poll_state()   
2018-03-18 09:26:12.580 RIL1< [00004b3a] OPERATOR  
2018-03-18 09:26:12.584 RIL1< 0000: 16 00 00 00 3a 4b 00 00                             ....:K..  
2018-03-18 09:26:12.585 RIL1< [00004b3b] VOICE_REGISTRATION_STATE  
2018-03-18 09:26:12.585 RIL1< 0000: 14 00 00 00 3b 4b 00 00                             ....;K..  
2018-03-18 09:26:12.585 RIL1< [00004b3c] DATA_REGISTRATION_STATE  
2018-03-18 09:26:12.585 RIL1< 0000: 15 00 00 00 3c 4b 00 00                             ....<K..  
2018-03-18 09:26:12.587 RIL1> SIGNAL_STRENGTH  
2018-03-18 09:26:12.587 RIL1> 0000: 01 00 00 00 f1 03 00 00  0b 00 00 00 00 00 00 00    ........ ........  
2018-03-18 09:26:12.588 RIL1  0010: ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff    ........ ........  
2018-03-18 09:26:12.588 RIL1  0020: ff ff ff ff 63 00 00 00  ff ff ff 7f ff ff ff 7f    ....c... ........  
2018-03-18 09:26:12.588 RIL1  0030: ff ff ff 7f ff ff ff 7f  ff ff ff 7f                ........ ....  
2018-03-18 09:26:12.588 drivers/ril/ril_netreg.c: ril_netreg_get_signal_strength() gw: 11, cdma: -1, evdo: -1, lte: 99  
2018-03-18 09:26:12.588 drivers/ril/ril_netreg.c: ril_netreg_strength_notify() 35  
2018-03-18 09:26:12.594 RIL1> [00004b3a] OK  
2018-03-18 09:26:12.595 RIL1> 0000: 00 00 00 00 3a 4b 00 00  00 00 00 00 03 00 00 00    ....:K.. ........  
2018-03-18 09:26:12.595 RIL1  0010: 08 00 00 00 63 00 6f 00  6e 00 67 00 73 00 74 00    ....c.o. n.g.s.t.  
2018-03-18 09:26:12.595 RIL1  0020: 61 00 72 00 00 00 00 00  08 00 00 00 63 00 6f 00    a.r..... ....c.o.  
2018-03-18 09:26:12.595 RIL1  0030: 6e 00 67 00 73 00 74 00  61 00 72 00 00 00 00 00    n.g.s.t. a.r.....  
2018-03-18 09:26:12.595 RIL1  0040: 05 00 00 00 32 00 36 00  32 00 30 00 31 00 00 00    ....2.6. 2.0.1...  
2018-03-18 09:26:12.598 RIL1> [00004b3c] OK  
2018-03-18 09:26:12.598 RIL1> 0000: 00 00 00 00 3c 4b 00 00  00 00 00 00 0b 00 00 00    ....<K.. ........  
2018-03-18 09:26:12.598 RIL1  0010: 01 00 00 00 32 00 00 00  ff ff ff ff ff ff ff ff    ....2... ........  
2018-03-18 09:26:12.598 RIL1  0020: ff ff ff ff 01 00 00 00  30 00 00 00 02 00 00 00    ........ 0.......  
2018-03-18 09:26:12.598 RIL1  0030: 32 00 30 00 00 00 00 00  ff ff ff ff ff ff ff ff    2.0..... ........  
2018-03-18 09:26:12.598 RIL1  0040: ff ff ff ff ff ff ff ff  ff ff ff ff                ........ ....  
2018-03-18 09:26:12.598 drivers/ril/ril_network.c: ril_network_parse_response() searching,(null),(null),-1,,0,20  
2018-03-18 09:26:12.598 drivers/ril/ril_network.c: ril_network_poll_data_state_cb() data registration changed  
2018-03-18 09:26:12.599 data reg changed 1 -> 2 (searching), attached 1  
2018-03-18 09:26:12.599 src/gprs.c: ofono_gprs_status_notify() /ril_0 status 2  
2018-03-18 09:26:12.599 RIL1> [00004b3b] OK  
2018-03-18 09:26:12.600 RIL1> 0000: 00 00 00 00 3b 4b 00 00  00 00 00 00 0f 00 00 00    ....;K.. ........  
2018-03-18 09:26:12.600 RIL1  0010: 01 00 00 00 31 00 00 00  04 00 00 00 31 00 37 00    ....1... ....1.7.  
2018-03-18 09:26:12.600 RIL1  0020: 39 00 34 00 00 00 00 00  08 00 00 00 37 00 66 00    9.4..... ....7.f.  
2018-03-18 09:26:12.600 RIL1  0030: 66 00 66 00 66 00 66 00  66 00 66 00 00 00 00 00    f.f.f.f. f.f.....  
2018-03-18 09:26:12.600 RIL1  0040: 01 00 00 00 33 00 00 00  ff ff ff ff ff ff ff ff    ....3... ........  
2018-03-18 09:26:12.601 RIL1  0050: ff ff ff ff 01 00 00 00  30 00 00 00 ff ff ff ff    ........ 0.......  
2018-03-18 09:26:12.603 RIL1  0060: ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff    ........ ........  
2018-03-18 09:26:12.603 RIL1  0070: 01 00 00 00 30 00 00 00  02 00 00 00 33 00 65 00    ....0... ....3.e.  
2018-03-18 09:26:12.604 RIL1  0080: 00 00 00 00                                         ....  
2018-03-18 09:26:12.605 drivers/ril/ril_network.c: ril_network_parse_response() registered,1794,7fffffff,3,umts,  (null),(null)  
2018-03-18 09:26:12.606 drivers/ril/ril_network.c: ril_network_poll_voice_state_cb() voice registration changed  
2018-03-18 09:26:12.608 drivers/ril/ril_netreg.c: ril_netreg_status_notify() ril_0 queuing notification  
2018-03-18 09:26:12.608 drivers/ril/ril_netreg.c: ril_netreg_status_notify_cb() ril_0   
2018-03-18 09:26:12.610 src/network.c: ofono_netreg_status_notify() /ril_0 status 1 tech 2  
2018-03-18 09:26:12.610 RIL1< [00004b3d] SIGNAL_STRENGTH  
2018-03-18 09:26:12.612 RIL1< 0000: 13 00 00 00 3d 4b 00 00                             ....=K..  
2018-03-18 09:26:12.614 src/cbs.c: cbs_location_changed() 1, 6036, 2147483647, 2, 26201  
2018-03-18 09:26:12.615 src/cbs.c: cbs_location_changed() 0, 0, 1  
2018-03-18 09:26:12.617 plugins/sailfish_manager/sailfish_sim_info.c: sailfish_sim_info_network_check() ril_0 home   network "congstar"  
2018-03-18 09:26:12.618 plugins/nettime.c: nettime_set_mcc_mnc() /ril_0 MCC: 262, MNC: 01  
2018-03-18 09:26:12.619 src/gprs.c: netreg_status_changed() 1    
2018-03-18 09:26:12.620 src/gprs.c: gprs_netreg_update() attach: 1, driver_attached: 1    
2018-03-18 09:26:12.620 RIL1> [00004b3d] OK    
2018-03-18 09:26:12.622 RIL1> 0000: 00 00 00 00 3d 4b 00 00  00 00 00 00 0b 00 00 00    ....=K.. ........    
2018-03-18 09:26:12.622 RIL1  0010: 00 00 00 00 ff ff ff ff  ff ff ff ff ff ff ff ff    ........ ........     
2018-03-18 09:26:12.624 RIL1  0020: ff ff ff ff ff ff ff ff  63 00 00 00 ff ff ff 7f    ........ c.......    
2018-03-18 09:26:12.625 RIL1  0030: ff ff ff 7f ff ff ff 7f  ff ff ff 7f ff ff ff 7f    ........ ........    
2018-03-18 09:26:12.627 drivers/ril/ril_netreg.c: ril_netreg_get_signal_strength() gw: 11, cdma: -1, evdo: -1, lte: 99    
2018-03-18 09:26:12.629 drivers/ril/ril_netreg.c: ril_netreg_current_operator_cb() ril_0     
2018-03-18 09:26:12.629 src/network.c: current_operator_callback() 0x46a980, 0x46e980    
2018-03-18 10:16:01.315 mce: Display is on

edit flag offensive delete publish link

Comments

Meanwhile I did some more investigation into this issue and comparing results from an old Jolla1 vs Xperia X. Jolla1 reconnects after GPRS connection dies (disconnected by provider). However if I change my network settings from "prefer 3G" to "prefer 4G" the Xperia X will reconnect once the GPRS is disconnected. Please note that I have only 3G data plan and no LTE option enabled.

Nekron ( 2019-12-28 15:23:57 +0200 )edit

Answer 7

0

answered 2016-09-03 11:24:00 +0200

Twinklestar1792
748 ●5 ●12 ●14

I was using 2.0.2.43 and faced connection swap between Wi-Fi and Mobile Data. Then I have manually updated to 2.0.3.x and couldn't connect to mobile data. So I reverted back to 2.0.2.51 early access so need to observe connection while going away from Wi-Fi.

edit flag offensive delete publish link

[Bug] Mobile data connection dies (since 2.0.1.X)

Comments

7 Answers

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

[Bug] Mobile data connection dies (since 2.0.1.X)

Comments

7 Answers

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions