Hey guys,
I'm with Vodafone (Australia) and lately I've been working in my garage a fair bit where I don't have reception. During this time numerous people have called me, however I don't receive any notifications of missed calls at all. And when I go into phone log it doesn't show any call logs.
Is this a setting on the phone or should I contact Vodafone to get this sorted?
Cheers
Good question Jonno. I'm also with Voda & honestly couldn't remember if this feature was working properly or not as I haven't missed a call for ages (people know not to call me at unsociable hours when I have the phone switched off ).
Soooo...I plonked my mobile broadband sim into my Nokia backup phone, turned my SGS2 to flight mode (to mimic not having coverage), called it from the Nokia & let it ring half a doz times then hung up.
Switched the SGS2's radio back on & haven't received a missed call notification (it's been almost 5 minutes). I've searched high & low thru my call settings & can't find anything that would turn such a feature on/off so I'm betting it's a network related thing. I'll update this post if the missed call notification comes thru at any stage tonight.
Yeah I've never got any missed call notifications with the phone. I have people trying to get on to me regarding some recent job applications so it's not very useful if I miss their calls and don't know who to call back!
Might try calling Voda tomorrow to see if they know anything about it...
Jonno...The thick plottens
I was ferreting around in the dialer/call settings & had a look at the call forwarding settings. Basically, forward when busy/unanswered/unreachable is set to that Voda number people who try to call you get when you don't answer & it asks whether you want Voda's "call catcher" to txt the person you're try to call to let them know they missed your call (with the number to call back on).
When I try to disable this feature on any of busy/unanswered/unreachable it tells me the network doesn't allow the feature to be turned off. So it seems Voda thinks their way of people being able to notify you by txt when you miss their call is the best way (only way by the looks of it) for this situation to be handled.
So I'd say people obviously haven't been choosing the option to send you a notification txt (via Voda's call catcher) and have simply been hanging up when they've been unable to reach you.
I guess the only way to get around this is to tell people to use the send notification txt option or to simply send you a txt themselves to say they tried to call & couldn't get you.
Unless you want to have fun calling Voda's uber helpful support ?
I just replaced my Verizon S4's camera module. Afterwards no more voice calls. However LTE data and text both work fine. I can also see the signal bars and they are just as strong as before. If I make a call no dial tone no sound but it will say "dialing..." for several seconds before "hanging up". No calls are actually sent to other phones. When someone calls it, phone won't react at all. It's as if the voice call feature is completely gone. Yet sms and data are both fine. Speaker phone, headphone, microphone and vibration also work. Also GPS won't get a fix now - it will keep searching forever until I turn it off. I wonder if it's related to the no-call issue? What part(s) did I accidentally break during the repair process? If I knew what went wrong I can probably find replacement for it. So far everything else works. Please help!
Guys, I have a strange issue, 3 hours of IDLE time on my phone and when you call my number from other phones, it says it is Switched off!!! The network signal is full, strangely if i callback someone it rings, and then if you call me back, my phone rings normally!
I do not know what the issue might be here, I have tried resetting the phone, reinserting the SIM card. Changing the Networking setting to only GSM, but nothing helps!
This is not good, and it is causing me lot of headache, as I am missing important Client calls anyone with a remedy?
Guys .... anyone who can help me out here ?
zeph_syk said:
Guys .... anyone who can help me out here ?
Click to expand...
Click to collapse
Sounds like a network issue. Make sure you don't set the network mode to automatic/auto connect. Other than that, I can't think of much.
Edit.
Check your edge preferences and turn off any of the flip to mute functions. Also double check call rejection in Phone to see if it's rejecting calls for some reason.
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
mghtymse007 said:
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
Click to expand...
Click to collapse
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
pdqgp said:
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
Click to expand...
Click to collapse
Sorry to hear you have a&t. Connected remotely and call forwarding are two completely different things as you may know but regardless of the matter its not Samsungs fault. Your device showed that it was connected remotely therefore it was....the real issue is your wireless carriers crappy network not pushing your notifications plain and simple not your watch or your phone. Both are working just fine from what you've stated which leads to the fact that its your network connection. Only GSM networks are capable of auto call forwarding which as I stated is completely carrier network based. No offense but at&t sucks anymore and havent seen these issues with anyone but at&t customers. Its on at&ts end. Call and complain about your issue but unfortunately I doubt they will do crap which is why I left at&t 3 months ago. Hope you can get them to figure it out.
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
pdqgp said:
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
Click to expand...
Click to collapse
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
rickleasa said:
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
Click to expand...
Click to collapse
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
pdqgp said:
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
Click to expand...
Click to collapse
ok glad to hear but that didn't work for me as when i went to call setting on my phone i still received the sim network error until i did the restore but glad it worked for you
djc-wi said:
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
Click to expand...
Click to collapse
I finally figured out this only happens to me after I have Bluetooth paired to my car or a headset. Only happens every once in awhile. If I reenter my car and turn it on, as soon as Bluetooth reconnects it's back to working. The problem will come back if I don't reset my phone. Then all is fine for a few days. In my case obviously the bug is in gear S bluetooth not my phone or my car as the same thing at times will happen with a Bluetooth headset.
SaintCrispin said:
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Click to expand...
Click to collapse
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
foulmouthedruffian said:
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
Click to expand...
Click to collapse
Hah I'm glad it's working for you now.
Hello!
I've tried to find an answer to my problem in this forum, but no luck. I'm on stock Pie, latest build for the Nordic region XXU2CSC8. SM-G965F. No root.
Under Oreo, when making calls to the last dialled number over my car Bluetooth device (ST Buddy R20) , the display would wake up, showing details of the person I was calling. A nice feature which gave the opportunity to verify that I was actually calling the person I wanted. Under Pie, the display does not wake up when making a call the same way. It wakes up, however, when hanging up (still via the Bluetooth device). Is this normal? Am I missing a setting somehow? Is it possible to change settings somehow giving me the same function that I had under Oreo? I'm thankful for any input.
Regards,
sten_amund