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

Tracked by Jolla

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 2.1.4.14 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 2.2.0.29! 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 2.2.1.18! 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.

edit retag 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

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

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

( 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.

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

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?

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

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/

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

Sort by » oldest newest most voted

the issue is still there with 2.1.4!

no improvement at all

more

1

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).

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

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 :(

more

3

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

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

THIS is ridiculous

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

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...

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

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

( 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.

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

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.

more

2

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

( 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

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

@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

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

@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.

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

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

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

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 2.2.0.29 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).

more

1

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)

( 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

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

I reported this in other threads already: Seemingly you won't get around a revert to Android and a reinstall of Sailfish. For me it solved everything (except for the "Sim card removed" issue @molan reported above). Just take the 2 hours and you will have peace after it. I know it is not a smooth solution or what you want to hear, but a functioning phone was worth it to me. By the way this also solved issues of failed reconnecting after network loss in my national network.

more

It would be great to have an official statement by Jolla about this major issue, as this question ist already tracked by Jolla. Somehow I get tired of hoping and waiting, playing and repairing around in the software and hardware of the XperiaX (Had a broken rear camera Module). This is a Major Issue and affects nearly every user in every country. there has to be a solution without reflashing back to android (what version anyway..? and how?) and again back to sailfish (backup of everything installed is also work...). Driverupdates or other stuff that causes these issues should be deliverable through an update.

( 2018-07-04 18:39:07 +0300 )edit

@Raymaen

I am not an expert in these things, just a regular user. This issue however is not affecting "nearly every user in every country" as you wrote which you can even deduct from the relatively low number of complaints here. It seems to have to do with the implementation of Sailfish OS into the underlying system layer, whatever that is exactly. Maybe others can help out there. In some cases (rare or not so rare might be arguable) something with the network module software goes wrong during SF installation causing connectivity issues. Jolla itself stated, the fundamental reason is not known (source: mail conversation with the support). It is not simply solved by a driver update, otherwise they had done so.

What you have to do is revert to Android and actually use Android for calls and data connection for some minutes. After that install Sailfish again. The link describing the whole procedure was given in a posting above. Yes, it is unfortunate, I have been through the whole process and also trying to find a workaround before. And yes it is a major issue. But the only solution as of now is the reinstall.

( 2018-07-04 19:43:56 +0300 )edit

Well, I must disagree with you. This roaming issue is present since the very beginning of Jolla. See question: https://together.jolla.com/question/48265/no-roaming/ or: https://together.jolla.com/question/34219/cant-get-data-connection-while-roaming/ and more (just search for "roaming" or: https://together.jolla.com/question/175003/bug-fixed-mobile-network-gets-lost-crossing-borders/ @leonneberga got a fix from the Jolla helpdesk. So there is a software solution for this problem! many people from different countries have reported this problem in the comentsection of a lot of those questions. Maybe most people dont go abroad but if they do, they dont report... I'm not willing to invest more time in a Maybe-Solution. Jolla schould react officially!

( 2018-07-05 10:20:55 +0300 )edit

I know those topics. I think two assumptions you made are not valid: First, a handful of reports for sure show an issue, but not neccessarily a general issue everyone has. There's enough Jollas and Xperias which work just fine in roaming. Just like the ones with a reinstall which now also work (with the same software). Complaints in support/community boards tend to distort the proportions of a problem, as happy people usually don't complain.

Second, Loenneberga got a fix after he sent the ofono logs to support. My logs however were unsuspicious and still I had no roaming connection. Could be issues with different origins but same symptoms.

I repeat myself: Get a reinstall and this topic will stop spinning in your head. In the end it will be faster than roaming (sorry) TJC for hours.

( 2018-07-05 11:11:05 +0300 )edit

I have the same issue still with latest update of Nurmonjoki 2.2.1.18. I have SIM card T-Mobile.CZ from Czech Republic. Now I am in Germany and the phone cannot get connected to any mobile network. I tried several things like restarted the phone, flight mode on/off, followed the steps described in Jolla Zendesk with Ofono Logger, done the 'rm -rf /var/lib/ofono/*' in developer mode, but the problem is still same. Only wifi works, otherwise the phone is unusable.

The same issue I had in Greece this summer. No signal of local operator at all.

I think this is a big bug, which needs to be solved. I have now sent to Jolla the report from Ofono Logger, hope it helps. Thank you.

more