Nrbelex

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.

See this post:

Haha, why am I not surprised they're completely at odds.

Not a Moto person misspeaking. Confirmed by Sprint that it was out of their hands: https://twitter.com/sprintcare/status/512420169277124608

See the below:

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.

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.

[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'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 never received a message in Hangouts and/or Google Voice, asking me to merge them together, which other people were reporting before Google rolled the whole thing back: http://www.droid-life.com/2014/09/11/dont-stress-if-you-didnt-get-asked-to-merge-hangouts-and-google-voice/

No - I've been integrated for years and I received the Hangouts update lat last night. But I don't think I was ever offered the option to "fully" integrate. That is, my Google Voice app still functions as always.

VoLTE worked fantastically this evening through integrated Hangouts. Call was crystal clear - possibly more so than regular calls - and I received an E-mail while the call was ongoing, all while walking around town with Wi-Fi turned off. Color me impressed. If you've been one of those people disappointed by the lack of SVLTE on Sprint, this would seem to be a great workaround.

Yea, that's what I meant by "aside from VoIP calling," but Wi-Fi calling is more accurate.

I've also not been offered the updated Hangouts app or any merger options. It seems possible that those using Sprint's GV integration are going to have to wait a bit. Also, since we're integrated, there's no benefit to having the new dialer app (aside from VoIP calling) correct?

I actually don't think that page describes the new replacement program. That seems to be the general exchange/defect policy. Don't think we'll know until someone tries it.

Any source for that?

Anyone happen to know if the apparently new Nexus 5 replacement policy applies to phones purchased from Sprint?

Also got a forced PRL update overnight. Woke up to find the screen just sitting on, which is somewhat annoying; who knows how long ago it happened. What is the deal with these forced updates?

Anyone experience this issue this weekend? http://www.androidpolice.com/2014/05/05/psa-sprints-google-voice-integration-has-been-kind-of-busted-all-weekend/

If you're still using your old phone on WiFi, update its profile. Had the same issue until I did that.

I didn't sideload, so the first update I got from the Play store was 76.

He probably means it's now available through the Play store, which I can confirm.

I believe the (standard, default) Google Voice app also routes SMS over whatever data connection the phone is using, including WiFi. Obviously no MMS there though.

I'm still aggravated with Google for killing Reader, but when Google kills something valuable, a smaller player usually comes in to fill the space (see Newsblur, Digg, etc.). In terms of notifiers - I was also annoyed when the Gmail notifier was killed off, but in-browser notifications have gotten significantly better than when the notifier was introduced, and I find between those (on either Firefox or Chrome) and other notifications (phone, just keeping a tab open with the total number of unread messages), I don't really miss it. I would hardly call Google breaking compatibility with unsanctioned, third party products "evil." Annoying, certainly, but Google is a company with a profit motive, after all. I reserve "evil" for things like cooperation with China's filtering or the NSA...

Radio silence from Google since the last integration rumors a few years back... Honestly, I think there's a 50/50 shot it'll still exist in a year. I'm just thrilled it hasn't (yet) been killed in this year's spring cleaning. Don't get me wrong, it's fantastic, but I don't think it caught on the way Google or Sprint hoped. (That could be said of Google Voice in general, but I digress).