We have moved to a new Sailfish OS Forum. Please start new discussions there.

[Xperia X] Roaming does not show local operator and does not show connection

Tracked by Jolla

asked 2018-01-07 15:39:14 +0300

Raymaen gravatar image

updated 2019-09-30 14:02:46 +0300

I'm from Germany. Over x-mas i was in Norway and after new Year in Switzerland.

My Phone (Xperia X) was always switched on. The roaming option was switched to "always on" in Norway (Oslo). But I did not get any connection. There was a striped sqare on the place where the 4G-symbol normally is. Setting to flightmode and back did not help. Also deactivating and activating mobile data did not work. After a restart, the system tried to connect to a network but it failed several times. I restarted again and tried to connect to a network manually, but there was no regional provider shown. All that was shown was "T-mobilde.de" and that 3 times! So I chose the first one. It got connected somehow, but it did not work well. So restart again and auto connection to network ("T-mobile.de" in Oslo???). Then I had to play around with those settings over and over again after loosing connection the whole time i was in Norway.

In Switzerland i switched off mobile Data because the data-roaming has enormous costs there (0,49EUR for 50kB)!!! The Problem was again, that i did not see the regional providers of Switzerland and an automatic connection did not work. So again and again restart the Phone until i got connection (sms). Also the Symbols showed a 4G Connection with the two active triangles while the Dataconnection was switched off. That bug could cause a lot of costs for customers and has to be resolved as fast as possible with a patch!! I've read about something similar in another thread: (--> https://together.jolla.com/question/175003/bug-fixed-mobile-network-gets-lost-crossing-borders/). There the Guy got a fix sent via Email after contacting jolla-support... will this fix get out fast to all the xperias in the coming days? This Issue makes Sailfish X unusable in other Countries!

Update: comment by Juvirkku: The upcoming 2.1.4 release (expected in February; early access in January most likely) contains a fix for mobile data. It concerns automatic network selection, especially when crossing country borders. So there is hope this stadard functionality will work after update 2.1.4!

Update 2: it looks like nothing has been patched in and the connectivity is still in a verry bad shape. How is Jolla planing on conquer the the markets with such a messed up connectivity of the system??? Please concentrate on these bugs before you invest your limited resources into other devices! Noone wants a new device that you have to restart again and again just to be able to make a call!

Update 3: This bug is stil present in the actual update! No promises made by Jolla how and when this huge problem gets resolved so far.

Update 4: This bug is stil present in the actual update! Since the last Sailfish meeting there are some answers about the progress of investigation: "Our modem sailor said that it is an involvingly complex task with Android's RIL daemon. He has looked in numerous times, but hasn't found a magic trick to make RIL behave. (It's yet to be confirmed whether an Android BSP update to 8 would fix the issue or not, but community with enough time/roaming and a xperia x to spare could flash AOSP and confirm) we're focusing the android 8 effort on xa2 first, and will consider xperia x thereafter only"

maybe somebody who is able and has the time to revert to android and confirm the above behavior could post an answer and make it a Wiki for others to join... maybe we could help Jolla to delimit this issue this way.

Update 5: This bug is stil present in the actual update! Due to the not planned release of a higher version of android layer for Xperia X this solution seems to be abandoned, as there is absolutely no news or hints about the progress. A lot of comunity members have gathered information, but there seems to be no solution in sight.

Update 6: This bug is stil present in the actual update! The Connenctivity Parts have been slightly updated but that did not solve the issues at all! Still waiting... :-( Jolla where is your priority???

Update 7: This Bug is stil present in the actual update! This week I was in France and had the Xperia X and XA2 with me. The roaming worked on the XA2 without any issues. This time without simcard issue after passing the border (Oprator in France: Orange, at home in Germany: Drillich O2). On the X it was again without any changes simply horrible and not usable. loooong waiting for network search, then no connection. Then somhow got connected... then again no connection.

I had to use Here Maps for navigation on my XA2. With the provider bug from O2 the app it was not usable. So I had to play around with the Thetering on XA2 to create a WLAN for the X to be able to use Here Maps in France! This is insane! Why do I have to use 2 phones to get a workaround for a standard functionality? Please Jolla fix that already!!!

Any coments Jolla?

edit retag flag offensive close delete



just came.from slovenia and croatia.

in slovenia all was working as expected.

in croatia i could not.get a.data connection. then i did remember that i had the same issue on jolla1 two years back.

i did download the docs from my provider and did adapt the conn settings. in my case from web to webaut

aftet that all was working.fine

pawel ( 2018-01-07 19:38:11 +0300 )edit

this is kinda crap if we have to do that manually... Jolla should update these informations automatically on a regular basis.

Raymaen ( 2018-01-07 21:40:13 +0300 )edit

Had the same issue with not getting connected after beeing in basemant where no network was available. Sometimes setting flightmode once helped, but most times restart needed. I'm from Germany and also have T-Mobile.

SaimenSays ( 2018-01-07 23:44:34 +0300 )edit

I'm currently Czech Republic, having just bought a .cz sim card, as both the .au & .pl sim cards I have (I'm holidaying in Poland from Australia)

@pawel What I understand you're saying is endusers need to contact Jolla when they go overseas to get the network settings?

This from a European company, for software that's only available for purchase in Europe? If I was based here this would be a dealbreaker.

Does anyone know what settings I need for t-mobile.pl to work in .cz?

rfa ( 2018-01-09 20:20:45 +0300 )edit

Living in Switzerland and crossing the border to France, got the same problem. I started a new thread : https://together.jolla.com/question/177574/mobile-network-issues/

pascalm ( 2018-01-10 17:29:13 +0300 )edit

13 Answers

Sort by » oldest newest most voted

answered 2018-12-26 06:44:03 +0300

updated 2019-01-08 08:38:10 +0300

Hi community, hi jolla, sorry I'm not smart enough to find where I can get in touch with the jolla support ;-) and unfortunately I cannot create a bug report in the mer bugzilla without any account, but I will try to get an account in the next days :-). That's why I post my results here.

Since Feb 2018, I have a Xperia X and when I got it, I flashed Sailfish X on this device. I try to use the SIM card from sipgate, but it didn't connect to the network with the same issues that are described here. With a vodafone SIM card, all is fine. I fixed the issue for my sipgate SIM and it works now.

Why I post my result here in the "Roaming" issue when I using a german network provider in Germany? Because sipgate is not a reseller like ALDI/TALK or BLau etc. Sipgate is a "own" network provider like O2, Telekome or Vodafone. This means, they have a SS7 connection to the mobile network but they didn't have any transmission towers/radio cell. They use the transmission towers/radio cell from O2/EPLUS and use the roaming technology for that.

What I found: I install the ofono logger app and every "bad" connection looks like this:

2018-12-19 06:23:21.136 drivers/ril/ril_cell_info.c: ril_cell_info_radio_state_cb() ON
2018-12-19 06:23:21.136 RIL1< [00000161] GET_CELL_INFO_LIST
2018-12-19 06:23:21.137 RIL1< 0000: 6d 00 00 00 61 01 00 00                             m...a...
2018-12-19 06:23:21.167 RIL1> [00000161] GENERIC_FAILURE
2018-12-19 06:23:21.167 RIL1> 0000: 00 00 00 00 61 01 00 00  02 00 00 00                ....a... ....
2018-12-19 06:23:21.275 drivers/ril/ril_sim_card.c: ril_sim_card_update_sim_io_active() SIM I/O for slot 0 is inactive
2018-12-19 06:23:23.098 drivers/ril/ril_network.c: ril_network_check_pref_mode() rat mode 1, expected 9
2018-12-19 06:23:23.098 drivers/ril/ril_network.c: ril_network_set_rat() setting rat mode 9
2018-12-19 06:23:23.098 RIL1< [0000016c] SET_PREFERRED_NETWORK_TYPE
2018-12-19 06:23:23.098 RIL1< 0000: 49 00 00 00 6c 01 00 00  01 00 00 00 09 00 00 00    I...l... ........
2018-12-19 06:23:23.107 RIL1> [0000016c] OK
2018-12-19 06:23:23.107 RIL1> 0000: 00 00 00 00 6c 01 00 00  00 00 00 00                ....l... ....
2018-12-19 06:23:23.107 RIL1< [0000016d] GET_PREFERRED_NETWORK_TYPE
2018-12-19 06:23:23.107 RIL1< 0000: 4a 00 00 00 6d 01 00 00                             J...m...
2018-12-19 06:23:23.110 RIL1> [0000016d] OK
2018-12-19 06:23:23.110 RIL1> 0000: 00 00 00 00 6d 01 00 00  00 00 00 00 01 00 00 00    ....m... ........
2018-12-19 06:23:23.110 RIL1  0004: 09 00 00 00
2018-12-19 06:23:23.110 drivers/ril/ril_network.c: ril_network_query_pref_mode_cb() rat mode 9 (lte)
2018-12-19 06:23:23.168 RIL1< [0000016e] GET_CELL_INFO_LIST
2018-12-19 06:23:23.168 RIL1< 0000: 6d 00 00 00 6e 01 00 00                             m...n...
2018-12-19 06:23:23.171 RIL1> [0000016e] GENERIC_FAILURE
2018-12-19 06:23:23.171 RIL1> 0000: 00 00 00 00 6e 01 00 00  02 00 00 00                ....n... ....
2018-12-19 06:23:25.173 RIL1< [0000016f] GET_CELL_INFO_LIST
2018-12-19 06:23:25.173 RIL1< 0000: 6d 00 00 00 6f 01 00 00                             m...o...
2018-12-19 06:23:25.180 RIL1> [0000016f] GENERIC_FAILURE
2018-12-19 06:23:25.180 RIL1> 0000: 00 00 00 00 6f 01 00 00  02 00 00 00                ....o... ....
2018-12-19 06:23:27.183 RIL1< [00000170] GET_CELL_INFO_LIST
2018-12-19 06:23:27.183 RIL1< 0000: 6d 00 00 00 70 01 00 00                             m...p...
2018-12-19 06:23:27.200 RIL1> [00000170] GENERIC_FAILURE
2018-12-19 06:23:27.200 RIL1> 0000: 00 00 00 00 70 01 00 00  02 00 00 00                ....p... ....
2018-12-19 06:23:29.203 RIL1< [00000171] GET_CELL_INFO_LIST
2018-12-19 06:23:29.203 RIL1< 0000: 6d 00 00 00 71 01 00 00                             m...q...
2018-12-19 06:23:29.210 RIL1> [00000171] GENERIC_FAILURE
2018-12-19 06:23:29.210 RIL1> 0000: 00 00 00 00 71 01 00 00  02 00 00 00                ....q... ....
2018-12-19 06:23:31.212 RIL1< [00000172] GET_CELL_INFO_LIST
2018-12-19 06:23:31.212 RIL1< 0000: 6d 00 00 00 72 01 00 00                             m...r...
2018-12-19 06:23:31.216 RIL1> [00000172] GENERIC_FAILURE
2018-12-19 06:23:31.216 RIL1> 0000: 00 00 00 00 72 01 00 00  02 00 00 00                ....r... ....
2018-12-19 06:23:31.216 drivers/ril/ril_cell_info.c: ril_cell_info_list_cb()

after that, it looks like my modem is "confused"/undefined behavior. It is searching for any network but didn't get any network. I found this combination of GET_CELL_INFO_LIST -> GENERIC_FAILURE also in the ofono logs from the Mobile network issues post

It was possible to register one time with my sipgate SIM and the result looks exactly like with vodafone SIM:

2018-12-19 07:09:06.851 drivers/ril/ril_cell_info.c: ril_cell_info_radio_state_cb() ON
2018-12-19 07:09:06.851 RIL1< [00000160] GET_CELL_INFO_LIST
2018-12-19 07:09:06.852 RIL1< 0000: 6d 00 00 00 60 01 00 00
2018-12-19 07:09:06.892 RIL1> [00000160] GENERIC_FAILURE
2018-12-19 07:09:06.896 RIL1> 0000: 00 00 00 00 60 01 00 00  02 00 00 00
2018-12-19 07:09:07.005 drivers/ril/ril_sim_card.c: ril_sim_card_update_sim_io_active() SIM I/O for slot 0 is inactive
2018-12-19 07:09:08.900 RIL1< [0000016b] GET_CELL_INFO_LIST
2018-12-19 07:09:08.902 RIL1< 0000: 6d 00 00 00 6b 01 00 00                             m...k...
2018-12-19 07:09:08.904 RIL1> [0000016b] GENERIC_FAILURE
2018-12-19 07:09:08.905 RIL1> 0000: 00 00 00 00 6b 01 00 00  02 00 00 00                ....k... ....
2018-12-19 07:09:09.093 drivers/ril/ril_network.c: ril_network_check_pref_mode() rat mode 1, expected 9
2018-12-19 07:09:09.093 drivers/ril/ril_network.c: ril_network_set_rat() setting rat mode 9
2018-12-19 07:09:09.094 RIL1< [0000016c] SET_PREFERRED_NETWORK_TYPE
2018-12-19 07:09:09.094 RIL1< 0000: 49 00 00 00 6c 01 00 00  01 00 00 00 09 00 00 00    I...l... ........
2018-12-19 07:09:09.104 RIL1> [0000016c] OK
2018-12-19 07:09:09.105 RIL1> 0000: 00 00 00 00 6c 01 00 00  00 00 00 00                ....l... ....
2018-12-19 07:09:09.105 RIL1< [0000016d] GET_PREFERRED_NETWORK_TYPE
2018-12-19 07:09:09.105 RIL1< 0000: 4a 00 00 00 6d 01 00 00                             J...m...
2018-12-19 07:09:09.113 RIL1> [0000016d] OK
2018-12-19 07:09:09.113 RIL1> 0000: 00 00 00 00 6d 01 00 00  00 00 00 00 01 00 00 00    ....m... ........
2018-12-19 07:09:09.113 RIL1  0004: 09 00 00 00                                         ....
2018-12-19 07:09:09.113 drivers/ril/ril_network.c: ril_network_query_pref_mode_cb() rat mode 9 (lte)
2018-12-19 07:09:09.488 RIL1> 0000: 01 00 00 00 ea 03 00 00                             ........
2018-12-19 07:09:09.488 drivers/ril/ril_network.c: ril_network_state_changed_cb() 
2018-12-19 07:09:09.488 drivers/ril/ril_network.c: ril_network_poll_state() 
2018-12-19 07:09:09.488 RIL1< [0000016e] OPERATOR
2018-12-19 07:09:09.488 RIL1< 0000: 16 00 00 00 6e 01 00 00                             ....n...
2018-12-19 07:09:09.488 drivers/ril/ril_network.c: ril_network_query_registration_state()

I looked into the source code of ofono and I did following change:

diff --git a/ofono/drivers/ril/ril_cell_info.c b/ofono/drivers/ril/ril_cell_info.c
index 2d012534..b28849b8 100644
--- a/ofono/drivers/ril/ril_cell_info.c
+++ b/ofono/drivers/ril/ril_cell_info.c
@@ -401,7 +401,9 @@ static void ril_cell_info_radio_state_cb(struct ril_radio *radio, void *arg)
        struct ril_cell_info *self = RIL_CELL_INFO(arg);

        DBG_(self, "%s", ril_radio_state_to_string(radio->state));
-       ril_cell_info_refresh(self);
+    if (self->radio->state != RADIO_STATE_ON) {
+        ril_cell_info_update_cells(self, NULL);                                                                                                                          
+    }                                                                                                                                                                    

 static void ril_cell_info_sim_status_cb(struct ril_sim_card *sim, void *arg)

With this change/patch it works and I can use now my sipgate SIM in Xperia X with Sailfish X :-)

So I did a quick look into the android source code, how is android doing the "GET_CELL_INFO_LIST" request, because it works on android. I found following in src/java/com/android/internal/telephony/LocaleTracker.java function updateTrackingStatus() line 356:

   mSimState == TelephonyManager.SIM_STATE_ABSENT

Also I found a comment in src/java/com/android/internal/telephony/LocaleTracker.java function onSimCardStateChanged() line 243:

   Called when SIM card state changed. Only when we absolutely know the SIM is absent, we get cell info from the network. Other SIM states like NOT_READY might be just a transitioning state.

If I look into ofono code in ofono/drivers/ril/ril_cell_info.c function ril_cell_info_refresh() line 391: I fonud this comment here

   /* RIL_REQUEST_GET_CELL_INFO_LIST fails without SIM card */
   if ( ...... && self->sim_card_ready) {

Hm, looks different ... unfortunately I didn't find any hints in the specs of the 3gpp.org about the cell info request.

Btw. on the Jolla 1 phone, they didn't execute any GET_CELL_INFO_LIST request.

I'm not sure yet if my change will help also the roaming issue after crossing the border, but I will try to test this, hopefully in the next month. Maybe somebody else/Jolla can verify in the log if you see the same GET_CELL_INFO_LIST request failures and test if my change/patch will fix this.

At least my patch / change will be necessary for sipgate.

But my patch is more or less a hack. After I looked into the source code of android, I think the better fix is to test if the SIM card is absent. I try to implement these in ofono, but the self->sim_card_ready state is not reflecting SIM CARD ABSENT state. I will take more time for the fix when it is clear that SIM CARD ABSENT state is the correct solution.


I digging more and more into the android RIL/Telephony stuff....

  • I found that this LocaleTracker.java is used in Android 9.0.0 and not in Android 7 or 8. So it doesn't matter.

  • I debugging the RIL communictation on a Samsung S7 with Android 7 and I see that they call getCellLocation() on TelephonyManager from the system_server or com.google.android.gms.persistent process. So I think my fix is fine and correct. I will create in the next days a pull request/bug report.

Unfortunately it does not fully fix the roaming issue. I taked a sim card from my college from the netherland and after reboot my XPeria X with Sailfish wasn't connected into mobile network. But after I enable and disable the Flight mode it was connected.

What will I do next?

  • Create pull request for sipgate sim.

  • Create bug report into mer project on ofono.

  • Try to get in contact with Jolla support/developer.

  • Diggin more into the Android/RIL stuff.

  • Analyze debug RIL log files from Android. (try to find another Sony XPeria X with Android)

  • Trace SIM card communication with my Simtrace from osmocom.org

  • Try some changes/fixes on ofono with the SIM card from my college

So stay tuned for updates. It may be take a while because I can do this only in my spare time. But I want to fix that issue (!) because I love my Jolla phone :-) and it is the only one that I have (no Android or iPhone) ;-).

Second Update:

I saw there is a roaming_issues commit in the ofono repo.

I currently test this and for my sipgate SIM, it is really an improvement! I can say, it works with/fixed my sipgate SIM. Create! Thanks.

For the roaming issue, hm ... unfortunately for me the first tests have not been reliable but maybe I did something wrong. Let me test more ....

I should change my priorit:

  • Frist, get in contact with jolla

  • More tests with the "fix"


edit flag offensive delete publish link more



Very brave! You are my personal 2019 hero if you get the roaming issues fixed :)

Nekron ( 2019-01-04 21:39:36 +0300 )edit

Great effort Bjoerg! :-)

ebjordal ( 2019-01-08 09:26:09 +0300 )edit

answered 2018-03-10 23:09:31 +0300

the issue is still there with 2.1.4!

no improvement at all

edit flag offensive delete publish link more



Unfortunately I must confirm that the problem is not fixed - at least in my case. After reading changelog I kind of expected that, but yesterday was in France and could not get my Xperia to connect to any network (phone function was not working, not only data). In the meantime I bought another phone (Android) and after swapping the SIM cards I had no problem to connect. So obviously there is something wrong with Sailfish setting on Xperia. My provider is blau (Germany).

Marius ( 2018-03-12 10:26:08 +0300 )edit

answered 2018-03-11 00:01:07 +0300

SaimenSays gravatar image

I've reported this issue to Jolla support while recognizing the bug is still existing in 2.1.4 EarlyAccess. They told me to send them logs, what I did. But after that, they told me that there will be no fix in 2.1.4 release.

They adviced me to try Reverting to Android and reinstalling Sailfish, but can't guarantee that this would fix the issue 100%. So I've not done this up to now and still doing multiple reboots a day when traveling around :(

edit flag offensive delete publish link more



another good reason to NOT buy into SailfishX. More broken software, what a joke, one that isn't funny.

Spam Hunter ( 2018-03-11 10:17:38 +0300 )edit

THIS is ridiculous

emschi ( 2018-03-11 19:53:31 +0300 )edit

Can someone explain the reason behind this? I have the same issue and also was advised by Jolla Zendesk to revert to Android & reinstall SF. I at least want to learn something if I sacrifice an afternoon trying to fix my phone...

Spark ( 2018-04-17 10:35:34 +0300 )edit

I'm having the same issue as well. Not really satisfied whith the solution to reinstall everything though... :(

SKD ( 2018-04-25 08:48:55 +0300 )edit

Do you maybe have a F5122 and installed SFOS before the official support for that phone model rolled out? Because at some point Jolla advised reflashing to the first officially released version (which possibly contained more than the original hacks that were circulated online to make the dual-SIM work). That would explain why reflashing is useful in this case.

Federico ( 2018-09-10 22:48:46 +0300 )edit

answered 2019-02-24 13:10:31 +0300

ebjordal gravatar image

Hello Jolla, Still no news or update on this? This weekend I was travelling from Norway to Sweden. I had no cellular connection the entire weekend. To be able to use the phone as a phone is an absolute and minimal requirement. The earliest bug report on this is about 1 year old, as far as I see? I am sorry Jolla.. I have been with you since N900 in the Nokia days. I have also accepted that development have been slower than I would like to. Though, I need to have a phone that works outside my livingroom. Hope you get things sorted eventually.

edit flag offensive delete publish link more



Critical phone issues which require a fix should be adressed to Jolla Zendesk.

Spark ( 2019-02-24 16:47:40 +0300 )edit

and then nothing happens... in this issue case...

Raymaen ( 2019-02-24 21:14:31 +0300 )edit

answered 2018-10-31 14:12:09 +0300

kultsinuppeli gravatar image

I've been traveling a bit around Europe lately, and I had an atrocious roaming experience.

Setup: SailfishX, new Finnish DNA SIM card, recently reflashed to Android to get rid of the data connection problem, Nurmijoki ( release of Sailfish.

The countries I visited were split into two categories. A) no connection at tall B) problematic.

For the no connection at all countries, I just coldn't connect to the mobile network. It just would not. No calls, no SMS, do data. The SIM card worked on an Android phone. Things I tested.

  • Restart device
  • Manual selection of network (tried all of the available ones)
  • Turn off data
  • Selecting, Prefer 4g, Prefer 3g, 2g only
  • Having phone closed for a while, and trying again.
  • Reinserting SIM

None of these worked. So for all intents and purposes I had no phone in these countries:

  • Italy
  • Montenegro
  • Croatia
  • Monaco

For the other category, the problematic countries, it usually took a long time to connect to the network. After it did, I got the same "SIM card removed. You need to restart the device to activate the inserted SIM card" message others have gotten.

Sometimes the connection dropped and I got the message again. Sometimes the connection just dropped, and I had to Flight mode on/off again to get a connection to the cellular network (not only data, everything went). After a while it seemed to get better and work more consistently in the country.

Countries with problems:

  • France
  • Germany
  • Netherlands
  • Malta
edit flag offensive delete publish link more



The issue "SIM Card removed" is already tracked by Jolla and discussed here:


I assume (resp. expect) that the issue will be solved in SFOS 3.

vision ( 2018-10-31 15:13:45 +0300 )edit

The repeated occurence of "sim-card removed" in foreign networks in my opinion originates from a change to a different network (which may happen automatically due to bad coverage). I could observe that for my phone too. In that respect it doesn't matter if you cross a border into a roaming network or switch between two roaming networks. In your home country that just may not happen as you never change networks there.

Spark ( 2018-10-31 16:12:20 +0300 )edit

@Spark : actually the "sim-card removed" issue may happen in home country, making owning this phone a terribly bad daily experience. See answer by BJoerg, See also my answer in the "sim-card removed" question.

In total these two questions have been voted 74 times. There has been a lot of input from affected users, and still not even a courteous statement from Jolla explaining what they are doing about it. They are totally irresponsive.

slowcyclist ( 2019-01-24 14:57:24 +0300 )edit

@slowcyclist could it be a national roaming issue in this case?

Spark ( 2019-01-24 15:15:58 +0300 )edit

answered 2019-05-15 11:37:12 +0300

ebjordal gravatar image

Is this still an issue with the latest release 3.0.3?

(Sorry, was so many notes on this that I got confused reading through it all)

edit flag offensive delete publish link more



Yes, sadly it still is (tested 2 days ago). I managed to get a stable connection when selecting "Prefer 3G" instead of 4G. This also stops the constant "Removed SIM-Card" pop-up - which otherwise shows up sometimes even when you manually chose a roaming network.

So it seems the issue is still there.

molan ( 2019-05-15 17:51:35 +0300 )edit

Thanks for the reply molan. I was hoping this was fixed now.

(There is several thing with the android Im now using that I really dislike compared to sailfish, though I see it is also easy to get used to a phone where everything works..) :-)

Anyway, the connectivity issues need to be resolved for me to use SF again..

ebjordal ( 2019-05-16 10:47:12 +0300 )edit

@ebjordal: Same here. I also had to use Android for a couple months last year and I didn't like it at all compared to Sailfish. But maybe I have to go back again this year since the connectivity issues are very annoying. Some people got rid of the connectivity/roaming issues by re-flashing Android and then again Sailfish. Unfortunately this didn't solve it for everyone. The problem is related to this one and occurs when the phone tries to switch roaming networks (it can also happen when the network is manually chosen): https://together.jolla.com/question/182073/sim-card-removed-issue-with-sailfishx/

molan ( 2019-05-16 14:08:00 +0300 )edit

same here. Really needs to fixed.

sfb ( 2019-05-16 18:06:04 +0300 )edit

answered 2018-05-31 17:47:43 +0300

arno784 gravatar image

I had the problem with 2.1.3 (Xperia X) and was in touch with jolla. I sent some logs and they tried to help, sending me a patch. After the update to 2.1.4 and still seeing the problem, I contact them again (they asked for feedback) but since then it's complete silence. I'm travelling this weekend again, so I will very likely have a spare device with me. I'm not a tehcnical person, but this is really frustrating! It does not seem that anything in 2.2.0 is related to that.

edit flag offensive delete publish link more



It would be great if you can test it this weekend with 2.2.0 - let's hope for the best. There are some changes in ofono mentioned: https://together.jolla.com/question/184470/changelog-220-mouhijoki/#184470-ofono

molan ( 2018-05-31 19:07:51 +0300 )edit

i experienced the problem also. a couple of days it was workibg in the foreign country and then it stopped. after it stopped O could never get it up running the mobile data. phone and sms needs multiple reboots. I'll see what will happen when back home

carepack ( 2018-06-01 00:00:34 +0300 )edit

@molan, yes, true... I might try that, but I don't really like the early access... there are enough bugs already, I don't want additional ones trying to fix the existing ones... let's see if I have time to update and try

arno784 ( 2018-06-01 11:08:30 +0300 )edit

@carepack: Thanks for your report. That's exactly what's happening and makes it almost impossible to use the phone abroad. @arno784: I totally understand. I hope I can make a short trip abroad myself soon to test the phone with Sailfish 2.2.

molan ( 2018-06-01 23:59:39 +0300 )edit

i'm on 2.2 and have this issue. to make it more complicated, my roaming was stopped through my provider but they removed the barrier. but still don't get data to.work. before the roaming was disabled data worked sometimes and sometimes not. had always to play around with selecting carries manually. but never got it working again after the barrier

carepack ( 2018-06-02 00:04:33 +0300 )edit

answered 2018-07-03 12:49:54 +0300

molan gravatar image

I'm not opening a new thread since it seems to be the same or related problem mentioned above. I've experienced the loss of connection abroad reported in this thread in 4 out of 5 countries and recently tried it again with the latest update. The issue unfortunately still occurs - but now, as soon as the mobile connection is lost, Sailfish displayed the message: SIM card removed. You need to restart the device to activate the inserted SIM card

This message reappears within seconds after pressing ok, until the device is rebooted (and it appears again as soon as network connection is lost again). At the same time ofono seemed to 'go crazy' (looking at ofono logs). I've sent the logs to address given in ofono logger. There is no problem with the SIM card or SIM card tray. Back on the local network the message didn't reappear anymore and there are also no issues using Android on the same Xperia X (which I had to reinstall in order to use the device abroad).

image description

edit flag offensive delete publish link more



Thank you for reporting this. I have exactly the same Issue on the Xperia X since the last update. And I had the same issue you reported first before the last update. Every time when i change the Roaming-Provider this is the behavior until i restart the phone. It occurs as well when changing a land side border (e.g. Germany-Austria/Germany-Swiss and back) as when e.g. leaving flight mode after landing in an other country (e.g. Germany/Spain)

fridl ( 2018-07-03 14:36:34 +0300 )edit

I also have this. Fortunately after that restart everything works in the roaming network the phone was trying to login. It's a bit annoying, but for people travelling occasionally this is a minor issue I guess

Spark ( 2018-07-04 12:58:37 +0300 )edit

answered 2018-10-10 12:14:57 +0300

ebjordal gravatar image

Any news on this?

I live in Norway and went to Ireland this weekend. I was not able to connect to any network (except wifi). I tried both to connect automatically and manually, though I just got connection error. I also had the same issue during the summer when I went to Croatia. At that point of time I was able to connect to the network by manually selecting "only 2g", though this did not work with version in Ireland this weekend.

edit flag offensive delete publish link more


Same thing happended to me in Scottland (Norwegian too), roaming between Telia and Telenor do not work either here in Norway. Make shure to say inside your operators coverage!

fishandchips ( 2018-10-10 13:58:24 +0300 )edit

Only what i have added as "Update 4"

Raymaen ( 2018-10-10 16:08:47 +0300 )edit

But there has not been any official statements on this, has it? It seems like a quite critical flaw in a phone so it would be nice to know if we could except a solution in for example sailfish 3 or so?

ebjordal ( 2018-10-10 16:16:06 +0300 )edit

Well that depends how we understand it. I see it as half official... It was an answer from a meeting with jolla staff. But i think such an official statement would be suicide for a company. "maybe, when we have time for it, maybe not, who knows..." pretty poor if you ask me. There are a lot of customers with this problem who have payed money for the os.... So basic functionality should be provided. II'm not talking about extra features... Its a phone, we all should be able to call somebody with it... Even from an other country.

Raymaen ( 2018-10-10 16:27:14 +0300 )edit

answered 2019-05-05 17:46:20 +0300

yiannako gravatar image

i guess i will have to use my iphone when i go to italy. what a shame because my xperia takes better pictures.

edit flag offensive delete publish link more



I've recently been to Italy and switched to "Prefer 3G" in network mode. Afterwards I didn't have any issues, even with "Select network automatically" enabled. But I still had to reboot the device when crossing country borders. Idk how reliable this solution is - but it's better than a device without any connection. I might have to switch back (again) to Android when I'm going abroad for several days.

molan ( 2019-05-14 18:00:35 +0300 )edit

After testing it a couple more days, "Prefer 3G" lowers the amount of broken connections, but it still happens.

molan ( 2019-06-24 13:27:29 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2018-01-07 15:39:14 +0300

Seen: 3,990 times

Last updated: Sep 30 '19