Jump to content

Google Hangouts w/Voice (Was Google Voice)


COZisBack

Recommended Posts

Contrary to pocketables news of it getting yanked, I got the merge message on my hangouts, I hit enable, but can't really tell any difference as of yet, so who knows..

 

http://www.pocketables.com/2014/09/google-hangouts-wvoice-gets-yanked.html

Link to comment
Share on other sites

Since I've got a business account, I can't do GVI anymore. However I can do forward-on-no-answer to GVoice (which allows me to use GV/Hangouts voicemail...and keeps my phone ringing a little longer), so I'm doing that. End result is that my phone will ring two different ways when someone dials my cell #: once for the normal voice network, once for Hangouts VoIP (at which point my computer rings as well). If my phone is off, the call goes directly to GVoice. Works for me :)

  • Like 1
Link to comment
Share on other sites

Got the hangouts integration. I can get SMS over data now (with airplane mode on) but cannot respond, must be a bug, can anyone else send SMS over 100% data like the GV app yet?

 

I also get SMS on my hangouts app on desktop, and can respond, which is HUGE.

 

I'm fully integrated with Sprint.

Link to comment
Share on other sites

With the new update, can we uninstall the Google Voice app or is it still required?

 

You can uninstall it as long as (at least for me) you don't need to send SMS over 100% data, thats not working for me yet. Everything else is on par with or better than the GV app.

Link to comment
Share on other sites

You can uninstall it as long as (at least for me) you don't need to send SMS over 100% data, thats not working for me yet. Everything else is on par with or better than the GV app.

At the bottom of the thread, click on the sms toggle and change it to hangouts and then back to sms. At first it showed only from my Sprint number, but after toggling it shows from my Google Voice number and now works on only data (airplane mode with wifi on). I can't figure out how to change it back but everything seems to work including mms on my sprint phone. I still can't receive mms on other devices, but I can send via hangouts.

 

When I receive a call, the stock dialer on my sprint and verizon phone come up with no indication at all that it is a google voice call. When answering on my verizon phone, if I didnt know better I would assume they called my work number directly. My tablet does not receive a call notification to receive calls, but I can make them from the tablet and computer via hangouts. Voice quality seems pretty good, lower than HD calling on sprint but better than verizon and about on par with a non HD sprint call.

 

Edit: It seems if you haven't had a hangouts conversation with some one you can't get it to toggle to sending via Google Voice.

Link to comment
Share on other sites

Ok i was pretty confused with all these moving parts. I was scared but finally accepted the updates. Since I have full gvi I decided against the merge since I use hangouts as my default SMS app anyway. So if I got it right, now I can use voip but still get SMS and mms on hangouts since it's my default messaging app. Still get VM on gv app which I'm ok with. The only thing I wanted was voip and I got that with the new hangouts app.

 

What else am I missing besides checking voicemail on hangouts? Keeping it on Google voice is a small price to pay for keeping mms between carriers in tact.

  • Like 1
Link to comment
Share on other sites

Ok i was pretty confused with all these moving parts. I was scared but finally accepted the updates. Since I have full gvi I decided against the merge since I use hangouts as my default SMS app anyway. So if I got it right, now I can use voip but still get SMS and mms on hangouts since it's my default messaging app. Still get VM on gv app which I'm ok with. The only thing I wanted was voip and I got that with the new hangouts app.

 

What else am I missing besides checking voicemail on hangouts? Keeping it on Google voice is a small price to pay for keeping mms between carriers in tact.

 

I'm also a little confused. If you have full Sprint/GV integration and your SMSs are already going to Hangouts, what do you gain by merging?

 

If I understand correctly, if you merge you may have MMS issues. The only real change is you'd see VMs in Hangouts. Does VM in Hangouts show a transcription?

 

What am I missing? Do SMSs now go to Hangouts in Gmail on the web? Can you still send SMS over Wi-Fi if you merge? If you don't merge, you can chose between Wi-Fi (GV app) or cell (Hangouts), correct? And under what, if any, circumstances do calls come in over Wi-Fi?

 

I've got to say that for something as important as placing/receiving phone calls and texts, this was a terribly explained roll-out - particularly for Sprint customers.

Link to comment
Share on other sites

I have full integration with Sprint/Google Voice. So far I have been able to send and receive mms between Sprint and Verizon perfectly fine through the new hangouts app, I have not been able to test sending/receiving to ATT/TMO yet. Calls do not come in via WiFi, they go to the stock dialer via cellular network and incoming calls will be missed without cellular signal. Outgoing calls can be made over WiFi by dialing within Hangouts, any calls made by stock dialer seem to be cellular. SMS does go to any device that has Hangouts, phone/tablet/computer. MMS will only come to my Sprint phone, but I can send them via any device with Hangouts. Using the Hangouts add on in Chrome on my computer is very convenient. It's a lot more refined than trying to use the Google Voice website.

 

SMS over WiFi seems a little odd how it works right now. I've been texting my sister, and by toggling to hangouts chat and back to SMS it is now messaging her via Google Voice using only data and works on WiFi with airplane mode on. I have not found out how to change it back to SMS via cellular, nor have I found a way to send via Google Voice in Hangouts to anyone that I haven't previously done a hangout chat with.

 

Edit: There is a setting to ring hangouts for any calls made to google voice number, I haven't been able to test if it will work via WiFi only yet.

Link to comment
Share on other sites

 

 

I'm also a little confused. If you have full Sprint/GV integration and your SMSs are already going to Hangouts, what do you gain by merging?

 

If I understand correctly, if you merge you may have MMS issues. The only real change is you'd see VMs in Hangouts. Does VM in Hangouts show a transcription?

 

What am I missing? Do SMSs now go to Hangouts in Gmail on the web? Can you still send SMS over Wi-Fi if you merge? If you don't merge, you can chose between Wi-Fi (GV app) or cell (Hangouts), correct? And under what, if any, circumstances do calls come in over Wi-Fi?

 

I've got to say that for something as important as placing/receiving phone calls and texts, this was a terribly explained roll-out - particularly for Sprint customers.

I agree this is very poorly explained for sprint customers and integrated customers. I thought the merge was a necessary evil to use voip. Thankfully it is not. Now google voice functions the same. So I can still use SMS via data or cell via the gv app. But mms still routes through cell radio no matter what, to your default messaging app, which just happens to be hangouts for me.

 

Calls can be received through hangouts if you select a box in the settings of the app. That can be toggled on and off. So its perfect for what I need it for. I think.

Link to comment
Share on other sites

[See Edit Below]

 

So I just encountered a pretty huge bug which seems like it must be specific to those with Sprint integration.

Steps to reproduce:

In the Hangouts app turn on "ring hangouts for incoming calls made to your Google Voice number" but don't connect to Wi-Fi - stay on a data connection.

When receiving a call, your phone should begin to ring as usual. But a moment later your ringer will switch from the standard phone to the Hangouts ringer, allowing you to take the call over data. The problem is, since LTE cuts out when receiving a cell call, the LTE call fails upon being answered, and the normal cell call can't be answered.

I guess the solutions are to change your GV settings to never ring your cell phone (and only take calls over data), to make sure you're on Wi-Fi when you receive calls, or to turn off receiving calls via Hangouts.

But it's funny that the settings don't prohibit this from happening.

 

Edit: In subsequent tests, Hangouts rings first and then the real phone rings second, so the real phone call takes the place of the Hangouts call. If you want to talk the call over data, it seems you can reject the regular call, wait a few seconds for LTE to reconnect, then take the call over data. By the same token, if you want to outright reject a call, you first must reject the regular call, then reject the Hangouts call as well. Very strange.

Link to comment
Share on other sites

[See Edit Below]

 

So I just encountered a pretty huge bug which seems like it must be specific to those with Sprint integration.

 

Steps to reproduce:

 

In the Hangouts app turn on "ring hangouts for incoming calls made to your Google Voice number" but don't connect to Wi-Fi - stay on a data connection.

 

When receiving a call, your phone should begin to ring as usual. But a moment later your ringer will switch from the standard phone to the Hangouts ringer, allowing you to take the call over data. The problem is, since LTE cuts out when receiving a cell call, the LTE call fails upon being answered, and the normal cell call can't be answered.

 

I guess the solutions are to change your GV settings to never ring your cell phone (and only take calls over data), to make sure you're on Wi-Fi when you receive calls, or to turn off receiving calls via Hangouts.

 

But it's funny that the settings don't prohibit this from happening.

 

Edit: In subsequent tests, Hangouts rings first and then the real phone rings second, so the real phone call takes the place of the Hangouts call. If you want to talk the call over data, it seems you can reject the regular call, wait a few seconds for LTE to reconnect, then take the call over data. By the same token, if you want to outright reject a call, you first must reject the regular call, then reject the Hangouts call as well. Very strange.

I've had some similar issues with lte and incoming calls. While on lte some hangouts calls come before the standard call but some come after. Like waaaay after. Like the hangouts dialer will ring after I complete a call 5 minutes later. This has happened 3 times already. It's happened after I've answered a regular call or if I've missed a regular call. I've answered the hangouts dialer afterwards and of course it's just dead air. Still some bugs to work out but yeah there should be a way in the app to disable forwarding.
Link to comment
Share on other sites

Another issue related to the one I earlier mentioned: if you have Hangouts set to ring when you receive a call, when both the cell call and the Hangouts call start ringing, once you answer the cell call, the Hangouts call will keep ringing even as you speak. It's pretty terrible.

Link to comment
Share on other sites

I'm also a little confused. If you have full Sprint/GV integration and your SMSs are already going to Hangouts, what do you gain by merging?

 

...

 

What am I missing? Do SMSs now go to Hangouts in Gmail on the web? Can you still send SMS over Wi-Fi if you merge? If you don't merge, you can chose between Wi-Fi (GV app) or cell (Hangouts), correct? And under what, if any, circumstances do calls come in over Wi-Fi?

....

Say I have an old nexus s lying around, not activated on a Sprint line. If I have Google voice integrated through Sprint, in theory I should be able to text from it and call on it through hangouts, and it should appear as my regular Sprint number. I think? Edited by djw39
Link to comment
Share on other sites

Say I have an old nexus s lying around, not activated on a Sprint line. If I have Google voice integrated through Sprint, in theory I should be able to text from it and call on it through hangouts, and it should appear as my regular Sprint number. I think?

 

Yup - I've been doing exactly that. So long as you're on Wi-Fi, you can do everything you would on a normal cell phone - place/receive calls and send/receive texts. Pretty cool.

Link to comment
Share on other sites

So I downloaded GV and did the integration through the app but I don't have an option in Hangout to use my GV. I set my GV as my mobile number. I have the latest of both GV and Hangout. I also have the dialer. Am I missing a step?

Link to comment
Share on other sites

I had an unexpected experience last night with this. I am not fully integrated. I have a separate Google Voice number and I simply use Google Voice as my Sprint voicemail.

 

I do have the new Hangouts and the new Hangouts dialer. I had set it up to receive GV text messages, voicemails and incoming phone calls through Hangouts on the phone.

 

Receiving GV incoming phone calls through Hangouts created an interesting result. When I get an incoming Sprint call on my Sprint number the phone rings and if I don't answer it then it rolls to Google Voice voicemail as expected. However, once it rolled then I received a new incoming phone call through Hangouts from my GV number and I had to wait for that call to expire before the caller could actually leave a voicemail message.

 

It appears that Google Voice is not distinguishing between no answer call forward from the Sprint line and an incoming call. It is ringing the Hangouts app in both circumstances. I'm going to play around with some of the call rules and see if there is a way to overcome this.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...