Hello, I have a Nexus 5 D820 running 6.0 and I'm having some connection issues when it comes to long distance calls, especially 1-800 number and some local calls. What its doing is i will be talking and i will have LTE full bars great signal and bam drop call. Sometimes i cant even get the number to go through. Thoughts?
I flashed back to 5.1.1 and its doing the exact same thing, I can call local like my wifes phone or parents and thier house but if I call even not a 1-800 number it wont even connect or it will ring once and hang up.
Thoughts on what to try or what it could be would be great..
Fixed
Ok, I got it fixed... This is my second time calling and this young kid knew what it was right off the bat! Its called (HD Voice) and what he said was its been causing trouble and is in the testing stages just like when LTE came out and was buggy... BS I been dealing with this crap for a few weeks! Anyway, he disconnected it and had me shut down my phone so he could reset it and called me back and had me try some of the numbers that I couldn't get to work and they worked great so that was it for sure.
Hope this helps someone if they run into the same thing...
I'm currently using the 3g AT&T Galaxy Watch S2 with a NumberSync on and for whole day, I wasn't able to get any calls.
Whenever someone calls me, it directs to 'this number cannot receive a call.'
It's weird since I can still receive a text message and I can still call from my end, just unable to receive any call, not even a voicemail. (Not getting on my phone and my watch)
And when I disabled the NumberSync, my phone suddenly worked like a charm.
NumberSync has been working nicely until today and I'm wondering what's going on.
Anyone has the same problem as me?
P.S. I talked to AT&T Customer Support for like 2 hours and they were not able to solve the issue. What my rep told me was it seems like an error from the AT&T Service side.
Mine did that too today!!!
So I found a quick fix to this issue, I turned the bluetooth off on my watch (with NumberSync On) and it seems working.
And the watch only says "Connected Remotely AT&T" rather than connected with bluetooth.
BTW, when I tried the combination of Bluetooth on + NumberSync Off, I couldn't get a call. It might have been just one day but at least this combination used to work when I found the problem 3 days ago. Now it just doesn't.. Only option I have for me right now is to completely disconnecting with bluetooth.
I have no Idea why there's a problem between having bluetooth on and getting a call.
This really disturbs me since disconnecting with bluetooth limits a lot of stuff, like I cannot control my phone music on my watch ..
I don't know who's to blame as in AT&T or Samsung but I hope this issue gets fixed.
P.S. I actually got an exchange on my watch thinking it might be a manufacturer error but nope, same problem.
paoloroeseke said:
Mine did that too today!!!
Click to expand...
Click to collapse
Hey guys!
Is there any way to force remote connection using wifi instead of BT? For some reason, my phone + gear s3 doesnt connect remotely anymore .. It can only connect via BT. It started happening today. Last night it was fine.
I go to my basement all the time and my BT disconnects due to distance (if i left my phone).
Now im worried its probably a defect. Both my phone and s3 are in the same wifi network. I tried using a different wifi network as well.
Thanks in advanced.
warpgatex said:
Hey guys!
Is there any way to force remote connection using wifi instead of BT? For some reason, my phone + gear s3 doesnt connect remotely anymore .. It can only connect via BT. It started happening today. Last night it was fine.
I go to my basement all the time and my BT disconnects due to distance (if i left my phone).
Now im worried its probably a defect. Both my phone and s3 are in the same wifi network. I tried using a different wifi network as well.
Thanks in advanced.
Click to expand...
Click to collapse
Have you tried a reset of the Gear?
Tel864 said:
Have you tried a reset of the Gear?
Click to expand...
Click to collapse
Im trying now.
I don't remember my S3 ever remotely connecting via WiFi. It would do it over the cellular network once I breezed out of Bluetooth range, but it never told me about WiFi.
In fact, the remote connection via cellular is awfully intermittent. The only thing that seems to restore it is a reset of the S3. Even after that, though, I've never seen mine remotely connect on WiFi.
The whole remote connection thing seems to be dicey at best, in my experience.
SFVDan said:
I don't remember my S3 ever remotely connecting via WiFi. It would do it over the cellular network once I breezed out of Bluetooth range, but it never told me about WiFi.
In fact, the remote connection via cellular is awfully intermittent. The only thing that seems to restore it is a reset of the S3. Even after that, though, I've never seen mine remotely connect on WiFi.
The whole remote connection thing seems to be dicey at best, in my experience.
Click to expand...
Click to collapse
I have the opposite mine seems to connect remote over wifi just fine but not really over cell connection.. i have not tested tho.. i will today and update you guys.
Yeah I have never seen it connect to the Phone via WiFi... only via BT. If the watch loses range, it will connect to a Wifi (if it is enabled, Always on or Auto), but would not communicate with the phone. So it's "Standalone, but with wifi".
It worked like this out of the box. Bought the GearS3 in the US. I'm not sure if connecting to phone via wifi is even possible....
I can confirm that it does connect via WiFi although I was totally unaware that it could.
Yesterday I returned to my house from visiting my daughters house and realised I didn't have my phone. Thinking that I had dropped my phone in the car I used my house phone to call my mobile and my S3 on my wrist started ringing. This convinced me that although I couldn't hear it ringing my phone must be in the car but then my daughter answered my phone that I had left at her house! So my mobile was connected to her WiFi and my S3 was connected to my WiFi, which are 30 miles apart, yet but my S3 was synced with my phone.
Half Colin said:
I can confirm that it does connect via WiFi although I was totally unaware that it could.
Yesterday I returned to my house from visiting my daughters house and realised I didn't have my phone. Thinking that I had dropped my phone in the car I used my house phone to call my mobile and my S3 on my wrist started ringing. This convinced me that although I couldn't hear it ringing my phone must be in the car but then my daughter answered my phone that I had left at her house! So my mobile was connected to her WiFi and my S3 was connected to my WiFi, which are 30 miles apart, yet but my S3 was synced with my phone.
Click to expand...
Click to collapse
That's really neat! I've never experienced that.
Samsung ought to create a small app that will reestablish whatever mechanism there is to make the remote connection thing reliable. It's fantastic when it works, but if you're not on Bluetooth, it's a crap shoot if it'll work or not.
One other observation. In my experience, updating Samsung Pay on the phone seems to break whatever mechanism there is for reliable remote connection. Even after logging in/verifying the Samsung Account, it seems to break it. Weird.
Dan
Yeah, it totally blew me when my daughter answered my phone because I was convinced it must be connected by Bluetooth and so in the car.
Half Colin said:
Yeah, it totally blew me when my daughter answered my phone because I was convinced it must be connected by Bluetooth and so in the car.
Click to expand...
Click to collapse
Now wait a min lol.. mine does not do that.. only get notification not calls.. i have a vzw note edge.. what kind of phone do you have? I was thinking when i bought the watch that it would take calls over wifi so i could basically leave my phone in my office and roam around the office and still take calls all on wifi.. that does not seem to be the case for me anyway.. guess i need to do some more testing. If it works like you say then this is great news.
---------- Post added at 08:59 AM ---------- Previous post was at 08:58 AM ----------
also mine says standalone when it has lost the BT from the phone says its connected via wifi..
I didn't say I answered the call on my S3. My S3 buzzed and showed call from home but before I could do anything else my daughter answered the call on my phone. So the S3 was obviously connected via WiFi and internet to my phone (Samsung A5) but what functionality that gives I don't know. Although, thinking about it I did hit reply on the S3 and the home phone rang, which I didn't answer, so who knows.
Half Colin said:
I didn't say I answered the call on my S3. My S3 buzzed and showed call from home but before I could do anything else my daughter answered the call on my phone. So the S3 was obviously connected via WiFi and internet to my phone (Samsung A5) but what functionality that gives I don't know. Although, thinking about it I did hit reply on the S3 and the home phone rang, which I didn't answer, so who knows.
Click to expand...
Click to collapse
Gotcha.. still sounds like you could have took the call.. maybe.. Thanks.
Yep, the weird thing is though when I'm at home and out of bluetooth range the S3 goes into WiFi standalone mode although both phone and S3 are on the same WiFi network. Yet, yesterday the S3 was showing connected which was why I was convinced the phone must be near.
So i just tested and i walked across the office and my watch says connected remotely. I called my cell and my S3 did not ring.. it did tell me i had a missed call tho and i got an email while i was over there..
Did you have a reply option to the message because I did? When I tapped reply it said 'connect remotely' to which I said yes.
Half Colin said:
Did you have a reply option to the message because I did? When I tapped reply it said 'connect remotely' to which I said yes.
Click to expand...
Click to collapse
For the missed call? or the email? Not sure about email but the missed call notification i tap on it and it pops up saying connect to phone via Bluetooth ? i get a x on the left and a check on the right.. if i hit x nothing happens and if i hit the check it will try to find my phones BT.. Just tested an email.. all i have when i scroll all the way down is delete but i can hit the dots on the right and i have a reply option.. i was able to send a quick reply to myself.. this is all while my phone says connected remotely..
I was just checking the connection dialogue and it says "... remotely via mobile data or Wi-Fi."
Dunno how I missed the Wi-Fi part.
The missed call. All my calls and taps happened over a matter of seconds whilst I was more concerned with finding my mobile than what the S3 was actually doing. The fact that it was doing anything in relation to a call to my mobile was pointing me towards the phone being close. So it seems from your testing, and nothing I experienced really contradicts that, that when you're connected by WiFi you do only get notification of a call. I did tap reply to the missed call and the house phone rang but I can't say for sure that the call was from the S3 because I never answered it and didn't check the S3 again because I was leaving to return to my daughters house.
By the way guys, I had to factory reset my S3 and remote connectivity worked again. I now learned to backup my S3 if this happens again. I rely mostly in remote connectivity thats why this is a big deal for me.
Mind you that I confirmed that I'm connected to WIFI on my phone and I can browse on it too. It just doesn't connect the phone.
I just hope there is a way to force remote connectivity in the settings so I know what going on!
I entered feedback into the Samsung support website about this particular problem. I explained that the remote connection between the S3 and my phone is intermittent. I was very dismayed to get a stock, canned answer back about rebooting my router. This is the second time that I've attempted to address this, once through the chat client and once through email. I'm very disappointed with Samsung's support considering the size of their company. Alas, guidance on how to correct this problem does not appear to be forthcoming.
I had massive problems getting my S3 Frontier to connect for calls. Text and email were no problem. I spend almost a month screwing around with T-Mobile Digit help folks to no avail. Finally, out of the blue, it hooked up. Always figured it was due to some magical switch they threw at TMobile. Apparently thats not the case.
I put a new watch face from GWD on the watch and inadvertently left Debugging on afterwards. Apparently that was all it took! I found this out because, today, I noticed Debugging on and switched it off. Suddenly I couldn't call anymore. Turned it back on and I can.
So if you get a problem making calls on your S3 make sure Debugging is in the ON position. Just a heads up...
Have a very weird problem, and think it is because of any app...
I use a galaxy tab s4 lte as a phone, it is a fully functional phone oversized... it is great, and im using tablest as phone 3 or 4 years ago... first was galaxy tab s2 lte, then s3, and now s4
S2 worked great... S3 worked great but from march of this year, randomly phone disconects fron network just to receive calls.... sms, 4g and wifi always work, but canr receive calls till i make a call... it is like it disconnects from network... i notice that, because i have (from the times of s2) my phone forwarding calls to my wife's phone when my phone is turned off or im in a plane for example...
But with tab se, from march, i was in home with my wife and someone that call me ringed directly to my wife phone... a lot of times saw that... but when i place a call... it start receiving calls again...
Went to tmobile, changed the sim and same problem...
Bought a new S4 lte ($1000) and from the day 1 same problem...
Any help? Im pretty sure it could be any app... but dont know where to start