New VOIP option for GV - single app solution: GrooVe IP

[mmarz]

It has been reliable for me, But I guess everyone's mileage will vary. I have used it several times today. We need a few echo numbers to test, so we can eliminate issue's like this.

Edit: I am using it right now to test AOSPCMOD. The Echo Number 909-390-0003 is working fine for me. I will place five 6-min calls. If I don't hit the bug at the end of those calls, I will assume Groove Ip works fine on AOSPCMOD.

That is so strange. Within 10 seconds of calling it right now, I ran into the audio issue. But groove has yet to have the audio issue with any of my other calls.

 

[Takenover83]

AOSPCMOD 4/27 (2.3.3 rom)
Groove IP 1.1.0
No troubleshooting options enabled
Using Echo Test Number
Test are being run over WIFI - sleep disabled

Test #1: 6-min no error
Test #2: 6-min no error
Test #3: 6-min no error
Test #4: 6-min no error
Test #5: 6-min no error

Nameless V1 (2.2.1 rom)
Groove IP 1.1.0
No troubleshooting options enabled
Using Echo Test Number
Test are being run over WIFI - sleep disabled

Test #1: 6-min no error
Test #2: 6-min no error
Test #3: 6-min no error
Test #4: 6-min no error
Test #5: 6-min no error

Note: Nameless has this weird bug where the screen is hard to turn on at times.

 

[mmarz]

AOSPCMOD 4/27 (2.3.3 rom)
Groove IP 1.1.0
No troubleshooting options enabled
Using Echo Test Number
Test are being run over WIFI - sleep disabled

Test #1: 6-min no error
Test #2: 6-min no error
Test #3: 6-min no error
Test #4: 6-min no error
Test #5: 6-min no error

Nameless V1 (2.2.1 rom)
Groove IP 1.1.0
No troubleshooting options enabled
Using Echo Test Number
Test are being run over WIFI - sleep disabled

Test #1: 6-min no error
Test #2: 6-min no error
Test #3:
Test #4:
Test #5:

For your tests, what are you saying or feeding into the phone for it to repeat back to you?

I just found out that the problem only exists if I say something extended. For example, I normally just say "testing" or "hello" repeatedly which works fine. But if I say "heeeeellloooooooooo," the end of the word will start to get choppy. Again, only when using this number and only after a little bit time. Otherwise I have the exact same setup as you.

 

[Takenover83]

I have sung my ABC's, counted to 10, 321,123, what the heck is bothering me lol. On BumbleBee 1.18, I had a 38-min call where I had plenty of extended sentences (that was not the echo number).

 

[mmarz]

You have way more patients than I do, lol. I'm going to log the call and send it to the app devs. Maybe it will be useful for them. I'm going to call the bug fixed until I can replicate it with other numbers. Thanks for the testing and most likely freaking out your loved ones: "What is he doing in there? I hear him quoting Family Matters repeatedly to himself. I think he's losing it."

YouTube - 3-2-1... 1-2-3... what the heck is bothering me?

 

[Takenover83]

Haha, that is where I got it from lol!

 

[scootincivic]

YouTube - 3-2-1... 1-2-3... what the heck is bothering me?

Classic...

.........................................

On a differnt note I have been following through on this thread for a while now and have noticed not many users are reporting if the issues are via 3G or WiFi..

I have yet to do any testings on my V while on 3G (Im lucky to even get a bar of 2G on my sig. at my location)..
However WiFi on my end is working great and I have not had a single issue with this app on my V while running stock 2.2.1~X over clocked at 806..

Ill try to stay in contact on this thread for any issues or suggestions I may at least have..
Keep up the great work SNRB~

 

[gallerocks]

i want to know how this works using 3g bc thats what I would mostly use it for. Let me know.

 

[JerryScript]

Ok, I'm pretty sure I've nailed my issues down to 3G.

I can make perfect calls to the echo number over wifi, no issues whatsoever, I can even hear my cat purring in the background.

(note- I refer to packets alot below, because that seems to be the issue with the audio stream)

When I switch to 3G at my home, I have issues right away. I only get 1 to 2 bars at home most of the time, and even get reduced to 1x occaisionally. It seems to be an issue with the packets being sent over 3G, you can tell you are only hearing a packet at a time, that is the stuttering issue (many thanks for that echo number). This happens regardless of what settings I use in troubleshooting, though the Outgoing Audio Processing setting does make the packets come in quicker, they are still one packet at a time which is the stuttering. Sometimes the packets are about 100ms apart, other times they seem to be more like 500-700ms apart.

This is with the latest GrooVeIP version 1.1.0 on Optimus V running aospCM7 04/27 release.

 

[mmarz]

All my tests have been over wifi to remove all side-effects caused by poor bandwidth. 3G speed vary wildly based on network congestion. In theory, it has plenty of bandwidth to work. In practice, you'll never know if you have enough bandwidth until you call. It is very YMMV.

 

[RoboBot]

My WIFI is over a 4G hotspot. That could be a source of contention, though GVoice Callback + SIP client still DOES work dandy. I don't know. I'd like the app to work, like most other people. Heh.

The other apps I run are minimal, nothing that controls battery/radios, etc.

 

[mmarz]

One small problem and one big problem.

Small problem: "Ignore" is misspelled on the incoming call dialogue.

Big problem: If I get an incoming call, and I am not around to answer it, my phone will ring and vibrate non-stop until I press answer or ignore. I have only tested this by calling from another GV account, but the behavior is consistent.

 

[snrb_labs]

One small problem and one big problem.

Small problem: "Ignore" is misspelled on the incoming call dialogue.

Big problem: If I get an incoming call, and I am not around to answer it, my phone will ring and vibrate non-stop until I press answer or ignore. I have only tested this by calling from another GV account, but the behavior is consistent.

I haven't been able to reproduce that, but someone else mentioned that happening to them as well. We're adding a timer for incoming calls. If the call isn't answered or disconnected in like 30 seconds we'll assume the signalling message never arrived and drop the call.

Also will fix the typo.

 

[scootincivic]

e're adding a timer for incoming calls. If the call isn't answered or disconnected in like 30 seconds we'll assume the signalling message never arrived and drop the call.

Now that is a great idea..
If you can (if anything) see if you can have it set to 5 or 10sec increments so we can have it either 5sec ring on up to what ever GV allows until Voice-mail pickup~

I for one would like to have a feature (or at least a button) for making an incoming calls go to voice-mail..
Ignore is nice and all however the normal 10 rings or so will still take place to the caller in witch many times my buds just cant stand to wait that many rings..
Just a thought as Im not sure if its possible to make incoming calls go strait to VM due to GV's limitations~

 

[digitaljeannie]

Just a thought as Im not sure if its possible to make incoming calls go strait to VM due to GV's limitations~

Within your google voice settings (on the website or in the GV app) you can set all your call to go directly to voicemail by turning on the "Do Not Disturb" feature.

 

[JerryScript]

I can confirm that the stuttering issues I have experienced where the person I call cannot hear me or hears everything choppy/stuttering, is due to the quality of the 3G connection.

I used the echo number posted again today, and made several calls via wifi with zero issues, crystal clear quality.

I then switched to 3G, and made a long call to the echo number rather than hang up 10-15 seconds after hearing stuttering. I found that the stuttering would get worse, then better, back and forth, but never go away completely. This was over a 5 minute test call. The stuttering ranged from bad but you could still kinda understand what was being said, to so bad you couldn't string together a recognizeable sentence. At times the delay was less than a half second, others it was over 2 seconds. Checking the Outgoing Audio Processing box did improve things a bit, but not enough to make things understandable when the stuttering was bad or the delay was long.

BTW- I get poor 3G at home, so I run a hybrid PRL which seems to have me tower hopping alot at home, according to the OpenSignal app.

Funny BTW- Once sentence I said while testing with the echo number was
"This seems to go from bad to good to bad and back again."
What I heard was
"...seems ...go ... om bad... to bad... again."

Love the app, glad I bought it, works great when I have a good signal over wifi, just wish I could get good calls over 3G as well.

 

[gallerocks]

yeah this app will be no good for me if it doesn't work well with 3g bc i don't use wifi that often on it and im always on the run. Let me know if it gets fixed to work better with 3g. Thanks

 

[mmarz]

It's not the app that is broken. It is your personal 3G connection that is not good. You need a minimum amount of bandwidth in order to do voip with GV or any other service. Mine works fine over 3G.

 

[ejlmd]

Shouldn't have to. I know Google Voice is having some issues today. Guess lot of people are making calls cause of mother's day. The one you need to make sure you're logged out of is google chat.

Since yesterday's update my phone rings once, then stops. I'm not logged in to google chat anywhere else. Of course Google Chat is checked for forwarding in Google Voice phone settings.
This is on latest bumblebee froyo rom.

Edit: SOLVED. It was a ringtone issue from latest bumblebee update.

 

[Takenover83]

It might work fine over 3G for you. It does for my brother who is 3hours away. Your mileage may vary. But honesly, the app is $4. You do not have much to lose and a whole lot to gain (more minutes!).