Jump to content

Google Hangouts w/Voice (Was Google Voice)


COZisBack

Recommended Posts

It seems to only send double if I select to send from my cell or if someone text me for the first time. I've tested sending from my phone (Nex 5) to my work phone (IPhone 5) and it is sending double and receiving 4 or 5 texts. It seems to work fine if I send the first text using google voice or there is a thread already started and using google voice number or smart reply. My number is full integrated so I'm sure that is part of the problem. ( same number for cell and gv) the only other problem I have is since its gv it's using data and if I send a text using gv and then take a call or have no data I won't receive a text back because its using gv.

Link to comment
Share on other sites

I finally got my merge finished. I thought I saw this in the thread somewhere but couldn't find it. When you have the box checked to ring hangout for incoming calls I can not answer in hangout because I lose data. Was there a work around for this?

 

See the below:

 

[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

You get a double when hangouts sends via SMS and it then shows up as gv as well. The setting to always send via gv doesn't work properly with the sprint integration.

 

With the Smart Reply feature, it will choose the send type based on the last message you received in the thread to which you are responding. With sprint integration on, incoming SMS are interpreted as gv, so responses will send via gv and you won't see a duplicate. However, group texts or pictures are interpreted as (non-gv) mms and are received at the sprint number. So replies to those will send via SMS and then spawn a gv duplicate.

 

Subject to change if google/sprint decide to fix it

Edited by djw39
Link to comment
Share on other sites

Hangouts was updated again overnight (17th). probably more bug fixes because I didn't notice additional settings. However, receiving MMS, sent to my Sprint GV#, on my Verizon S4 still doesn't work. bummer!

 

Sent from my SCH-I545 using Tapatalk

Link to comment
Share on other sites

I don't like the calling from Hangouts. I like how the Google Voice app let's me choose between Making all calls from my Google Voice number or ask me every time I make a call.

 

This gives me the option to choose from making calls from my Verizon number or my Sprint GV#.

 

If seems to me if I enable the dialer in Hangouts, all my calls will go through Hangouts. Which is not good. The purpose of me getting the Verizon service and my S4 is for rock solid voice/data coverage with no dropped calls and call clarity.

 

I use Wi-Fi Calling with my Sprint S4 720T and VoIP at my job...trust me... making regular calls from Hangouts, after the newness has worn off, will eventually be irritating. Perhaps not... but my experience has been mostly good with Wi-Fi Calling and VoIP, but at times there as been delays and call interference, where the other party has said... "I couldn't hear you, your voice was breaking up."

 

As long as Google keeps the Google Voice App alive and kicking... I will use that for my Voice calling on my Verizon phone and now I will use Hangouts for my SMS.

I completely agree!

 

I am the same way. I have phone number that is my mobile work number, that I ported to GV, and I also have a personal mobile phone number that is my Sprint number.

 

58faea6bcd09e31e394b4d1a7ef1d24d.jpg

 

I like the fact that when I dial an outgoing call, I have the ability to choose between using my GV business mobile number or my personal Sprint number.

 

I too am going to hang on to my Google Voice app for as long as possible, and once I am forced to integrate my Google Voice with Google Hangouts, I sincerely hope that the Google Hangouts integration does not take away the ability to choose between my two phone numbers.

  • Like 1
Link to comment
Share on other sites

what do you means "deals?" are you talking Google or Sprint?

 

 

AJ

  • Like 1
Link to comment
Share on other sites

I an bailing out this Sprint Google Voice and Hangouts intergration. Many people have reported that they are receiving any where from 5-10 duplicated messages.

 

Here is what I speculate.... There is a serious bug when you send a GV/hangouts SMS.... every session of Google thatv you have logged in.. Sends out a text message. Any browser and smartphone.. recognizes you send and SMS.... and sends SMS out.. Hangouts can't determine that the SMS has been sent already.

 

That is just my educated guess.. because every Hangouts session I have logged it... that is how many SMS messages the other party gets.

 

I will switch back to my old setup again...

Link to comment
Share on other sites

I an bailing out this Sprint Google Voice and Hangouts intergration. Many people have reported that they are receiving any where from 5-10 duplicated messages.

 

Here is what I speculate.... There is a serious bug when you send a GV/hangouts SMS.... every session of Google thatv you have logged in.. Sends out a text message. Any browser and smartphone.. recognizes you send and SMS.... and sends SMS out.. Hangouts can't determine that the SMS has been sent already.

 

That is just my educated guess.. because every Hangouts session I have logged it... that is how many SMS messages the other party gets.

 

I will switch back to my old setup again...

Since integration I haven't had any issue with text or mms.
Link to comment
Share on other sites

The SMS were fine.. then just today... Three people have said.. " dude. there must be something wrong with your phone.. I am getting duplicate messages from you. Not just 1 or 2... but 6,7,8,etc.. " there was an update last night.. Wonder if what ever they fixed.. They broke something else.

  • Like 1
Link to comment
Share on other sites

The SMS were fine.. then just today... Three people have said.. " dude. there must be something wrong with your phone.. I am getting duplicate messages from you. Not just 1 or 2... but 6,7,8,etc.. " there was an update last night.. Wonder if what ever they fixed.. They broke something else.

I had the same issue. A coworker got 11 of each text I sent.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I had the Hangouts update two nights ago, and I just got another one now: 2.3.75731955. No idea what they're changing, but hopefully resolving the issues you guys mentioned.

Just got it.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

It seems to only send double if I select to send from my cell or if someone text me for the first time. I've tested sending from my phone (Nex 5) to my work phone (IPhone 5) and it is sending double and receiving 4 or 5 texts. It seems to work fine if I send the first text using google voice or there is a thread already started and using google voice number or smart reply. My number is full integrated so I'm sure that is part of the problem. ( same number for cell and gv) the only other problem I have is since its gv it's using data and if I send a text using gv and then take a call or have no data I won't receive a text back because its using gv.

 

I an bailing out this Sprint Google Voice and Hangouts intergration. Many people have reported that they are receiving any where from 5-10 duplicated messages.

 

I had the same issue. A coworker got 11 of each text I sent.

 

Guys - Important message from Google:

 

If you're using Google Voice on your Sprint phone, you shouldn't turn on text messages and voicemails in Hangouts. This will cause problems with your text messages.

 

Not sure when that went up, but they must know about the issue. This merger has been a disaster. How could they let this happen to Sprint integrated customers?

  • Like 1
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...