11-08-2024 04:29 PM
I have galaxy watch ultra and a one plus 9 pro mobile (dual sim) . Not using esim in the watch.
After setup, I choose Mobile plan from phone's galaxy wear app, settings. It presents the 2 sims I have in my phone and says "select a sim to setup on your watch".
Does this mean it will use the sim in my phone to communicate with the Internet (subject to some limits I set in the "plan"), or is it some bug, or just unfinished software??
🙏
11-08-2024 04:57 PM - last edited 11-08-2024 05:06 PM
11-08-2024 05:38 PM
12-08-2024 05:53 AM
So it shares the sim from the phone, or it must be different? I had assumed esim would be unique.
Why is it doing this? If I want an esim profile I would expect it is unique, otherwise it's like having 2 phones with the same sim, no? Why would I put the sim in my phone, when really I want it in my watch? There are different ways it could work, some basic rules need stating.
12-08-2024 07:09 AM
I spoke to Samsung customer service. For my scenario (no esim configured in watch) they say it will configure an esim profile based on the choice of mobile sim I answer (ignores my android configure of what sim I use for calling and what sim I use for Internet). I would end up with a *copy* of the sim from my phone.
Apparently there's then configuration about prioritising watch or mobile for receiving text and calls. However it seems to me there's a security risk regarding sms 2fa, now that the sim is on 2 devices. I'm guessing there's also issues regarding the sim contract provider. Perhaps they are OK with the copy scenario, or perhaps they are not. I think their knowledge of the esim profile includes that the device is a watch, but I'm guessing.
From a user and security point of view, more information needs publishing in a form that is easy to find and easy to understand.
At the moment it feels a bit wild/cutting edge?