Nrbelex

That was very likely a misinterpretation of what that representative was trying to say: http://www.xda-developers.com/hold-your-horses-huawei-nexus-rumors-may-have-been-misinterpreted/

The rumor mill has fully geared up, so it seems time for a thread in which the potential HTC-made 2016 Nexus phones can be discussed. Rumors suggest two phones: a 5" device codenamed Sailfish, and a larger device codenamed Marlin. Both are thought to be produced by HTC. [There's also a report that Google is making its own phone, without an OEM partner--along the lines of a Pixel phone--but that report has been largely discounted.] Android Police has claimed it knows with 8/10 certainty some specs of the smaller device--Sailfish: Manufactured by HTC 5" 1080p display (~440PPI) Quad-core 2.0GHz 64-bit processor (model unknown) 4GB RAM 2770mAh battery 32GB storage (unknown if multiple models will be available, or even if this is the base storage level) 12MP rear camera, 8MP front Rear-mounted fingerprint scanner USB-C port (bottom) Bottom-firing speaker or speakers (unknown if dual) Top-mounted headphone jack Bluetooth 4.2 Any thoughts on these devices? The last several Nexus devices have been Sprint compatible; is there any reason to think these won't be? Any hints in regulatory filings? How is HTC's radio performance, generally? Will Sprint sell them directly, and even if they do, will it still be preferable to buy directly from Google?

Yea, not on my agenda. Just hoping they're willing to give out SIMs and not charge an exorbitant fee. I've actually seen them refuse to give out SIMs before, but that was back in the age of contracts and before phones could really be moved between carriers—particularly CDMA. Fun fact: sent my N5 (purchased from Sprint) into LG for a weird power issue without a SIM, and it came back with a new Sprint SIM.

Argh, guess that means Sprint store and all the nonsense that entails. Or shaving down the SIM—which I'd really like to avoid.

So assuming the Google store doesn't have its act together, and the phone doesn't ship with a Sprint SIM, A. can we just pop the SIM from a 2013 Nexus 5 into the new one, or B. will we have to go to a Sprint corporate store, and if so, are they going to know what to do, and will they charge?

I'll second all those saying those who sideloaded the OTA (or those who applied the standard OTA) might want to consider doing a factory restore. I sideloaded the OTA and had choppiness and unexplainable battery drain, but things seem better after the restore. The whole process took roughly 2 hours, but I do a lot of tinkering with settings, activating encryption, etc., so it probably won't take most users that long to get back where they were.

Well that's what I get for trusting random Internet people. Went for the sideload. Looks good.

Well yea, but I'd like to figure out what stage they're at. Apparently stage 0 as of now. Not interested in sideloading because, as I understand it, sideloading an OTA doesn't necessarily update your radio (and to manually update your radio you need root, and to get root, you need to wipe your device).

I know it technically started, but I was hoping to find out if anyone has actually received it yet. There's often about a two-week lag between the roll-out and most people getting it. See: https://www.reddit.com/r/Nexus5/comments/2mdv8n/anybody_else_not_receive_their_ota_update_yet/

Bump. Any reports of OTA actually rolling out yet?

Any reports of OTA yet?

With all those LTE bands, how will roaming work for Sprint customers?

This has already been discussed, but basically Google botched GV/Hangouts integration for Sprint customers. If you want to avoid problems, integrate your Sprint # into GV, but do not merge Hangouts and GV. You'll still have two separate apps, but everything will work the way it's supposed to. With any luck Google and Sprint are actually working on the issue and we can merge them soon. At the very least they are aware of the problem.

Yea, but I wonder about Sprint changes and fixes to radio firmware, if they're responsible for that.

Did Sprint just EOL the Nexus? Has this already been discussed? http://www.androidpolice.com/2014/09/26/sprint-sends-the-nexus-5-to-the-end-of-life-underworld-but-no-one-cares-because-nexus/ Does this have any practical impact on those who already own it?

That last article even has a nifty map of supposed cell phone interceptors:

Here are a bunch more articles: Wired - Phone Firewall Identifies Rogue Cell Towers Trying to Intercept Your Calls Washington Post - Tech firm tries to pull back curtain on surveillance efforts in Washington Ars Technica - FCC to examine “unauthorized” cell snooping devices And today, CNBC - If you're on a phone in DC, someone could be listening Some of this is just PR for the company selling a so-called "cryptophone," but I'm sure some of the issues being raised are also real. My understanding is that IMSI Catchers are GSM specific, so they might not target Sprint, but with Verizon being the biggest network in the country, I'm sure there's a CDMA equivalent. Given that many of you guys are real experts in this area, my questions are: Do the techniques described pass the smell test of technical feasibility? Have you ever noticed anything which leads you to believe similar techniques are being used on the Sprint network? Is this something you're worried about? Anything you can do to avoid or deter being caught up in this kind of tracking/surveillance?

Yup, we've been discussing it in the GV thread, but there's also a GV support forum page: https://productforums.google.com/forum/#!searchin/voice/Sprint/voice/UeXGeI1lVeY/Q-Lzc-Ma0FcJ

Not quite. Google currently says Sprint customers using GV "shouldn't turn on text messaging and voicemails in Hangouts. This will cause problems with your text messages." So while you want to integrate Sprint and GV, you don't want to merge GV and Hangouts. Does that make sense?

Yes, that's the issue. You have to be using GV for the call to come from your number.

See also: https://productforums.google.com/d/msg/voice/UeXGeI1lVeY/YWD9-L1PXPwJ And if you're on Reddit, bump this thread up so the issue gains some attention: https://www.reddit.com/r/Android/comments/2gtico/google_if_youre_using_google_voice_on_your_sprint/

Yup, that little badge means he's verified. You can check for yourself: https://plus.google.com/+josuejoseph1991/posts/XaPbNesBPoD He said the following:

Punit Soni is VP, Product Management at Motorola Mobility. Looks like we're at stage 1. Next should come anger...

You can do it via data (LTE/3G) too and thereby achieve pseudo-SVLTE (at the expense of using up additional data).

Guys - Important message from Google: 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?