Develop Bugs

my particular play droid goes to voicemail too quickly

my particular play droid goes to voicemail too quickly, goes to voicemail after only one ring. the behavior of calling out is also a little off as there are about 10 seconds of just dead waiting before the call goes through and begins counting the seconds on the dialing screen.
taking the ota update to 7.1.1 did not resolve it.
putting my tmobile mvno gsm sim in other unlocked phones does not present this issue. when 1st put in sim it did not say enter unlock code but did say sim is not from verizon.
doesn't seem like it is quite fully unlocked or there is some software or radio issue.
UPDATE
found the APN settings for the sim card been using and that solved the issue.

S20 Ultra Exynos missing calls intermittently

So I have used my S20 Ultra since March this year.
I've noticed that the cellular network just "sleeps" and doesn't receive calls/SMSes after some time of phone idling/usage on WiFi.
I tried googling and found many other users reporting similar issues, noticing also that it seems majority if not all are Exynos variant users (not based in US).
Personally, this is definitely not a telco provider issue as I have had this issue on my old SIM (which was working fine on my old phone) and new SIM that I recently got after switching providers to see if the issue went away.
For me, sometimes the calls come in a few minutes late, and then the phone rings but when picking up, the call just gets stuck because the other party is no longer calling.
This is particularly noticeable as due to mostly staying home during COVID-19.
Toggling flight mode to "wake" the cellular network makes the phone be able to receive calls again.
Forum thread for reference: https://us.community.samsung.com/t5/Galaxy-S20/S20-Ultra-not-receiving-calls/td-p/1190155

Lucky me. Didn't have this problem on my s20+ exynos
Sent from my SM-G985F using Tapatalk

lynxlok94 said:
So I have used my S20 Ultra since March this year.
I've noticed that the cellular network just "sleeps" and doesn't receive calls/SMSes after some time of phone idling/usage on WiFi.
I tried googling and found many other users reporting similar issues, noticing also that it seems majority if not all are Exynos variant users (not based in US).
Personally, this is definitely not a telco provider issue as I have had this issue on my old SIM (which was working fine on my old phone) and new SIM that I recently got after switching providers to see if the issue went away.
For me, sometimes the calls come in a few minutes late, and then the phone rings but when picking up, the call just gets stuck because the other party is no longer calling.
This is particularly noticeable as due to mostly staying home during COVID-19.
Toggling flight mode to "wake" the cellular network makes the phone be able to receive calls again.
Click to expand...
Click to collapse
I also have this issue (S20+ exynos, dual sim). I use wifi at home/work and I had several missed calls and delayed text messages during this time.
Now I turned on the text alerts about the missed calls. At least when my phone connects again to the network I get these notifications.

I am also having this issue. People call and it rings out at their end but not at my end. Is there any fix?

Try switching the active number to slot 2. I tried it for a couple of days and I think it was better. I have switched back to slot 1 to monitor as I just got the ATE6 update and wanna see if it changed anything.

I had this issue and figured out what was causing it. You need to disable VoLTE if you are not registered to use this service on your carrier's network.

ctp9 said:
I had this issue and figured out what was causing it. You need to disable VoLTE if you are not registered to use this service on your carrier's network.
Click to expand...
Click to collapse
My sim cards are already registered to use VoLTE, my carrier notified me a few months ago about it.
I tried to disable VoLTE on both sim cards. It was OK for 2 weeks until now.
I got a new missed call notification text message and after 5 minutes a message from the caller.
Now I enabled VoLTE again for one sim card. Let's see if there will be more missed calls with this setting.

Galaxy Watch Active 2 LTE - Unable to make/receive calls

Hi folks,
I recently bought an Active Watch 2 and already have a Vodafone UK mobile account to which I added the One Number service.
I've discovered that on my watch while on 4G, I cannot make or receive phone calls.
There is definitely a data connection there, as I can send a text message or use the Internet browser app to view a website.
What happens is I dial a number, I get 2 beeps and then a Call Ended message. I've spent over 10 hours on the phone/chat to Vodafone trying to get this resolved to no avail. I've done a number of resets, SIM swaps etc.
This morning I noticed on the watch under Settings in the Phone app, that there is an option for "Preferred Number for Calls" which is greyed out and set to 'Watch'. I'm sure at one point when I first got the watch I was able to select Phone or Watch. Could this have something to do with it? Is the VF network blocking the call because the watch is trying to phone from the One Number secondary number instead of my contract phone number ?
Any help appreciated!

Hey there.
I have the exact same problem myself, my carrier is o2 and have an Active2 LTE.
Set everything up through the esim QR Code. I am the £5 data per month, and yet am unable to make or receive phone calls through LTE / Wi-Fi. No issues though with data and messaging.
It occasionally worked when I first set it up a couple of months ago, but since the latest Tizen update to 5.0 something, there is no option under 'remote connection' in the Galaxy Wearable app to make/receive calls. When testing my original Galaxy Watch out, the call option is there and it is on Tizen 4.0 and I am able to make WiFi calls.
At first I thought the issue was with o2 but am now thinking it is related to Samsung services. Via Bluetooth the Active2 works fine with call functionality but through WiFi/lte, nothing. The odd issue as well, is that, when testing through LTE on the watch it remotely connects very briefly to the phone when attempting the call but then the phone automatically disconnects from remote dialling.
I would say that it is definitely software related, I also have tried all troubleshooting issues and more with no luck.

Hey there. Have you managed to get a fix for this?
I have been in contact with both o2 and Samaunf on this very issue and Samsung are saying to send it in for repairs. I am very dubious though that it is a hardware issue, rather software related.

Hi I have now got both a galaxy watch and a galaxy watch3 here in the UK to now work stand alone on a pay as you go ESIM and wondered if some of my findings may help.....
First the Galaxy Watch i bought second hand on an auction site
it had been on EE in the UK and when i first loaded an esim on it I could not make calls or connect to the network...
I looked under settings connections mobile networks only to find that there was no option to select 3g / 3g4g mode ....
Hence the unit was setup only to connect via 4g data ....by default ....and so would only send Voice calls over LTE ...and hence when i changed the ESIM from EE yo Vodafone I could not make calls or SMS ...and only had emergency calls over vodafone if i was in a 4g service area with no ability to search for or connect to 3g
So I downloaded OXX versions of the firmware instead of OXA for the UK ...and i got the earliest version i could find.
Then loaded it onto the watch ... then I checked the CSC and EE where using a non BTU CSC code so first...
I changed the CSC to BTU so I could support non EE ESIMs
Next I Uploaded an ESIM from Vodafone via Galaxy Wear on a samsung phone over a bluetooth link after first activating
the esim test feature of wear app to enable QT code scanning to load the ESIM.
The OXX firmware activated the 3g 3g-4g section option under settings connections mobile networks so i could enable 4g/3g auto selection .....then the watch could find and connect to 3g or 4g networks and make voice calls and send / recieve sms.
then I put the watch into firmware download mode to install OXA firmware ...and it was an the oldest version i could find
the watch rebooted and so i now had OXA firmware with the 3g-3g/4g toggle still present under settings.
checked it was on 3g-4g auto selection.
then I enabled Dexv mode and made sure the CSC was still on BTU for generic UK ....it wasnt it had changed so I reset it to BTU
then I upgraded the firmware to the latest version via wear app ...
So end up with a generic BTU UK CSC with the latest Firmware BUT with the 3g/4g selection option under mobile networks.
with another service providers ESIM installed 3g/4g to auto select and it all works fine.
hence myadvice is if you dont have 3g/4g then the watch may be locked to 4g ONLY and VOLTE as its only mode with the CDC set to something generic EE for example...
Hope this is of assistance as many conplain that the watch wont work stand alone for voice calls or sms properly
my days of time and many esim tests until i got 3g support and 3g-4g auto load lead mr to think that the watch is often
locked to 4g data and VOLTE only ....
I now have done this on watch and watch 3 models with full sucess stand alone pay as you go esims ....with the watch fully stand alone...working like a normal cell phone ....with esim service with a different provider to the sim in my samsung phone
comment please .... hope that helps

Hi. My problem is different from this. I can make and receive calls from My Active2 LTE and I can also send text messages. However, I cannot receive text messages. Basically I bought this watch to rely on this for calls and messages and this got totally disappointed me.
Any advise on how we can receive text messages?

I have had this problem too. The issue is in phone settings. Go to ADVANCED FEATURES and turn on ALLOW CALLS ON OTHER DEVICES also turn on mobile data in this setting.

Can't use former Sprint/Ting Galaxy S9 on Ting

I can't use a former Sprint/Ting Galaxy S9 on the Ting network.
Primary symptom: CAN NOT make outbound phone calls.
It has been sitting in a drawer for a couple of years, probably from 2019 to 2022.
I put in a new Ting X3 Sim and activated it.
And it won't make outbound phone calls.
Is it just a parts phone at this point?
Or, is there any hope of making outbound phone calls with it?
Model: Samsung Galaxy S9 SM-G960U 64GB
Geographic location: USA 425 area code.
Ting tells me that:
-Ting no longer uses Sprint network.
-Sprint merged with T-Mobile.
-IMEI stuck with Sprint towers that have been decommissioned.
Nothing to be done - it is now a brick as far as outgoing cell phone calls concerned.
Symptoms:
CAN NOT make outbound phone calls.
- Dial out to another phone, get "attempting"
- returns to dial screen in a few seconds.
CAN: receive inbound phone calls
CAN: send outbound SMS
CAN: receive inbound SMS
Properly registered and activated on the Ting network, according to Ting.
get Activation incomplete ... Connection error (6601)
or
get Activation incomplete ... please contact your service provider to activate your device for service, internal error (407)
tried different APN's: "T-Mobile US LTE", "Ting Data"
after reboot, get notifications:
Sprint OMADM: Activation not completed
Carrier hub: processing requests

GWA2 - LTE connected but can't make calls?

I have a GWA2, bought from an authorised and officially supported vendor.
ESIM is activated, watch can register itself onto network whenever it goes out of BT scope.
Internet is also working, so technically the connection works.
However the watch can not make any outgoing calls at all. I contacted Telekom (provider) but they are stating there is no issue has been found on their site.
Once I turned on the VoLTE on the watch (had to send a specific SMS to the provider), calls are working as they should. However there are many locations where VoLTE is not available due to bad signal and at those places the watch is still unable to make calls.
I have completely removed the eSIM and re-registered it. Didn't help.
Is anyone having similar issue recently?