-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[APP] GrooVe IP - Google Voice VoIP
- Thread starter snrb
- Start date
zuben el genub
Extreme Android User
Can this be used on demand? I've got a Nexus S on TMO and it doesn't have wifi calling.
We travel to areas with one or no bars and would like to keep in touch with our pet sitter. Finally got Google voice to make a call from the pc.
When we are home, would prefer network and keep GV out of it.
We travel to areas with one or no bars and would like to keep in touch with our pet sitter. Finally got Google voice to make a call from the pc.
When we are home, would prefer network and keep GV out of it.
Whyzor
Android Expert
Yes, the app has an 'exit' menu to completely disable it (wish more apps had this), then next launch will bring it back (displayed in notification bar)
As mentioned by Whyzor there is an exit menu in the app. You can also set start/stop times for the app to automatically start and shutdown. For example if you didn't want it to run at night because you have free night/weekends you could have it shutdown at 9pm and start up again at 6am
JohnDotCom
Lurker
Using GrooVe version 1.2.20... Getting better than cell network quality voice with GrooVe and a Plantronics headset, over WiFI, with one exception (a big one... 2 to 3 second delay)! I have weeks of experience (really frustration) trying many combinations of settings, but I am very incouraged by this improvement, if I could only shorten the delay. What causes delay? It seems that the delay is only on the outgoing voice stream, not the incoming voice stream.
johndotcomsam
Lurker
I see that you "brotherswing" and "idoun" are using VM... I am too. I am using the latest GrooVe 1.2.20 over WiFi, and the voice quality is better than the VM / Sprint mobile network voice quailty. I have one big problem remaining... a 2-3 second delay. Any thoughts, anyone?
johndotcomsam
Lurker
I see that you "idoun" and "brotherswing" are using VM... I am too. I am using the latest GrooVe 1.2.20 over WiFi, and the voice quality is better than the VM / Sprint mobile network voice quailty. I have one big problem remaining... a 2-3 second delay. Any thoughts, anyone?
A few things can cause delay. First being latency on the network. It can also be caused by a task killer or battery manager app on the device interfering with calls. Or an app running in the background using CPU or data, I would suggest trying to stop any background apps to see if that improves the delay. In GrooVe IP you can also try the two lock settings. I'd also suggest trying Keep Screen Alive and trying to change the mic buffer size. Try small and x-large to see if either works better.
JohnDotCom
Lurker
No Task Killers or managers, except the native Froyo. No Battery Managers, except me with my stack of 5 batteries always running in chargers. I am running Watchdog to watch foreground and background apps and have white listed IPGrooVe and blacklisted for killing (other known offenders such as Maps, Appstore, Market, and Astrid @ 66% CPU usage).
I will try small and large Mic Buffers and report back. What is the option Synchronize voice? I read the description in the App (great policy... don't change it). The name and description implies preventing interference from the quasi duplex voice streams, but it doesn't say that. What (in more detail, does it do)?
When you say the two lock settings and then you mentioned Keep Screen On... I will add the high performance lock here. I tried an experiment. I said to the other party, I am going to count to 10, when you hear 3, say "Now". I then said, 1...2...3...4...5...6 and I didn't hear "Now" till I said 6.
JohnDotCom
Lurker
Edit: you said, kill any background app running during a call, right? Does GrooVe run any background processes, during a call?
semperfi1860
Lurker
What settings would you recommend for the HSPA Galaxy Nexus? I've been tinkering for a while, but voice quality has always been variable.
Only two settings I would adjust are Keep Screen Alive and the mic source. For mic source try Android Default and VoIP.
GrooVe IP has one background service that runs when the app is signed in and during calls. By other apps I meant like Google+ or Facebook or dropbox. Anything that could be uploading data or syncing in the background.
Not sure what caused the issue you had with ICS. The app does work with ICS on other devices. It could be an audio driver issue on that device. Or it could be that something was going into a power saving state when the screen turned off. You can try the Keep Screen Alive checkbox to see if that helps. It could also be that the default setting are no longer the best settings for that device with ICS. So something like changing the mic source from under troubleshooting or enabling Audio Processing may also help.
Frogbone
Well-Known Member
I currently have my cell phone number forwarded to Google Voice while travelling in Europe. Groove IP works well to stay in touch but my callers tell me that the phone rings for a very long time before I answer or before it goes into GV voicemail.
On my end the phone rings once or twice before I get to it though.
I am worried that some callers might hang up before getting through to me or the voicemail system.
Any suggestions?
Thanks
On my end the phone rings once or twice before I get to it though.
I am worried that some callers might hang up before getting through to me or the voicemail system.
Any suggestions?
Thanks
Hi snrb
Yesterday my contract with T-Mobile ended, and I ported my phone number over to Google Voice with the intent to use GrooVe IP in order to make and receive calls among my family and friends over WiFi or data to the number they're familiar with. (I'm moving overseas next week.)
Google finally ported the number over early this morning and when I woke up, I attempted to set-up the Google Voice app on my phone (HD2), not knowing that I could not do so without a physical phone number. (I thought that the initial verification to port my number was what they needed to set up the service.) Anyway, I assumed the GrooVe IP application did not need the Google Voice app installed on my phone in order to work, and indeed I was correct. I was able to make and receive calls both on WiFi and data without having the application installed, or a physical number in Google Voice.
I was able to make calls all day up until (I think) I decided to use my new T-Mobile prepaid plan to set up the Google Voice app on my phone... it ended up setting up the app on my phone, but in the process (I believe) killed my ability to hear the person on the other line, and for them to hear me. (The reason I went ahead and set up the Google Voice app was to use the Google Voice Full Integration app to send and receive text messages to GO SMS, rather than the Google Voice app.)
I have no idea what is going on. I am able to make calls using the Gmail app, I can see history of my calls update not only in Google Voice, but also my phone's dialer... The calls are even able to connect... just neither the recipient nor I can hear each other.
This started after I noticed in the Google Voice history that I had missed a call from my dad that didn't show up in my dialer history. (His call came before several other calls I made and received.) When I tried to call him back (after I had set up this stupid number on Google Voice) the phone dialed and connected, but I could not hear him. When I tried to hang up, the button was responding to my touch, however it was not ending the call. I ended up force closing the app and restarting the phone, which led to me to the point where the calls connect (incoming and outgoing), but neither party can hear anything afterwards. (I talked to my over the Gmail app, and she explained she could not hear anything either after the connection.)
*One other note, the last call in which I was able to hear and be heard, I turned Audio Processing on right before, because my friend's voice sounded very robotic and tinny. I turned it off afterwards, nothing.
*Last note, there is no dialing tone on my end in GrooVe IP. My brother just called me and I called him back while I had Synchronize Voice and Audio Processing checked. Still nothing.
I hope I didn't screw this up. :\
EDIT: ****ing reboot fixed it, for now, I guess. I'm so confused because when I reboot after it initially started screwing up, the problem got worse. Now it's working... >_<
Yesterday my contract with T-Mobile ended, and I ported my phone number over to Google Voice with the intent to use GrooVe IP in order to make and receive calls among my family and friends over WiFi or data to the number they're familiar with. (I'm moving overseas next week.)
Google finally ported the number over early this morning and when I woke up, I attempted to set-up the Google Voice app on my phone (HD2), not knowing that I could not do so without a physical phone number. (I thought that the initial verification to port my number was what they needed to set up the service.) Anyway, I assumed the GrooVe IP application did not need the Google Voice app installed on my phone in order to work, and indeed I was correct. I was able to make and receive calls both on WiFi and data without having the application installed, or a physical number in Google Voice.
I was able to make calls all day up until (I think) I decided to use my new T-Mobile prepaid plan to set up the Google Voice app on my phone... it ended up setting up the app on my phone, but in the process (I believe) killed my ability to hear the person on the other line, and for them to hear me. (The reason I went ahead and set up the Google Voice app was to use the Google Voice Full Integration app to send and receive text messages to GO SMS, rather than the Google Voice app.)
I have no idea what is going on. I am able to make calls using the Gmail app, I can see history of my calls update not only in Google Voice, but also my phone's dialer... The calls are even able to connect... just neither the recipient nor I can hear each other.
This started after I noticed in the Google Voice history that I had missed a call from my dad that didn't show up in my dialer history. (His call came before several other calls I made and received.) When I tried to call him back (after I had set up this stupid number on Google Voice) the phone dialed and connected, but I could not hear him. When I tried to hang up, the button was responding to my touch, however it was not ending the call. I ended up force closing the app and restarting the phone, which led to me to the point where the calls connect (incoming and outgoing), but neither party can hear anything afterwards. (I talked to my over the Gmail app, and she explained she could not hear anything either after the connection.)
*One other note, the last call in which I was able to hear and be heard, I turned Audio Processing on right before, because my friend's voice sounded very robotic and tinny. I turned it off afterwards, nothing.
*Last note, there is no dialing tone on my end in GrooVe IP. My brother just called me and I called him back while I had Synchronize Voice and Audio Processing checked. Still nothing.
I hope I didn't screw this up. :\
EDIT: ****ing reboot fixed it, for now, I guess. I'm so confused because when I reboot after it initially started screwing up, the problem got worse. Now it's working... >_<
Hi,
I'm guessing you have Google Voice setup as your voicemail for your regular cell number? The callers will get many rings because it will ring on your regular cell before being sent to voice mail. That will trigger it to ring on your Google Voice account, which causes GrooVe IP to ring. But since it's not a regular call you won't get the full number of rings (why you only hear 2) before they get sent to your Google Voice voicemail.
Think you also emailed us, responded to your email
Frogbone
Well-Known Member
No, I am not using Google Voice's voicemail for my regular number. I use Sprint's VVM.
The Sprint number is currently forwarded to the GV number via *28
Whyzor
Android Expert
I've noticed on occasion the Groove IP connection disconnects on my wifi network, and only noticed this when I wake the phone from sleep, then it reconnects automatically. Most of the time it works fine, I haven't determined an exact time or cause yet. It would be nice to have an option to have an audio notification when it goes from green connected to red disconnected when the phone is unattended, and maybe even repeat audio beep every 5 mins until the user acknowledges it. Otherwise I have no idea that GV disconnected thinking it's just idling fine.
BTW I'm using this on LG G2x running CM7. No troubleshooting or enhancement tweaks used in the app settings, all of them are disabled and it works fine otherwise.
BTW I'm using this on LG G2x running CM7. No troubleshooting or enhancement tweaks used in the app settings, all of them are disabled and it works fine otherwise.
Hi,
I'll take a look at adding an audible notification. It sounds like maybe your device is putting the wifi into a power saving state when the screen is off for some time. There should be a setting for that in the android settings. In GrooVe IP you can also try the Partial Wake Lock and/or High Perf WiFi Lock to see if they help. There's also an auto resign in interval you can configure to have the app automatically re-sign in at that interval
Hi,
Can you try setting the Partial Wake Lock setting in GrooVe IP to see if that helps the app detect the incoming call earlier? It sounds like your CPU may be in a power saving state so GrooVe IP isn't detecting the call until only 1 or 2 rings before voice mail.