Guys...
I have a canadian version of galaxy watch lte R805W paired with my Note 9. Now I'm using jio network on my watch. I can use data only because no VOLTE in my watch. I have tried to change csc but the codes not installed in my watch it haves only XCA.
I need indian CSC
Please help to get Volte in my watch
Hi there, greetings from Brazil. I just purchased a Samsung S9 SM-960F (XEF) from France, running Exynos. I am being able to use it here (Brazil) with 4G, both sim cards, however VoLTE calls are not active. I have it selected on networks settings and my sim card activates it on my wife's S10e. It seems that the issue is somehow related to the device. Is there any setting or procedure that needs to be done in order to activate it? I have already hard reseted the device and it is still not working.
Marciocons77 said:
Hi there, greetings from Brazil. I just purchased a Samsung S9 SM-960F (XEF) from France, running Exynos. I am being able to use it here (Brazil) with 4G, both sim cards, however VoLTE calls are not active. I have it selected on networks settings and my sim card activates it on my wife's S10e. It seems that the issue is somehow related to the device. Is there any setting or procedure that needs to be done in order to activate it? I have already hard reseted the device and it is still not working.
Click to expand...
Click to collapse
voLTE is something that is carrier dependent and can sometimes need provisioning in the telephony switch. Could be as simple as that particular line not having it enabled on an account level. It could very easily be a firmware thing too. My carrier offers voLTE but i lost that option in my settings menu when i flashed the U1 firmware. I bet it would come back if i flashed an at&t firmware set tho even tho im using an at&t mvno
It is carrier dependent. I have a dual SIM Exynos S9 here in the US. I have a Mint SIM (T-Mobile MVNO) in one slot and VoLTE & Wi-Fi calling work just fine. The other SIM is a Cricket SIM (AT&T MVNO) and, of course, there is no VoLTE or Wi-Fi calling on that line. Cricket only supports those features in phones they sell and, of course, iPhones.
Yeap, I got the point that VoLTE is carrier dependent. The issue is that my Brazilian Carrier (VIVO) does support VoLTE in my region and I was able to confirm it by inserting my simcard in my wife´s smartphone (Samsung S10e). I have been reading some articles and threads about CSC and other stuff, like firmware flashing. As I told, my device is a S9 SM-G960, with XEF (France) firmware version installed on it.
Marciocons77 said:
Yeap, I got the point that VoLTE is carrier dependent. The issue is that my Brazilian Carrier (VIVO) does support VoLTE in my region and I was able to confirm it by inserting my simcard in my wife´s smartphone (Samsung S10e). I have been reading some articles and threads about CSC and other stuff, like firmware flashing. As I told, my device is a S9 SM-G960, with XEF (France) firmware version installed on it.
Click to expand...
Click to collapse
if the S10e is allowing voLTE, then it has the firmware built in for voLTE which might be particular to the the S10's, but thats something for the S10 forums. Regarding the S9, it needs the carriers firmware in order to utilize the voLTE feature
What is the current steps to do a csc change on this version. Needing to do a CSC change from TMB to XAA. I have a Galaxy 8 plus G955usqs7dsk2 with a provider of TMB/XAA/TMB. Can not find any version 7 bianary files that I am able to download to do a CSC change.
I have a second phone s8 plus with G955usqs5dsf2 and it works fine with provider showing XAA/XAA/USC using the same sim card.
My issue seems that TMB does not like the tower at my house and doesn't connect to it. I can drive away from my house and all other towers work fine. I even changed out all the phone boards all but the cpu board just in case it was hardware related. If there is another way of doing a csc change on this phone let me know.
Hey all
I've got a Galaxy Watch 4G SM-R805F (firmware? SM-R805FZSASWSC with software version R805FXXU1FSL3) which I bought from someone in France off eBay - default language was German though so it may have been sourced from there.
I'm in New Zealand and there's only one provider that supports eSim watches (Spark NZ). Over LTE my watch works fine for data and texts and can sync with my phone remotely, but I can't make or receive any phone calls on the watch or use 3G at all. Spark believes the watch I've got doesn't support the 3G bands they use for voice calls, and I'm hoping that this is a software issue rather than a hardware one seeing as their the same base model. The NZ firmware appears to be SM-R805FZSAXNZ.
Is it possible that either changing the firmware or software, or changing the CSC region could let my watch use the 3G bands that the NZ version of the watch uses? Or is this a hardware limitation I just can't get around?
Thanks!
XNZ leads to OXX region... SM-R805FZSAXNZ
Code:
R805FXXU1ESE3/R805F[B]OXX[/B]1ESE3/R805FXXU1ESE3
Code:
SM-R805FZSAS WSC
Can you give details from Code:
Code:
*#1234#
So we can detect Region...
Best Regards
Edit 1.
After hard brain storming voodoo dancing ..
Maybe you mean SWC...
OXA region
Code:
R805FXXU1FSL3/R805F[B]OXA[/B]1FSL3/R805FXXU1FSL3
Sorry... NO ehm LOW chance to switch from OXX to OXA nor from OXA to OXX...
I saw nobody trying hard enough... but I never saw somebody with success... last 3 4 years... with LTE Watches from Samsung...
Best Regards
adfree said:
XNZ leads to OXX region... SM-R805FZSAXNZ
Code:
R805FXXU1ESE3/R805F[B]OXX[/B]1ESE3/R805FXXU1ESE3
Code:
SM-R805FZSAS WSC
Can you give details from Code:
Code:
*#1234#
So we can detect Region...
Best Regards
Click to expand...
Click to collapse
AP: R805FXXU1FSL3
CP: R805FXXU1FSL3
CSC: R805FOXA1FSL3
Cheers!
adfree said:
After hard brain storming voodoo dancing ..
Maybe you mean SWC...
OXA region
Code:
R805FXXU1FSL3/R805F[B]OXA[/B]1FSL3/R805FXXU1FSL3
Sorry... NO ehm LOW chance to switch from OXX to OXA nor from OXA to OXX...
I saw nobody trying hard enough... but I never saw somebody with success... last 3 4 years... with LTE Watches from Samsung...
Best Regards
Click to expand...
Click to collapse
Yes my mistake it was SWC. Even if we could change it from OXA to OXX (is this just a firmware change?), would that have any impact on the 3G compatibility? I don't care about Samsung Pay or anything else, just getting voice over 3G working.
Cheers!
zaphodalive said:
Hey all
I've got a Galaxy Watch 4G SM-R805F (firmware? SM-R805FZSASWSC with software version R805FXXU1FSL3) which I bought from someone in France off eBay - default language was German though so it may have been sourced from there.
I'm in New Zealand and there's only one provider that supports eSim watches (Spark NZ). Over LTE my watch works fine for data and texts and can sync with my phone remotely, but I can't make or receive any phone calls on the watch or use 3G at all. Spark believes the watch I've got doesn't support the 3G bands they use for voice calls, and I'm hoping that this is a software issue rather than a hardware one seeing as their the same base model. The NZ firmware appears to be SM-R805FZSAXNZ.
Is it possible that either changing the firmware or software, or changing the CSC region could let my watch use the 3G bands that the NZ version of the watch uses? Or is this a hardware limitation I just can't get around?
Thanks!
Click to expand...
Click to collapse
Yes its possible! What you need is to enable the hidden menu "Network Mode" inside Settings. Then you will have the option to select "3G Only". After that watch calls / SMS should be working fine.
This is the procedure I followed:
https://www.youtube.com/watch?v=O9LVGJfCX0w
I am having a hard time enabling call recording on this phone. For my G990B2 there seems to be no firmware with XID or other countries that I used on my S20 FE last year.
I just tried using Samkey to change my CSC to XID and INS. Both did not work. After reboot it was still on EUX. According to Samkey support the G990B2 cannot be changed to INS. I have asked which CSC I can use on that phone for call recording. But so far no reply.
Anyone that was able to fix this?