Has anyone else who has installed the latest version of Google Maps including the Latitude feature for seeing where your friends are had any problems with receiving calls?
I'm not 100% sure it is related but since installing it I have had loads of calls going straight to voicemail with my phone not ringing, sometimes I immediately got the text saying that someone had called but not left a message. It was usually fixed by me rebooting the phone, or making an outgoing call, but after a few hours it seemed to break again.
I have now uninstalled Google Maps and so far the problem has not reoccurred so I'm interested to see if anyone else has noticed this?
Not seen this at all and had Latitude installed since it was announced.
Hard to see why g maps could be causing the problem as it uses the gprs channels.
I suspect the problem might be you are running too many apps at once and then with g maps the memory usage is too much ?
if you are using GM on EDGE or 2G, and you have it running, you cannot have voice and data at the same tine coming through.
this is why 3G came by to allow data and voice simultaneously. no way you can have both on a 2G Network. And since GM will ALWAYS keep your Internet connection alive and transfer data, guess what? ur calls go to VM all the time
Is it possible to stop the phone from pausing music when a call is recieved? If the ringer volume is set to 0 then the music just pauses for the duration of the ringing then resumes. I work at a club and I use slacker radio for the first hour and its kind of annoying to have random pauses if I get a call -- and I obviously cant use airplane mode.
Maybe in the Media player settings... i thinkt there is an option
What if you set all calls to automatically go to voicemail during that hour where you don't want to talk to them anyways?
mikebeatrice said:
What if you set all calls to automatically go to voicemail during that hour where you don't want to talk to them anyways?
Click to expand...
Click to collapse
Thats fine with me, how do you do that?
bump...anyone know how to send all calls directly to voicemail?
I found the setting to forward my calls to other numbers....but id rather not my friends be getting all my calls for me haha
Do you have wifi available?
If you do you could first enable airplane mode and then enable wifi.
Your phone will then be disconnected from the cell network but have a working wifi connection.
(haven't tested this on my nexus but it worked on my hero)
The wifi there is not as solid of a connection at my 3G and I dont know if I trust it....I guess I can just set my phone to forward all numbers to like 9999999 or something haha...Kinda sucks there isnt an option to forward all calls to voicemail though...
could have sworn i saw an option in there to forward to voicemail.
you could set your forward number as your voicemail number.. should work the same I would think
*edit* oh and yes.. i have tried the wifi after airplane mode trick and it works just fine on the nexus.
I've noticed that the Nexus 4 is unusable for VoIP calls due to no echo cancellation, and no background noise filtering (using the second microphone). This issue occurs for all VoIP calls, no matter the client. Some clients attempt to fix this with software filtering, etc, but none do a very good job.
Please star the following issue on the Android bug tracker to bring this to Google's attention. https://code.google.com/p/android/issues/detail?id=41626 The following comment provides more details on the issue:
SIP is unusable on the Nexus 4 because the device doesn't provide an AcousticEchoCanceler[1], AutomaticGainControl[2] or NoiseSuppressor[3]. Additionally, the VOICE_COMMUNICATION[4] audio source designed for VoIP applications returns the same audio as if the application asked for raw microphone data, which is completely unusable for VoIP calls.
The reason cell calls sound good is because the cellular phone takes advantage of the second microphone on the device to perform background noise cancellation and presumably has a hardware chip for echo cancellation. Why these necessary items are not exposed via the APIs listed below on Google's flagship phone is a mystery to me.
Also, the reason SIP is still pretty good on the Galaxy Nexus is because it provides implementations for the AcousticEchoCanceler, AutomaticGainControl and NoiseSuppressor. So even though it doesn't have a second microphone, it does some processing on the audio (via hardware or software) to make it usable for a call. The Nexus 4 provides none of this.
[1] http://developer.android.com/reference/android/media/audiofx/AcousticEchoCanceler.html
[2] http://developer.android.com/reference/android/media/audiofx/AutomaticGainControl.html
[3] http://developer.android.com/reference/android/media/audiofx/NoiseSuppressor.html
[4] http://developer.android.com/refere...Recorder.AudioSource.html#VOICE_COMMUNICATION
Click to expand...
Click to collapse
Have other people noticed this issue. I've noticed it with the stock SIP client, sipdroid, csipsimple, and Talkatone.
I have only used GrooVe IP, and it works fine with stock settings.
I use sipdroid and it works well. No complaints.
Sent from my Nexus 4 using xda app-developers app
Try talkatone. Works well most of the time for me.
Sent from my Nexus 4 using xda premium
While indeed it is an issue, I'm seeing good enough results with sipdroid using gsm codec. Did run into major issues recently because newer cm nightlies changed mcast filtering / ARP. Manually revert that and its fine again. At the least, I've struggled with sip calls with many phones in the past and this is the smoothest experience yet (never had the gnex).
Note I used to use speex for its obvious benefits over gsm but gsm seems to work fine for me and I figure it may be less CPU intensive
Sent from my Nexus 4 using xda app-developers app
Try making a call outside, or with background noise. When I make a call while walking down the street, or in a windy location, the background noise is quite loud for the other person. I've tried several different clients and configurations, and all of them have this issue. The problem is that the phone is not filtering out background noise using the second microphone, and software can only attempt to make this better.
Slightly old thread here, sorry, but I'm wondering if anyone has tried using the built-in VOIP functionality. I currently have a T989 but am considering Mako, and I always had better results using CM10's built-in VOIP than with GrooveIP (i.e. people would complain a whole lot about static and echo when I used GrooveIP). Can anyone comment on this?
I agree. Tried all voip apps from market: groove, talkatone, spare phone, vonage, Skype. Terrible results. I did find one that is working great though (knock on wood): EverVoice. Tried it over the last few days and haven't had any problems on wifi and T-Mobile 4g.
Sent from my Nexus 7 using xda app-developers app
sec6 said:
I agree. Tried all voip apps from market: groove, talkatone, spare phone, vonage, Skype. Terrible results. I did find one that is working great though (knock on wood): EverVoice. Tried it over the last few days and haven't had any problems on wifi and T-Mobile 4g.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Edit: Spoke too soon. EverVoice is unreliable also. Decided to just ditch google voice and add prepaid minutes to tmobile 30 dollar prepaid unlimited plan.
Pandemic187 said:
Slightly old thread here, sorry, but I'm wondering if anyone has tried using the built-in VOIP functionality. I currently have a T989 but am considering Mako, and I always had better results using CM10's built-in VOIP than with GrooveIP (i.e. people would complain a whole lot about static and echo when I used GrooveIP). Can anyone comment on this?
Click to expand...
Click to collapse
Built in voip also echos for me on the Nexus 4. I wondering if regular voice calls go through a different chip or something that does echo cancellation. Is it possible that this chip isn't available for voip?
I am using the built in SIP client with Callcentric. I was using SipSorcery, but I had "no audio" issues on HSPA. Callcentric is NYC based (as am I) so the latency is much better, and echo is reduced as well. My only suggestion is find a SIP server with the lowest ping / least hops.
Skype was excellent on my Nexus S, but has a lot of issues on my N4, so I scrapped it.
For those of you who want the best quality out of your $30 smartphone plan, I made a 12-part video tutorial showing how to do it.
http://www.youtube.com/watch?v=u9DzN1Pu6-Q&list=PLE_de-PBwrTSUMm-Y48aiOOHt_YyT69t0
It's much better than GrooveIP, Vonage, Talkatone, Pbxes.org, and everything else, especially those with the "one big green button" solution.
This method gives you HD Voice (G.722 codec), bettery battery life, and much better options for logging/blocking/recording. You can even set up hold music. Yup, I said hold music.
It used to be difficult to set up until I made it as clear as the nose on your face in the video tutorial (with actual commentary instead of techno music).
Spread the word if you do it and it works out for you. I believe everyone deserves high quality and limitless VoIP WiFi/4g calling.
HowDoIVoIP said:
For those of you who want the best quality out of your $30 smartphone plan, I made a 12-part video tutorial showing how to do it.
http://www.youtube.com/watch?v=u9DzN1Pu6-Q&list=PLE_de-PBwrTSUMm-Y48aiOOHt_YyT69t0
It's much better than GrooveIP, Vonage, Talkatone, Pbxes.org, and everything else, especially those with the "one big green button" solution.
This method gives you HD Voice (G.722 codec), bettery battery life, and much better options for logging/blocking/recording. You can even set up hold music. Yup, I said hold music.
It used to be difficult to set up until I made it as clear as the nose on your face in the video tutorial (with actual commentary instead of techno music).
Spread the word if you do it and it works out for you. I believe everyone deserves high quality and limitless VoIP WiFi/4g calling.
Click to expand...
Click to collapse
I did this method....works very good except for an echo....
I fixed the echo(over 3g) on the nEXUS 4 doing this:
Csimple has an option to enable software control or volume instead of the android OS/hardware.....enable it...I suspect that fixed it combined with the following:
Echo cancellation(never worked until ti checked the above....works great now) in Csimple.
Faux kernel or something compatible with his software for fixing audio gain.
Faux sounds and Faux speakers app. I chose the quality preset plus my own sleight modifications and also the voice setting for speakers.
Echo was annihilated.....I also tried voice audio detection but I didn't like it...
I posted this in the PIAF thread since I used that method but this will help you guys as well.
Nexus 4 SIP echo fix - It's pretty bad for many users but this solved it 100% for me
It worked for me and I tested numerous different setting and configurations along with measuring my latency to ensure it works. YMMV but it's easy to try. At first I thought it was a Latency issue since echo didn't occur over wifi but with ping times lower than 60ms I still got echo over 3g without this method.
I'm using the silk codec(Silk 24 wifi/Silk 12 or 16 over 3g/4g); YMMV with other codecs.
*Before starting*
Root your phone, flash radio .27 or .33 if your on T-mobile or in Canada: We want to enable Nexus 4g! 3g is usually fine but 4g tends to have significantly lower latency(3G: 50-70ms versus 4g: 20-40ms). Sometimes my 3g speed was fine but latency sucks(100-250+ms)....3g has enough speed for VoIP but any latency issues/spikes/jumps will ruin a call.
This is a good guide to follow: Hippowise"s guide
For the first few steps plus a audio fix some users encountered with the radio downgrade; there are 2 scripts you can run via any terminal emulator app scripter(I used this $Scripter). The actual Script to be run can be found on XDA in the nexus 4 LTE thread(download or save them as txt files). The XML file I suggest editing your self(I just replaced all instances of epc.t-mobile with fast.t-mobile for T-mo users).
If said "scripting...wut?" just follow Hippowise's guide to the tee. Scripting is just faster/easier.
It took a few days for my 4g/LTE to kick in so be patient; It's worth the trouble!
**Now to the guide**
First, get the Faux kernel for Nexus 4 or use another kernel that has applied his patch.
2nd, get his apps from the Play store(they cost money but worth it): Faux Speakers and Faux Sound: Configure them for "voice" and "quality" respectively(you can adjust on your own from there, I upped the gain a bit).
3rd, Use Csipsimple and enable "Software volume control" instead of the default android/os/hardware based volume/gain control. I wonder if this bypasses Faux and puts volume control solely in the hands of Csipsimple. I would do 1-3 steps anyway because it fixes the SQ issues in general with the nexus 4.
4th. Enable Echo cancellation; until I did the previous steps, echo cancelation didn't work at all: YMMV.
I choose Echo mode Webrtc becuase Speex echo cancellation didn't work for me. If your codecs are different the other choices or auto might work better. Experiement.
5th: *Optional*
Noise Cancelation: Worked so-so....didn't need so I turned off
Voice Detection: I didn't like it but experiement.
Compact SIP packets: I use it, optional
STUN: I turned it on, I don't think it will hurt.
Audio troubleshooting in the Csip menu has tons of options to mess with. If all else fails, read some guides and experiment. I didn't need to chance anything here but some of it looks promising and has some fixes for specific models like the galaxy.
7th: Latency
Get Speedtest app from the play store and test your speed. In some areas over 3g I would get decent down/up speeds but godawful latency (300ms+ ). If your 3g latency consistently sucks, do the 4g fix for the nexus; Much better latency and I always get 4g in most places on T-mobile.....rural areas might be screwed on getting 4g although I noticed my 3g speeds increased overall after the fix.
8th
Finished; report back in the thread and tell me if it helped!! And if anybody knows a good I.T. position open for a VoIP office/callcenter; let me know cause I'm quitting mine.
Sorry for my ignorance. But all those SIP methods fix all VoIP calls? (Viber, Facebook Messenger, etc).
I just want to fix the terrible echo I am exporting to others Viber users.
Sent from my Nexus 4 using Tapatalk 4 Beta
thesebastian said:
Sorry for my ignorance. But all those SIP methods fix all VoIP calls? (Viber, Facebook Messenger, etc).
I just want to fix the terrible echo I am exporting to others Viber users.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
bump
detdett said:
bump
Click to expand...
Click to collapse
Seems fixed, at least, from the N4's end.
https://code.google.com/p/android/issues/detail?id=42978#c16
raz123 said:
Seems fixed, at least, from the N4's end.
https://code.google.com/p/android/issues/detail?id=42978#c16
Click to expand...
Click to collapse
Nope. Tried to use it on fongo but it didn't work.
Update. Fongo released a new beta today and it seems like the echo problem is gone...
Sent from my Nexus 4 using Tapatalk 4
I tried different voip apps including built-in voip client with CM 10.2. Best sound quality and no echos I've got with CSipSimple with echo reduction enabled.
swimma said:
I tried different voip apps including built-in voip client with CM 10.2. Best sound quality and no echos I've got with CSipSimple with echo reduction enabled.
Click to expand...
Click to collapse
Which cm 10.2 build are you on
GrooveIP does not work for me on N 4.
Did anyone manage to make it work?
It works fine on my other devices w/same username/password.
could you elaborate a bit?
in what way does it not work?
it works just fine for me. i'm running the latest pa (3.65 from 7/10) and the latest franco nightly (r163).
Works fine for me...even used it 2weeks ago while in Canada.
Works fine for me. Better call quality then cellular.
I use it for the most part without issue. If you are trying to use it over you network and not wifi you net to go into the settings and check 3G/4G calling.
Sent from my Nexus 4 using xda app-developers app
I actually had trouble with it and didn't have time to troubleshoot yet. Check out GV Phone. Worked for the couple of test calls that I did.
Sent from my Nexus 4 using Tapatalk 4 Beta
I've had some troubles with GrooveIP this past month and a half. It works sometimes when I try, but receiving calls is very hit-and-miss. The app doesn't maintain connection to Google Voice very well. I tried using it as my main source of voice, but it hasn't worked well for me so I have to switch back to using cell minutes. It's weird; when it acts up, the app thinks it's connected to Voice, but it definitely isn't. Incoming calls hit Google Voice, but don't ring my phone. Outgoing calls don't even get to Google Voice, the app just sits at "Dialing..." and doesn't do anything. I've posted in a few threads on these forums and on their Play store page so hopefully they figure out what's wrong.
GrooveIP works well
I am on stock ROM and also tried it with CM 10.1
I have absolutely no issues. Used it in Canada as well as Hong Kong. Had it on N4 from day one. Previously used it on Atrix. HTC One S without any issues as well.
Johmama said:
I've had some troubles with GrooveIP this past month and a half. It works sometimes when I try, but receiving calls is very hit-and-miss. The app doesn't maintain connection to Google Voice very well. I tried using it as my main source of voice, but it hasn't worked well for me so I have to switch back to using cell minutes. It's weird; when it acts up, the app thinks it's connected to Voice, but it definitely isn't. Incoming calls hit Google Voice, but don't ring my phone. Outgoing calls don't even get to Google Voice, the app just sits at "Dialing..." and doesn't do anything. I've posted in a few threads on these forums and on their Play store page so hopefully they figure out what's wrong.
Click to expand...
Click to collapse
If you have Google Voice set for forwarding your Google Voice number to your phone, that is most likely the reason you are not receiving incoming calls to GrooveIP. Turn the forwarding off and then recheck the behavior.
Solutions Etcetera said:
If you have Google Voice set for forwarding your Google Voice number to your phone, that is most likely the reason you are not receiving incoming calls to GrooveIP. Turn the forwarding off and then recheck the behavior.
Click to expand...
Click to collapse
I have Google Voice only forwarding to Google Chat, which I believe is what GrooveIP uses (correct me if I'm wrong). I've ticked almost every option in GrooveIP, allowed it to use all wakelocks and everything. It just sometimes disconnects from the servers and refuses to reconnect automatically because it thinks that it is still connected when it isn't. I even have it reconnect to the servers every 5 minutes, still nothing. I have to manually go in and refresh the connect (by re-logging into Google Voice through GrooveIP)
Johmama said:
I have Google Voice only forwarding to Google Chat, which I believe is what GrooveIP uses (correct me if I'm wrong). I've ticked almost every option in GrooveIP, allowed it to use all wakelocks and everything. It just sometimes disconnects from the servers and refuses to reconnect automatically because it thinks that it is still connected when it isn't. I even have it reconnect to the servers every 5 minutes, still nothing. I have to manually go in and refresh the connect (by re-logging into Google Voice through GrooveIP)
Click to expand...
Click to collapse
Hmmm... not seeing that here, of course I only pretty much use it on wi-fi. Are you using it on cell data when you see this behavior?
I've seen people with this same issue and I am sure Busybox is the culprit. Just tried installing to a variety of paths like /system/bin and /su/bin and it still breaks Wifi calling. You may ask yourself how I can be so sure this this is the cause. I uninstalled Busybox and immediately Wifi calling was working again.
eggydrums said:
I've seen people with this same issue and I am sure Busybox is the culprit. Just tried installing to a variety of paths like /system/bin and /su/bin and it still breaks Wifi calling. You may ask yourself how I can be so sure this this is the cause. I uninstalled Busybox and immediately Wifi calling was working again.
Click to expand...
Click to collapse
How are you testing to make sure its a WiFi call? Are you turning on airplane mode while on WiFi? That ensures all radios are off except WiFi.
Also what do you mean its not working? What happens? Do you get an error message? Does it make a noise? Does it do a song and dance instead? (Kidding)
The more details you give the more likely someone will be able to help.
AndroidPurity said:
How are you testing to make sure its a WiFi call? Are you turning on airplane mode while on WiFi? That ensures all radios are off except WiFi.
Also what do you mean its not working? What happens? Do you get an error message? Does it make a noise? Does it do a song and dance instead? (Kidding)
The more details you give the more likely someone will be able to help.
Click to expand...
Click to collapse
You're right, my bad. Well, underneath the mobile data toggle in quick settings, it switches to "T-Mobile Wi-Fi Calling" when it's active, and just T-Mobile whenever else. Almost immediately as I remove Busybox, Wi-Fi calling returns. Phone calls also display if it's calling using wi-fi.
eggydrums said:
You're right, my bad. Well, underneath the mobile data toggle in quick settings, it switches to "T-Mobile Wi-Fi Calling" when it's active, and just T-Mobile whenever else. Almost immediately as I remove Busybox, Wi-Fi calling returns. Phone calls also display if it's calling using wi-fi.
Click to expand...
Click to collapse
No problem, but still I don't know what you mean by it does not work. When trying to call does it say the call is connected or call failed or some other error or what?
Honestly I'm not really sure what the problem or fix is since I'm not super experienced with busy box or unix commands myself. I believe you can manually choose which utilities busy box installs. So the best thing to do first is to narrow down which specific Unix utilities in busy box that might be causing this. Install 1 of the utility in busy box and try to WiFi call, then repeat until wifi calling stops working again. Then come back and report which one it was that breaks WiFi calling.
Can anyone else test this?
Just tested your theory and my WiFi calling still works. Even rebooted in between uninstalling and installing busy box. Was curious because as soon as I read this thread I tested and saw my WiFi calling was not working so I decided to test your theory.. I uninstalled busy box and it still was not working. I rebooted my phone and WiFi calling was working again. I installed busy box and WiFi calling still working. I rebooted again and busy box still installed and WiFi calling still working. Hope this helps.