Majidnasser
Active Level 1
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2025 01:15 AM in
Galaxy SI have an S24 Ultra phone with a dual GSM SIM system. I'm facing an issue where one of the SIM cards occasionally shows as not connected and displays the message "Emergency calls only," then it reconnects to the network again. This problem started appearing in recent months, even though I didn’t experience it during the first year after purchasing the phone. Has anyone else faced the same issue, and has a solution been found?
2 Comments
Rahul_Radhakris hnan
Active Level 7
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2025 06:14 AM in
Galaxy S
You're not alone—many Galaxy S24 Ultra users have reported similar issues where one of the SIMs shows “Emergency calls only” or no service intermittently, then reconnects after a few moments. Since it only started recently, it's likely related to software updates, network compatibility, or SIM slot contact issues.
Possible Causes:
1. Recent software update may have caused instability with network handling.
2. SIM card wear or damage over time.
3. SIM slot or tray alignment issue.
4. Network-related compatibility or temporary outages.
5. Background battery optimization killing the SIM services.
Steps to Fix the Issue:
1. Swap SIM slots:
Place the problematic SIM in the other slot and observe.
If the issue follows the SIM, it's likely a SIM problem, not the phone.
2. Test SIM in another phone:
See if the issue happens there too. If yes, replace the SIM card.
3. Reset network settings:
Go to Settings > General Management > Reset > Reset network settings.
This will not delete your data but will reset Wi-Fi, Bluetooth, and SIM configurations.
4. Disable 5G temporarily (if not available/stable in your region):
Go to Settings > Connections > Mobile networks > Network mode, and select LTE/3G/2G.
5. Turn off Dual SIM always on (if enabled):
Settings > Connections > SIM Manager and toggle off Dual SIM always on if not needed.
6. Clean and reinsert the SIM:
Gently wipe the SIM card with a microfiber cloth and reinsert it securely.
7. Check for software updates:
Go to Settings > Software update > Download and install.
8. Disable battery optimization for SIM services:
Settings > Battery > Background usage limits > Never sleeping apps, and add SIM/Network services (if visible).
Possible Causes:
1. Recent software update may have caused instability with network handling.
2. SIM card wear or damage over time.
3. SIM slot or tray alignment issue.
4. Network-related compatibility or temporary outages.
5. Background battery optimization killing the SIM services.
Steps to Fix the Issue:
1. Swap SIM slots:
Place the problematic SIM in the other slot and observe.
If the issue follows the SIM, it's likely a SIM problem, not the phone.
2. Test SIM in another phone:
See if the issue happens there too. If yes, replace the SIM card.
3. Reset network settings:
Go to Settings > General Management > Reset > Reset network settings.
This will not delete your data but will reset Wi-Fi, Bluetooth, and SIM configurations.
4. Disable 5G temporarily (if not available/stable in your region):
Go to Settings > Connections > Mobile networks > Network mode, and select LTE/3G/2G.
5. Turn off Dual SIM always on (if enabled):
Settings > Connections > SIM Manager and toggle off Dual SIM always on if not needed.
6. Clean and reinsert the SIM:
Gently wipe the SIM card with a microfiber cloth and reinsert it securely.
7. Check for software updates:
Go to Settings > Software update > Download and install.
8. Disable battery optimization for SIM services:
Settings > Battery > Background usage limits > Never sleeping apps, and add SIM/Network services (if visible).
junioramboy
Active Level 1
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2025 10:52 AM in
Galaxy S
I have the same issue since 2 updates before One UI with Fold 6. Resetting and tinkering didn't fix it.
