11-16-2015 12:23 PM
692 ... 1718192021 ...
tools
  1. xur17's Avatar
    Thanks for the info. We plan on buying a Galaxy Nexus as soon as it comes out. From the SDK it doesn't look like anything should have to change in the app, but we'll try it as soon as things are officially released.
    I am really hoping ICS lets you use the built in echo canceller.
    10-27-2011 05:59 PM
  2. snrb_labs's Avatar
    I am really hoping ICS lets you use the built in echo canceller.
    It's not really something tied to the OS. It mostly depends on how the manufacturer implements the audio driver.
    10-27-2011 07:19 PM
  3. xur17's Avatar
    It's not really something tied to the OS. It mostly depends on how the manufacturer implements the audio driver.


    So using a different rom could potentially fix this for me?
    10-28-2011 09:32 AM
  4. snrb_labs's Avatar
    So using a different rom could potentially fix this for me?
    It could. We're also going to expose a new setting to select the mic source. In Honeycomb the SDK added a voice communication mic source for VoIP that is supposed to do echo cancellation and auto gain control. If the rom implements that api it should use the hardware echo canceler.
    10-28-2011 09:41 AM
  5. xur17's Avatar
    Is there any way you can make an optional setting to set "MODE_IN_COMMUNICATION"? I ran a logcat on csipsimple, and based on that and several comments such as this, I think this will fix the echo issue for Nexus S devices.

    Eg: It shows up as the following in logcat:
    D/AudioHardwareInterface( 144): setMode(IN_COMMUNICATION)

    I would really appreciate it!
    11-02-2011 11:58 PM
  6. snrb_labs's Avatar
    Is there any way you can make an optional setting to set "MODE_IN_COMMUNICATION"? I ran a logcat on csipsimple, and based on that and several comments such as this, I think this will fix the echo issue for Nexus S devices.

    Eg: It shows up as the following in logcat:
    D/AudioHardwareInterface( 144): setMode(IN_COMMUNICATION)

    I would really appreciate it!
    Ya we started that last week. About half way through the change that would make the mic source configurable. Will likely have a new beta up with the change this weekend.
    11-03-2011 09:00 AM
  7. xur17's Avatar
    Ya we started that last week. About half way through the change that would make the mic source configurable. Will likely have a new beta up with the change this weekend.
    Sounds awesome! I'll be watching for it.
    11-03-2011 01:02 PM
  8. db306#AC's Avatar
    Has anyone had any luck using Groove from a cruise ship using the boats wifi to call back to the U.S? Thanks
    11-06-2011 09:53 PM
  9. mi7chy's Avatar
    Verizon HTC Thunderbolt running official Gingerbread 2.3.4 v2.11.605.5 ROM.
    Blueant S4 bluetooth speakerphone v1.6
    Groove IP v1.2.9.

    Native dialer works fine with bluetooth. However, with Groove IP configured as the dialer I can initiate a successful bluetooth call but once the call is ended any subsequent bluetooth calls will no longer have audio even though the device is showing paired/connected and bluetooth via Groove IP dialer is toggled. The only way to restore bluetooth audio is to unpair/repair.

    Any suggestions or possible software fix to Groove IP?
    11-07-2011 01:07 AM
  10. snrb_labs's Avatar
    Verizon HTC Thunderbolt running official Gingerbread 2.3.4 v2.11.605.5 ROM.
    Blueant S4 bluetooth speakerphone v1.6
    Groove IP v1.2.9.

    Native dialer works fine with bluetooth. However, with Groove IP configured as the dialer I can initiate a successful bluetooth call but once the call is ended any subsequent bluetooth calls will no longer have audio even though the device is showing paired/connected and bluetooth via Groove IP dialer is toggled. The only way to restore bluetooth audio is to unpair/repair.

    Any suggestions or possible software fix to Groove IP?
    Some devices seem to have this issue Issue 15092 - android - AudioManager.stopBluetoothSco() not working - Android - An Open Handset Alliance Project - Google Project Hosting where the api to close the bluetooth connection isn't working. Don't know of any solution to that since that's the only api to disconnect the bluetooth. Still looking into it.
    11-07-2011 07:35 AM
  11. rubydreamer's Avatar
    Ok, slight issue that's semi recent.

    I'm using a Galaxy Tab (7, using verizon) and 1.2.9 and it works well enough, except that it ramps the CPU to full, freezes the screen, and pretty much just stops responding. Sometimes the call even just cuts out. Ive actually had to do a hard reset several times to get out of a call (or an occasional call that cuts out and doesn't seem to drop the connection, causing a terminal freeze).

    Any idea how to get around this?

    Note: Just got a 2.3.5 OS update, but its still the same problems... Both 2.2 and 2.3.5 seem to have the problem.
    11-07-2011 11:25 PM
  12. snrb_labs's Avatar
    Ok, slight issue that's semi recent.

    I'm using a Galaxy Tab (7, using verizon) and 1.2.9 and it works well enough, except that it ramps the CPU to full, freezes the screen, and pretty much just stops responding. Sometimes the call even just cuts out. Ive actually had to do a hard reset several times to get out of a call (or an occasional call that cuts out and doesn't seem to drop the connection, causing a terminal freeze).

    Any idea how to get around this?

    Note: Just got a 2.3.5 OS update, but its still the same problems... Both 2.2 and 2.3.5 seem to have the problem.
    Do you have Synchronize Voice checked? What other options under troubleshooting do you have enabled? Is the echo canceler enabled?

    Can try increasing the mic buffer to x-large.
    11-08-2011 07:19 AM
  13. rubydreamer's Avatar
    Synchronize Voice is checked, as well as echo cancellation (which did seem to help a bit)
    11-08-2011 12:13 PM
  14. snrb_labs's Avatar
    Synchronize Voice is checked, as well as echo cancellation (which did seem to help a bit)
    Were calls not working before you enabled Synchronize Voice? On some devices that setting can cause problems. It basically depends on how your manufacturer implement the audio recording api's. I'd suggest disabling Synchronize Voice and seeing if that fixes the issue.
    11-08-2011 06:13 PM
  15. arcticathlon's Avatar
    I just purchased the app GrooVe IP and it keeps rebooting my T-Mobile Samsung Galaxy S 2 every 30 mins. what setting changes does anyone suggest i do to fix this?

    cheers
    11-08-2011 06:33 PM
  16. snrb_labs's Avatar
    I just purchased the app GrooVe IP and it keeps rebooting my T-Mobile Samsung Galaxy S 2 every 30 mins. what setting changes does anyone suggest i do to fix this?

    cheers
    Is your device stock? We test with the Galaxy S2 haven't noticed any issues with it. It could be the app install was corrupted. You can try uninstalling the app, restarting the device, then installing the app.
    11-08-2011 09:04 PM
  17. xur17's Avatar
    Ya we started that last week. About half way through the change that would make the mic source configurable. Will likely have a new beta up with the change this weekend.
    I tried the new beta version on my stock nexus s, and MODE_IN_COMMUNICATION is still not being set. I tried a few different microphones (including the VOIP one), and I still had echo issues.

    PLEASE consider adding MODE_IN_COMMUNICATION, as it seems to have fixed voip problems for other users on Nexus S device.

    Thanks!!
    11-10-2011 02:45 PM
  18. snrb_labs's Avatar
    I tried the new beta version on my stock nexus s, and MODE_IN_COMMUNICATION is still not being set. I tried a few different microphones (including the VOIP one), and I still had echo issues.

    PLEASE consider adding MODE_IN_COMMUNICATION, as it seems to have fixed voip problems for other users on Nexus S device.

    Thanks!!
    The VoIP option sets MODE_IN_COMMUNICATION if it is implemented on the device. If using that throws a source not supported exception then the app defaults back to the default mic source.
    11-10-2011 03:47 PM
  19. xur17's Avatar
    The VoIP option sets MODE_IN_COMMUNICATION if it is implemented on the device. If using that throws a source not supported exception then the app defaults back to the default mic source.
    I stand corrected. MODE_IN_COMMUNICATION wasn't working in csipsimple either for my device. I had another setting set in csipsimple that was doing similar echo correction as groove ip is.

    Looks like I will just leave the echo canceller beep option on. My only issue is when the volume is low at the beginning of the call, and the beep that is emitted doesn't work (I am assuming this causes the microphone not to be able to hear it). My auto-detected echo tail varies too much for me to set a range, so that isn't an option.
    11-10-2011 07:01 PM
  20. snrb_labs's Avatar
    I stand corrected. MODE_IN_COMMUNICATION wasn't working in csipsimple either for my device. I had another setting set in csipsimple that was doing similar echo correction as groove ip is.

    Looks like I will just leave the echo canceller beep option on. My only issue is when the volume is low at the beginning of the call, and the beep that is emitted doesn't work (I am assuming this causes the microphone not to be able to hear it). My auto-detected echo tail varies too much for me to set a range, so that isn't an option.
    The beta has some improvements for that also. Should work better in low volume situations.
    11-10-2011 07:50 PM
  21. xur17's Avatar
    The beta has some improvements for that also. Should work better in low volume situations.
    I just installed the newest beta - It may be a little bit better, but I am still having issues with the echo detection not working if I left the volume lower from a previous call (which I do sometimes). Is there any way to make the beep at the beginning of the call just be emitted at a constant (loud) volume so it always works?
    11-13-2011 01:39 PM
  22. snrb_labs's Avatar
    Version 1.2.10

    - Fix Korean Galaxy S WiFi
    - Add inclusion and exclusion regex setting
    - Ensure correct layout is used for in-call screen
    - Support Gtalk invisibility
    - Allow mic source configuration to take advantage of VoIP mic in Honeycomb
    - Add option to ignore weekends in start/stop time setting
    - Improve voice cut-off on call connect
    - Bug fixes
    11-13-2011 08:21 PM
  23. xur17's Avatar
    I just installed the newest beta - It may be a little bit better, but I am still having issues with the echo detection not working if I left the volume lower from a previous call (which I do sometimes). Is there any way to make the beep at the beginning of the call just be emitted at a constant (loud) volume so it always works?
    And with the beta, I am having problems with invisible mode randomly re-enabling. I enabled it once to try it, and after I disabled it, it seems to be randomly re-enabling (and causing my other clients to switch to invisible mode).

    Edit: I installed the new version from the market, and invisible mode doesn't appear to be randomly toggling, but I didn't try toggling the invisible check box.

    Edit again: Groove IP still seems to be toggling all my clients to invisible randomly. I haven't touched the check box, and a few times yesterday, and this morning I noticed all of my clients were in invisible mode.
    11-13-2011 08:53 PM
  24. Godfather47's Avatar
    i can make calls with grooveip but no receive, when i call google number from home number i get voicemail saying i have no messages, when i go to phone settings of google voice, i see 'registered number' which is the number i put, and underneath is 'google chat', the problem is i don't see anything saying forward and there are no check boxes beside either !!
    11-19-2011 09:31 PM
  25. snrb_labs's Avatar
    i can make calls with grooveip but no receive, when i call google number from home number i get voicemail saying i have no messages, when i go to phone settings of google voice, i see 'registered number' which is the number i put, and underneath is 'google chat', the problem is i don't see anything saying forward and there are no check boxes beside either !!
    Hi,

    If you aren't seeing any checkboxes I'd recommend contacting the Google Voice support. There's likely something messed up with your account that they could fix. Or alternatively creating a new account should fix the issue. You can use this form to transfer your existing Google Voice number if you want to keep it. Google Voice Help
    11-20-2011 07:10 PM
692 ... 1718192021 ...

Tags for this Thread

LINK TO POST COPIED TO CLIPBOARD