On my Samsung Galaxy S24 Ultra I'm using dual-SIM with 1 physical SIM card and 1 eSIM. I configured a different ringtone on each SIM. - Personal SIM card: Ringtone -> *Galaxy Bells* - RAM eSIM card: Ringtone -> *Over the horizon 2024* But regardless of which SIM card receives a call, I only hear the ringtone that is configured on the physical SIM (Personal). In the example of the attached screenshots, I only hear 'Galaxy Bells'. To be clear, I do hear the other ringtone when I select it (in the Ringtone settings), but the chosen value appears to be ignored by the phone. I've googled my problem but did not find anyone else experiencing the same issue. So, possibly the issue only occurs on my specific setup. Tried so far: - Reboot phone - Tried several ringtones on each SIM, but in all cases, only the ringtone configured on my Personal (physical) SIM is used - Updated to the latest official firmware - Confirmed that the ringtones are configured correctly in the dialer app settings (as suggested by Andrew, thanx) ***UPDATE 03 feb 2025:*** I dropped my phone and it broke the screen :-( Fortunately I had it insured, so, last week I had it replaced. I Even got lucky as they swapped it for the version with 1TB storage (from 512GB). But the reason why I'm sharing this story is that I'm still/again experiencing the issue with the ringtones (that I described in my initial post). For some reason, On my new phone I was unable to restore my apps and setting from my previous phone. Therefore I had to (re)install everything from scratch. So, that tells me that the issue was not caused by some personal settings that got corrupted. I am convinced that there is a bug in the firmware of the S24 Ultra preventing individual ringtones per SIM when used with one physical SIM and one eSIM. PS: I could not reproduce the problem on my friend's Galaxy S24 plus. So it must be S24 Ultra specific.

I'm using Asus Zenfone Max Pro M2. I found there's **Mobile Plan** in **Network & Internet** settings. But I'm not sure it is for eSIM. When I tap on it, it says: *"Network has no known provisioning website"* How to check if an Android device supports eSIM?

I'm trying to rename a eSim card on my Samsung phone (Android 14) But I get the following error ("SIM name already in use"): It's because previously I had use this name for my physical SIM card, but it has been removed and replaced by eSim card, so it's not even there anymore: This is so annoying. And what am I supposed to do in this case? I mean, it's just a bug...

I have a Pixel 8 Pro that the carrier (Spectrum) and Google both say is unlocked. The phone is definitely not unlocked. OEM unlocking is greyed out and says, "unavailable on carrier-locked devices." One of the rude managers I talked to at Spectrum told me that spectrum doesn't lock devices. I talked to several rude people at Spectrum that all said that they did not see any lock on the device. (Did I mention that they were all extremely rude. And I have been an internet customer with them for years.) I chatted with Google for over an hour and they said the device appears to be unlocked and that they didn't find any problems with the phone. They said that the issue is most likely on the carriers end. I tried with a physical sim from Cricket but it is an older sim so not sure if it would work correctly even if everything was running optimally. With the physical sim I get the message, "Sim card isn't supported. Ask Spectrum Mobile if the device can be unlocked" I tried two esims from different carriers and I get the message, "Can't connect to network Your device is locked. Contact your carrier to see if the device can be unlocked. I told the people at Spectrum what the message said, and they act like I'm crazy, "The device is not locked." I felt like I was in the twilight zone. I hope someone out there has a solution.

I have a Pixel6 and it supports 1 eSim. Since eSims are just software, **what are the limiting factors** to not have basically unlimited eSims on a smartphone? Where is it coming from?: - The lawmaker? - The telcos? - The phone manufacturers? - The phone operating system manufacturer?

What's the maximum number of eSIM cards that can be saved on a Samsung Galaxy S23 Ultra? I found https://www.reddit.com/r/GalaxyS22/comments/yco7om/how_many_esims_can_be_present_on_an_s22_ultra/ but that's for S22 and the answers vary between 2, 3, 4 and unlimited. I'm curious to know for Android 13 and 14.

Multiple old questions (here , here , here , and here ) document that even when mobile data is switched off, mobile data still gets used as part of 4G voice service. I'm looking for up to date information (e.g. possibly relating to 5G, eSIMs, latest Android version, retirement of 3G, etc.) to see if the following scenario is possible without rooting my phone: - Home SIM active for SMS (but not MMS) - Home SIM active for voice calls (this is not essential to me) - eSIM for ALL mobile data used while travelling Why am I so keen on this? The ability to receive SMS codes is sometimes needed to verify oneself to a service. (Yes, I know it is not as good as other alternatives.) As of 2023 eSIMs provide very cost effective data service almost anywhere in the world, while international data roaming charges from one's home carrier can be exorbitant (e.g. $10/MB for me). At those rates, tiny amounts of unexpected data use can add up fast. Doing all of the following is NOT sufficient to avoid use of mobile data: - Turn off mobile data AND turn off data roaming for the home SIM - Send zero text messages and make/receive zero voice calls - Turn off MMS for the home SIM - Turn off "Data during calls" Questions: - Are any new strategies/settings available or in development? - Does 5G have the same problem as 4G - using data to establish itself on the roaming voice network? - Would setting preferred SMS to my home SIM, but voice calls to a data-only eSIM be possible? - I would consider moving to iPhone: Is this an Android-specific issue?

I have Oneplus 8T with Android 13. My SIM was on Slot 2 yesterday. Then I accidentally clicked on "Disable SIM". Now it says "No eSIM" "Disable eSIM to u.." (it only shows second line partially) when I insert it in Slot 2. When I insert it in Slot 1, it says "No SIM card detected". Note: 1. If I use any other SIM, it works on either slots. 2. When I this SIM on other android phones or even a feature phone, it works correctly without any issue whatsoever. 3. I've already tried the "Reset Network Settings" feature. Ideally I don't want to reset my phone completely

I would like to set up an SM-DP+ server to provision my own eSIM profiles. These usually get certified by GSMA and are used for large-scale Remote SIM Provisioning, but I would want to use this for home testing only, so getting official certification would be overkill. I understand that I will need my own mobile network to work with it, which I also want to set up at home. My main concern is that either Android or the device manufacturers impose limitations that would only allow certified eSIM profiles to be installed on a device. I was thinking of using a Google Pixel 3A for testing, so I would be installing the eSIM profiles on this phone. I also tried to find information on what's inside a SIM profile but there isn't much on the internet. I know it contains ISMI and some shared keys which it uses to connect to the MNOs network. I would like to know what else is needed to create a functional eSIM profile and set up a server that provisions these to a Google Pixel 3A for a mock cellular network.

I have recently changed phone carriers. I cannot download an eSIM for my new carrier while it is supposed to be compatible with the Pixel 3a. They claim this is because I still have the eSIM profile from my previous carrier. For some reason, I cannot erase this old eSIM profile manually. I get the following error message: “Can't erase SIM. This SIM can't be erased due to an error. Restart your device and try again.” Of course, I still can't erase the eSIM when I restart the phone. I have contacted both carriers, as well as Google. They had me reset Wi-Fi, mobile & Bluetooth which didn't work. The next step they advise is a factory reset. I'd like to find another way to erase this faulty eSIM profile and I'm not completely sure that a factory reset would be “strong enough” actually. Has anyone ever encountered a similar problem or knows a way to force the deletion of the old eSIM profile? Edit: as Robert suggested I have checked the device log. Here is the result: 12-25 19:36:01.101 2463 2463 I Showing dialog with title = %s: Effacer ce profil SIM téléchargé ? 12-25 19:36:01.145 1770 1921 I ActivityTaskManager: Displayed com.android.settings/.network.telephony.DeleteEuiccSubscriptionDialogActivity: +122ms 12-25 19:36:01.200 2463 2463 W Choreographer: Frame time is 0.220733 ms in the future! Check that graphics HAL is generating vsync timestamps using the correct timebase. 12-25 19:36:01.200 2247 2247 W Choreographer: Frame time is 0.220733 ms in the future! Check that graphics HAL is generating vsync timestamps using the correct timebase. 12-25 19:36:01.560 1770 3866 I WifiService: startScan uid=1000 12-25 19:36:01.577 1770 3866 I WifiService: startScan uid=1000 12-25 19:36:02.188 2463 2463 I DeleteEuiccSubscriptionDialogActivity: Subscription deletion confirmed 12-25 19:36:02.188 2463 2463 V SidecarFragment: SidecarFragment.setState(): Sidecar Class: com.android.settings.network.telephony.DeleteEuiccSubscriptionSidecar, State: State.RUNNING, Substate.UNUSED 12-25 19:36:02.189 2463 2463 I DeleteEuiccSubscriptionSidecar: Deleting subscription ID: 3 12-25 19:36:02.192 2463 2539 D OpenGLRenderer: endAllActiveAnimators on 0x70de910f50 (RippleDrawable) with handle 0x6fee8d2fd0 12-25 19:36:02.193 2457 2941 D TelephonyProvider: Using old permission behavior for telephony provider compat 12-25 19:36:02.193 1770 3866 W InputManager-JNI: Input channel object 'd46f1bc com.android.settings/com.android.settings.network.telephony.DeleteEuiccSubscriptionDialogActivity (client)' was disposed without first being removed with the input manager! 12-25 19:36:02.210 2662 2662 I EuiccGoogle: EuiccServiceImpl.onCreate: onCreate DSDS mode: simCardState is 0 12-25 19:36:02.217 2662 10194 I EuiccGoogle: EuiccServiceImpl.onDeleteSubscription: onDeleteSubscription: delete slotId = -1, iccId = 89330120209449770550 12-25 19:36:02.218 2662 10194 I EuiccGoogle: EuiccServiceImpl.lockWriteLock: Successfully grant SIM state write lock 12-25 19:36:02.218 2662 10194 I EuiccGoogle: EuiccServiceImpl.ensureSlotIsEuiccAndActive: ensureSlotIsEuiccAndActive: slotId = -1, forceDeactivateSim = true 12-25 19:36:02.221 2662 10194 I EuiccGoogle: EuiccServiceImpl.ensureSlotIsEuiccAndActive: Passed in slotId=-1; euiccIsActive=false; targetSlotIsRemovable=false; forceDeactivateSim=true. 12-25 19:36:02.221 2662 10194 E EuiccGoogle: EuiccServiceImpl.ensureSlotIsEuiccAndActive: Multiple active slots supported, but slotId -1 is not active 12-25 19:36:02.221 2662 10194 E EuiccGoogle: com.google.android.flib.log.WhatATerribleException 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at com.google.android.flib.log.Blog.wtf(Blog.java:157) 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at com.google.android.euicc.logging.EuiccGoogleLog.wtf(EuiccGoogleLog.java:20) 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at com.android.euicc.service.EuiccServiceImpl.ensureSlotIsEuiccAndActive(EuiccServiceImpl.java:3747) 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at com.android.euicc.service.EuiccServiceImpl.onDeleteSubscriptionInternal(EuiccServiceImpl.java:1676) 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at com.android.euicc.service.EuiccServiceImpl.onDeleteSubscription(EuiccServiceImpl.java:1640) 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at android.service.euicc.EuiccService$IEuiccServiceWrapper$9.run(EuiccService.java:815) 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 12-25 19:36:02.221 2662 10194 E EuiccGoogle: at java.lang.Thread.run(Thread.java:920) 12-25 19:36:02.229 1770 10195 I DropBoxManagerService: add tag=system_app_wtf isTagEnabled=true flags=0x2 12-25 19:36:02.229 2662 10194 I EuiccGoogle: EuiccServiceImpl.onDeleteSubscriptionInternal: onDeleteSubscriptionInternal: slotId = -1, iccId = 89330120209449770550, ensureSlotIsEuiccAndActive = Pair{131083 false}. 12-25 19:36:02.229 1770 10195 W DropBoxManagerService: Dropping: system_app_wtf (1306 > 0 bytes) 12-25 19:36:02.229 2662 10194 I EuiccGoogle: EuiccServiceImpl.onDeleteSubscriptionInternal: onDeleteSubscriptionInternal: slotCheckResult = 131083 12-25 19:36:02.230 2662 10194 I EuiccGoogle: EuiccServiceImpl.unlockWriteLock: SIM state write lock is locked by the current thread. Unlock it. 12-25 19:36:02.230 2662 10194 I EuiccGoogle: EuiccErrorMapper.mapErrorCode: Mapping for error code: 131083 12-25 19:36:02.231 2662 10194 I EuiccGoogle: EuiccErrorMapper.mapErrorCode: Mapping error code: 131083 to: 33554432 12-25 19:36:02.231 2662 10194 I EuiccGoogle: EuiccServiceImpl.onDeleteSubscription: onDeleteSubscription errorCode: 131083, mapped to: 33554432 12-25 19:36:02.242 2463 2463 I EuiccOperationSidecar: Result code : 2; detailed code : 0 12-25 19:36:02.242 2463 2463 E DeleteEuiccSubscriptionDialogActivity: Failed to delete the subscription. 12-25 19:36:02.242 2463 2463 V SidecarFragment: SidecarFragment.setState(): Sidecar Class: com.android.settings.network.telephony.DeleteEuiccSubscriptionSidecar, State: State.INIT, Substate.UNUSED 12-25 19:36:02.242 2463 2463 V SidecarFragment: SidecarFragment.setState(): Sidecar Class: com.android.settings.network.telephony.DeleteEuiccSubscriptionSidecar, State: State.INIT, Substate.UNUSED 12-25 19:36:02.246 3829 3829 I GoogleInputMethodService: GoogleInputMethodService.onFinishInput():3301 12-25 19:36:02.246 3829 3829 I GoogleInputMethodService: GoogleInputMethodService.onStartInput():1979 12-25 19:36:02.247 3829 3829 I DeviceUnlockedTag: DeviceUnlockedTag.notifyDeviceLockStatusChanged():79 Notify device unlocked. 12-25 19:36:02.909 2463 2539 D OpenGLRenderer: endAllActiveAnimators on 0x70de8e37e0 (RippleDrawable) with handle 0x6fee8db040 12-25 19:36:02.910 1770 3246 W InputManager-JNI: Input channel object '7633076 com.android.settings/com.android.settings.network.telephony.DeleteEuiccSubscriptionDialogActivity (client)' was disposed without first being removed with the input manager! 12-25 19:36:02.950 2463 2463 D NetworkSettings: onResume() subId=3 12-25 19:36:02.974 2457 2941 D TelephonyProvider: Using old permission behavior for telephony provider compat 12-25 19:36:02.999 2457 2941 D TelephonyProvider: Using old permission behavior for telephony provider compat 12-25 19:36:03.012 3829 3829 I GoogleInputMethodService: GoogleInputMethodService.onFinishInput():3301 12-25 19:36:03.013 3829 3829 I GoogleInputMethodService: GoogleInputMethodService.onStartInput():1979 12-25 19:36:03.013 3829 3829 I DeviceUnlockedTag: DeviceUnlockedTag.notifyDeviceLockStatusChanged():79 Notify device unlocked. 12-25 19:36:03.049 1770 3246 W InputManager-JNI: Input channel object 'a5961ab com.android.settings/com.android.settings.network.telephony.DeleteEuiccSubscriptionDialogActivity (client)' was disposed without first being removed with the input manager! 12-25 19:36:03.057 1770 3246 W InputManager-JNI: Input channel object '15c0fa7 com.android.settings/com.android.settings.network.telephony.DeleteEuiccSubscriptionDialogActivity (client)' was disposed without first being removed with the input manager! 12-25 19:36:03.928 1770 2180 D ConnectivityService: NetReassign [no changes] Sorry for the log length, I can't really find where the problem is. From what I understand, it has to do with eUICC. I would bet the old carrier has messed up with permissions, but I can't be sure. Hopefully, someone may be able to identify the problem.

According to specs, Google Pixel 3 supports eSIM, but under Settings > Mobile networks, there are no relevant options. Is this depending on whether I'm currently in the service area of a mobile network operator supporting eSIM or should this option appear regardless? If so - why doesn't it appear?

I have Google Pixel. When trying to factory reset it, it says "downloaded SIMs may remain on the device". What does that mean? How do I erase these data?

I am wondering whether, with eSIM technology, I would be able to mirror my smartphone physical SIM to my smartwatch eSIM (as if I had cloned my phone, like in the movies). Telling you my final goal could explain better what I am trying to achieve. Basically I am trying to understand if I could leave my smartphone at home (SIM included), then going out with my smartwatch (e.g. running/cycling/etc) and still receive my smartphone's notifications, texts, etc from the 3G/4G network (essentially I'll be out of bluetooth range).