Hello there,
I buy new Galaxy watch (Bluetooth version) yesterday and trying to make call through my watch. As soon as I start calling anyone, call automatically routed to phone (whether phone is in my pocket or table) and audio came through phone. On other side calling screen from Watch disappear and return to back screen (where I have contact number to dial).
Call receiving is normal, I can pick up and talk on my Watch.
Any help or am I missing something?
Phone I use: Samsung Galaxy S9
Watch: Samsung Galaxy watch (Non-LTE, Bluetooth version only)
I had this issue too.
Tried dialing and it went straight to my phone.
I would also like an answer to this.
I would guess your phone service provider must support eSIM.
But it is just a guess
Related
So, my phone can't make calls and I've tried everything I was able to find online to force it to do so. I took my sim card from my moto x and put it in you'd nexus 5x, but when I try to make a call it immediately hangs up. I've gotten a new SIM card and gone to multiple Verizon stores to fix it, to no avail. Lastly, I heard that I could make calls inever i enabled advanced/hd calling so that i could use data for the call. Whenever i go into testing settings to make the VoLte work and reboot, it seems to not keep the setting. I'm lost, and I just want to make calls. Any help?
In the past (16 years ago, in times of Siemens S55) there was a way to enable a second line on the mobile phone. I think it was something like pressing 0 for a few seconds to switch between the lines.
When activated without access to a second line, you were not able to make any phone call. Not sure if this function is still available at actual smartphones. Only a hint where you can search for.
Or, another hint, you've activated the call restriction (not sure if this is the correct translation from German). In the options of the phone you're able to block some or all numbers for outgoing calls.
Try to check in test menu (*#*#4636#*#*)if the phone is on LTE-only mode and put it on LTE/CDMA/UMTS
Sent from my Nexus 5X using Tapatalk
My H798 came across bootloop, after a fix from Huaqiangbei, Shenzhen, was sent to me today. The phone runs into a similar issue. Data and SMS work well, while any call will be held on "Calling…" for 30 seconds, with no sound, then end up with a beep of hanging up.
But my mobile carrier is China Mobile.
Same thing here, replaced with chinese motherboard and now no calls, but sms and data works fine.
It seems that there are different SMC for 4g and 2/3G, so it seems that there is a hardware fault on the 3g/2g chip.
Gonna try to gunheat it.
Hey friends,
I'm looking to take my Note 8 from Verizon to Tmobile. The problem I'm having at the moment is while on T-Mo's network all calls forward to voicemail, no problem with making outgoing calls. Spoke at length with Tech support and we ran a test and did ##21# to deactivate the unconditional call forwarding. The phone received a call immediately afterward, but after 5 minutes reverted back to forward all calls to voicemail. I have 2 note 8's from Verizon and both did the same thing. Brought over 2 iPhone SE's with no problem. In addition, the data drops completely during a call. The call will not connect until the data is dropped then the call beings to ring.
I tried first unrooted then rooted them as they both are V2 via SamFail. Any thoughts? Anyone experienced anything similar. Tech support from T-Mobile said that If the phone had a 2G Only option that the service would work fine. Weird... Regarding the root, should I flash a home_CSC from Tmobile?
Thanks in advance for those they respond. :good:
I have bought a Galaxy watch 46mm Lte version with a stand-alone E-sim. Is there any app for automatic call forwarding, when the watch losses Bluetooth connection to the phone like on the old S3? If yes, can ask for a detailed instruction on how to make this to work?
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.
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?