Ask / Submit
53

SIM card removed issue with SailfishX

Tracked by Jolla

asked 2018-03-26 23:44:47 +0300

richie gravatar image

updated 2019-06-24 13:25:26 +0300

molan gravatar image

Hi

Since upgrading to 2.1.4.14, it maybe a coincidence, but I keep on getting this message on Sony X, official SailfishX

SIM card removed

You need to restart the device to activate the inserted SIM OK

Yet I have not taken the SIM card out. I have a cover on the X, so to fix it I reboot. Considering I do not touch the SIM at all and a reboot gets the SIM recognised again, I'm wondering if it is a bug, as I have only noticed it since upgrading. It doesn't happen that frequently, 3 occasions since updating.

Is anyone else seeing this as an issue?

Update: Bug still present in SFOS release 3.0.3.10

edit retag flag offensive close delete

Comments

2

Hi

I have remarked that behaviour. At first I thought of a bad contact and cleaned up my SIM contacts but I am now sure there is a bug or similar making the system believe the SIM was removed.

I eventually use a F5122.

Regards

ddelamarre ( 2018-03-28 15:19:02 +0300 )edit
1

The frequency of this happening has increased for me, so I too have removed the SIM card and cleaned it. I'll see how it goes.

richie ( 2018-03-31 12:00:42 +0300 )edit
1

Hi Same for me. The frequency is, however, not regular at all.

I realize the phenomenon is exacerbated by an intensive WIFI or IO like updating maps for OSMscoutServer. Also it occurs only from 2.1.4.14 upgrade, it occurs irrespective of my phone moving, or staying stable on a table i.e. exposed or not to vibrations. Therefore definitely not a hardware issue.

Regards

ddelamarre ( 2018-04-13 14:33:35 +0300 )edit

Hi

I had an answer from Jolla support saying this is probably due to the fact I use a F5122 i.e. dual SIM that is not formally supported in 2.1.4 worked with 2.1.3 by chance. Release 2.2.0 will support F5122 and is due in May.

I hope that helps being patient and avoid smashing the phone against a wall like I feel sometimes like an itching when it tells me the SIM was removed too often ...

Regards

ddelamarre ( 2018-04-18 22:59:13 +0300 )edit
1

Hi

just for information, I did the community recommended changes for dual SIM like in https://talk.maemo.org/showpost.php?p=1534540&postcount=1061 and few other places.

I have not got any new incident. However, I cannot swear this is the reason and a solution ...

Regards

ddelamarre ( 2018-05-01 00:11:54 +0300 )edit

12 Answers

Sort by » oldest newest most voted
12

answered 2019-01-23 23:41:40 +0300

slowcyclist gravatar image

I want to add that this does not require crossing borders or being in remote areas as other answers/comments report. It happens to me while staying whithin 3km of my home, 30 km away from Paris. Not really a region with poor cellular coverage! Sometimes the bugs occurs 4 times in a single day. And then it may not occur for 10 days in a row...

For those who are not affected by that issue let me also clarify that when the bug strikes, you have no way to know until you actually check your phone. You may have been offline for 5 minutes or 5 hours... Good luck explaining to your spouse/partner/boss that you were unreachable because of a bug in your phone's OS... Major usability issue!

Since I'm so frequently affected, I have offered to help debugging. I have spontaneously emailed ofono logs; I've tried to get attention in zendesk; I have received no answer whatsoever...

According to the original post it seems to be a regression introduced with Sailfish 2.1.4... That should not be so hard to check what was changed in the telephony stack (likely ofono). It has been 10 month since this has been reported and still not even an official statement about what Jolla has found, what needs to be done regarding fixing this bug...

At the top this issue is marked "Tracked by Jolla". Seriously? Come on Jolla! All we can see is the just the opposite. In the end I find this false statement really offensive. By the way, why not using a proper bug tracker facing the open world like everyone in FOSS? Something to hide, maybe? Like doing absolutely nothing on this issue?

In the end, sick and tired of this situation, I came up with a workaround for myself: I have a script watching for the SIM "getting lost" and when that occurs, it reboots the phone ("sudo reboot" -- Rebooting only the SIM card reader would be clearly better, but it is not documented how that can be done). That requires using my auto pin enter script to get back online automatically. That works, and the phone is offline only the time it takes to reboot... However, it is not a solution, it's a hack: It needs developper mode (for sudo), editing text files, setting up systemd services...

In conclusion my Xperia X F5122 running Sailfish OS is not intrinsically dependable for being reached. I think I have been very patient, quite supportive of Jolla and Sailfish (I own a Jolla 1 and I bought an an Xperia X license), but I am frustrated not seeing any solid and useful interaction with Jolla and not trusting Jolla is going to do what its users need and expect. I'm seriously considering moving to something else, trully and fully open.

edit flag offensive delete publish link more
7

answered 2018-09-16 18:00:52 +0300

vision gravatar image

Confirming the issue as well for both F5121 and F5122. Since the issue is known now for almost 6 months I am wondering whether Jolla has it on his list of bugs to be fixed ASAP!? If not... please do so ;).

My experience this week:

Travelling from Germany to Austria:

SIM card removed. You need to restart the device to activate the inserted SIM OK

One hour later… travelling from Austria to Slovakia:

SIM card removed . You need to restart the device to activate the inserted SIM OK

Expecting the same annoying behaviour this evening when travelling back. Since I have persuaded my wife to use SFOSX instead of Android I now have the discussion about the reliability of SailfishX on the Xperia X ;).

@Jolla: It's your turn now ;)

edit flag offensive delete publish link more

Comments

2

when traveling in boarder areas, Germany, Austria, Switzerland the F5122 2.2.1.18 is not usable, cause either sim1 or sim2 is "removed". The message even pops up every some some seconds, to the device is unusable! Workaround: flight mode or disable both sims. Thats not what i did expect...

jollaticktack ( 2018-11-11 10:52:04 +0300 )edit
6

answered 2018-07-17 09:32:22 +0300

krisko gravatar image

As a workaround you can select network manually.

Note that this does not work when the issue already occurs, so you have to reboot the phone before choosing the network.

This is definitely a SW issue and is present also in SFOS 2.2.0 (I have Xperia X).

edit flag offensive delete publish link more

Comments

2

confirming

mcencora ( 2018-07-17 15:00:56 +0300 )edit
2

Confirming too. I had it the first time when roaming in France and then lot of times. Xperia X with official SailfishX.

silta ( 2018-08-02 13:08:44 +0300 )edit
6

Confirming @silta 's comment. I have the F5121 and it occurs in roaming. Always when switching borders to a new network. But also from time to time when staying in a foreign country. For me about once a day, possibly due to change of the roaming provider/network.

Spark ( 2018-08-02 21:42:54 +0300 )edit
3

I get the same issue consistently when switching networks while roaming, but also in my home country if I happen to lose a network connection, or have a very weak signal strength: so it seems like it's not just roaming that causes this. Interestingly, the cellular connection goes on and off while the issue happens, and so the phone is still capable of receiving texts etc.

tadzik ( 2018-08-29 16:16:33 +0300 )edit
4

I confirm the issue. The situation appeared to me only when crossing borders (same case as @Spark). I was some days between Italy and Switzerland and each time I changed between CH-IT networks, I got the SIM not recognized message. I live in Germany and have a German SIM used in a F5122.

lupastro ( 2018-09-02 22:31:46 +0300 )edit
6

answered 2018-12-27 13:11:22 +0300

deepblue17 gravatar image

Same problem here even after upgrading to Sailfish X version 3 on an single sim F5121. Problem occurs with various Sim cards from different providers in different countries (tested mainly in Asia in the last months). The main issue is, that this problem also occurs, if there is no network at all, especially in remote areas. Hence, a reboot doesn't or cannot solve the problem at all. In theory that would not been a problem, but as this message pops up every 5 seconds, it makes the phone useless, especially if you still have a GPS signal and want to use it. Also setting the phone to flight mode (before) you're entering remote areas doesn't help at all. The annoying message still pops up. Sometimes it helps to deactivate the mobile data connection, but not always. After returning to an area with network connection (of a supported provider) a simple reboot solves the problem and it does not occur any longer...until the next border crossing or entering remote area.

edit flag offensive delete publish link more

Comments

3

And most likely during these days a lot of Sailfish X users were/are facing this issue while visiting family/friends around the world. It again was very annoying when I was crossing borders four times during the last days.

@Jolla: Issue (9 months old) is "Tracked by Jolla".... Seriously???

vision ( 2018-12-27 14:10:06 +0300 )edit
5

answered 2019-06-13 14:34:20 +0300

wb1000000 gravatar image

updated 2019-06-24 22:02:05 +0300

I've experienced the same issue with my Xperia XA2 Ultra Dual SIM with 3.0.3.9. Once roaming in NL my DE SIM (congstar) in slot 2 started generating the "SIM card removed" message. The phone was unusable until I disabled this SIM.

What appears to have helped for me so far (2 days without the message, still roaming) is to set "Prefer 3G" instead of "Prefer 4G".

UPDATE: After crossing the border from NL back to DE, the issue started again. Changing from 3G back to 4G on my DE SIM solved it again.

However this weekend I was in the Basel area and both my NL and DE SIM suffered from this issue. The phone was basically useless for the whole weekend. Changing between 2G/3G/4G seemed to alleviate the issue sometimes for an hour or so but after that it started again. Not too happy about that :-|

Best regards,

Jasper

edit flag offensive delete publish link more
3

answered 2018-08-01 18:06:22 +0300

ddelamarre gravatar image

Hi

I tried it with no success. Maybe did I do it too late in the process. I try this workaround again. Hopefully, it will be better.

Ironically, while versions before 2.1.4 were not at all made for F5122, they worked flawlessly ...

Let us hope a fix will soon be available. I am defending Sailfish & Jolla wherever I can, but having an unreliable phone is annoying : I missed some urgent messages because of that issue.

Regards

edit flag offensive delete publish link more

Comments

1

I confirm it does not help much.

Another post mentions that using a micro SIM , even with decreased thickness may be the cause. I started to wonder whether the fact I have been using a cut micro SIM, even if I did grind it a bit in thickness, later on replaced by a proper nano SIM could have bent contacts ...

That said, it would not explain why it started on 2.1.4 while it worked like a charm before with the nano SIM.

Maybe should I stop looking for an explanation ...

ddelamarre ( 2018-08-20 17:01:45 +0300 )edit
3

answered 2019-04-25 16:01:00 +0300

koka gravatar image

Same here with an XA2 dual sim. Crossing a border could be the cause. It started about a week ago. Version 3.0.3.8 and 3.0.2.x affected. Upgraded this morning.

edit flag offensive delete publish link more

Comments

1

Sometimes I need to activate the empty slot 2 in settings so that my phone recognizes the SIM in slot 1 again. Happens occasionally after rebooting.

Kopekenscheich ( 2019-04-30 13:48:34 +0300 )edit
3

answered 2019-06-08 23:22:33 +0300

this post is marked as community wiki

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

updated 2019-06-25 08:37:33 +0300

Raymaen gravatar image

Maybe a list of affected devices and the exact versions would be helpful:

  • Xperia X F5121 since the 2.1.14 release
  • Xperia X Dual SIM F5122 since ?
  • Xperia XA2 H3113 since 3.0.2.x or 3.0.3.x? (no occurrence under the 3.0.1.14 beta release)
  • Xperia XA2 Dual SIM H4213 since ?
  • Xperia XA2 single SIM (always when roaming) 3.0.3.10!
edit flag offensive delete publish link more

Comments

XA2 H4213 Dual Sim, same issue. I have two of these phones, one running SFOS (Hossa), the other one Android. Sim card works fine on Android, but gets disconnected on SFOS, as such I would suspect an OS issue.

This is the one bug stopping me from using SFOS as a daily carry.

Kobold ( 2019-06-09 11:54:52 +0300 )edit

@Kobold Do you know in which version this error occurred for the first time?

Epicuri ( 2019-06-09 13:02:17 +0300 )edit

It started with the first realease of SFOS 3, which was the main reason to go xa2. The only delta being the frequency with which it happens.

Kobold ( 2019-06-10 11:19:47 +0300 )edit

i have it on the Xperia X F5122 since 3.0.3.9, most of the time when i cross a boarder.

BlaeX ( 2019-06-13 18:06:57 +0300 )edit
3

answered 2019-06-10 14:56:49 +0300

pakman gravatar image

updated 2019-07-18 21:58:39 +0300

I get this with my F5122 as well, almost always when entering a new country, although it has happened once or twice at home. It has happened both when coming out of flight mode after landing in another country, and when crossing a border by train. Usually a reboot is enough to fix the problem, and now I normally reboot when starting to roam or crossing a border. However, around last Christmas/New Year in France (Marseille) it got so bad that my phone became unusable. Luckily, it mostly affected one SIM, so I was able to disable it and buy a data pack for the other one. That saw me through the rest of my stay, with only the occasional reboot.

As @slowcyclist pointed out, part of what makes this really serious is the impact that this has on other people who are trying to get in touch with you. They won't cut you any slack because you have been let down by the weird phone that you insist on using, and that can't do half of the things that theirs can.

EDIT 2019-07-18: I have just come back from another short trip to France and Spain, and phone-wise it was a nightmare. I will never go abroad again without my trusty old Wileyfox Swift (now running Lineage) as a backup. The problems started when I arrived in France, and found that SIM 1 couldn't send or receive SMS messages, although it could still make calls. I called the SIM issuer, who couldn't see any problem from their end. After a day or two, that SIM started showing the "SIM card removed" message repeatedly. I had to disable it. When I crossed into Spain, SIM 1 was OK, but SIM 2 started giving the same problem. I know it is frustrating for devs to read reports about these kinds of things without detailed logs or diagnostics, however when these problems hit me, I am usually in the company of people who don't have much tolerance with me taking time out to fiddle with my phone rather than getting one that works (like theirs). I am going abroad again in a few weeks, and the people that I will be with are less bothered by this kind of thing: I will try to get some more detailed diagnostics if it happens again.

I know that reflashing to Android and back to SFOS might fix the problem, but:

  1. OTOH it might not fix it
  2. this is not something that I expect to have to do with a daily driver. I already have another device that needs to be reflashed and set up again from scratch, and I am waiting for the free evening that I will need for that.
edit flag offensive delete publish link more
2

answered 2018-09-16 22:34:58 +0300

txus gravatar image

Same behavior while travelling from Germany to Netherlands on arrival in Amsterdam, after switching off Airplane mode AND getting reception and a few seconds/minutes of internet, same thing from Netherlands to Spain, and same thing on the way back.

edit flag offensive delete publish link more

Comments

I experienced these problems frequently but not all times in Poland, Germany, Netherlands, Great Britain, Belgium and France. I could not track down what is causing these problems but they seem to occur when the phone first locks in while roaming. Also poor network conditions seem to be influential. I visited some very rural areas in France, Belgium and England where the problem seemed to occur more often.

WT.Sane ( 2018-09-22 16:51:34 +0300 )edit
2

Bad news : it occurs on version 3.0.0.8.

I tried resetting it to auto select the network and after some time : boom ! it tells me my SIM Card was removed.

Conclusion : back to force network and get in trouble when traveling abroad ...

ddelamarre ( 2018-11-16 15:43:15 +0300 )edit
Login/Signup to Answer

Question tools

Follow
22 followers

Stats

Asked: 2018-03-26 23:44:47 +0300

Seen: 2,310 times

Last updated: 2 days ago