- 05-02-2011, 08:25 AM #51
- 05-02-2011, 01:34 PM #53Banned
- 60 Posts
- 05-02-2011, 02:13 PM #54Banned
- 60 Posts
The Developer should pimp this on some of the travel forums I know on the Carnival Cruise Line board on Cruise Critic they are always looking for cheap/free ways to call home from foreign ports assuming that it would work on wifi outside the usa.
- 05-02-2011, 02:59 PM #55
I'm pretty excited about the next version.
- 05-02-2011, 03:01 PM #56
- 05-02-2011, 03:55 PM #57
- 05-02-2011, 04:00 PM #58
I just don't want to over-promise. Haven't really tested anything that was coded over the weekend. But proximity sensor support, first stab at bluetooth, native call log integration, and registering as a dialer (so you can click a phone number in an email and GrooVe IP is an option to use to dial) all got "code completed" this weekend. Now just have to test and debug.
- 05-02-2011, 04:07 PM #59
Sounds awesome. That should make many people happy. Guess you didn't take a day off as planned. Did you ever find out anything with the outgoing codecs? From my understanding, Google Voice supports a number of codecs for outgoing, but is limited for incoming? I remember reading about it somewhere, just do not remember where...
- 05-02-2011, 04:10 PM #60
- 05-02-2011, 04:53 PM #61
I know you warn that you need to be logged out of our various gmail accounts for incoming calls to work, but I haven't seen this to be necessary for me. I have a gchat client and gmail checking client open on a desktop. I have my phone setup with the gmail app, google voice app, and the google talk app always on and logged in. And to top it off, I have my google voice account set to forward incoming calls both to gtalk and my cell number. I have gotten all of my incoming test calls so far from a land-line. Both groove IP and my cellphone ring.
Just letting you know that maybe the problem you are experiencing is not as clear cut as you think.
- 05-02-2011, 05:12 PM #63
Not sure what causes it, but seems like something triggers Google to route the calls to other instances. Someone suggested it could be whichever one had activity last. Not sure.
For people who have issues with incoming calls the quickest suggestion is to logout from their other instances. If you're not having problems then there's really no need to.
- 05-02-2011, 06:05 PM #64
I am having a issue where the call is fine for a few minutes, then after that the person can no longer hear me. I can hear them just fine. Last time it happened I was 3min 45sec into a call. I do run "wifi keep alive" when I am using wifi. I will test "Keep Screen On" and see if that helps.
Edit #1: Just happened again, only about a minute into the call.
Edit #2: I have plenty of bandwidth but the person is telling me, they can hear me fine then suddenly, it breaks up really really bad on my end. I can always hear them just perfect. But for some reason they stop being able to hear me. Maybe some weird bug when sending audio? Because incoming audio is always perfect. It never breaks up.
- 05-02-2011, 06:07 PM #65
- 05-02-2011, 06:15 PM #66
- 05-02-2011, 06:54 PM #67Daydream Believer
- 2,058 Posts
I had the same troubles today I experienced yesterday with GrooVeIP registering with GV. Only way I could get it to register is by opening the browser to google.com, switching to classic view, signing out, then signing back in. A few seconds later, GrooVeIP's icon switched to green and all was good.
I think my issues are with google not syncing properly. When this first occured, I began by opening email, and trying to load gmail, but it reported an error. No matter what I did in sync settings or gmail settings on the phone, I could not sync gmail or get GrooVeIP to register. Only by following the browser based steps I listed could I get either gmail or GrooVeIP working.
I have seen some reports of gmail sync issues in threads relating to my ROM, aospCM7, but they have not been confirmed bugs, so I don't know where the fault is, gmail, the ROM, or something else.<> Github/JerryScript <>
- 05-02-2011, 06:59 PM #68
Google+ Devices: HTC Mogul, Touch, TP, TP2, Samsung Moment & Intercept, Motorola Triumph, LG Optimus V & Slider, Nook, Iconia Tab, HTC Sensation
- 294 Posts
- 05-02-2011, 07:08 PM #69
- 05-02-2011, 08:41 PM #70
- 05-02-2011, 09:58 PM #71
- 05-02-2011, 10:15 PM #73
- 05-02-2011, 10:33 PM #74
- 05-02-2011, 11:37 PM #75