Got my note 7 yesterday (love it!) My watch is set to vibrate for everything (no sound) as this is working fine for notifications but when I get a call the phone and the watch ring. I even tried setting the phone to vibrate too and it still rings (same ringtone as the phone). Is anyone else having this issue?
I am having the same issue. Since i never have my phone set to ring (Always rely on my S2 classic for alerts) I just set my Note 7 ringtone to "Silent" no it seems to "Work" ok.
Not the ideal solution, but a "fix" for now...
Thank you.... I'm glad it's not just me. I called Samsung today about it and they were clueless...
I've sent a message to Samsung. Hopefully this gets patched. I'm pretty sure turning off bluetooth audio will stop the issue. Anyone tried it? In bluetooth settings.
Sent from my SM-N930V using Tapatalk
I will try that but, then we can't use it to answer calls. It is definitely a bt issue....i tested it by turning off bt and calling the watch's phone number and it vibrated as it's supposed to. Hopefully enough people contact samsung so that they can get working on a fix for this.
Watch ring ? Or vibrates ?
Wysłane z iPad za pomocą Tapatalk
Me too
Yes I'm having the same issue too. It's really annoying. It's just with the Note7 since it didn't happen with my S7E. Sucks since I can't wear it at work now since I have my phone on vibrate I don't need my watch ringing.
me23brown said:
Yes I'm having the same issue too. It's really annoying. It's just with the Note7 since it didn't happen with my S7E. Sucks since I can't wear it at work now since I have my phone on vibrate I don't need my watch ringing.
Click to expand...
Click to collapse
As a "quick fix" change the phone ring tone to "silent" that works for me.
Thanks but when I tried that neither the watch or the phone would vibrate so I wouldn't know if I was getting a call or notification.
I called samsung about this, has anyone else? I think the the more people that report it the better chance we have of getting a fix for it quicker.
I was able to get it to work but both the ringer AND media in the phone need to be on vibrate. Basically what I did was open the sound setting on my phone and was messing with the settings while calling my phone from another phone until I found the right mixture. This is what worked for me. Now my phone and watch vibrate. I would suggest doing what I did until you find the right mixture.
If I take it off vibrate on my phone they both ring. Hope this helps.
I've got a ticket opened with Samsung. My first inquiry got redirected. Hope this one sticks.
Sent from my SM-N930V using Tapatalk
Happening with me as well, did an online chat with samsung support to report it and gave them a link to this topic.
Has anyone heard anymore about this? I've periodically checked for an update/fix but haven't seen anything.
Same issue
I've had this problem too. been having the issue Since day one with the note 7. I've called Samsung at least 3 times about it. They were clueless. The first 2 times they kept telling be to call my carrier. I know it's not a carrier issue. For god sakes you're the maker of the watch! Brought it to the Samsung kiosk... Also clueles only answers i can seem to get are factory reset it, which didn't work. Come on Samsung! I'm going to try some of the options you guys gave.
Was having the same issue after I got my new phone setup with my gear... tried mutiple things, ended up doing a factory reset on my watch, reconnected to my n7 and my previous settings were restored to my watch via gear manager...and I was back in business.. no more ringing from the watch...
I've reset watch 3 times.....but I'll try 1 more
bump
Mine is doing it also. I have factory reset wach times
4th factory reset didn't fix it
Related
Two times this has happened to me. I will be talking and about 3-5 minuets into the conversation my side goes dead, I can not hear them, but it shows as connected to call. I hang up, try to redial, but it will not actually dial out, just sits on the dialing screen. After I turn it off and back on it works.
Anyone experience this, or heard of it? AT&T Variant.
I've experienced something very similar; as with you, it randomly happens after a couple of minutes of conversation. I have also noticed once this happens all audio on the device is muted (will play tracks in the music player or video but no sound). once restarted all is well again. Does this happen on your device?
Furthermore, I have experienced the device restarting on a couple of occasions mind call. unsure if this is related or not?
international Dual sim variant
I experienced the same after setting network to 4G only. Switched back to auto and havent had this problem so far again.
The other side of the line hears lots of noise when this happened to me. I did call my own number the second after and got the same.
Fingers crossed this was the thing for me..
same for me....after call drops no audio at all...
only reboot fix the problem
it happened at least 4-5 times
i noticed that this problem occures whithin low signal area.
It happened to me yesterday after I got in the underground parking from our office. I tried to call someone from my car after I got out and it showed the message "Call failed". Strange that my former iPhone 7 Plus had the same issue. I am on Vodafone Romania.
i am experiencing the same issue. Every 2-3 days my S8+ mutes it self while on call and i have to restart. I am on Cytamobile-Vodafone Cyprus.
I removed my SD card, changed signal from Auto,2G-3G and 2G with no difference.
This only happens while on call and maybe on low area singals (cannot be 100% sure).
Seems like a software issue but Samsung has not said anything regarding this issue yet.
Try to install the 'Soundabout' app.. With no further settings, Just install it. Its something like all sound to be diverted to another output source... 4 days with this app, no symptoms
Sent from my SM-G955F using XDA Free mobile app
jtace said:
Try to install the 'Soundabout' app.. With no further settings, Just install it. Its something like all sound to be diverted to another output source... 4 days with this app, no symptoms
Sent from my SM-G955F using XDA Free mobile app
Click to expand...
Click to collapse
thanks will test also and let you know
I can confirm that Soundabout doesn't solve this issue..... The problem always shows up in my office, where i have a very low signal spot.
It happens about two times per week and always needs to perform a reboot in order for the sound to work again
Sent from my SM-G955F using XDA Free mobile app
tsquare2112 said:
Two times this has happened to me. I will be talking and about 3-5 minuets into the conversation my side goes dead, I can not hear them, but it shows as connected to call. I hang up, try to redial, but it will not actually dial out, just sits on the dialing screen. After I turn it off and back on it works.
Click to expand...
Click to collapse
Have you tried toggling Airplane Mode on and off instead of rebooting?
Yes tried that... Not working
Needs restart always.
Sent from my SM-G955F using XDA Free mobile app
Any news ? Any progress on that ??
jtace said:
Any news ? Any progress on that ??
Click to expand...
Click to collapse
+1
its realy annoying
Has anyone tried resetting the phone to factory defaults? Let us know please
I did first: factory reset, same problem.
Second: on support they replaced microphone, same problem.
Third: replaced board, same problem after few hours.
Problem is always the same: I can hear them but they can't hear me. If call back again everything is ok and working.
i think its factory fault they changed whole motherboard and the problem still happening most times, i have 2 phones same problem and signal full bar on both sim, waiting Samsung answer
My S8+ drops calls like crazy... What an expensive piece of crap.
There have been reports of Samsung's fps software causing unrelated modules to periodically stop working until reboot (modules such as iris scanner or WiFi internet connection).
As an experiment, try turning off Fingerprint Gestures and all fingerprint security functions in Settings, as well as deleting all registered fingerprints. Then reboot and see if the call-dropping problem goes away.
Spoke with some people today and seems that in Cyprus all of the users that reported this issue are with Cytamobile/Vodafone. Noone of the MTN and Primetel users are reporting related issues.
Seems that the issue is with Vodafone?? I noticed that in most of my calls the sound is clearing like switching to HD Voice so maybe this has something to do with it? With MTN and Galaxy S7 Edge i did not have that.
Hi,
Since my phone got updated to G955FXXU1AQF7 the issue seems to be resolved. I have been using the phone for 5 days now without any issues whatsoever. i will update if anything changes.
I am having my phone NOT RING, often. I get notifications of missed call.
I'm not sure if it is my carrier and weak signal, or if it is a problem with the phone.
How's it going for you?
Sorry to revive such an old thread, but only just recently I've been told that my phone just goes to voicemail when someone calls me. It seems like just a random occurence and after multiple attempts, the call finally goes through. Any thoughts? On a side note, my ex has a honor 5x and has similar issues too
shdw03 said:
Sorry to revive such an old thread, but only just recently I've been told that my phone just goes to voicemail when someone calls me. It seems like just a random occurence and after multiple attempts, the call finally goes through. Any thoughts? On a side note, my ex has a honor 5x and has similar issues too
Click to expand...
Click to collapse
JFYI...I am still having the problem. I'm about to consider getting rid of the Mate 9. I'd hate to, as I love the phone.
I find it interesting that there are not others experiencing the problem.
I am tempted to wipe everything and start fresh...but I have so much set up, I hate to go through all that, and then have it just be a phone problem anyway.
Quite frustrating.
ewingr said:
JFYI...I am still having the problem. I'm about to consider getting rid of the Mate 9. I'd hate to, as I love the phone.
I find it interesting that there are not others experiencing the problem.
I am tempted to wipe everything and start fresh...but I have so much set up, I hate to go through all that, and then have it just be a phone problem anyway.
Quite frustrating.
Click to expand...
Click to collapse
I haven't owned the Mate 9 long. but I don't have any call issues at all. Maybe check with your carrier first. Replacement SIM should always be step 1...Then if it continues. Wipe....My wife and I both had Note 4's (Hers is still kickin)...We would have that happen all the time. Its normally a carrier/signal issue.
If you receive a call with the screen on, does it show the incoming call? Make sure do not disturb is not on some weird timer or something.
Sent from my MHA-L29 using Tapatalk
cash2387 said:
I haven't owned the Mate 9 long. but I don't have any call issues at all. Maybe check with your carrier first. Replacement SIM should always be step 1...Then if it continues. Wipe....My wife and I both had Note 4's (Hers is still kickin)...We would have that happen all the time. Its normally a carrier/signal issue.
Click to expand...
Click to collapse
I must admit that AT&T in my area pretty much sucks.
My wife still has her Note 4, and never has that problem. So, that leaves me thinking it is not carrier related.
My wife thinks it's because of all the apps I have on it.
I think I will try a new SIM, then a reload.
Oh another interesting note: most of the time I get missed call notifications, and it shows the number in the missed call log.
I'm in france , my phone is not ringing sometimes... Will reset the phone and see if problem's still here.
Our phones had the same problem ( me: Note 3, wife Samsung S4 then S5). We even upgraded one of the phones, hoping the extra LTEbands will solve the problem. It turned out to be the carrier. I now bought the Mate 9 outright, with dual SIM and on a different carrier. No calls lost yet, fingers crossed.
I finally have come to the realization that lui Do Not Disturb is malfunctioning.
I have it in a timer of:
- Turn on at 10:00pm
- Turn off at 7:00am next morning
But it is not turning off.
I'm going to post a thread about this.
Just had a S2 classic a few days now.
I work outdoors and am connected to S8 and bluetooth headset.
Today I accepted a call on my watch, I said goodbye and tried to end call from watch, I couldn't find the end call icon.
My previous Pebble watch did this, am I missing something?
Thanks.
No one able to assist?
Thanks
john306 said:
Just had a S2 classic a few days now.
I work outdoors and am connected to S8 and bluetooth headset.
Today I accepted a call on my watch, I said goodbye and tried to end call from watch, I couldn't find the end call icon.
My previous Pebble watch did this, am I missing something?
Thanks.
Click to expand...
Click to collapse
Rotate the bezel to end the call
abmahmood said:
Rotate the bezel to end the call
Click to expand...
Click to collapse
Thanks for trying to help.
I've just done it and it doesn't end the call unfortunately.
john306 said:
Thanks for trying to help.
I've just done it and it doesn't end the call unfortunately.
Click to expand...
Click to collapse
It does try again
Sent from my SM-G955F using Tapatalk
omeryounos said:
It does try again
Click to expand...
Click to collapse
I'm glad you are saying it can be done, as it's the only thing that annoys me about the watch.
I've just rang my daughter's phone off my watch, when she answers I only have the choice of call or text on my watch, which won't end call, even by rotating bezel.
If I leave the screen it then goes to my watch display, I then tried rotating the bezel, both ways but it doesn't end the call, it just goes through notifications/weather/events/heart rate etc.
It's my phone faulty or am I still not doing something right?
Thanks
No way to end call?
I just received a used one and I'm having the same issue. Do
Did you ever find a resolution? I can find no way to end the call....even tried to find an app to do it, but no luck. I found a suggestion to rotate the bezel, but that didn't work either. It's too odd to make a device that can answer a call with no concern of ending it...
And the issue is real... especially if the phone isn't in your hand, or near you, and you initiate a call by accident - yep, I did that.
I just got the Gear Fit2 Pro this week and began using it yesterday as I also have a Gear S3, so the first thing I noticed is that I was missing all my notifications. The watch doesn't have a speaker so we just rely on the vibration to know that we got a notification.
At some point yesterday I noticed that I had about 4 or 5 emails and other notifications pending but never felt the vibration, so I immediately went to the settings to see if there was a Vibration intensity or something but I just noticed that the only other option besides the vibration on and off is the long buzz, so it should vibrate longer for each notification. I decided to give that a try but the same thing, no vibration with the notification.
I decided to reboot the watch and then as soon as I received the first notification it vibrated but then no more vibration after that, so it seems that it only vibrates once after each reboot (I have tested it a couple of times now).
Looking around on Google and other forums I can't find another Gear Fit2 Pro with the same issue but there are dozens of similar reports from Gear Fit2 users, one of them worried me a little as he said that it was fixed only asking for service from Samsung, I think he mentioned that they replaced the vibration motor or something.
Problem for me is that I got this used on Swappa, no receipts, so no service from Samsung (I don't live in Continental US so here in Puerto Rico we don't exist for them) plus the seller, original owner, insists that it was working fine when he had it. I know that I can always open a claim on Paypal and ask for a full refund but I was just wondering if this is indeed a software issue and not hardware, I mean, it works after a reboot, that alone tells me that it may be software related. So I'm wondering if someone else is having or had a similar issue and if it was solved, somehow.
I've resetted it twice now and I'm currently testing it again, I just did a reset an hour ago, so I'm hoping for the best, but if you have any more details about this I'd really appreciate any help you may provide to me, thanks
I've the same issue it vibrates only one
Sent from my [device_name] using XDA-Developers Legacy app
erasat said:
I just got the Gear Fit2 Pro this week and began using it yesterday as I also have a Gear S3, so the first thing I noticed is that I was missing all my notifications. The watch doesn't have a speaker so we just rely on the vibration to know that we got a notification.
At some point yesterday I noticed that I had about 4 or 5 emails and other notifications pending but never felt the vibration, so I immediately went to the settings to see if there was a Vibration intensity or something but I just noticed that the only other option besides the vibration on and off is the long buzz, so it should vibrate longer for each notification. I decided to give that a try but the same thing, no vibration with the notification.
I decided to reboot the watch and then as soon as I received the first notification it vibrated but then no more vibration after that, so it seems that it only vibrates once after each reboot (I have tested it a couple of times now).
Looking around on Google and other forums I can't find another Gear Fit2 Pro with the same issue but there are dozens of similar reports from Gear Fit2 users, one of them worried me a little as he said that it was fixed only asking for service from Samsung, I think he mentioned that they replaced the vibration motor or something.
Problem for me is that I got this used on Swappa, no receipts, so no service from Samsung (I don't live in Continental US so here in Puerto Rico we don't exist for them) plus the seller, original owner, insists that it was working fine when he had it. I know that I can always open a claim on Paypal and ask for a full refund but I was just wondering if this is indeed a software issue and not hardware, I mean, it works after a reboot, that alone tells me that it may be software related. So I'm wondering if someone else is having or had a similar issue and if it was solved, somehow.
I've resetted it twice now and I'm currently testing it again, I just did a reset an hour ago, so I'm hoping for the best, but if you have any more details about this I'd really appreciate any help you may provide to me, thanks
Click to expand...
Click to collapse
It is good to listen!!!!!!!!!!!!!
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
squareballz said:
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
Click to expand...
Click to collapse
Yes and it is quite irritating.
Hi, I have exactly the same problem.
Do you have a case on the phone? Perhaps it's detecting that you are in dock mode? Just throwing some things out there since it does not seem to be widespread.
squareballz said:
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
Click to expand...
Click to collapse
I thought I was going crazy when I picked up a call it was super loud prior to putting it to my ear lol I have no case nor screen protector so this is a legit bug.
Interesting....just applied March update. I'll see if this remedies it.
bakemcbride21 said:
I thought I was going crazy when I picked up a call it was super loud prior to putting it to my ear lol I have no case nor screen protector so this is a legit bug.
Interesting....just applied March update. I'll see if this remedies it.
Click to expand...
Click to collapse
March update did not fix it. It's getting really annoying
Time for an RMA. This can't be software related since very few are seeing it. Could be hardware so a different unit is in order. Good luck.
Sent from my Pixel 2 using XDA-Developers Legacy app
I'll bet this is happening to more people than we think. Very rarely do I chime in, I'm usually a lurker. But I figure I better say something because this problem has already happened to me twice today. It is really really frustrating. Especially for a device as expensive as this one.
bobby janow said:
Time for an RMA. This can't be software related since very few are seeing it. Could be hardware so a different unit is in order. Good luck.
Sent from my Pixel 2 using XDA-Developers Legacy app
Click to expand...
Click to collapse
RMA time??? Not on Verizon lol I don't use my phone to talk enough to justify getting an unlockable phone on RMA.
I'll deal with the occasional speakerphone pickup for the $50 I paid for the phone (well work paid) and having it unlocked/rooted etc
jascolli said:
I'll bet this is happening to more people than we think. Very rarely do I chime in, I'm usually a lurker. But I figure I better say something because this problem has already happened to me twice today. It is really really frustrating. Especially for a device as expensive as this one.
Click to expand...
Click to collapse
I'll bet it's not. The device has been out 6 months and I see 4 users with the problem out of thousands out there. If you don't want to RMA then there is no reason to complain especially if you paid 50 bucks. That's why they do RMA for instances like this. Manufacturing flaws happen, deal with it or replace the device
'nuff said.
Sent from my Pixel 2 using XDA-Developers Legacy app
Guys, I think I found out what's causing this to happen.
The 3.5 audio adapter.
I did not plug in the adapter for 2 days, and the phone did not default to loudspeaker during phone calls.
But last night I plugged in and listen to music, after unplugging, the phone all go into loudspeaker again when phone calls are made/received. Restart the phone and now it never happened.
Gonna monitor few more days and update here.
OK, it is confirmed after using the audio adapter, the phone will definitely switched to loudspeaker mode during phone calls on default , it happens randomly and i would say 70 percent of the time.
its been the 5th day i did not plug in the audio adapter , all my phone calls are not defaulted to loudspeaker, and worked flawlessly.
Google team if you're seeing this, please make a fix to it!
I've had this issue a few times and I've never used the audio adapter. I did send Google feedback about it through the settings menu a couple of months ago, but I've never heard back from them. It's been a while since I've experienced this issue and for sure it's annoying when it happens. I thought it happened because of a previous phone call loudspeaker state. If you had the loudspeaker on on a previous call then the next call would also have the loudspeaker on when it shouldn't.
miamistevie said:
I've had this issue a few times and I've never used the audio adapter. I did send Google feedback about it through the settings menu a couple of months ago, but I've never heard back from them. It's been a while since I've experienced this issue and for sure it's annoying when it happens. I thought it happened because of a previous phone call loudspeaker state. If you had the loudspeaker on on a previous call then the next call would also have the loudspeaker on when it shouldn't.
Click to expand...
Click to collapse
I still use the loudspeaker during phone calls, but at the next call, the phone does not default to loudspeaker.
I have been having two problems with my Pixel 2:
1) i cannot use a headset all the time for phone calls. I have to reboot the phone first then it's ok. I don't use the phone enough to have determined what has been done beforehand to cause this.
2) Sometimes the phone defaults to speaker phone for a phone call. Rebooting fixed it. I did use the headset the other day and then the past 2 calls were on speaker phone and tapping the speaker button did not change the setting.