Develop Bugs

Numbersync after MM update

Anyone getting issues with setting up numbersync following the update? I keep getting a backend error.
Sent from my SAMSUNG-SM-N920A using Tapatalk

I work for ATT (and use a Note 5 ATT variant with number sync to an Gear s2). We have noticed some issues getting number sync functioning on our phone after the MM update. Some things to check to help ( I did get mine working after a few headaches):
- Does your phone line have the cloud message backup and sync feature on it? (It's required for number sync to work)
- Are you using a unique MyAtt account, the way number sync works, it requires a separate MyATT account using a separate primary phone number for each device trying to setup number sync.
- Are both the watch and the phone fully updated (both firmware and gear manager need to be on the latest version)
If all else fails, factory reset the watch and then attempt to connect number sync again. If that fails its gonna end up being a factory reset on the phone, but only use that as a last resort.
Unfortunately customer care is very undereducated on the numbersync feature. If your in an area that has a device support center you may catch an employee that knows their stuff - but even that's rare. Feel free to PM me if there's anything else I can to to help out.

neopolotin75 said:
Anyone getting issues with setting up numbersync following the update? I keep getting a backend error.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Try there : https://addressbook.att.net
You can sync from your pc.
Sent from my SAMSUNG-SM-G935A using XDA Premium HD app

DTR204 said:
I work for ATT (and use a Note 5 ATT variant with number sync to an Gear s2). We have noticed some issues getting number sync functioning on our phone after the MM update. Some things to check to help ( I did get mine working after a few headaches):
- Does your phone line have the cloud message backup and sync feature on it? (It's required for number sync to work)
- Are you using a unique MyAtt account, the way number sync works, it requires a separate MyATT account using a separate primary phone number for each device trying to setup number sync.
- Are both the watch and the phone fully updated (both firmware and gear manager need to be on the latest version)
If all else fails, factory reset the watch and then attempt to connect number sync again. If that fails its gonna end up being a factory reset on the phone, but only use that as a last resort.
Unfortunately customer care is very undereducated on the numbersync feature. If your in an area that has a device support center you may catch an employee that knows their stuff - but even that's rare. Feel free to PM me if there's anything else I can to to help out.
Click to expand...
Click to collapse
Sorry I missed this....it started working but I still have issues where if I get too far from my phone my watch numbersync sign disappears and it doesn't work.
Sent from my SAMSUNG-SM-N920A using Tapatalk

Chat Features in Messages

Anyone else have the issue with enabling chat features in Messages? I'm not sure if it is a carrier issue or an issue with Messages or the device? I've tried contacting my carrier and getting them to reset my RCS profile, but apparently they are having "issues" with doing this. I have read that others have had this issue and replacing the sim card has fixed it. I tried doing that yesterday to no avail. I get the attached message and then nothing ever happens. I've tried clearing cache and data for Messages, trying again, rebooting, etc. No go. This was a feature I really wanted to get enabled on this device. My carrier (Rogers) does offer RCS messaging, but this simply is not working or not provisioning with the carrier server.

Since no one ever responded here and the carrier still hasn't come up with a fix, here is what I did to enable chat features and get past that "excuse the wait..." screen:
Restarted the device
Go to settings-apps-android messages and then force stop
Launch Google Play and uninstall messages
Then go back to Google Play and install latest version again
Chat features are then enabled. Not that it's that big of a deal because if the people you are texting don't have a phone that supports RCS and even if they do, if they don't have chat features turned on, then it still won't work. It was simply bugging me because the option was there and I couldn't get it enabled.

I am with rogers and have same issue. How do you uninstall messages? It only uninstall its update. Do you root to uninstall complete messages app?

I'm also with Rogers, and this is the solution that worked for me. I found it on the Rogers Community forums.
You have to disable the app called Carrier Services, now setup RCS through the Messages app.
Then you can reenable Carrier Services.
I also rebooted, but I don't know if that's necessary. I hope this helps.

zeeshee said:
I am with rogers and have same issue. How do you uninstall messages? It only uninstall its update. Do you root to uninstall complete messages app?
Click to expand...
Click to collapse
If you force stop it, you can uninstall. It may only uninstall the updates, but it does uninstall after you finally get it to force stop. I had to try force stop a couple of times.
RPAusCan said:
You have to disable the app called Carrier Services, now setup RCS through the Messages app.
Then you can reenable Carrier Services.
Click to expand...
Click to collapse
I didn't have to do this portion. When I went into Messages after doing my steps, chat features were automatically enabled.
What was really funny is Rogers kept sending me emails telling me they were "working on a fix but hadn't found one yet." When I got another email yesterday stating this from them, I chatted with tech support and told them I had fixed it myself so they could stop sending me emails about them working on it. Then I get an email from them stating that "they had fixed my issue..." LOL. Sure, sure you did.

I can't honestly say this was the cause, but my issues didn't happen until I updated to the January Security Patch. I'll try these steps tonight to see if I can get them re-enabled.

TheIgster said:
Since no one ever responded here and the carrier still hasn't come up with a fix, here is what I did to enable chat features and get past that "excuse the wait..." screen:
Restarted the device
Go to settings-apps-android messages and then force stop
Launch Google Play and uninstall messages
Then go back to Google Play and install latest version again
Chat features are then enabled. Not that it's that big of a deal because if the people you are texting don't have a phone that supports RCS and even if they do, if they don't have chat features turned on, then it still won't work. It was simply bugging me because the option was there and I couldn't get it enabled.
Click to expand...
Click to collapse
Does Rogers sell the Pixel 3 in their stores? I'm curious because I have purchased my Pixel 3 from Google and I'm using it on a carrier (T-Mobile) who doesn't sell the P3, but is starting to support RCS. However, their version of RCS support appears to only be enabled through a carrier supplied software update to T-Mobile branded phones. I'm afraid I'll never be able to use RCS on the ONE phone that comes with RCS support out of the box.
But if you were able to get RCS support without Rogers selling the phone, then there may still be hope for me someday!

PuffDaddy_d said:
Does Rogers sell the Pixel 3 in their stores? I'm curious because I have purchased my Pixel 3 from Google and I'm using it on a carrier (T-Mobile) who doesn't sell the P3, but is starting to support RCS. However, their version of RCS support appears to only be enabled through a carrier supplied software update to T-Mobile branded phones. I'm afraid I'll never be able to use RCS on the ONE phone that comes with RCS support out of the box.
But if you were able to get RCS support without Rogers selling the phone, then there may still be hope for me someday!
Click to expand...
Click to collapse
Yup. Both the Pixel 3 and Pixel 3 XL in their stores, online,etc.

If anyone's RCS won't work after clicking "yes, I'm in", just disable carrier services, go back to messages and opt in again. Once working, enable carrier services.

Chat features work in Messages App by Google LLC for me nearly everywhere now:
- Huawei AL10 P9 running Emui 8 Oreo on Telekom network in Hungary on WiFi (no Data subscription)
- Samsung Note 4 N910V LineageOS 16.0 Pie on Telekom network in Hungary on WiFi and Data
- Samsung Note 4 N910V LineageOS 16.0 Pie on GoogleFi roaming in Hungary on WiFi (cannot get LTE Network/Data connected to any tower)
- new device Google Pixel 2 XL Android Q on GoogleFi roaming in Hungary (will test in July)
On my home MikroTik router WiFi, where I run a domain and webserver, i forward port 80/443 to the webserver.
This is the only WiFi network, where I cannot use chat features for unknown reasons.
QUESTION: WHAT PORT(S) DOES RCS / CHAT FEATURES USE ON A WIFI NETWORK FOR COMMUNICATION TO OTHER PARTY AND THE PROVIDER SERVER (IN CASE OF FILE TRANSFER)
Google Fi support and Telekom HU Support dont understand the simple question or they resist to answer me, by replying constantly with the copy/paste of troubleshooting guides that I read all already. Either those are bot replies, or Google started to employ Level 1 people that are forced to reply automatic text. Telekom HU Support always was a big pain in the ass.

did you every figure it out?
Did you ever get this figured out? I've put my router in full DMZ and I still can't get RCS chat features to work on my home WiFi … but They USED TO WORK until a month or two ago... not sure when, It was my wife who noticed. tred 4 phones on 3 carriers, non work. many businesses have notices on the front doors too because it's killing employee's batteries while they work all day. Google refuses to answer.
ant0nwax said:
Chat features work in Messages App by Google LLC for me nearly everywhere now:
- Huawei AL10 P9 running Emui 8 Oreo on Telekom network in Hungary on WiFi (no Data subscription)
- Samsung Note 4 N910V LineageOS 16.0 Pie on Telekom network in Hungary on WiFi and Data
- Samsung Note 4 N910V LineageOS 16.0 Pie on GoogleFi roaming in Hungary on WiFi (cannot get LTE Network/Data connected to any tower)
- new device Google Pixel 2 XL Android Q on GoogleFi roaming in Hungary (will test in July)
On my home MikroTik router WiFi, where I run a domain and webserver, i forward port 80/443 to the webserver.
This is the only WiFi network, where I cannot use chat features for unknown reasons.
QUESTION: WHAT PORT(S) DOES RCS / CHAT FEATURES USE ON A WIFI NETWORK FOR COMMUNICATION TO OTHER PARTY AND THE PROVIDER SERVER (IN CASE OF FILE TRANSFER)
Google Fi support and Telekom HU Support dont understand the simple question or they resist to answer me, by replying constantly with the copy/paste of troubleshooting guides that I read all already. Either those are bot replies, or Google started to employ Level 1 people that are forced to reply automatic text. Telekom HU Support always was a big pain in the ass.
Click to expand...
Click to collapse

ptv83 said:
Did you ever get this figured out? I've put my router in full DMZ and I still can't get RCS chat features to work on my home WiFi … but They USED TO WORK until a month or two ago... not sure when, It was my wife who noticed. tred 4 phones on 3 carriers, non work. many businesses have notices on the front doors too because it's killing employee's batteries while they work all day. Google refuses to answer.
Click to expand...
Click to collapse
I never succeeded yet
I assume (as a RCS novice) support has no idea what RCS is and Google has support agents that have also no idea and the people who developed this left the company or got kicked out...

I also think that my webserver port 80 and 443 causes this, I will try disabling the forward cause my webserver died waiting for replacement unit

ant0nwax said:
I also think that my webserver port 80 and 443 causes this, I will try disabling the forward cause my webserver died waiting for replacement unit
Click to expand...
Click to collapse
I changed the forwarding to not forward ports 80 and 443 to a dedicated IP, still did not help
the router behind my mikrotik router and its wifi is capable of getting a status Connected
the mikrotik router itself and its wifi cannot get beyond Connecting...
I wonder if that might have to do something with IPv6?

Hi. After resetting the phone to factory settings, I can not turn on the chat features, the message configures is displayed, after a few attempts the message "confirm your number" appears, after three attempts the message "limit exceeded try again tomorrow" and so on overnight trying. There is a solution to this problem?

g323 said:
There is a solution to this problem?
Click to expand...
Click to collapse
Hi,
Do you have Data activated during setup? Could help.
Good luck...
Sébastien.

Yes, I have, matches have been with this for a month and I even turned off the chat for 8 days as I write in google help, but it did not work. of course, cleaning the data did nothing

Galaxy watch Reactivation Lock : ON (SM-R800)

I have a Galaxy Watch SM-R800 and the Galaxy Wearables app installed on my S10+ but couldn't pair my watch with my phone. Both my phone and watch were bought in India, but I use them here in Italy cause I live here.
I used this watch for many days with no problem at all and then one day I upgraded my phone to One UI 2 (beta) and I encountered this bug with security module, which locked me out from entering the phone even though I was entering the correct Pin or passcode.
After that I rolled back my phone to Android 9 (stable) version.
So my assumption is that the procedure that I followed to upgrade my phone to One UI 2 might have caused this issue with my watch.
Firstly I created a Samsung account with my email which by default is Italian cause of location, but I had to sign up for the beta program using an India account. No beta testing in Italy.
As suggested on XDA forums by someone I had to delete my Italian Samsung account and create Indian account with same email if I want to enroll for the beta program, which I did.
So I didn't use the watch for few days and later when I tried to pair it with my phone it says, "Couldn't Pair your watch" (Try Again/ Cancel)
I'm using the same email Id for Signing In to finish the setup of pairing with which I initially setup both the Phone and watch. It sometimes says I am using a different account from the one I used earlier to setup. I'm definitely sure that I never used any other account of mine or a friend. (No others)
I need your help if someone has a solution for this situation.
Thanks,
Akhil Bellam.

akhilbellam said:
I have a Galaxy Watch SM-R800 and the Galaxy Wearables app installed on my S10+ but couldn't pair my watch with my phone. Both my phone and watch were bought in India, but I use them here in Italy cause I live here.
I used this watch for many days with no problem at all and then one day I upgraded my phone to One UI 2 (beta) and I encountered this bug with security module, which locked me out from entering the phone even though I was entering the correct Pin or passcode.
After that I rolled back my phone to Android 9 (stable) version.
So my assumption is that the procedure that I followed to upgrade my phone to One UI 2 might have caused this issue with my watch.
Firstly I created a Samsung account with my email which by default is Italian cause of location, but I had to sign up for the beta program using an India account. No beta testing in Italy.
As suggested on XDA forums by someone I had to delete my Italian Samsung account and create Indian account with same email if I want to enroll for the beta program, which I did.
So I didn't use the watch for few days and later when I tried to pair it with my phone it says, "Couldn't Pair your watch" (Try Again/ Cancel)
I'm using the same email Id for Signing In to finish the setup of pairing with which I initially setup both the Phone and watch. It sometimes says I am using a different account from the one I used earlier to setup. I'm definitely sure that I never used any other account of mine or a friend. (No others)
I need your help if someone has a solution for this situation.
Thanks,
Akhil Bellam.
Click to expand...
Click to collapse
Hello. did you tried to reinitialise the watch?

The watch is locked (reactivation lock (not other security lock)) by original samsung account used when it was locked. You MUST NOT DELETE this account UNTIL the watch was UNLOCKED. If you delete the original account you will (never) not able to unlock the watch. (or use hack (paid) method))

I can help u have to use netodin and install combination file and then u have to remove reactivation lock and then install official firmware. Indeed a long and complicated process. Msg me on whatsapp 923107671256

Iron_UV said:
Hello. did you tried to reinitialise the watch?
Click to expand...
Click to collapse
It doesn't work if you try anything else other than flashing it.
By the way I fixed my watch finally.
I had to use the firmware and other combination files, but I couldn't find them anywhere on the web.
And then finally I found this video on Youtube showing how to remove that re-activation lock on Gear S3. youtube . com/watch?v=Afx3RWWFSfg&t=1s
and I contacted the guy on Facebook.
He redirected me to his website, where I paid him a little money $15 and he provided me with the necessary files to do the task.
https: // electrovo.com/

akhilbellam said:
It doesn't work if you try anything else other than flashing it.
By the way I fixed my watch finally.
I had to use the firmware and other combination files, but I couldn't find them anywhere on the web.
And then finally I found this video on Youtube showing how to remove that re-activation lock on Gear S3. youtube . com/watch?v=Afx3RWWFSfg&t=1s
and I contacted the guy on Facebook.
He redirected me to his website, where I paid him a little money $15 and he provided me with the necessary files to do the task.
https: // electrovo.com/
Click to expand...
Click to collapse
hi bro i have same watch R800 wich is samsung account lock. can you plz share your file with me ?

For Those who are facing problem on the galaxy watch SM-R800 i finally found the solution to by pass the Samsung Account it's a little long method but working fine

'Call not sent' error on Android 10 beta

Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.

Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.

"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(

Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007

I am really glad I blocked updates, I am still running on Pie

billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?

ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.

billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...

ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)

I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.

kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.

Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.

i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.

I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…

i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020

winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.

kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!

S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).

billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.

dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.

Galaxy Watch 4G LTE

Hello everyone, I've had a problem for a few days. (I am from France)
I have a galaxy S10 running Android 10
And a Galaxy watch under tizen 4.0.0.4 (I'm waiting for 4.0.0.7)
The stand-alone mode works, but the remote connected mode (4G) no longer works. However, I am good in 4g on the phone and on the watch. Also, I have activated on galaxy wearable, the remote connection box. (see picture)
Is this a problem from Samsung? Watch? Phone? Thanks for your help ?

mminoss said:
Hello everyone, I've had a problem for a few days. (I am from France)
I have a galaxy S10 running Android 10
And a Galaxy watch under tizen 4.0.0.4 (I'm waiting for 4.0.0.7)
The stand-alone mode works, but the remote connected mode (4G) no longer works. However, I am good in 4g on the phone and on the watch. Also, I have activated on galaxy wearable, the remote connection box. (see picture)
Is this a problem from Samsung? Watch? Phone? Thanks for your help ?
Click to expand...
Click to collapse
Have you enabled it with your carrier? Mine required an extra plan to be able to use the 4g with my watch.

Thanks U for your Answer.
Of course, it s actived

Sometimes I have to reboot watch to make it work

Good day to you I'm working on the assumption that it is something that has worked and stopped functioning temporarily.
I wouldn't worry about it too much to be honest.
The watch connects to the phone over LTE via some cloud servers, occasionally they have issues with getting the watch to connect with the phone effectively, it happened to me a few weeks back but sorted it's self out after a few hours.
If it's something that's been going on for a longer time than a day or so, then it's time to start troubleshooting.

renton82 said:
Sometimes I have to reboot watch to make it work
Click to expand...
Click to collapse
thanks U and i already reboot the two

step0011 said:
Good day to you I'm working on the assumption that it is something that has worked and stopped functioning temporarily.
I wouldn't worry about it too much to be honest.
The watch connects to the phone over LTE via some cloud servers, occasionally they have issues with getting the watch to connect with the phone effectively, it happened to me a few weeks back but sorted it's self out after a few hours.
If it's something that's been going on for a longer time than a day or so, then it's time to start troubleshooting.
Click to expand...
Click to collapse
thank you for the answer. I also think that it comes from samsung servers because even when my watch is connected by Wifi and the mobile in 4g (or wifi because I also tested) it does not work anymore. However, it's been over 2 days now, so I don't think it comes from the watch ... Am I wrong?

Hmmm, try uninstalling the wear app, then reinstall again, if that isn't working you can try resetting the watch to factory settings and try again, it is possible it's a Samsung service issue, definitely something isn't handshaking somewhere, 2 days seems a bit of a long time for it to be a service issue though :/

Well, I tested everything to find out where the problem could come from. However, less than one could say is that Samsung technicians are not ... How to say ... Responsive! And that's a shame. That said, the main thing is to have found (I hope) the solution, and that it could help people.
The problem came from the toggle of the request "notif arriving on lel" and which is sent to the samsung account and then that the watch receives it and by analyzing my samsung account (with a pc on the samsung site), it generates that the "cloud" part of my account was not active but in error (and no response from samsung on an e-mail that I sent to them, hence my amazement about the reactivity).
Suddenly, I had a second samsung account, I re-paired everything, put this new account in wearale (essential), checked on the samung site that cloud state "active" and the ca worked direct .....
So the mystery: why my cloud (which is used to receive notifications) was in error .... I would never know lol. Or was it a confluence between the 2 accounts? I don't think it worked before ... In advance, I completely deleted this account that had the error.
I hope this solution will be eternal lol and that it will help