Naming of Dual SIM cards

General
#1

I have dual SIM cards, one personal and second from company. Unfortunately, both are from same provider and displayed name is the same for both, so it is not easy to know which card I’m using.
I have two questions:

  1. How to rename SIM cards. Example SIM1 Personal and SIM2 Business.
  2. When trying to call a contact from the Phone app, the menu to pick the SIM card appears I can make a choice. How to save the SIM selection when calling?

Did someone may have any idea on how I can make it (can to edit configuration file)?

2 Likes
Bluetooth and Car Kit and Dual-SIM: calling (still) unreliable/random
Dual-sim mobile phones: dissociate uses by cards and simultaneous activation of 2 cards in transmission and reception
#2

For question 2 - in SIM Cards settings, there is an option to choose the default sim for calls and messages.

Screenshot_20210923_001
Screenshot_20210923_0011080×2160 588 KB

1 Like
#3

Thank you for the answer, but I did not mean this in question 2, but how to link sim1 or sim2 to a certain phone number (as on android), so that next time you do not choose?

#4

I am not providing an answer but I wonder if it is so hard to remember - it is only two of them.
Average person can remember 4-5 things. I do not want to offend you, but you can surely do better.
The best you do is turn this into feature request and hope Jolla or someone else implements it.

#5

It was about the convenience of using the phone, wouldn’t you agree with me? I consider it a utopia to request a function and wait for the release. These questions were rather intended for people who understand SFOS and I really hope for their help.

#6

I still think that if the function is not available and you do not request it, it will never become available.

IMO it is very good idea to have such option and it would not be very difficult to implement, but I am not sure if this part of the code is open.

Regarding the convenience of using the phone - I still do not understand how one can not remember in which slot he put which sim.

I do not agree with your statement regarding utopia. I have very good experience in the cooperation with Jolla and the community. Of course it does not become true tomorrow, but again, if you do not request, it will never happen and I wanted to motivate you to request it.

#7

For 1 simpler question, as far as I understand, ofono receives an answer with the network name from the operator and substitutes it after the SIM. The question is, where does he write it down? Knowing, it will be possible to manually correct it.
PS deloptes I do not want to offend you, please do not answer in topic, if you have something to say, write in PM.

#8

It seems like I found a file with an operator record along the path
/var/lib/ofono/<tab to select sim>/cache
connoisseurs, correct if I’m wrong. Can you still tell me to change it so that the recording is not overwritten?

1 Like
#9

I do not think it is so simply - someone should code something, so that you can see a different name corresponding to the network name and card

#10

While we wait, I invite you to test this:

https://coderus.openrepos.net/pm2/project/patch-named-sims

NOTE: this will only apply cleanly on multi-SIM devices!

I have so far only tested on SFOS 4.0, so please report back with your findings for any other versions.

4 Likes
Improve Dual-SIM support
#11

nephros I am very glad that you paid attention to my post and thank you very much for the work done!
According to the patch, it is compiled for the 32bit version of Sailfish OS, I am currently using Sony Xperia 10 II 64bit and therefore the path to SimManager.qml is in a different path
/usr/lib64/qt5/qml/Sailfish/Telephony/SimManager.qml
for multisim.qml the path has not changed. Made changes to the files from the patch and rebooted.

001
0011080×2520 421 KB

Fields for entering your own SIM name appeared, but after filling in they are not saved.

#12

Thanks for testing.

It is unfortunate that the lib path is now different for silica components. This means most patches will have to ship a 32bit/64bit version. :frowning:

This is a general problem with all patches now, there’s an issue for patchmanager for dealing with it:

Please make sure you hit Enter on the keyboard after changing the name. Does it save them then?

1 Like
#13

нефрос

Please make sure you hit Enter on the keyboard after changing the name. Does it save them then?

Great, now it is saved! Thanks again for the work done!
How difficult will it be to implement point 2? Assigning your SIM to a phone number?

#14

As far as I can see, not possible by the community/patching. Also probably mightily complicated.

You will have to ask Jolla for that.

#15

Which SFOS Version is that? Can you confirm that apart from the lib64 path the patch applies cleanly?

#16

nephros

SFOS 4.2.0.21 Xperia 10 II Dual
Initially, I manually made changes to the files, while preserving the originals.
Now rolled back to check the patch with the changes made to the path for SimManager.qml on
/usr/lib64/qt5/qml/Sailfish/Telephony/SimManager.qml
Checked the patch works, the scope of the patch in the files is the same.

2 Likes
#17

Hi Nephros,

This URL isn’t working. Could you please advise where I could download your patch? This is exactly what I need to rename my SIM cards and I haven’t been able to find a solution elsewhere. I have an Xperia 10 III Dual but I assume it will work with the path modification suggested by comsorg.

Thanks very much, in advance!

#18

The site hosting the patchmanager Web Catalog website is down at the moment. It will be back in a few days. Then that link will work, also you will be able to download the patch directly from Patchmanager (which is the preferred way of installing patches).

#19

Thank you so much for the information, and the quick reply. In that case, I’ll just wait a few days and try the same URL again. I’m very grateful for you making this patch and look forward to using it.

Thanks again – Hope you have a very nice weekend!

#20

It will work unmodified if using Patchmanager, as it has gained an automatic path conversion feature.