Hi everyone,
So I've been using voip.ms as my phone service for a few years now, and the native SIP client on Android has always worked like a charm on my previous phones (Nexus 5, Nexus 6, Nexuis 5X).
I just got a Samsung Galaxy S7 G930F, and it seems like the native SIP client is broken and not working properly.
I got to configure the SIP settings by following this guide, but it seems like I cannot get outoing calls to work (incoming calls work perfectly).
Whenever I make a call, I cannot use the volume controls (stuck at max volume), and when the other party answers my call, they hear a loud strident machine sound, but they cannot hear me at all. I can hear them, but the sound is really choppy.
I've tried factory resetting the phone, I've also tried using the Google Dialer, but the problem persists.
Normal calls work just fine, so it seems like this has something to do with the SIP stack.
My questions to you guys are, has anyone had success in using the native Android SIP client on their Samsung Galaxy S7 phone? Has anyone experienced the same issue?
I'm now using Zoiper for making VOIP calls, but its implementation of Bluetooth car controls is broken. That's one of the reasons I liked the Android native SIP client so much: it worked perfectly out of the box on my previous Nexus phones.
Thank you.
same problem here, with the addition that the noise also occurs on incoming calls, thus making the internal SIP client useless. It was working fine on my S5mini (an otherwise crippled phone), and I have the exact same setup on the S7. I tested safe mode and uninstalling a call recorder app, but to no avail.
Samsung, I bought your premium phone, so get this fixed!
k-m-c said:
same problem here, with the addition that the noise also occurs on incoming calls, thus making the internal SIP client useless. It was working fine on my S5mini (an otherwise crippled phone), and I have the exact same setup on the S7. I tested safe mode and uninstalling a call recorder app, but to no avail.
Samsung, I bought your premium phone, so get this fixed!
Click to expand...
Click to collapse
Same problem on my S7. CSipSimple works but without the native client integration I cannot use BT.
Im using Canadian Exynos if that makes a difference. Anyone who has tried the Nougat beta, does it fix it?
the problem seems to be fixed after upgrading to Android 7.0
k-m-c said:
the problem seems to be fixed after upgrading to Android 7.0
Click to expand...
Click to collapse
I have 7.0 (stock rom) on my A320FL (Galaxy A3 2017) and i'm still having this exact problem with the native SIP client I hope they fix it on android O or i'll have to wait for a custom rom to be released ;-;
s8 active choppy sip sound
Incoming calls are working but outgoing have choppy sound. I tried different codecs on freepbx side but still the same. Any updates for better sound quality?
for whatever reason (one of the last updates?), internet calling now works on Samsung Galaxy S7, Android 7.0, G930FXXU2DRA9.
updated to Android 8.0 today. VoIP connections not usable anymore. After installing "Galaxy SIP Accounts" I can again edit the connections and send and receive calls, but the connection is completely silent - not even the cracking noise I had for a while with Android 7 before it magically disappeared.
Any ideas what to do?
k-m-c said:
updated to Android 8.0 today. VoIP connections not usable anymore. After installing "Galaxy SIP Accounts" I can again edit the connections and send and receive calls, but the connection is completely silent - not even the cracking noise I had for a while with Android 7 before it magically disappeared.
Any ideas what to do?
Click to expand...
Click to collapse
It works fine on S7 & Oreo with my provider (odorik.cz). Already did a few calls without any issues.
one day later after installing Zoiper but not changing any phone or network settings, the native client is working again... quite strange behavior...
SOLVED - Problems with VOIP Client
hi there,
since this thread helped / enlightened me, i thought i contribute some observations of mine.
Used hardware: Samsung Galaxy S7
Aprox. one and a half year ago i started with VOIP and of course as a newbie i did it with apps like Zoiper IAX or CSip Simple, but never was really happy to have to use an extra app for phone calls.
While later i discovered the both apps "Galaxy SIP accounts" and "Galaxy SIP settings" in an article, downloaded them from playstore, setup them in a minute and was totally happy.
Was glad that i could remove those other apps then.
Because my S7 starts to loosen its display now, i got myself another one and because i now knew that those two Galaxy SIP apps worked perfectly i installed them from the start being extremely disappointed about echoes and heavily distorted sound.
Then read this thread and thought i'd give it a try (because couldn't get the built-in client work properly anyway) and installed zoiper, did my phone call and everything worked smoothely.
Then i remembered that on the former phone i had external apps installed before as well.
So to me it seems that, at least on the S7 with Nougat/Oreo those external apps change something and make the hidden client work properly which can then be utilized with the two Galaxy SIP apps.
Now i have deinstalled zoiper but the VOIP client still works fine !
Hope my story gives useful information to someone as well
Karl
Related
Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App
its TOOOOOOOOOOOOO Bad that otherside cant hear my on FACEBOOK MESSENGER, and my phone works pretty good on normal phone calll skype call. and LONG PRESS TO SEND VOICE MESSAGE on facebook messenger. anyone had the same problem??
anyone who could help me koz. i stay abroad and need to be in contact with my family al the time. PLEASE HELP
everyone'S MESSENGER CALLS WORKING FINE??
It's weird that "press to send voice message" works and not the voice during a call, but maybe the first one is not directly related to your app. Did you check that Messenger has the permission to use your microphone ?
In Settings > Apps > Messenger > Permissions > "Microphone" should be activated.
yes
_lua said:
It's weird that "press to send voice message" works and not the voice during a call, but maybe the first one is not directly related to your app. Did you check that Messenger has the permission to use your microphone ?
In Settings > Apps > Messenger > Permissions > "Microphone" should be activated.
Click to expand...
Click to collapse
YEAH i tried the permissions. if not permission for MIC why would it send sound clips. still the same problem. anyone else had this problem?
I currently have the same problem on my Samsung Note 4 (n910f). Everything works perfect, except video calls on facebook messenger. Sending voice clips over messenger works. I tried to mess with the permissions, updated messenger app, updated phone firmware, tried everything. On every other apps the microphone work flawless. I event send facebook a report, but haven t heard anything.
how to make permission allow there is not any open close mark
Know this is an old thread but I found it through a Google search with same problem.
I found the problem for my self.
It's not only microphone permission it needs, I needs phone permissions too. Why I can't tell. Poor development maybe.
Iphones too
I have the same issue with messenger BUT it was working great on my android devices, but I had to switch to iOS... and guess what... I used an SE then a 6s and later a 7 (bootloop so back to 6s. I don’t want to spend a fortune on new ones) every single one had the same issue with the mic. I’ve tried to install the messenger first after a clean factory reset... and I had the same problem. My wife is using her iPhone with no issues at all. I am still using android as a secondary but my main phone must be an iPhone (flickin company)...
I got the same problem on my Galaxy note 10 plus with messenger microphone.
But ONLY when i make a video call. When i recieve a video call it's working fine!! I call back and they can't listen me.
All other similar apps like DUO, Viber, What's Up, Skype are working fine.
Phone app working fine too. All apps and the device are working fine.
I reset the device and it solved but after some days it's back again!!
It makes me crazy!
AfXv237 said:
I currently have the same problem on my Samsung Note 4 (n910f). Everything works perfect, except video calls on facebook messenger. Sending voice clips over messenger works. I tried to mess with the permissions, updated messenger app, updated phone firmware, tried everything. On every other apps the microphone work flawless. I event send facebook a report, but haven t heard anything.
Click to expand...
Click to collapse
Same problem over here with N910C rooted & N916K non rooted custom roms,
Update: Fixed using Lesser AudioSwitch to fix this, after switching to headphones!
AfXv237 said:
I currently have the same problem on my Samsung Note 4 (n910f). Everything works perfect, except video calls on facebook messenger. Sending voice clips over messenger works. I tried to mess with the permissions, updated messenger app, updated phone firmware, tried everything. On every other apps the microphone work flawless. I event send facebook a report, but haven t heard anything.
Click to expand...
Click to collapse
Used Lesser AudioSwitch to fix this, tested & working after switching to headphones!
https://apkpure.com/ar/lesser-audioswitch/com.nordskog.LesserAudioSwitch
Lesser AudioSwitch - Apps on Google Play
Force your audio output to switch to headphones, speakers, or any other output!
play.google.com
Hi all,
I wanted to let you guys know that the Gear S2 and Gear S2 Classic both work on Android 7.0 Nougat
I'm using a Oneplus One running 7.0.
The point I tried to connect the watch my phone denied it and told be connection couldn't be made.
After turning the Bluetooth on and off again I was able to connect my Gear S2 with my phone (Probably a ROM bug)
[Improvements]
Everything seems to work fine and I even saw improvements.
Since Android Nougat I am able to see pictures of whatsapp messages, I wasn't able to do that on Marshmallow.
[Bugs]
There is 1 bug, I'm not sure if it's my ROM or the compatibility.
When I browse through my quick launch apps I see the messaging app, the app to send and receive Sms with.
I never saw this app on Marshmallow and it worked!
The app isn't available in the application list, only in the quick launch widget.
Too bad, after adding the app the widget will reset itself or the messaging app disappear from the quick launch widget after a certain time.
You can re-add it and use it, it's just an annoying bug.
[So, does it work?]
Yes, The S2 as well as the apps you need (S health included) works fine, no problems at all so far.
And if I will find one, I will post it here.
Hi, is your device encrypted? I'm planning on buying the s2..but grew hesitant after reading that encrypted phones are having synchronization issues.
(Btw i'm on nexus 6p)
Thanks.
How about phone calls? I have this weird bug that whenever i get a phone call, the names would show up on the gear....but on the phone, only numbers... like i dont have the person thats calling in my contacts.
And my phone wont display names until I delete samsung apps that connects to my phone.
Are you getting the same thing too?
I have the V20 (now with android 7)
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders
I'm pretty good normally but my problem has got me.
When I make normal phone calls people hear me fine.
When I use whatsup, messenger, Skype, people complain I'm fading in and out and can only hear 3 out of 4 words clearly.
The problem is the same on wifi or data.
I have reset the phone twice then installed only one app e.g what's app... Same issue.
Taken it to samsung who also reset it and checked everything said the phone is fine and said they will not check problems with 3rd party apps.
The microphone is fine when I make a video or normal phone call. .
I'm prepared to pay samsung to replace the microphone or motherboard but not sure what needs replacing... Exynos version
no power saving on or sleeping apps
This has got me
Thanks for any ideas
I think the issue could be connectivity at each end of the call. Both parties should have relatively stable connectivity and if unmatched or there is traffic congestion then call quality arise. The fact that your normal call are clear as they should be makes me think it is poor connectivity.
But when I use my old note 8 I have no problems using same sim or wifi.
It's only when I use apps like messenger what's ap Skype