GrooVe IP - Google Voice VoIP

[xur17]

Don't know what settings you have currently in the app. I know that changing the mic source to Android Default improved things in ICS, which is weird because VoIP is the new mic source specifically for VoIP applications, but it seems not to be working well in ICS.

I had issues even with the default settings (after a fresh install). I was using the default microphone, but I will try Tue android default option, and see if that improves stuff.

 

[SpeedEuphoria]

The dialpad is fine when placing the call. Just during the call to select options its extremely laggy, most of the time the numbers dont even light up when pressed, sometimes the 1st number pressed will stay lit and wont unlight till when it finally sends the numbers

 

[snrb_labs]

The dialpad is fine when placing the call. Just during the call to select options its extremely laggy, most of the time the numbers dont even light up when pressed, sometimes the 1st number pressed will stay lit and wont unlight till when it finally sends the numbers

Can you email us? Might have to send you a build with logging to see where the delay is

 

[SpeedEuphoria]

I did email, I'll pm you the address

 

[xur17]

I had issues even with the default settings (after a fresh install). I was using the default microphone, but I will try the android default option, and see if that improves stuff.

I just tried the default android microphone, and I had the same issue (I tried all other microphone options too). Any other ideas? I would really love to fix this!

 

[snrb_labs]

I just tried the default android microphone, and I had the same issue (I tried all other microphone options too). Any other ideas? I would really love to fix this!

What settings have you tried in the app? I'd first suggest increasing the mic gain to x-large and enabling Keep Screen Alive. If that doesn't help then I'd try Synchronize Voice. If still nothing then disable Synch Voice and enable Audio Processing. Odd thing is I just worked with someone else with a Nexus S and ICS. The only setting change they needed was to change the mic source to android default. Not sure what the difference is.

 

[snrb_labs]

Version 1.2.14
- Bug Fixes
- Change auto selected mic for ICS to android default
- Fix bug with bluetooth handset not disconnected when call is ended
- Change default settings for LG Enlighten
- App should display dialer instead of settings on first load
- Allow higher speaker volume settings (previously the speaker volume in audio/echo had a max of 10, it is now 30)
- Redirect help button to snrb Labs website instead of text help

 

[xur17]

What settings have you tried in the app? I'd first suggest increasing the mic gain to x-large and enabling Keep Screen Alive. If that doesn't help then I'd try Synchronize Voice. If still nothing then disable Synch Voice and enable Audio Processing. Odd thing is I just worked with someone else with a Nexus S and ICS. The only setting change they needed was to change the mic source to android default. Not sure what the difference is.

I just uninstalled, rebooted, and installed the lasted version from the android market. I changed the microphone to android default, and still had the same issue. I tried each of the suggestions above, each with the same results.

I ran a logcat while making a call, and I noticed that as soon as the call starts the following message appears in the debug window. This message repeats until the call is ended, and displays at a rate of approximately 10-20 messages per second.

E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting

 

[smoovedude12]

hi i have a nexus s4g and since the last update i cant hear anyone speaking....ive changed the accept call time and even pressed 1 but nothing seems to be working

any suggestions?

 

[snrb_labs]

hi i have a nexus s4g and since the last update i cant hear anyone speaking....ive changed the accept call time and even pressed 1 but nothing seems to be working

any suggestions?

Would suggest doing a clean install (uninstall the app, restart the device, then install the app) it could be something just wasn't installed properly. Are you running ICS? We changed one setting, the mic source from VoIP to Android Default. You can try setting it back to VoIP if you are running ICS.

 

[karen's 1st android]

i have the verizon galaxy nexus and am having issues with garbled phone calls using groove ip. i've messed with the setting a ton and have phone calls to where i can be understood and can understand the other caller...but the voice quality is not great.

any suggestions?
thanks!!!

 

[staplebox]

Alright - I've read the whole thread and registered just to post here.

I've been running this app for about a month now and it has been pretty solid. The biggest complaint is that people on the other end can't hear me well - but it is hard for me to judge how good or bad that may be. Overall it has been very good because I am usually around wifi and I don't talk on the phone very much. Perfect companion to the T Mobile $30 / 100 minute plan. Saves me a ton.

I am looking for any cheats/shortcuts to the best settings for a Nexus S running ICS on T-Mobile. This app has so many settings that I get lost in them all. I see a couple of NS ICS posts in the last few pages and it looks like the only setting recommended is the Android Default mic setting. Anything else?

Also - is it possible to use this app on Edge? It seem to work over Edge sometimes but I am not sure what the exact signal is when I am moving on the road.

And finally- any work around to the Amazon App store being so slow with their app updates? I bought this on sale there and now I regret that. If not, I may need to re-buy it through the Android Market and drop Amazon for good.

 

[snrb_labs]

i have the verizon galaxy nexus and am having issues with garbled phone calls using groove ip. i've messed with the setting a ton and have phone calls to where i can be understood and can understand the other caller...but the voice quality is not great.

any suggestions?
thanks!!!

Which version of the app do you have? Version 1.2.14 has the settings we use on our Galaxy Nexus set by default. If you are using WiFi would also suggest Keep Screen Alive. If you have task killer or battery manager apps installed those could interfere with calls.

 

[snrb_labs]

Alright - I've read the whole thread and registered just to post here.

I've been running this app for about a month now and it has been pretty solid. The biggest complaint is that people on the other end can't hear me well - but it is hard for me to judge how good or bad that may be. Overall it has been very good because I am usually around wifi and I don't talk on the phone very much. Perfect companion to the T Mobile $30 / 100 minute plan. Saves me a ton.

I am looking for any cheats/shortcuts to the best settings for a Nexus S running ICS on T-Mobile. This app has so many settings that I get lost in them all. I see a couple of NS ICS posts in the last few pages and it looks like the only setting recommended is the Android Default mic setting. Anything else?

Also - is it possible to use this app on Edge? It seem to work over Edge sometimes but I am not sure what the exact signal is when I am moving on the road.

And finally- any work around to the Amazon App store being so slow with their app updates? I bought this on sale there and now I regret that. If not, I may need to re-buy it through the Android Market and drop Amazon for good.

For the Nexus S ICS leave the app defaults and change only the mic source to Android Default. That's what we've done in version 1.2.14.

We upload the update to amazon at the same time we post it on the android market. But Amazon does their own testing and adds their copy protection before making the update available.

 

[xur17]

I just uninstalled, rebooted, and installed the lasted version from the android market. I changed the microphone to android default, and still had the same issue. I tried each of the suggestions above, each with the same results.

I ran a logcat while making a call, and I noticed that as soon as the call starts the following message appears in the debug window. This message repeats until the call is ended, and displays at a rate of approximately 10-20 messages per second.

E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11d1830 vs. 0x11269d0); auto-correcting
E/dalvikvm( 2516): JNI ERROR: env->self != thread-self (0x11269d0 vs. 0x11d1830); auto-correcting

I just tried a factory reset on my phone (T-Mobile Nexus S), and installed stock ICS 4.0.3, and I am still having this issue (audio breaking up, and latency becoming horrible). I have tried multiple wifi networks, and done everything possible to try and fix this. Any help would be greatly appreciated!

I'm on a low minute T-Mobile plan, so I really need to use Groove IP. Thanks in advance, and I really appreciate the software.

 

[primeasus]

Hi,

I installed Groove IP on my Asus Transformer Prime. Using the tablet I can hear the other party fine. Unfortunatly, it is not the same story for the person on the other side. If I move the tablet slightly, the noise it makes overpowers my voice. I have spent hours changing all the settings (echo settings, microphone gain, auto processing, synchronize voice, mic buffer, etc) with no luck.

Google voice works perfectly using my laptop. My tablet work perfectly using other applications (such as Skype). I really don't know what to do to make this work anymore. Do you have any suggestions?

 

[snrb_labs]

Hi,

I installed Groove IP on my Asus Transformer Prime. Using the tablet I can hear the other party fine. Unfortunatly, it is not the same story for the person on the other side. If I move the tablet slightly, the noise it makes overpowers my voice. I have spent hours changing all the settings (echo settings, microphone gain, auto processing, synchronize voice, mic buffer, etc) with no luck.

Google voice works perfectly using my laptop. My tablet work perfectly using other applications (such as Skype). I really don't know what to do to make this work anymore. Do you have any suggestions?

On a tablet I wouldn't use audio processing. Is the issue only when you move the tablet? Sounds like something is brushing against the mic. You can try the mic source settings, I'd suggest Android Default or VoIP.

 

[StephenUSA]

The app works very well. I have two suggestions.
1. I would like to be able to change the ring. I have not been able to find that option.
2. The app is fairly large, so I have it installed on the SDcard. This installation does not allow the app to start automatically when the phone is re-booted. I believe that this is a limitation of the Android OS. How about writing a companion app which has a tiny footprint that can be installed on the on-board memory? The tiny app can start automatically when the phone is booted. Its only task is to start the Groove IP app which resides on the SDcard. Far fetched?

 

[snrb_labs]

The app works very well. I have two suggestions.
1. I would like to be able to change the ring. I have not been able to find that option.
2. The app is fairly large, so I have it installed on the SDcard. This installation does not allow the app to start automatically when the phone is re-booted. I believe that this is a limitation of the Android OS. How about writing a companion app which has a tiny footprint that can be installed on the on-board memory? The tiny app can start automatically when the phone is booted. Its only task is to start the Groove IP app which resides on the SDcard. Far fetched?

For #1 there is a ringtone override setting. Believe it's under the audio/echo settings. That will change the incoming ringtone.

#2 is a limitation of the android os. Not sure about writing the companion app but will write that down.

 

[galaxynexususer7]

I have a Galaxy Nexus and boosting the "speaker volume" up or down seems to have no effect. The volume is still quite low compared to when I would use Google Voice in conjunction with my regular cell service. Can someone recommend Galaxy Nexus settings?