GrooVe IP - Google Voice VoIP

[dchawk81]

I haven't either. That's why I asked you.

Do you know if there's a specific order in which I need to connect my bluetooth to get it to work with your app?

Sometimes I'll get a call, but won't know if I need my BT (for privacy) until after I answer. I haven't been able to successfully connect my BT in that scenario (while in the middle of a call) so far. It does connect fine that way in the native dialer/mobile network mode.

 

[snrb_labs]

I haven't either. That's why I asked you.

Do you know if there's a specific order in which I need to connect my bluetooth to get it to work with your app?

Sometimes I'll get a call, but won't know if I need my BT (for privacy) until after I answer. I haven't been able to successfully connect my BT in that scenario (while in the middle of a call) so far. It does connect fine that way in the native dialer/mobile network mode.

Right now the app only looks to see if a headset is connected when the call screen is initially created. I think we can change that to allow you to sync your headset in the middle of a call. I'm assuming the bt button stays grayed out or disabled for you?

 

[dchawk81]

That explains it. Yes it does. Taking it a step further, can you fix it so that BT can be used to answer and hang up calls as well? Just like the default system.

 

[pacolococt]

I notice that the listing mentions that it can use up battery if used all the time. How bad does it appear to be in your use?

I have it enabled all the time and it has worked perfectly to allow my optimus v to ring while connected to wfi and the screen off. I do not use my phone much but on my last charge it was a little over 1 day before I had to charge it ago 1d 4hrs or so. It doesn't seem to affect battery too much then, either way it is well worth it to know when someone is calling right away.

 

[camf3xu]

I'm actually really interested in this BC my rooms in the basement and I get no service. Can you set this app to enable and scan for wifi when you have no service?

Edit: nvm just saw u have to use a different number

 

[dchawk81]

I still have an issue where the other person doesn't hear me for the first second or two of a call, and vice versa.

Is there a setting in the app to adjust for that?

 

[snrb_labs]

I still have an issue where the other person doesn't hear me for the first second or two of a call, and vice versa.

Is there a setting in the app to adjust for that?

Looking into that issue. It happens to us sporadically, but have heard that for some people it happens every call.

 

[dchawk81]

I wonder if it's related to the connection's latency. Mine always connects with a delay but the amount varies ever so slightly, as does my 3G latency. It's always enough that when I call voicemail with no messages, the first thing I hear is "place a call, press 2." I don't ever get to hear "you have no new messages" like I should and do on the normal dialer.

 

[snrb_labs]

I wonder if it's related to the connection's latency. Mine always connects with a delay but the amount varies ever so slightly, as does my 3G latency. It's always enough that when I call voicemail with no messages, the first thing I hear is "place a call, press 2." I don't ever get to hear "you have no new messages" like I should and do on the normal dialer.

Will update here with whatever we find. Even if it just turns out to be latency.

 

[dchawk81]

I figured out what it's doing. It's ringing over top of the initial part of the call. I didn't notice this before, but when I call voicemail over the network, it doesn't ring first....it just connects. When I call voicemail over GrooVe, it rings even though it's already connected, covering part of the greeting.

The same thing is happening for regular calls too, both in and out.

 

[snrb_labs]

I figured out what it's doing. It's ringing over top of the initial part of the call. I didn't notice this before, but when I call voicemail over the network, it doesn't ring first....it just connects. When I call voicemail over GrooVe, it rings even though it's already connected, covering part of the greeting.

The same thing is happening for regular calls too, both in and out.

That means the app hasn't received the connect message yet from Google Voice.

 

[dchawk81]

Ah okay. Hopefully you all can get it sorted. I tried to make a business related call with it the other day and because of that issue, the other person didn't hear me, got confused, and hung up. Twice. I had to use the regular system to get a hold of them.

 

[snrb_labs]

In case you haven't already purchased the app, tomorrow we plan on increasing the price. If you've been planning to purchase the app, may want to do it tonight.

 

[dchawk81]

I don't think you should be raising the price just yet. It's not really ready for primetime.

I say this as someone who did already purchase it.

 

[wch_one]

I don't think you should be raising the price just yet. It's not really ready for primetime.

I say this as someone who did already purchase it.

I have to agree -- there are still some bugs that cause serious problems. For example, it's still unusable for me for incoming calls because of the ringer conflict issue.

 

[snrb_labs]

I have to agree -- there are still some bugs that cause serious problems. For example, it's still unusable for me for incoming calls because of the ringer conflict issue.

Can you detail what ringer conflict you are having? If you have calls forwarded to both your cell number and to google chat there's no way to avoid google voice sending the incoming call to both. If your device maintains it's data connection what should happen is GrooVe IP ring first, then the native phone system will begin ringing. Then after 2 seconds GrooVe IPs incoming call screen should come back on top. If your data disconnects when the native phone system is in use then GrooVe IP will be disconnected and won't continue ringing.

 

[dchawk81]

GrooVe shouldn't let the native screen pop up at all when it's signed in. Two seconds is forever when talking about incoming rings.

I also had an issue where the GrooVe would pop up for the first call but never for subsequent calls. That makes it unusable too.

Add to that the issue you acknowledged where GrooVe doesn't get the connect message right away.

All these little things should be telling you that the app is still a beta product and raising the price would kill your sales...or tick a lot of people off.

It needs to function as smoothly as the regular system to be useful. It'll be worth more then, but it's not now. Even $4 is too much considering it can't be used to converse with anyone you haven't already explained the problems to somehow beforehand. A business thought I was prank calling them when I tried to use GrooVe, for heaven's sake.

 

[snrb_labs]

GrooVe shouldn't let the native screen pop up at all when it's signed in. Two seconds is forever when talking about incoming rings.

I also had an issue where the GrooVe would pop up for the first call but never for subsequent calls. That makes it unusable too.

Add to that the issue you acknowledged where GrooVe doesn't get the connect message right away.

All these little things should be telling you that the app is still a beta product and raising the price would kill your sales...or tick a lot of people off.

It needs to function as smoothly as the regular system to be useful. It'll be worth more then, but it's not now. Even $4 is too much considering it can't be used to converse with anyone you haven't already explained the problems to somehow beforehand. A business thought I was prank calling them when I tried to use GrooVe, for heaven's sake.

There's really no way to prevent the native phone system from ringing. The android OS doesn't allow 3rd party apps from blocking native phone functionality. There are issues we can control and fix. Others we can't.

I appreciate yours and others feedback, but really it's not a debate. It's something we've decided to do. I posted here before hand to give people some advanced notice in case they were already planning on purchasing the app. We do have a pretty liberal refund policy for anyone who isn't happy with their purchase.

 

[dchawk81]

Okay well that I didn't know. Why does it behave the way it does then? Can you not code the GrooVe screen to stay longer rather than it does? Personally, I can work around it by using my GV number exclusively for GrooVe and only forward it to Chat. So this particular issue doesn't necessarily make it unusable for me.

However, this call connect notification delay does. I can't make or take calls if people can't hear me for those critical first few seconds and hang up out of confusion. Is that fixable?

I'm not debating. I'm giving you an end user perspective. You're obviously free to do what you like.

 

[snrb_labs]

Okay well that I didn't know. Why does it behave the way it does then? Can you not code the GrooVe screen to stay longer rather than it does? Personally, I can work around it by using my GV number exclusively for GrooVe and only forward it to Chat. So this particular issue doesn't necessarily make it unusable for me.

However, this call connect notification delay does. I can't make or take calls if people can't hear me for those critical first few seconds and hang up out of confusion. Is that fixable?

I'm not debating. I'm giving you an end user perspective. You're obviously free to do what you like.

We're playing around with what we can do for the dual incoming call issue. The problem is the native call system will ring as soon as it gets a call. So can't really control when it takes focus. Might be able to reduce the time before GrooVe IP comes back on top. Also thinking of adding a config or an option so you can go back to the native screen if you don't want to pick up from GrooVe IP.

We're looking at the call connect delay. There's a bunch of different possible causes. So there is some chance we'll be able to influence it. If it's completely caused by delays on the Google side or latency then there's not much we can do. Should know more as we look more into it. But again it's a tricky problem because it doesn't happen on every network or every device.

And I appreciate your feedback. I know we won't always make decisions that everyone agrees with but it helps to get different view points. We try and pay close attention to what our users are telling us.