Hello,
I got a Gear s2 and i love it but recently its starting to act bizarre. Randomly when people call me it goes straight to voicemail. It doesn't even give me a notification on my phone that i got a miss call. Sometimes it goes straight to my gear s2 and shows nothing on my phone and sometimes the opposite. I dont know whats wrong with it. has other people been having the same issue? My gear s2 is the 3g version, ATT, and i do have number sync on! All help is appreciated !
Thank you
On the watch, under connections If I turn mobile networks from automatic to always on, the mobile data selection in the same menu branch usually goes green. If not turn it on manually and then things start working. However, If I reject a call using the watch it hangs up on the caller without voicemail. Letting the call ring until it automatically goes to voicemail works. Turning off the Bluetooth also makes things work without the above change, but I think that uses more power and for sure more mobile data from att.
Related
Is the call forwarding working on your ATT S2 3G watches? On mine sometime is working but mostly is not working. It is only working when i force it to work. What i mean with "force it" is i either turn off the Bluetooth connection on the phone or the watch and i watch the steps ... When the popup from the gear manager shows up that the phone is connected remotely, on the popup i get two buttons, "OK" and "Settings". If i press "OK" then the call forwarding works. If i do it unintentionally (really forget my phone at home or in the car), then the call forwarding fails four out of five attempts. Only once i had it forward the calls without me fiddling with settings or popups ... The ATT Gear S was the same way and i had to return it ... I was lucky that time that the manager allowed me to return it after the 14 day window. I do not want to be in the same situation (wait for the 14 day window to expire) and then wrestle with the ATT store manager ...
Any tricks or steps that i'm missing? I'm pairing it with ATT S6 Edge ... I did factory reset the phone and the watch ... In the Gear Manager "Use remote connection" is ON and "Auto call forwarding" is setup with the number of my watch and is ON. If i turn off the bluetooth on my watch, then i can receive and place calls with my watch number, so the watch sim is active ...
As of now, it seems to me that the ATT Gear S2 3G functionally is no different that the ATT Gear S 3G, which was nightmare to get it to forward calls. Just visually improved, but it seems that Samsung didn't worked out the issues with ATT on ATT's backend to iron out the kinks ...
I hope i'm wrong but i have very narrow window to test it that is working ...
I wonder if its an ATT issue, as my T-Mobile version, using a Nexus 6 phone, works perfectly, every time..
its weird that using a Samsung phone you would have issues with that..
bormasina said:
Is the call forwarding working on your ATT S2 3G watches? On mine sometime is working but mostly is not working. It is only working when i force it to work. What i mean with "force it" is i either turn off the Bluetooth connection on the phone or the watch and i watch the steps ... When the popup from the gear manager shows up that the phone is connected remotely, on the popup i get two buttons, "OK" and "Settings". If i press "OK" then the call forwarding works. If i do it unintentionally (really forget my phone at home or in the car), then the call forwarding fails four out of five attempts. Only once i had it forward the calls without me fiddling with settings or popups ... The ATT Gear S was the same way and i had to return it ... I was lucky that time that the manager allowed me to return it after the 14 day window. I do not want to be in the same situation (wait for the 14 day window to expire) and then wrestle with the ATT store manager ...
Any tricks or steps that i'm missing? I'm pairing it with ATT S6 Edge ... I did factory reset the phone and the watch ... In the Gear Manager "Use remote connection" is ON and "Auto call forwarding" is setup with the number of my watch and is ON. If i turn off the bluetooth on my watch, then i can receive and place calls with my watch number, so the watch sim is active ...
As of now, it seems to me that the ATT Gear S2 3G functionally is no different that the ATT Gear S 3G, which was nightmare to get it to forward calls. Just visually improved, but it seems that Samsung didn't worked out the issues with ATT on ATT's backend to iron out the kinks ...
I hope i'm wrong but i have very narrow window to test it that is working ...
Click to expand...
Click to collapse
Wait for Numbersync to start, then it wont be an issue at all. Gear S2 was supposed to launch with it, but it got delayed a bit. I am hearing next month for the role out. Then you watch will share the same phone number as your phone. Problem solved.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Is Numbersync an ATT only feature, or is that something native to the Samsung Watches?
Wondering if it will be that way on T Mobile also
thanks
wase4711 said:
Is Numbersync an ATT only feature, or is that something native to the Samsung Watches?
Wondering if it will be that way on T Mobile also
thanks
Click to expand...
Click to collapse
The NumberSync-like feature is supported by the hardware inside the S2 3G. In Korea, a similar feature is already being utilized. The USA carriers just need to create & activate such a feature.
Sent from my Nexus 5X using Tapatalk
thanks, so it will probably depend on how many of the 3G watches get sold; if its not alot, then the carriers probably wont bother activating this feature..
drmacrofish said:
Wait for Numbersync to start, then it wont be an issue at all. Gear S2 was supposed to launch with it, but it got delayed a bit. I am hearing next month for the role out. Then you watch will share the same phone number as your phone. Problem solved.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Thanks. I did not know about this Numbersync. I'm afraid that the carriers here will not bother about this and besides that i will not wait for a month. I bought (and then returned it) Gear S because of the 3G modem ... I do not need a always tethered watch ... I bought Gear S2 3G with hope that Samsung and ATT worked out whatever was messed up on ATT's backend. If the watch doesn't have a 3G/LTE modem i do not need it ...
Another return it is then ...
NumberSync is specific to AT&T (it is a network service not a Samsung feature) and will let you use your primary smartphone number for both your phone and Gear S2. Other carriers have said they are working on similar services. It isn't a call forwarding solution - calls are routed to both watch and phone simultaneously and neither has to be powered on for the other to make/receive calls. Also calls from either show as the same caller ID. The call forwarding issue is odd since the commands issued to the network to start call forwarding are the same regardless of you forcing it off bluetooth.
I was having the same issue with my Gear S paired to my Note 5. When they seperated it would be random whether call forwarding turned on or whether they'd reconnect via BT when back in range. The last Note 5 update AT&T pushed out fixed it and they connect/re-connect properly 100% of the time. Here's a workaround I used that solved the problem for a short period of time. Go in to Application Manager and clear data on the Bluetooth app. It doesn't erase your devices or settings it appears to clear the cache. It worked right for a week then I'd have to reset the app again.
Anyone here using tmo with their S2? when in stand alone are you able to take/make calls and have them look like they're coming from your cell number?
(trying to figure out if tmo screwed my setup)
if you are connected via bluetooth, your calls made from the watch should look like your cell phone number
if you are in "stand alone" mode, with no phone connected, it should look like your watch phone number is making the call
how do text messages from your cell get to your s2 if in stand alone? (just on the s2 number?)
they dont get forwarded to your watch when in stand alone if the text is to your cell phone number, since your watch has a different phone number than your cell..
tmo mislead me then. good times. they told me in stand alone all my calls and texts would use the same number as my ph. thanks for the info.
If you have remote connection on, they do forward.
where do you enable that?
thanks
On your gear, go to settings-call-auto forward I believe will do it
I believe that just forwards calls, NOT texts..
I have mine linked with a moto x pure. Although it doesn't save them in the messaging app, I can reply and read, and get texts remotely
on my nexus 6. no matter what settings I use, I do NOT get texts forwarded to my watch; everything else, like emails, facebook, etc does get forwarded, but no texts..
Mine works in standalone with watch number and with cell number when connected with Bluetooth. When remote connected all calls forward after 4 rings on my cell and all text messages are forwarded. I had to call t-mobile to get it working properly. They said the had to change the way the auto forwarding was setup on the network. I would suggest calling them if yours doesn't function as mine does
Sent from my SM-N920T using Tapatalk
thats a good idea, since mine doesnt work that way now..
thanks:good::good:
wase4711 said:
I believe that just forwards calls, NOT texts..
Click to expand...
Click to collapse
On a Samsung Note 5 my text get forwarded to me when I am in stand alone mode. My phone is on Verizon, my Gear S2 is on T-Mobile. When I leave my phone at home (phone is on), my text are forwarded. If I turn the phone off the text do not come through. When I leave my phone on and am using the Gear S2 in standalone (physically separated from my phone), I get all notifications, calls, text, social media, etc...
good news/bad news.
I've got everything working as I'd hoped. I had to trade in my LG G3 and now have a samsung phone. I see more apps in the gear store, and I noticed when I reset the watch, I now have different options in the call forwarding area than i had before. I honestly believe that the watch was made to work with samsung gear only...and any other handsets are an afterthought.
Also, it works on it's own with autoconnect. I turn off bluetooth, and the watch goes to stand alone, and once remotely connected tells the handset to fwd calls/sms to it.
I am straying here from the original issue but I think this is related. I have a Moto X Pure (MXP) on AT&T. I have the AT&T Gear S2 (GS2) LTE. I am going to be verbose with this. Both have unique SIM's, IMEI's, phone numbers. I have successfully forwarded the MXP# to the SG2# when connected over the LTE network. MXP will ring 4-6 times, then roll over and ring to SG2 2-4 times. Voicemail goes to SG2.
I have used the watch's settings and S. Gear app settings to forward/unforward (so I thought). I have recently noticed I am not getting voicemails on my phone (doesn't happen much anyways as I don't get many calls I don't pick up). Odd part is that more than once, the voicemail on the GS2 only pops up when I disconnect bluetooth connection between devices. I have figured out this is likely tied to when the GS2 is connected via bluetooth to the MXP, it acts in headset/handsfree mode and controls my MXP dailer.
When I go into S. Gear app, under call forwarding, I see "Turn Off" as "Deactivated XX:XX". When I push Turn On, I see "a request has been made..." on the MXP and "Request has been made..." on the GS2. Toast on MXP after success is "Call Forwarding, Registration was successful". Turn On shows "Activated XX:XX". Then I push Turn Off, and see "A request has been made...." on the MXP, then a "Call forwarding, Connection problem or invalid MMI Code" on the MXP, and then a "A request has been made..." on the GS2. No error on the watch. Funny is that under Turn Off, it shows "Deactivated XX:XX" again.
Calls first go to MXP, then to GS2 and end up in GS2 voicemail. When to MXP Dailer settings, Calls, Call Forwarding. Interestingly, 3 of last 4 options for call forward show forwarding to the GS2. When I click on any of the 3 of the 4 forwarding, I can push Turn Off. Error toast shows up as "Your operator doesn't support disabling call forwarding when your phone is busy". What constitutes "busy"?...and why can't I turn this off?
---------- Post added at 06:38 PM ---------- Previous post was at 06:24 PM ----------
UPDATE: I went to the Call Forwarding wiki and used some of the codes to help. ##67#, ##61#, ##62# were used successfully. All is back to normal. I can pick up via the watch, transfer to the phone, reject as needed. Voicemail goes to the MXP as expected. Network really wouldn't let go of the number. I am sure there is a good reason for that but don't get why.
Samsung Galaxy S7 on Tmobile SM-G930T android version 6.0.1
I can make outgoing calls but I cannot receive any calls, they go straight to voicemail
If I restart my phone I can receive calls for a while but then after being locked for a bit the calls next come through. I wake the phone up and even then the call still wont come through until i restart it again.
Anyone know why this happens, it sure hasnt always happened?
No one has any tips on this?
I turned wifi calling on and turned off location and it works every time now.
Not sure why. I hate wifi calling and id like to keep my location on but whatever, i need to receive calls.
I found problem using "Do Not Disturb", custom settings staying in effect even when turned off! Change to "Accept All Calls" and you will be able to receive callers not in your contact list. BUG??
-Micro
Hello,
FIrst time gear LTE user here. Call forwarding does not seem to be working for me. In the the Gear app i put the new phone # for my Gear S3 under the ""number setting" field and turn it on. Then I disconnect BT by turning it off on the phone. The watch goes into stand alone T-mobile mode with good lTE strength. I then get a message on the watch that says "calls are not being forwarded to Gear Tap OK to try again", and I do and the message comes up again immediately.
So am i missing something? Did I skip a step? There are no instructions on this in the manual...
Any help appreciated.
thanks,
Not sure if it just takes time. I got my Gear S3 yesterday and had that same message. Today, I hadn't changed anything and it is working correctly now.
Ok- I found I just was not waiting long enough for it to forward, but it does eventually forward to the watch, and if you miss the call on your watch the call will go to your watch VM.
Sent from my SM-G935T using XDA-Developers mobile app
Ok, so Tmobile finally got my digits working and it's awesome to be able to leave the house without my phone. Now with spotify, I don't have to take my phone to the gym anymore. I just hook my BT ear buds and I have everything I need. I can even use it like a phone with a BT headset and when I call people see as if I'm calling from my phone.
Now with that being said, I have only had one issue so far but it's not a digits or tmobile problem. The way I figure I'll just live with it. The nature of having your watch share the same phone number means you get duplicate notifications. For example, if I'm connected to the phone through Bluetooth or I have call forwarding set to get my notifications from my phone and somebody sends me a text, I get the notification from the phone and I clear it. Now when I disconnect from the phone. My text messages and missed calls show up as notifications from the watch.
It makes sense. If the watch is sharing the same phone number, the phone will forward the message to the watch but the watch is also receiving the message to. I know there is an option to block but I want to be able to get my texts and missed calls if I turn off my phone and am using the watch in stand alone mode.
I figured a fix though for those who use the forwarding function and will always have stuff forwarded from the phone is to block the watch notifications. My solution it to just go to the text messaging app and clear them manually, ignore them or just delete the message conversation.
Just something to make people aware of when using Digits if you haven't signed up for it already. I personally like it so far and will probably pay for the service if it's reasonable.
I had a heck of a time getting tmobile to set it up right but when they finally got it working I like it now.
I'm having the same issue...wonder if there's a way to stop the dual notifications?
Just for my S3 frontier and having the same issue. Any fixes?