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

    • I have my Dish phone locked to NR-only.  That keeps it on Dish and only occasionally will it see T-Mobile NR SA for brief periods before going to no service. I also don't have mine band locked beyond that, except that I have some of the unused bands turned off just to try to reduce scan time.  Fortunately, my Dish phone is the one with the MediaTek chipset, so it has NR neighbor cells, and I can usually see n71, n70, n66, and sometimes n29 (market-dependent) through those regardless of which band it's connected to as primary. - Trip
    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
  • Recently Browsing

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