KG1019

Hi,

So this is what I did:

1. I uninstalled my old groove ip application and restarted my phone.

2. Signed into the Android market with a new Gmail address (GmailID2) and bought the Groove IP app again ( The 1st app I bought was through Amazon app store using GmailID1and they dont have the updated version yet. Android wouldnt let me buy the app from their store using this GmailID1)

3. This time, with the new installation, I was able to make and receive calls in a fine manner.

4. Soon after, I again had to use the bluetooth connection on my phone to transfer some data.

5. Today, I am back to square one. I am again not able to make or receive calls using Groove IP.

Basically, I cannot use Bluetooth on my phone if I want Groove IP to function properly. Once I use the bluetooth it corrupts the exisiting GrooveIP app on my phone in some way.

I have already spent $10 in trying to use this app. Please offer a reasonable solution to this. Thank you!

jango123

I just started trying to use tasker today to make my groove ip setup more integrated but some of this stuff I would prefer was in groove ip itself. Locale Google Voice Set Plug allows you to change on the fly what google voice forwards to on conditions. Better Locale Airplane mode lets you turn of radios on conditions, not just all of them but like say just the cell radio while on wifi. Last Idea I had was if you had some sort of 3-way calling trick built into it so that you could say click move to cellular and it would call your cell number answer it and hang up google voice so you could leave your wifi network and still have your call up. Maybe have like a little noise when your wifi signal is getting too weak and maybe emphasis the move to cellular when your wifi signal was weak while not harassing you with it. I don't want to come off too needy but i thought these would be some pretty cool features if possible.

snrb

I'm not sure what to suggest. It seems like the bluetooth is hijacking the audio feeds. If you restart your phone does that fix the issue? You can also try disabling bluetooth from the GrooVe IP miscellaneous settings to see if that helps.

mcsheltie

Hi, I have been trying to verify my cell phone w/GV for days now. The auto system can't seem to hear when I put in the verification code. I have tried everything I can think of. I tried a tone generator, I tried from a different location, I forwarded the call to another cell phone that has been verified on GV and several other things... I give up (unless someone has something else to suggest) I have a GV phone number and my work cell is verified on GV. It is my personal cell that I can't verify.

Can I use GrooVe IP to integrate my cell w/my GV account, even tho the phone isn't verified? I don't want to try it and find out the hard way that something screwed up! I have an Atrix 4G on ATT.

Thanks!

snrb

Hi, you don't need the phone to be verified to use GrooVe IP. If you already have a Google Voice phone number that's all you need to make and receive calls. The app works through the same interface as gmail calling, so if you can use that on a PC you can use GrooVe IP on the phone. We have a user guide with more info available here http://snrblabs.com/snrb/Apps/GrooveIP/UserGuide.aspx

mcsheltie

It works! Great app!

irunfar

I have run in to a couple of issues after upgrading to the latest version from the Android Market. I am using a Samsung Galaxy Nexus with the stock ICS 4.0.2.

1) GrooveIP crashes when I dial a conference call number and try to enter the conference code. As I enter the conference code it crashes consistently after entering the first number in the code. This happens on both WiFi and 3G/4G connectivity.

2) When I leave a WiFi connection and pick up the cell phone providers' data connection, GrooveIP gets disconnected during the transition and does not connect back automatically when the screen is not active. I have to connect back manually by opening GrooveIP.

In the meantime I have been using Talkatone and it seems to work fine.

Thanks for any help.

snrb

You may want to try a clean install of the app. It could be something was messed up on download/install. Uninstall the app, restart the device then install the app again. I've been trying to reproduce the issue on our Galaxy Nexus but haven't been able to yet.

irunfar

Just tried that and have the same issue of GrooveIP crashing. I'd be happy to send the number to call in a private message if it would help debug the problem. Thanks.

snrb

If you can send me a logcat capture via email that would be the most helpful. Easiest way would be with the free catlog app. It will let you start/stop recording the logcat and then you can email me the resulting file. snrb.labs@gmail.com

thebobp

This app is great; however, it doesn't seem to play well with my Motorola HX550 bluetooth headset (I'm on a galaxy nexus, if it helps). I can't just press on the headset to answer a call; it just brings up a voice dialog when I do so.

If possible, headset answering would definitely be a feature request from me, along with the option to autolock the phone when a call is answered via a headset. (Sometimes you want to just answer with the headset and leave the phone in your pocket while walking, but I've found there's a huge risk of accidentally triggering the hang up button! An option for a more complicated hangup procedure would work here too.)

(Indeed, I have another app for autolocking, but it only works with the default phone program. So I guess if you could have an option to redirect incoming calls to the default phone, that would make me happy as well! Although I suppose the above features would make more users happy in general ; )

Thanks for the great app!


(Edit: description mistakes.)

Last edited by thebobp; February 4th, 2012 at 02:08 PM.

snrb

Have been looking into supporting physical bluetooth buttons. If there's an api it doesn't seem to be very well documented. But others have reported being able to access them so we have a few leads to try.

tcat007

This is the 4th time I have lost incoming voice on a connected call (in 2 months). Normally the app works well on my Galaxy Player 5.0. To get the calls to work again, I need to check the "wifi tablet" box. With this checked, the call connects and I hear the incoming voice (but it's through the speaker, and speakerphone does nothing). If I reboot with the wifi tablet box not checked (best call quality, and speakerphone button works), I still don't get incoming voice. But if I reboot with wifi tablet box checked, then uncheck the box after the boot, all will start work normally... for about a week. Then I loose incoming voice again and need to go through the "custom" reboot sequence.

I could leave it on "wifi tablet" mode, but I don't like the sound through the speakers... any ideas?

snrb

Not really sure what to suggest. It sounds like the audio driver or voice stream is getting into a bad state. Not really sure what could cause that to happen. Have you tried Synchronize Voice or a different Mic Source or Mic Buffer setting in troubleshooting?

tcat007

Haven't tried those (since it works fine with none of that 80% of the time). Next time I lose incoming, I'll try those to see if it comes back without rebooting. "Audio" related things on my device:
1. Cubed Player
2. DSP Manager
3. Ivona Voice
4. Navfree
5. Speaktoit (uses it's own voices)
....and any system things (GV, Player, Voice Search)

#5 has the best odds of being the problem, but could also be DSP Manger, since it sets equalizer to speakers.

snrb

Haven't tried those apps. But something like DSP Manager could cause the issue since it changes settings on the audio streams.

Automate

Using a Vizio Tablet VTAB1008 without Bluetooth (Andriod 2.3) The non-VOIP caller is hearing a lot of their own echo since the tablet mic is next to the tablet speaker. What is the best way to eliminate this?

Last edited by Automate; February 7th, 2012 at 07:47 AM.

snrb

First thing to try would just be the echo canceler in the audio/echo settings. Can also try changing the mic source to VoIP from the troubleshooting settings.

Habbit

Hi snrb,

Your response to this inquiry was,

I was wondering if in newer versions you were able to fix this problem, or if getting a custom version from you was still the only way to go about solving this problem? I'm moving to Japan in May and I am most likely going to encounter the same issue as techninja2.

Thanks!

Automate

I had already turned on the echo canceler. Setting the mic source to VOIP seemed to help but there is still a little echo.

dggopal

I have a non rooted N1 with no prior wifi connection problems and i tested the phone wifi with other apps and it is remaining stable. But for some reason groove ip is causing the phone to loose the wifi connection momentarily and thus sign out. I see the wifi go out on the phone and after a second it comes back and groove ip starts signing in again. have tried checking the keep screen on, sync voice, partial wake lock, high perf wifi lock but still happens. cant hold on to calls for longer than a few mins at a time... in stand by it does it much less but during calls it does it consistently since I got the app a few days ago. without the app running I am able to maintain the wifi without a problem... but with groove ip something is causing the wifi on the phone to dc and then reconnect right away. Any work around or fix?

ps: other devices are maintaining connection to wifi, router is brand new belkin, router is in same room as cell when testing and usually when calling, tried changing channels on router, there is a cordless phone in near proximity to the router but other devices are having no prob maintaining connection including the phone as long as groove ip is not actively on.....

tcat007

Do you see any issues with the new Google Voice update? I made a call directly with GV only and was fine, but force closed once I hung up. Then I went to make the same call with Groove and it also force closed when I hung up. Since both are obviously using Google Chat, there must be a conflict of some sort.

snrb

No, the update is only to their android app. GrooVe IP doesn't use the Google Voice android app at all. Google Voice android app doesn't use Google Chat. They should be completely unrelated. The only thing that the Google Voice android app sometimes does is change your forwarding settings. If you want grab a logcat capture and I'll see why GrooVe IP crashed. Easiest way is with the free catlog app (lets you start/stop recording logcat to a file)

EwanG

Looking for recommendations for a Dell Streak 7 4G. I uninstalled and then reinstalled the latest version. It seems to work ok, but I am told there is an echo at the other end even though I have set the mic down to -9. I was thinking of getting a Bluetooth headset, but would that fix this problem, or just introduce issues with the Bluetooth.

The streak is running Honeycomb 3.2 to the extent that might affect your recommendation.

Thanks!

snrb

Did you try the echo canceler setting? Also may want to try changing the mic source (under troubleshooting). Try VoIP and Android Default

aston4

I've been trying to figure this out, read through this thread and didn't see an answer.

I have GrooveIP installed on two phones, a Motorola Defy running Stock ROM 2.2.2, and a Motorola RAZR (GSM stock ROM) running 2.3.5.

On the RAZR it runs PERFECTLY!!! Amazing app.

On the Defy, it makes a call OK, but after 2-3 minutes the call is cut off.

Then, under the "Recent" tab, it shows the call duration from anywhere from 0-4 seconds, even though I am sure the call lasted at least 2 minutes.

It *always* cuts off, it never goes more than about 3 minutes. Any ideas besides flashing a new ROM on the phone? I really don't feel like flashing a new ROM, the Defy is just fine for my purposes otherwise.

aston4

I overlooked this last time I read the thread. I'm going to try these settings for my Defy & see if it solves the disconnect issue I'm having.

aston4

...didn't work, still disconnects after 1-2 minutes.

jjmai

Failed to sign in over 3G on my HD2 running NDT MIUI ROM.
Logged in ok via wifi, but force close when making call, even messed up my standard phone software, had to reboot to get my phone working.
Is this a known incompatibility with HD2?
It works fine on my HTC G2 though...

Last edited by jjmai; February 10th, 2012 at 07:15 PM.

kingnut

Gonna try this week.

Last edited by kingnut; February 11th, 2012 at 10:02 AM.

snrb

Would try the Keep Screen Alive. Could be something on the device going into a power saving state.

aston4

I tried that previously. Same deal. It's weird. I also suspect something the phone is doing, like maybe disconnecting wifi occasionally for power saving. I'm hoping that an official Motorola Defy update to 2.3 happens someday, it would probably solve the problem. I've also done a lot of experimentation comparing the two phones on outgoing by recording myself on voicemail & then listening with a landline phone & the RAZR is far less choppy for outgoing voice regardless of all the settings I try on the Defy. Actually the RAZR has no choppiness/clippiness at all. I think mostly because the dual core processor just kicks butt.

I wish the RAZR was a cute & waterproof as the Defy though -- it is a HUGE phone. I suspect in 2 or so years there will be a RAZR that is only as tall & wide as the defy, but super thin. I'm drooling just thinking about it.

BTW, the reason I have both of these phones is because of their exceptional microphones. They put all other phone microphones on the market to shame, especially Samsung, who has NEVER made a phone with anything other than atrocious outgoing voice quality. I've been suckered by Samsung "features" three times now, NEVER AGAIN!

thebobp

Edit: This sort of hit me in the head while I was writing this post: you should be able to bypass the API, at least until it's better understood, with an auto-answering mode. Not only is it a useful/popular feature in general, but in this specific case, people who want to exclusively use headsets wouldn't lose a lot from being unable to decide about the answer button: might as well just answer it for them! You could even have a "bluetooth mode" that only auto answers when a headset is connected. Add in an option, within bluetooth mode, to make the hangup procedure more complicated (i.e. less prone to accident), and you'd have a bona fide capacity for answering calls with the phone still in one's pocket



My original post no longer seems nearly as interesting (having an auto answer mode that works before the main phone is triggered would definitely solve the problem), but I'm leaving it below in case you find the case relevant.

-----
-----


Hi, I have another usage observation (I'm not sure if it's a bug or not) which leads to a feature request for ignoring the first x seconds of ringing.

I set my google voice to forward not only to groove ip, but also to the ordinary phone number in case I don't have access to data. That way, I can choose which one to pick up.

When both are available, though, what happens is that groove ip starts ringing first, followed quickly by the ordinary phone ringer, and then after a second or so groove ip pops back up on top of it again.

Bluetooth headset: if I pick up during groove's first ringing, it works fine. However, if I pick up during the phone ringing or groove's second ringing, the sound inexplicably switches over to speakerphone (despite "bluetooth" still being enabled for both). I have to turn the bluetooth option off and back on in order to get the sound back into the bluetooth headset. (I have already tried all the suggested troubleshoots for speakerphone-rerouting, but none of them seem to solve this particular issue.)


I think the problem here is that either program, when faced with a hangup, causes sound to revert to speakerphone. Because google voice immediately terminates the other connection when you pick one up, the other app would then trigger speakerphone (unless you picked up in the very first stage where only one app was active).

So my feature request: an option for groove to ignore the first x seconds of ringing (only starting the call screen if they're still on after x seconds). That way, I am able to answer early via bluetooth without disruption from a hangup. (It would also be nice to have a minor sound notification that a call is incoming but being delayed; that way we could know that the data service is indeed active!) Since, currently, picking up a groove call via bluetooth is not possible, the opposite issue would not occur.

The feature could also be used for other things, say, to weed out unimportant calls when on vacation. (Though I admit it'd probably be more of a "troubleshooting" feature.)

Thanks for reading my very long expose! I wish google would set it up so that delayed forwarding was easier, but it's probably not to be!

Last edited by thebobp; February 14th, 2012 at 06:30 AM.

duhorg

Hi snrb!

I have access to two Intercepts, relatively recent, from Virgin Mobile USA. One has been rooted and loaded with CrappyKernel 1.5, and the other is stock. Both seem to work with audio in/out on the earpiece via this workaround, which might be something that can be put into a hack setting:

1. Dial or answer.

2. Turn on speakerphone explicitly. (It's "on" already by virtue of default audio routing, but the speaker indicator in GrooVe IP is not on. This turns the indicator green, and switches to the app's speakerphone volume setting.)

3. Turn off speakerphone explicitly.

The audio is now on the internal earpiece, and the mic does work. I suppose that it's the cycling of default audio routing -> speaker on -> speaker off that does the trick. Ugly, but it appears to work, and I'm available to test a hack setting for this if needed.

(Oh, and none of the existing troubleshooting settings are enabled.)

[edit: I do use a separate app to keep wifi alive, but Keep Screen On would probably work too. Obviously, I don't think this is related to audio routing, but figured I'd mention it for completeness.]

Last edited by duhorg; February 14th, 2012 at 03:32 PM.

snrb

I love the idea of an auto answer mode. I'm going to add that to the feature list, don't think it should be too difficult either to implement.

snrb

Just so I understand. You toggle speaker phone on then off again manually and that fixes the audio routing even on the stock intercept? I can check for the device type in the code and just do that automatically. Please shoot me an email, think it will be easier to work this through and give you a beta over email. snrb.labs@gmail.com

duhorg

Gah! No, it doesn't work on stock after all. (I personally use an Intercept with CrappyKernel, part of the xda-dev "Almost Stock ROM" package; my friend has stock, and misreported results to me.)

E-mailing with more detail, though, because it's still worth adding for those willing to swap out the kernel.

snrb

Got your email, thanks.

donbr56

Any chance we could get a list of bluetooth headsets that have been confirmed as working?
Also, the ability to answer calls using the button on the BT device... is that device-dependent or not possible at all right now?

snrb

I don't really have a list of headsets. That will depend on the phone/tablet and what kind of support the manufacturer has implemented for apps (bluetooth support for apps is different than what the native dialer supports). Some manufacturers only support bluetooth for music apps.

donbr56

The BT I use is motorola H17 with a galaxy tab 10.1
Just downloaded the app and it seems to be working fine.
The only downside is the button on the bluetooth headset to answer the call doesn't answer the call. Major inconvenience to have to pull out the tablet and hit answer in order to start talking.
Is that a limitation in the app itself or something to do with the bluetooth headset? or were you already answering that in your previous response?
If it is app-related, is it possible to make that work in the future?

thanks a bunch

aston4

Just as a followup, I don't know what the heck you did with that last update, but the problem is now fixed without my having changed anything else on the Defy except installing your latest version. AMAZING!!!!!!

snrb

Glad it's working better for you.

msneon1980

I have a Tmo Samsung Galaxy S (1st Gen) that I put Groove IP on yesterday. There is not data service on this phone, it's factory (no rooting) but I did not do a reset on it. It was my old phone I gave to my daughter. It seemed to work fine, would take incoming calls, but now today it's only doing outgoing, and the calls are fuzzy. If you call it from another number it rings, but nothing happens on the actual phone, it doesn't ring. What could I do to fix this? Any suggestions? Thanks in advance.


Also I noticed last night that Groove Ip will log itself out and have trouble logging back on, even though I have the WIFI set to stay on.

snrb

For the incoming call issue I'd suggest double checking your Google Voice account to ensure calls are still being forwarded to Google Chat. You may also want to try enabling one or both of the lock settings in GrooVe IP troubleshooting. Some devices, mostly HTC devices, still put the wifi into a power saving state even if you have it set to stay on. Also if you have any task killer or battery manager apps they could be interfering.

BeratE

I have been using GrooveIP for a bit now and really enjoy it, thanks! I have a request though. I have a personal GV number and a business GV number and would like to be able to be logged in through GrooveIP to both at the same time. Extra points would be given for a hold function between the two if a call come in one while I am on the other.

Thanks

snrb

Both are features we're actively working on. Hold will most likely be in the next update. If not that then for sure in the update after that. Supporting multiple sign ins may take a bit longer.

BeratE

Great to hear! Keep up the good work. Are we talking weeks or months do you think on the multiple sign-ins?

donbr56

I remember reading about an auto-answer feature request earlier, is that something which is in development?
It would be a way around the bluetooth answer buttons not working on tablets.

snrb

Yup, in development. Close to complete.