GrooVe IP - Google Voice VoIP

Hmm. Well calls themselves are better but the initial connection delay still makes this app unusable. When I call someone, they say hello twice and I don't hear the first one. Same thing happens for inbound calls. This can frustrate some people and make them hang up prematurely.

By comparison, Skype is 100% seamless. When the person I call picks up, it's immediately connected and we're talking as if it's any normal phone call.

We still have the one other change planned. But again that will only reduce about 200ms. Skype controls both end points, gives them more flexibility and control.
 
I figured as much. I'm thinking this app won't really fit my needs, but I'll wait and see what that change does.
 
I like the auto tail setting feature. I have a quick question about it though - does that vary based on connection latency, or based on the phone (or both)?

Also, can the other person hear the beep used to setup the echo tail?
 
I like the auto tail setting feature. I have a quick question about it though - does that vary based on connection latency, or based on the phone (or both)?

Also, can the other person hear the beep used to setup the echo tail?

It's based on both. The other person, in most cases, will not hear the beep. If the beep bothers you, at the end of each call the detected echo tail is reported. You can use that to switch to the correct manual setting.
 
It's based on both. The other person, in most cases, will not hear the beep. If the beep bothers you, at the end of each call the detected echo tail is reported. You can use that to switch to the correct manual setting.

I just did a few quick tests, and I couldn't hear the beep on the other end - it doesn't bother me, so I'll just leave it on.

Two quick questions - does turning on echo cancellation increase the latency in the call? Does checking the post processing box along with the echo cancellation box increase latency anymore than just having echo cancellation on?

Also, I think I found a bug - I am on a Nexus S, and when playing around with the echo cancellation settings, I noticed that if I mute the call in the Groove IP app, and end the call without unmuting it, it will remain muted for my next call (this also causes the automatic tail detection to fail). If I toggle the mute on then off, it is fixed though.
 
I just did a few quick tests, and I couldn't hear the beep on the other end - it doesn't bother me, so I'll just leave it on.

Two quick questions - does turning on echo cancellation increase the latency in the call? Does checking the post processing box along with the echo cancellation box increase latency anymore than just having echo cancellation on?

Also, I think I found a bug - I am on a Nexus S, and when playing around with the echo cancellation settings, I noticed that if I mute the call in the Groove IP app, and end the call without unmuting it, it will remain muted for my next call (this also causes the automatic tail detection to fail). If I toggle the mute on then off, it is fixed though.

Neither option should add latency.

Will take a look at the mute issue you ran into.
 
How long does it take the Amazon app store to publish your updates?

Sent from my EVO 3D
 
How long does it take the Amazon app store to publish your updates?

Sent from my EVO 3D

I haven't found any pattern, and they don't give us an ETA. It's ranged from a few hours to a few days. Once it took them two weeks.
 
Thanks for the help. Wifi fixer did nothing to help. I then tried an app called advanced wifi lock. It seems that it may have fixed the problem.

I know I'm kind of late to the party here, but I also found that Advanced Wifi Lock did the trick. With this app, GrooVe IP starts ringing almost immediately after the call is placed.

The other app, Wifi Fixer, didn't help. With this app, there are several rings (on the calling side) before GrooVe IP starts to ring.

It seems to me that if this app can keep WiFi on, it should be possible to add Android 2.2 support to the High Perf WiFi Lock option (which presently only works with 2.3).
 
I know I'm kind of late to the party here, but I also found that Advanced Wifi Lock did the trick. With this app, GrooVe IP starts ringing almost immediately after the call is placed.

The other app, Wifi Fixer, didn't help. With this app, there are several rings (on the calling side) before GrooVe IP starts to ring.

It seems to me that if this app can keep WiFi on, it should be possible to add Android 2.2 support to the High Perf WiFi Lock option (which presently only works with 2.3).

I believe Advanced WiFi Lock gets a different wifi lock. We're going to be adding support for that directly into GrooVe IP so you don't need to use another app.
 
Hi, I purchased the GrooVe IP yesterday but so far haven't been able to get it to work on my unrooted Droid X (Verizon). I'm located in North Carolina.

I've had Google Voice on my phone for a while for the voicemail feature. I signed into Google Voice on my computer and:
1) got a new google phone #
2) checked the box for calls to be forwarded to Google Chat
3) un-checked the box for calls to be forwarded to my mobile #
4) signed out of Google Chat in gmail

I turned on WiFi on my Droid X and connected to a network

I opened GrooVeIP, logged in with my Gmail/Voice username and password. GrooVeIP said I signed-in successfully. My main goal with this app is to send/receive calls from our place in the mountains where we have WiFi but no cell service, so I didn't select to Allow 3G/4G Calling.

Tried to make a call to my wife's phone from the dialer in GrooVeIP, it sounded like the call went through and rang for a split-second before dropping the call. Tried again, same thing. Then tried calling another number, same result. When I got home, my wife did say she had a missed-call or two from my Google #.

Now this morning I'm trying to get GrooVeIP figured out. On my phone - I'm signed-in on GrooVeIP and connected to WiFi. I'm sitting here next to my office land-line and trying to call that # from GrooVeIP. When I do, GrooVeIP shows "Calling..." on my mobile's screen, but my office phone never rings.

I also tried calling my Google # from my office line and my mobile won't ring, the call goes straight to my Google Voicemail.

I signed into Google Voice and selected for calls to be forwarded to my mobile #. Dialed my Google # from my office phone and my mobile rang, so I've got the Google # correct.

Any idea what I'm doing wrong here? Should I try deleting and re-installing the app?

Thank you in advance for your help.
 
Last edited:
Hi, I purchased the GrooVe IP yesterday but so far haven't been able to get it to work on my unrooted Droid X (Verizon). I'm located in North Carolina.

I've had Google Voice on my phone for a while for the voicemail feature. I signed into Google Voice on my computer and:
1) got a new google phone #
2) checked the box for calls to be forwarded to Google Chat
3) un-checked the box for calls to be forwarded to my mobile #
4) signed out of Google Chat in gmail

I turned on WiFi on my Droid X and connected to a network

I opened GrooVeIP, logged in with my Gmail/Voice username and password. GrooVeIP said I signed-in successfully. My main goal with this app is to send/receive calls from our place in the mountains where we have WiFi but no cell service, so I didn't select to Allow 3G/4G Calling.

Tried to make a call to my wife's phone from the dialer in GrooVeIP, it sounded like the call went through and rang for a split-second before dropping the call. Tried again, same thing. Then tried calling another number, same result. When I got home, my wife did say she had a missed-call or two from my Google #.

Now this morning I'm trying to get GrooVeIP figured out. On my phone - I'm signed-in on GrooVeIP and connected to WiFi. I'm sitting here next to my office land-line and trying to call that # from GrooVeIP. When I do, GrooVeIP shows "Calling..." on my mobile's screen, but my office phone never rings.

I also tried calling my Google # from my office line and my mobile won't ring, the call goes straight to my Google Voicemail.

I signed into Google Voice and selected for calls to be forwarded to my mobile #. Dialed my Google # from my office phone and my mobile rang, so I've got the Google # correct.

Any idea what I'm doing wrong here? Should I try deleting and re-installing the app?

Thank you in advance for your help.


Hi,

The stuck at "Calling" issue started affecting people this morning. It appears that either there is a problem on the Google servers or Google may have modified the calling specification slightly. Incoming calls appear to still work. We're looking into it and should have more answers or a solution soon.
 
Thanks. Deleted and re-installed the GrooVeIP app, still not receiving calls, Wifi connection is "fair".

To receive calls you need to go into your google voice account (google.com/voice) and forward calls to google chat. Have you done that?
 
Yep. In Google Voice, the box is checked for Forward Calls To Google Chat. Do not have the box checked for calls to forward to my mobile number. Am signed out of Chat in Gmail, and not signed into Chat on my phone. Not sure what I'm doing wrong. Will try again when I get home and have a stronger Wifi signal.
 
How do you get the Google Chat box back? I did something to it and now it gone can't find a way to get it back so I can click on it. Please help NE1...