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

[jlstark]

I'm running AOSP CM7 and version 1.2.0 of GrooVe IP.

I can receive calls but when I make a call it dials, rings and then the dialer closes, phone call ends and I go back to my home screen.

It behaves this way on both WiFi and network using either native dialer or app dialer.

Anyone have any suggestions?

 

[Darkside86]

I'm running AOSP CM7 and version 1.2.0 of GrooVe IP.

I can receive calls but when I make a call it dials, rings and then the dialer closes, phone call ends and I go back to my home screen.

It behaves this way on both WiFi and network using either native dialer or app dialer.

Anyone have any suggestions?

I had the same problem after installing cm7 on my V. I restored a froyo backup and my grooveip works fine now. Im thinking it has something to do with GB.

 

[blarf]

Looks like it crashes as soon as we try and read from the mic. Also see this error in a few places

E/AudioHardwareMSM72XX( 113): Parsing error in AudioFilter.csv.

It's a red herring. You'll see that on pretty much any phone with any sort of debug build. It's a misnomer as it's not actually parsing AudioFilter.csv each time. Rather it means is that the fancy on-chip audio postprocessing stuff has not been enabled because there was an error processing the file at boot time.

 

[JerryScript]

Under settings>>troubleshooting>>Synchronize Voice prevents the crash, but I don't hear my voice on the echo number I test with, just static. If another logcat or dmesg would help, I'll be happy to post one.

 

[pcp135]

Does anyone get a good voice quality from both side of the conversation using this app? If so, would you mind posting some settings so that we can have an idea of what works and what does not. I have tried to use it over wi-fi and its always pretty poor quality. The echo number I have tried also gives me static instead of my voice so I am pretty sure I am not using the optimum settings.

 

[snrb_labs]

Does anyone get a good voice quality from both side of the conversation using this app? If so, would you mind posting some settings so that we can have an idea of what works and what does not. I have tried to use it over wi-fi and its always pretty poor quality. The echo number I have tried also gives me static instead of my voice so I am pretty sure I am not using the optimum settings.

If you're having trouble over wifi the first thing to try would be the Keep Screen Alive checkbox. Many devices put the wifi into a power saving mode when the screen turns off. Also, task killer or battery manager apps like juice defender or advanced task killer can also interfere by killing GrooVe IPs background service.

For echo, 1.2.0 has echo cancellation as an option. The new synchronized voice option under troubleshooting can also improve call quality.

 

[pcp135]

If you're having trouble over wifi the first thing to try would be the Keep Screen Alive checkbox. Many devices put the wifi into a power saving mode when the screen turns off. Also, task killer or battery manager apps like juice defender or advanced task killer can also interfere by killing GrooVe IPs background service.

For echo, 1.2.0 has echo cancellation as an option. The new synchronized voice option under troubleshooting can also improve call quality.

I am using 1.2.0 with echo cancellation enabled. I have also tried a couple of 'echo tail' settings and nothing has worked so far. All of this is done over strong wifi connection.

The reason I asked people to post some settings tweak they have success with is that nothing I try does any good. My wifi is set to always be on so I am not dropping from that. I have no trouble staying logged in to google voice, it's getting the sound to work to a point where a reasonable person might want to have a conversation is the problem.

Edit: Do you guys (the devs) actually use this app? I doubt it b/c when I am using it, half the words in a conversation turn into static. If you were having this problem after an hour of tinkering, you'd probably throw your phone against the wall or something.

 

[snrb_labs]

I am using 1.2.0 with echo cancellation enabled. I have also tried a couple of 'echo tail' settings and nothing has worked so far. All of this is done over strong wifi connection.

The reason I asked people to post some settings tweak they have success with is that nothing I try does any good. My wifi is set to always be on so I am not dropping from that. I have no trouble staying logged in to google voice, it's getting the sound to work to a point where a reasonable person might want to have a conversation is the problem.

Edit: Do you guys (the devs) actually use this app? I doubt it b/c when I am using it, half the words in a conversation turn into static. If you were having this problem after an hour of tinkering, you'd probably throw your phone against the wall or something.

We use the app constantly...on multiple different devices, over wifi and 3G. No other way we can test the app without using it.

- Are you running a stock rom?

- Humor me and try the Keep Screen Alive checkbox

- Any task killers or battery manager apps like juice defender or advanced task killer? They can interfere with the app

- I assumed you had an Optimus V, but just to confirm that is the device you are using right?

- What options in what combination have you tried?

For right now turn off echo cancellation, once we can get voice in both directions we can worry about echo.

 

[pcp135]

We use the app constantly...on multiple different devices, over wifi and 3G. No other way we can test the app without using it.

- Are you running a stock rom?

- Humor me and try the Keep Screen Alive checkbox

- Any task killers or battery manager apps like juice defender or advanced task killer? They can interfere with the app

- I assumed you had an Optimus V, but just to confirm that is the device you are using right?

- What options in what combination have you tried?

For right now turn off echo cancellation, once we can get voice in both directions we can worry about echo.

I am running AOSP CM7, 05/23/2011 build.
No task killers or battery managers.
I am using Optimus V.
These are my settings:
Echo cancellation: On; Post processing: On; Echo Tail: 100-300ms
Speaker volume: 3; Microphone gain: -8;
Keep screen on: Off; Audio processing: On; Synchronize voice: On; Mic buffer: Medium; High perf wifi lock: On

I will try checking the 'Keep screen on' option and see how it works.
I have tried various echo tail, speaker volume and microphone gain settings, too many to list. The one above work the best.
Thanks.

 

[radiobufff]

I am running this app on three O'V's and my new DELL Steak 7 and it works great on all of them.

 

[JerryScript]

It appears all Gingerbread based ROMs on the Optimus V have the same issues. Attempting to place a call works until the call connects, once the mic is accessed, it crashes. The logcat also shows some thread issues.

Edit: I was able to get a sinlge word through using the following settings:

Troubleshooting
--Audio Processing (checked)
--Synchronize Voice (checked)
--Audio Routing (checked)
--Mic Buffer (Large)

This allows the call to be placed, and I hear a single word come back on the echo number, then you can hear some type of background sound when you say another single word, kinda like the difference between an open/closed mic, but that's it. I posted a new logcat to pastebin, hope it helps track down the issue.

http://pastebin.com/61B7awnc

 

[GeekOutDog]

Does anyone get a good voice quality from both side of the conversation using this app? If so, would you mind posting some settings so that we can have an idea of what works and what does not. I have tried to use it over wi-fi and its always pretty poor quality. The echo number I have tried also gives me static instead of my voice so I am pretty sure I am not using the optimum settings.

I only use this app when I am on vacation with no cell service. As such I haven't used 1.20 yet.
With the previous version, I had perfectly acceptable performance. I won't say flawless, but I was able to call multiple people and reliably communicate with them as needed over WiFi using this app.

 

[thekraven]

Did the last version work fine with cm7? I think 1.1.8? Is there an option to know when the call ends or drops? Like a beep.

 

[ejlmd]

It appears all Gingerbread based ROMs on the Optimus V have the same issues. Attempting to place a call works until the call connects, once the mic is accessed, it crashes. The logcat also shows some thread issues.

Edit: I was able to get a sinlge word through using the following settings:

Troubleshooting
--Audio Processing (checked)
--Synchronize Voice (checked)
--Audio Routing (checked)
--Mic Buffer (Large)

This allows the call to be placed, and I hear a single word come back on the echo number, then you can hear some type of background sound when you say another single word, kinda like the difference between an open/closed mic, but that's it. I posted a new logcat to pastebin, hope it helps track down the issue.

GrooveIP progress on IHO - Pastebin.com

I've been GrooveIP since the beginning and also just realized outgoing voice drops completely after one or two words, confirmed on the echo test number. This is with latest version 1.20 on 2 Gingerbread ROMS (AOSP 6/1 build and JerryScript's IHO build 7/30).

I just tried Sipdroid, CSipsimple and the native VOIP capability, all of which seem to have the same issue!

 

[metalman#AC]

It appears all Gingerbread based ROMs on the Optimus V have the same issues. Attempting to place a call works until the call connects, once the mic is accessed, it crashes. The logcat also shows some thread issues.

Edit: I was able to get a sinlge word through using the following settings:

Troubleshooting
--Audio Processing (checked)
--Synchronize Voice (checked)
--Audio Routing (checked)
--Mic Buffer (Large)

This allows the call to be placed, and I hear a single word come back on the echo number, then you can hear some type of background sound when you say another single word, kinda like the difference between an open/closed mic, but that's it. I posted a new logcat to pastebin, hope it helps track down the issue.

GrooveIP progress on IHO - Pastebin.com

I use ROM-ish Gingerbread on my OV and have no problems with Grooveip. All my Grooveip settings are default with the exception of the microphone gain which I bumped up a bit.

 

[ejlmd]

I've been using GrooveIP since the beginning and also just realized outgoing voice drops completely after one or two words, confirmed on the echo test number. This is with latest version 1.20 on 2 Gingerbread ROMS (AOSP 6/1 build and JerryScript's IHO build 7/30).

I just tried Sipdroid, CSipsimple and the native VOIP capability, all of which seem to have the same issue!

My problem with VOIP on the Optimus V is even more pervasive than I thought. I also have the same outgoing voice failures with GrooveIP on the latest Bumblebee (Froyo) ROM.

Also, even if I uninstall GrooveIP and then make an outgoing call with the actual Google Voice app enabled, same problem with outgoing voice. But outgoing voice is fine using the stock dialer or Skype.

 

[GeekOutDog]

I used the last version of GrooVe IP on my V running AOSP for conversations lasting over 20 minutes without dropping out. I'll have to test the latest version of it soon...

 

[snrb_labs]

Wanted to warn you guys. In case you haven't already purchased the app, tomorrow we plan on increasing the price. If you've been planning to purchase the app, may want to do it tonight.

 

[GeekOutDog]

It appears all Gingerbread based ROMs on the Optimus V have the same issues. Attempting to place a call works until the call connects, once the mic is accessed, it crashes. The logcat also shows some thread issues.

Edit: I was able to get a sinlge word through using the following settings:

Troubleshooting
--Audio Processing (checked)
--Synchronize Voice (checked)
--Audio Routing (checked)
--Mic Buffer (Large)

This allows the call to be placed, and I hear a single word come back on the echo number, then you can hear some type of background sound when you say another single word, kinda like the difference between an open/closed mic, but that's it. I posted a new logcat to pastebin, hope it helps track down the issue.

GrooveIP progress on IHO - Pastebin.com

I am on AOSP 6/1 build without the camera fix. Now using GrooVe IP 1.20

I made a call over 3G to my home phone and left a message on my answering machine. I spoke for 20 seconds and the entire monologue was transmitted successfully.


Nothing checked under Troubleshooting. Mic Buffer is medium.

Echo cancellation is on, with post processing on. Echo tail 200-400

Speaker Volume 0
Mic Gain -6

 

[snrb_labs]

It appears all Gingerbread based ROMs on the Optimus V have the same issues. Attempting to place a call works until the call connects, once the mic is accessed, it crashes. The logcat also shows some thread issues.

Edit: I was able to get a sinlge word through using the following settings:

Troubleshooting
--Audio Processing (checked)
--Synchronize Voice (checked)
--Audio Routing (checked)
--Mic Buffer (Large)

This allows the call to be placed, and I hear a single word come back on the echo number, then you can hear some type of background sound when you say another single word, kinda like the difference between an open/closed mic, but that's it. I posted a new logcat to pastebin, hope it helps track down the issue.

GrooveIP progress on IHO - Pastebin.com

Took a look at the new logcat. Don't see a crash anymore. But don't see any obvious errors either. Nothing that indicates why it only worked for a short while. Does increasing the mic buffer to x-large change anything?

Also don't do both Audio Routing and Audio Processing. Should be only one or the other.