I have a Galaxy S10+ and Tab S4 Wifi (both US models unlocked). I have the call and message continuity feature enabled on both devices.
Regarding calls, Incoming calls work perfectly fine.
When I make an outbound call from the tablet, the call gets dialed out successfully from the phone but the audio shifts to phone and no longer stays on the tablet. So, I can only dial the number out on the tablet, but I have to use the phone to talk. Is this behavior expected (or) a software bug?
Both devices are running the latest patches.
Thanks!
Related
I have two Sprint phones. My primary phone is the Note 2 with my main phone number being my Google Voice number. The second phone is an S3 that is also set up with Google voice and pointing to my main phone number. Most features are working but I have an interesting problem that just started when I added the S3. Specifically, when I have both phones on sometimes the phone rings first on the S3 which may then answer the call and send the message to the Sprint Voice message app and not to Google voice. This is problematic since I often keep both phones on. Any ideas?
My second issue is when I reject a call by swiping the screen to reject the calls goes go the sprint voice message and not the Google.
Other than these issues everything else works. Calls go to both phones okay and calls out of both phones work okay and the caller I'd shows my Google voice number.
inmnbob said:
I have two Sprint phones. My primary phone is the Note 2 with my main phone number being my Google Voice number. The second phone is an S3 that is also set up with Google voice and pointing to my main phone number. Most features are working but I have an interesting problem that just started when I added the S3. Specifically, when I have both phones on sometimes the phone rings first on the S3 which may then answer the call and send the message to the Sprint Voice message app and not to Google voice. This is problematic since I often keep both phones on. Any ideas?
My second issue is when I reject a call by swiping the screen to reject the calls goes go the sprint voice message and not the Google.
Other than these issues everything else works. Calls go to both phones okay and calls out of both phones work okay and the caller I'd shows my Google voice number.
Click to expand...
Click to collapse
Only way to make sure to resolve this is tie your voice account to only one phone. As for the voicemails going to your sprint voice message app, check your settings and make sure the voicemails setting is made up to be shown in the call log. that might correct the issue.
Hello,
Recently I received brand new Samsung Galaxy J6 from my company.
Since I use this phone only for sms & internet, I configured call fowarding to my other number.
Problem is that call forwarding only works when phone is in airplane mode or turned off. When the phone is connected to gsm, redirection is on and someone calls the number they receive a message "The number you're calling doesn't exist". When I switch on airplane mode then call forwarding works as expected.
I'm using the newest software version avaialble and tried to configure call forwarding either via menu or via codes - result is the same.
Just to confirm the problem is not with the SIM card, I put it in my old nokia lumia - there call forwarding works as expected, tried also with samsung galaxy s5 - it also works fine.
According to my company's IT department they're aware of it, and it is present on all samsung phones from J series.
Did anyone encounter similar issue and knows how to resolve it? I guess it shouldn't be normal behaviour that you have to turn on airplane mode or switch off the phone for call forwarding to work.
Thanks
So I can't seem to get any help from Sprint. This worked fine on my Note 9 (as recent as a few days ago), but on my Note 10+ I can only seem to get unanswered calls forwarding to Google Voicemail if I don't answer at all. If I decline the call it goes to Sprint Voicemail.
So for example call comes in. I let it ring 5 times and it forwards the call to my Google Voicemail. Now if the call comes in and I hit the decline call option, it goes right to my Sprint Voicemail. So the question is what is declining the call on the Note 10+ doing differently then declining the call on the Note 9.
Yes I did use the *73XXX-XXX-XXXX to setup noanswer call forwarding. *74XXX-XXX-XXXX doesn't work as when I set that and I hit decline call nothing happens at all, it actually breaks my phone from being able to decline the call.
I have sprint as well. I setup the same as you and it is working for me. Maybe try Update Profile and try again?
Open the phone app.
3 dots settings.
Supplementary services.
Call forwarding.
Mine is ATT but that is where the settings are for me to change that. Might be the same for you.
Sent from my SM-N975U using Tapatalk
T-Mo here and none of the conditional forwarding settings will accept a number on my 10+ 5G
Hi.
I got my Samsung Galaxy Buds+ last week and love them, accept for one annoying thing.
I want my buds to announce who is calling, a feature the do have. When I first connect them to my phone (a Samsung Galaxy S8) the setting for incoming calls is in the list off notifications, and the feature works. But next time I connect the buds to my phone the setting is not there and the caller is not announced. I have had contact with Samsung support and they have gotten me to wipe cache and data in the phone app, remove the buds from the phone and reconnect them, but the problem is still there. The incoming call setting is there the very first time I connect the buds to the phone and the next time it is gone.
And yes, I have enabled the reading caller id feature on the phone to.
Has someone else experienced this? Any idea of what I can do to get this to work as it should?
I have my eSIM configured in my Pixel Watch LTE, and all is working fine so far. However, from time to time I'd look to have my little son wear the watch, when he is out and about alone by himself, so he can call me in case he gets lost, or I can find his location. Generally, this works, but the problem is that the watch also rings when I receive calls: The eSIM is a MultiSIM of my Vodafone contract, so it has the same number as mine in my main phone. Of course I don't want my son to receive my phone calls on the watch.
Is there any way of disabling incoming phone calls, or the the notifications / vibrations of them? Or, ideally, disabling the signaling of any incoming call except if it comes from a certain number (like my own landline)?
gorthon said:
I have my eSIM configured in my Pixel Watch LTE, and all is working fine so far. However, from time to time I'd look to have my little son wear the watch, when he is out and about alone by himself, so he can call me in case he gets lost, or I can find his location. Generally, this works, but the problem is that the watch also rings when I receive calls: The eSIM is a MultiSIM of my Vodafone contract, so it has the same number as mine in my main phone. Of course I don't want my son to receive my phone calls on the watch.
Is there any way of disabling incoming phone calls, or the the notifications / vibrations of them? Or, ideally, disabling the signaling of any incoming call except if it comes from a certain number (like my own landline)?
Click to expand...
Click to collapse
I haven't received the watch yet, but it should have Do Not Disturb settings which you should be able to configure as you wish. For instance, your son could receive calls from Starred contacts only, while all the others are blocked.
Edit: See here
" Do Not Disturb: Turn off all notifications and silence incoming calls. Press and hold to customize exceptions for priority and repeat callers, alarms, and media sounds. "
That's the perfect solution, thank you very much!