• 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

I believe I've notice a battery hit on 1.2.4. Never saw GrooveIP near the top of any battery stats until today. Now it's #1 on partial wake usage.
 
tcat007 said:
I believe I've notice a battery hit on 1.2.4. Never saw GrooveIP near the top of any battery stats until today. Now it's #1 on partial wake usage.
Click to expand...

The partial wake lock keeps your CPU awake, it will use battery. If you don't need it on, turn it off.
 
Trying to purchase your app. I click on BUY, then I click on ACCEPT PERMISSIONS. I get the same message over and over again: Server Error. Many thanks for any help anyone can provide.
 
Version 1.2.5 & Version 1.2.6
- Allow rotation by default
- Improve landscape layout of in-call screen for phones and smaller tablets
- Fix a force close on Honeycomb devices when hanging up
- Bug fixes
 
I just installed 1.2.6. But my phone only has 240x320 resolution. So, with the new dialer-contacts-recent bar, the dial pad becomes very crowded. Actually, I am not able to see the whole number in the input bar. Can you fix this in the next version? Thank you
 
HI,

This is a great App that I don't need Csipsimple+Sipgate anymore. I have it worked in Starbuks, but not in some other wifi. I think is the Firewall issue.

Just out of curiosity. How does it work out with Firewall? Is it simply using core functions from Gtalk,Gmail Video and Audio Chat Plugin,'s XMPP, Dingle? So that would essentially like using those services on Android?

My wireshark capture from my Laptop is showing all TCP/TLS. That's probably how Gtalk/Gmail works well in strict firewall, like in Public Libraray. I had problem with SIP/UDP in those environment.

I am a networking person and naturally want to know a bit more to get more confidence in this apps way dealing with Firewall so I can introduce more friends to use it with more assurance.

I introduced GV+Sipgate for some friends and it didn't work with SIP/UDP in some place and they complainted a bit.

thanks
peng
 
zyiyong said:
I just installed 1.2.6. But my phone only has 240x320 resolution. So, with the new dialer-contacts-recent bar, the dial pad becomes very crowded. Actually, I am not able to see the whole number in the input bar. Can you fix this in the next version? Thank you
Click to expand...

Will take a look, if you could email us screen shots to snrb.labs@gmail.com that would be helpful.
 
Version 1.2.7
- Fix dialpad not appearing in calls for certain tablets

Sorry for the deluge of updates. Amazon still has 1.2.4, we'll be working with them to go straight to 1.2.7. If that isn't possible 1.2.5 will come out and then we'll update to 1.2.7 and skip 1.2.6
 
When looking at the Atrix I was told the Samsung Galaxy SII will be coming out in October. Think I will hold off to see what it looks like.
Will the App support this phone?
Thanks
 
rfb813 said:
When looking at the Atrix I was told the Samsung Galaxy SII will be coming out in October. Think I will hold off to see what it looks like.
Will the App support this phone?
Thanks
Click to expand...

The Galaxy SII is already out outside the US. We've had a few people use the app on the phone and it works well for them.
 
HI snrb,

I saw an early post about port 443 and port 5222. We all know that Google's Gmail voice/video chat works, even in strict firewall situation, like, in company, public library, public shcool, etc. However, it sees, Gtalk's connection to port 5222 is a problem(being blocked). Even it's connected at some place and we can ring each other, RTP is blocked once phone is picked up.

Would that be possible for your team and maybe some help from community, or google's libjingle, to get GrooveIP uses TLS/TCP 443 to tunnel all Singling and RTP voice?

Thanks so much for the work.
peng
 
I noticed that in the newer versions, there is a delay when receiving calls. I mean, when someone calls you, it takes several seconds (about 10s?) for your phone to ring. While in gmail, it will ring immediately.
I used the older versions of groove ip when the gmail has the higher priority. At that time, it seems like my phone will actually ring immediately like in gmail.
Can you explain this? Can this situation be improved?
Thank you!
 
zyiyong said:
I noticed that in the newer versions, there is a delay when receiving calls. I mean, when someone calls you, it takes several seconds (about 10s?) for your phone to ring. While in gmail, it will ring immediately.
I used the older versions of groove ip when the gmail has the higher priority. At that time, it seems like my phone will actually ring immediately like in gmail.
Can you explain this? Can this situation be improved?
Thank you!
Click to expand...

Newer versions have increased priority so calls should be forwarded to the app first. If you're not getting calls immediately you can try the partial wake lock setting in the app troubleshooting options.
 
linuxlinux said:
HI snrb,

I saw an early post about port 443 and port 5222. We all know that Google's Gmail voice/video chat works, even in strict firewall situation, like, in company, public library, public shcool, etc. However, it sees, Gtalk's connection to port 5222 is a problem(being blocked). Even it's connected at some place and we can ring each other, RTP is blocked once phone is picked up.

Would that be possible for your team and maybe some help from community, or google's libjingle, to get GrooveIP uses TLS/TCP 443 to tunnel all Singling and RTP voice?

Thanks so much for the work.
peng
Click to expand...

TCP port 5222 is used for call setup and signalling. Voice traffic is UDP and GrooVe IP uses ports 19003/4. We are going to make the UDP ports for voice configurable in the app so you can switch those to ports you know are open. We did experiment with port 443 but were unable to sign in using that port. It is something we are going to revisit.
 
Howdy,

I have a Samsung Galaxy S Wifi 5.0 and I am having some problems with the call screen. I can make calls just fine, but the call screen becomes unresponsive. The person can still hear me and all, but nothing will respond on the screen. I can't hang up, use the speaker, use the number pad, or anything. If I want to hang up before the other end hangs up, I have to force quit the app.

Any thoughts on what's going on?
 
uwflatlander said:
Howdy,

I have a Samsung Galaxy S Wifi 5.0 and I am having some problems with the call screen. I can make calls just fine, but the call screen becomes unresponsive. The person can still hear me and all, but nothing will respond on the screen. I can't hang up, use the speaker, use the number pad, or anything. If I want to hang up before the other end hangs up, I have to force quit the app.

Any thoughts on what's going on?
Click to expand...

Android has a flag to ignore accidental cheek presses on a screen. We set that on the in-call screen. My guess is that device doesn't implement that flag properly and is ignoring all presses instead.
 
I have a problem when i call someone with Groove IP. I cannot hear the person, or the voicemail for the first few seconds. Basically the phone rings a few times and then the person either picks up and says "Hello", and they are waiting for me to respond, but I never hear the initial "Hello", so there is just silence. Same thing with going to voicemail, I never hear their greeting because of the delay.
After that initial delay, everything is fine.

Any ideas on how to fix?

Thanks.
 
EP24 said:
I have a problem when i call someone with Groove IP. I cannot hear the person, or the voicemail for the first few seconds. Basically the phone rings a few times and then the person either picks up and says "Hello", and they are waiting for me to respond, but I never hear the initial "Hello", so there is just silence. Same thing with going to voicemail, I never hear their greeting because of the delay.
After that initial delay, everything is fine.

Any ideas on how to fix?

Thanks.
Click to expand...

Not really much you can do to fix that. On different networks you'll have a different connection delay.
 
linuxlinux said:
HI Snrb,

Pelase do spend some time researching this. Here's a link
Blocking Google Talk in your Organization C S Shyam Sundar's Thoughtpad

also this,
How to configure Pidgin to work with Google Talk at ibn Mas’ud

Gtalk does support all 5222,443,80,etc, with Pidgin and other clients. Please research how Pidgin make it work and hope you can make it work with groove so we can use it in public library and school and other restricted firewall situaiton.
thanks
peng
Click to expand...

As mentioned before, it is something we have spent time looking into and plan on spending more time.
 
Hey, first off I love this app. It's amazing.

I know this is most likely not the apps fault, but it would be nice to use the native dialer when you don't have a sim card. IF you know a way to do that, it would be amazing.
 
himynamesnoah said:
Hey, first off I love this app. It's amazing.

I know this is most likely not the apps fault, but it would be nice to use the native dialer when you don't have a sim card. IF you know a way to do that, it would be amazing.
Click to expand...

Will take a look and see if that is possible.
 
You must log in or register to reply here.
Back
Top Bottom