Related
Mates,
I don't know if the Kevo/Kwikset app folks are dumb, lazy or if there is some fee they have to pay to support new phones, but hear my tale of woe, with a happy ending (a minstrel on a mandolin is playing in the background as you read this).
I put Kevo locks everywhere when they first came out with android support. When they work, it is one less key I have to carry, one more thing my everpresent phone can do. They were announced as partners for the Gear S2 which, as we all know, is bull. The tech writers who said it worked were clearly Samsung lapdogs.
The Kevo website says that the app won't work on the Galaxy S7 edge but it did. Right from the start, right out of the gate. Then T-Mobile rolled out a patch last week and it stopped. Nothing. Bupkus. Google Play says the app is not supported by my device.
A little bit of searching led to the actual newest Kevo apk. I downloaded it, deleted the old app, installed it and voila! Back in business. The new version supports remote open and close, which I haven't checked yet- I bought an upgraded lock but it isn't installed.
So, there you have it. I have no idea why Kevo/Kwikset/Unikey didn't test with the newest phones, why they don't know it works or whatever. Their developers are much more interested in supporting iOS and the sheeple that use it, but it will work for us too!
where did you find the latest? i looked for almost 2 hours and the best i could come up with was the 0.99 beta in the google groups. had to sideload an app that lets you change your device to trick Play into letting you install it.
Googled Android kevo apk, found version 1.2.57.2p everywhere. I presumed that was the latest since it has the remote buttons on it.
yeah i saw those results as well, but none of the apk downloaders worked for me. several even said their 'device' was incompatible, which was the same problem i was having.
I'm in the same boat. I have an S7 Edge and while kevo still works with just the proximity and tap lock to open...I've never been able to get the tap to unlock/lock work. Even on my moto360 (gen1) kevo force closes non stop. Another problem I had was my old S5 was on Lollipop and it worked, but then Tmo rolled out the update to MM and now it doesn't even see the lock. I've had multiple emails to Kevo and the only thing I get is that "We're sorry, we have no plans to support MM".
If you got anything to help out with Kevo working on Marshmallow, then I'd appreciate it as well!
I might be a little late on the the subject but I had the Kevo app since the beginning from my Note 4 on KK all the way up to My Note 5 on MM. I rarely use my Moto 360 (1) to open the door but this time I did and the watch went haywire and kept showing a notification indicating that the app is no longer working. So I decided to uninstall the Kevo app and then proceeded to sync the watch and phone, stopping the annoying notification. When I went to the app store to reinstall I found the "phone not compatible"..
Well, decided to sideload to have the Kevo app to look and work the same way I had it before.. after several attempts I figured it out. 1st sideload the Kevo 0.9.58p apk, sign in, then sideload the updated version 1.2.57.2p and it will finally look and feel like the updated one on Lollipop. Sefar is right, why the devs were so lazy in checking for compatibility is beyond me but it works.!!
Sent from my SAMSUNG-SM-N920A using Tapatalk
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.
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
This question is only directed to people who had issues from day 1, please don't reply if your GPS has always been working fine.
Are folks who had GPS issues with snapdragon models still continuing to have those issues? Interested in this phone but it definitely isn't worth it to me if I can't get a reliable GPS lock. Sounds like a hardware issue, and after experiencing it with the LG G5 on 3 replacements, I'm just not willing to risk it again.
I've had this issue since day one. Google Maps, GPS locks on without issue but when the APP isn't on "focus" or the screen is locked, my GPS signal is lost. Meaning the blue GPS icon is grey but when I go back into the APP it'll re-enable itself and locks on again. Repeats everytime.
Samsung s20 Ultra US Unlocked. I've reloaded the phone with both versions, U1 and U AT&T but same result. I've used really old version of Google Maps as well as newest version, same issue. I've also tried every kind of battery settings as well.
I don't know what to do next. I was on Samsung support, in hopes they will replace my phone, ultimately said it was a Google Maps issue.....
Help?
I've had S20+ US SD model since day 1 of launch and I've never had a GPS issue....
Edit-I saw you said don't reply if your phone has been working, AFTER I replied lol. My bad.
Samsung released Firmware Update R825USQU1BTH9/R825UOYN1BTH9 for the Galaxy Watch Active 2 (SM-R825U) (on 9/23/20)
One UI Watch Version 2.0
Tizen Version 5.5.0.1
ECG, etc. !
Build Number : R825USQU1BTH9 Tizen version : Tizen 5.5.0.1 Release Date : 2020-09-23
• Advanced Running Analysis : Giving you the insights you need to improve your running form.
• VO2max : Check the maximum amount of oxygen you utilize during exercise to improve your endurance.
• Added the new Samsung Health Monitor App for ECG Measurements.
(※ Available on Galaxy smartphones with Android 7.0 and later.)
• Detect falls : Watch can send out SOS call and messages to emergency contact when a hard fall is detected.
• Enhanced Notification : Upon receiving a message notification, a chat window appears and can also view images.
• AR Emoji/Bitmoji : Send AR Emoji and Bitmoji through the watch.
• Capture : Supports scroll capture feature that automatically sends the screen-capture image to the phone.
Samsung released Firmware Update R825USQU1ATH1 for the Galaxy Watch Active2 (SM-R825U) on 9/02/20
Change Log Indicates:
· Improved system reliability
Samsung released Firmware Update R825USQU1ATF2 for the Galaxy Watch Active2 (SM-R825U) on 7/24/20
edit: I finally got the ATF2 update on my Unlocked SM-R825U on 9/24/20. After that update, the 9/23/20 R825USQU1BTH9Tizen Update Downloaded.
Samsung Unlocked Version: https://doc.samsungmobile.com/SM-R825U/XAR/doc.html
AT&T Version: https://doc.samsungmobile.com/SM-R825U/ATT/doc.html
· Device stability improvements, bug fixes.
· New and / or enhanced features.
· Further improvements to performance
Samsung's description is lacking
Does anyone have further insight to any of the updates above?
I received this too... very vague. Anyone?
I just updated and now my numbersync doesn't work. It's as if it turned it off but watch says it's on.
Ughh. .
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
LuvrGirl said:
I just updated and now my numbersync doesn't work. It's as if it turned it off but watch says it's on.
Ughh. .
Click to expand...
Click to collapse
Same here. Watch updated and now numbersync isn't working and when I try to get a numbersync code, it always fails saying "Numbersync is currently unavailable."
Hi, where do you guys live? Where is this update released? Nothing here in Sweden
yeah
Arzo001 said:
Hi, where do you guys live? Where is this update released? Nothing here in Sweden
Click to expand...
Click to collapse
nothin in norway either, we'll probably be getting it a few months after the rest of the world gets it, as always. :good:
that's why I switched to apple.
still love my active 2 though
peace
LuvrGirl said:
I just updated and now my numbersync doesn't work. It's as if it turned it off but watch says it's on.
Ughh. .
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Click to expand...
Click to collapse
So last night I tried doing a reset on my active 2 watch to see if that would help. The Numbersync option in the watch no longer showed it was on so I tried turning it on but I would get an error message saying "Mobile network unavailable". Tested it out by calling myself and sending myself a text from another phone and nothing was received on the watch. So watch only worked independently using it's own phone number.
Here's the weird thing now... this morning I wake up and started receiving calls and text messages and they started showing up on my watch! So I go into the watch menu for numbersync and it looks as if it's not turned on but somehow it's synced with my phone?
So currently it's working as if it's synced. So now I'm wondering if I should even go thru the menu option to enable numbersync even though it's working as if it's enabled?
Edit: watch receives calls and messages but because it's connected via bluetooth to my phone. Once disconnected from bluetooth the watch just works independently. Still getting same error message of "Mobile network unavailable" everytime I go into the watch menu and try to get a sync code.
rmcomer said:
Same here. Watch updated and now numbersync isn't working and when I try to get a numbersync code, it always fails saying "Numbersync is currently unavailable."
Click to expand...
Click to collapse
I'm having the same issue. Has anyone found a fix for this yet?
ssnssmom said:
I'm having the same issue. Has anyone found a fix for this yet?
Click to expand...
Click to collapse
No fix that I know of. I did several resets and went thru 2 esim changes all at the AT&T store and nothing worked. The watch has no internet connection after this last update. Phone calls work but no internet. Test it by disconnecting Bluetooth and using it standalone. You should be able to get into the Galaxy Store or update Weather and nothing works because there's no mobile data.
I ended up having to file a warranty claim thru Samsung and my watch is in route right now to Samsung.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Same problem!
rmcomer said:
Same here. Watch updated and now numbersync isn't working and when I try to get a numbersync code, it always fails saying "Numbersync is currently unavailable."
Click to expand...
Click to collapse
I have also experienced extremely long wait times for support, and usually just hang up now. I was told AT&T was aware of the problem and say it has to do with an update from Samsung and a new update from Samsung will be needed to solve the problem. I hope we can learn more!
LuvrGirl said:
No fix that I know of. I did several resets and went thru 2 esim changes all at the AT&T store and nothing worked. The watch has no internet connection after this last update. Phone calls work but no internet. Test it by disconnecting Bluetooth and using it standalone. You should be able to get into the Galaxy Store or update Weather and nothing works because there's no mobile data.
I ended up having to file a warranty claim thru Samsung and my watch is in route right now to Samsung.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Click to expand...
Click to collapse
Update:
So apparently my watch is in route back to me. Samsung repair ticket indicates the solution was "REPLACED PBA".
I don't know what PBA stands for. However, I could have sworn it was due to the recent software update since a lot of other people are having the same issue.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Call from AT&T Tech Support
LuvrGirl said:
Update:
So apparently my watch is in route back to me. Samsung repair ticket indicates the solution was "REPLACED PBA".
I don't know what PBA stands for. However, I could have sworn it was due to the recent software update since a lot of other people are having the same issue.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Click to expand...
Click to collapse
I received a call today and learned that AT&T was working on some "profile problems" in their NumberSync program that many are experiencing (such as those in this thread). The person called to verify my login name. Before the call, I did update the Galaxy Wear App (that I was told earlier should solve the problem), but that made no difference. I was also told that I would receive a return call in 24 to 48 hours when they had fixed the problem and they would help me connect to NumberSync. I am glad they escalated my ticket a few days ago; hopefully that means I am in the queue of known people with problems to have the problem fixed (if that is the problem and there is a fix). There must be hundreds or thousands with the same problem for them to give some attention to it????
LuvrGirl said:
Update:
So apparently my watch is in route back to me. Samsung repair ticket indicates the solution was "REPLACED PBA".
I don't know what PBA stands for. However, I could have sworn it was due to the recent software update since a lot of other people are having the same issue.
Sent from my AT&T Samsung Note8 [SM-N950U] using Tapatalk
Click to expand...
Click to collapse
“PBA” stands for Product Board Assembly.
I’m having the same problem as you. The watch works fine when paired with my phone, but in standalone mode I can’t get any mobile data, and I can’t activate Numbersync.
Do you know if your watch overheated when downloading the update? While the update file was downloading to my watch, it overheated and shut itself off because the file was so large. After I restarted the watch, the update completed and everything was working except mobile data. I’m wondering if this has something to do with it.
Please let us know if everything works after replacing the PBA. I may need to send my watch in to Samsung for a replacement as well.
Zagzagel said:
“PBA” stands for Product Board Assembly.
I’m having the same problem as you. The watch works fine when paired with my phone, but in standalone mode I can’t get any mobile data, and I can’t activate Numbersync.
Do you know if your watch overheated when downloading the update? While the update file was downloading to my watch, it overheated and shut itself off because the file was so large. After I restarted the watch, the update completed and everything was working except mobile data. I’m wondering if this has something to do with it.
Please let us know if everything works after replacing the PBA. I may need to send my watch in to Samsung for a replacement as well.
Click to expand...
Click to collapse
I can't remember exactly if it overheated or not. I know it did reboot but don't remember if I myself turned it back on or if it rebooted by itself after the update...
I"ll come back and update once I get my watch back and can confirm.
LuvrGirl said:
I can't remember exactly if it overheated or not. I know it did reboot but don't remember if I myself turned it back on or if it rebooted by itself after the update...
I"ll come back and update once I get my watch back and can confirm.
Click to expand...
Click to collapse
Thanks! Also, what kind of phone are you using? I am using my Galaxy Watch Active 2 paired with an iPhone 11 Pro Max, or setup independently in standalone mode. You can set the Watch Active 2 up in standalone mode by scrolling down on the watch’s initial setup screen and pressing the “?”. Either way, I am unable to receive mobile data after the update.
The reason I ask about the type of phone you have is when I called AT&T support, they said it was impossible to receive mobile data if the Watch Active 2 is paired with an iPhone or setup in standalone mode, but this doesn’t make sense because it was working fine for me before. I’m wondering if the update disables mobile data unless the Watch is paired to an Android phone.
Zagzagel said:
Thanks! Also, what kind of phone are you using? I am using my Galaxy Watch Active 2 paired with an iPhone 11 Pro Max, or setup independently in standalone mode. You can set the Watch Active 2 up in standalone mode by scrolling down on the watch’s initial setup screen and pressing the “?”. Either way, I am unable to receive mobile data after the update.
The reason I ask about the type of phone you have is when I called AT&T support, they said it was impossible to receive mobile data if the Watch Active 2 is paired with an iPhone or setup in standalone mode, but this doesn’t make sense because it was working fine for me before. I’m wondering if the update disables mobile data unless the Watch is paired to an Android phone.
Click to expand...
Click to collapse
I have a Samsung Galaxy Note 8 and both my watch and Note 8 were purchased directly with AT&T and have had continued service since day 1.
That doesn't make sense at all actually because if it's an LTE watch and it has it's own line, it's supposed to have all the functions available - and that includes phone calls, texts, and internet (data).
My Numbersync issue is resolved
Tumbleweedtoo said:
I received a call today and learned that AT&T was working on some "profile problems" in their NumberSync program that many are experiencing (such as those in this thread). The person called to verify my login name. Before the call, I did update the Galaxy Wear App (that I was told earlier should solve the problem), but that made no difference. I was also told that I would receive a return call in 24 to 48 hours when they had fixed the problem and they would help me connect to NumberSync. I am glad they escalated my ticket a few days ago; hopefully that means I am in the queue of known people with problems to have the problem fixed (if that is the problem and there is a fix). There must be hundreds or thousands with the same problem for them to give some attention to it????
Click to expand...
Click to collapse
Last Friday I called AT&T about my NumberSync issues after my Active2 watch update. They said they'd call back when they researched it. I received a call this afternoon from AT&T about profile issues due to the new watch software and now my NumberSync issue is resolved. I was able to get my Sync Code and sync up my Galaxy s20 Ultra without any problems. A minute or so after syncing, I received tons of text messages that were sent to my phone from last week before the watch update.
rmcomer said:
I also received a call this afternoon from AT&T about profile issues due to the new watch software and now my NumberSync issue is resolved. I was able to get my Sync Code and sync up my Galaxy s20 Ultra without any problems. A minute or so after syncing, I received tons of text messages that were sent to my phone from last week before the watch update.
Click to expand...
Click to collapse
Congratulations and thanks for this helpful information! I have yet to receive a call to finally resolve the issue, and I just tried to get a code and still get the same error message. Perhaps tomorrow I will be fortunate to receive a call too. I will let everyone know. I will also be curious to know if those who sent their watches in for warranty work will have a seamless syncing with their new or refurbished watches. At least I now know where the problem lies and that AT&T has found a solution at least for some! Thanks again! BTW: I was thinking of upgrading to the s20, but did not want to do so if this problem continued..
guys can u tell me in R825U unlocked which csc u used ...as iam on R825F (XSA) and want to shift to USA..unlocked
And do anyone has the latest firmware that can be used to after changing the CSC region.
rmcomer said:
Last Friday I called AT&T about my NumberSync issues after my Active2 watch update. They said they'd call back when they researched it. I received a call this afternoon from AT&T about profile issues due to the new watch software and now my NumberSync issue is resolved. I was able to get my Sync Code and sync up my Galaxy s20 Ultra without any problems. A minute or so after syncing, I received tons of text messages that were sent to my phone from last week before the watch update.
Click to expand...
Click to collapse
As of today, August 7, no one has called me back to resolve this issue and numbersync still does not work for me. When trying to call or chat with ATT Support, I am told they have a high call volume. So, I have been promised by tech support that they have a solution and that I would be called within 48 hours and still no call. After trying several times, it appears they have to fix the problem and call you to fix the problem, because I still cannot get a code. I hope we can hear some good news from someone that we can finally get a code without needing a tech support call. I suppose we will get no tech support calls over the weekend.