Ask / Submit
10

[BUG] did the roaming bug return?

asked 2019-02-05 00:19:03 +0300

updated 2019-03-18 14:14:25 +0300

After visiting #FOSDEM I noticed strange behaviour wrt roaming on my Jolla 1 (SF version 3.0.1.11). It is identical to the one described here:

https://together.jolla.com/question/175003/bug-fixed-mobile-network-gets-lost-crossing-borders/

When enabling mobile data and allow roaming the notification continuously switches between "connect/enable" (but doe not actually work). When not allowing roaming the connect indicator is permanently "on" but no data is received (after all roaming is off). When consulting the "radio switch" app it correctly display roaming state and radio state (i.e. 2G,3G,4G). But of course there is no actual data connection.

Just like https://together.jolla.com/users/12099/loenneberga/ full functionality return once I reenter my home network.


added march 18th 2019:

Recently the exact same happened on a trip to Antwerp. I had another phone with me so I did not notice it until late. It seems this bug also depletes the battery. So when I finally returned to The Netherlands on my home network all returned to normal but my battery was almost dead eventhough I had not used it.

To me this is a pretty serious problem. Make a phone not useable when travelling internationally :(

edit retag flag offensive close delete

3 Answers

Sort by » oldest newest most voted
11

answered 2019-02-09 00:04:34 +0300

slowcyclist gravatar image

Well, for the roaming bug to return it should first have been fixed. AFAICT this is not the case : If you read all comments down to the end in the question you refer to, it does not seem fixed (even though the question is marked "[bug fixed]" in the title!).

There are several other severe roaming bugs reported here at TJC (at least here and here) which have seen no sign of progress on Jolla's side for a year. Not even a polite word.

The news for me is that roaming issues also affects the J1. I though it was only the Xperias.

I cannot believe how Jolla handles this. I have no idea of the fraction of sailfish users affected by such roaming bugs, but even if it were 1%, that makes Sailfish a terrible experience: Basic functionality taken for granted with a mobile phone is not there. I would never recommend sailfish. Having the best user interface does not make up, sorry folks. If Jolla does not have the ressources to address this, why not taking advantage of those who propose to help? At the very least communicate and be transparent with users about these issues... Open your bug tracker! Being "together" and forming a "vibrant community", what a joke!

I'm no longer waiting/hoping Jolla will fix this. I'll probably end up reflashing my Xperia X with LineageOS, but before that I'll give a try to Halium/UBtouch which appears to be runing on this phone (and with a linux kernel 4.4!).

edit flag offensive delete publish link more

Comments

1

I agree, I also think it was never really fixed. I encountered it first in 2014 and it came back during my holidays like a good friend, in irregular intervals, though.

ossi1967 ( 2019-03-27 14:17:13 +0300 )edit

Unfortunately the roaming problem is even bigger for me due to the fact that some Danish mobile network providers has started doing ”domestic roaming” meaning they cooperate so that I as a customer of ”3” should be transferred to the network of TDC in areas where ”3” does not provide 4G through their own network.

Sailfish can’t work properly under these conditions. My Xperia X can connect to 3’s network but cannot utilizing the 4G provided by the domestic roaming so it remains on 3G.

But my Xperia XA2 can’t make a connection at all in areas where this domestic roaming is active, it constantly switches between ”connect/enable”. As soon as I’m in an area where 3 has it’s own 4G network it works OK. Unfortunately I live exactly in an area where domestic roaming is active, so my XA2 is still lying idle :-((

My XA2 worked flawlessly with this roaming situation on Android before flashing Sailfish on it.

I communicated with Zendesk about the issue some time ago but as we can see the roaming problem persists in 3.0.2.8

DK-Sailor ( 2019-03-27 15:29:34 +0300 )edit

This was the main reason for me to leave sailfish. After three travels abroad and having reported after each trip that my xperiaX were useless after crossing borders I simply reinstalled android. Solving basic functionality should be the highest priority.

There are many things I dislike with now using an android phone, though every thing is working now. Even bluetooth low energy that have been requested for half a decade.

ebjordal ( 2019-03-28 14:15:58 +0300 )edit
0

answered 2019-02-10 05:11:16 +0300

polarphone gravatar image

updated 2019-02-10 05:12:21 +0300

Brussels is by some reason tricky with mobiles. It always takes a long time to get connected. One often get kicked out of the network and it takes a long time to get reconnected. This happens also with other os than sfos which I experience since I travel with another also (work related). Could be due to overoad in capacity of network? Sailfish X bug usually looses names of networks.....

edit flag offensive delete publish link more

Comments

Recently I travelled to Antwerp and had the same issue :(

JayBeRayBearGun ( 2019-03-18 14:10:55 +0300 )edit
0

answered 2019-03-27 13:35:40 +0300

Kobold gravatar image

Yes, it did, all was fine crossing the border until the point I activated WIFI which immediately triggered the bug. Looks as if there is an issue with networkmanager.

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

Question tools

Follow
2 followers

Stats

Asked: 2019-02-05 00:19:03 +0300

Seen: 561 times

Last updated: Mar 27