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)
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
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?
Had not seen a thread for this yet,
I see some definite consumer advantages with Sprint's Network combined with TMob and Wi-fi.
I have had many Nexus devices and I love my Nexus 6, although it is a bit big.
The price is good for the service. ($20 / unl talk/txt, $10/gb)
I hope the technical aspects work as they propose. I am a Google Voice Number user and love the "Any device" call capability and use it on my Tablet, Chromebook and phone. I rarely actually answer my Phone at the house. Answer the tablet or Chromebook.....
I love Sprint's network, the upgrades they are putting forth and this Site, but if Project Fi works as advertised, it might lure me to sign on.....
Not necessarily. Depends who bids for it, how much they get and what they have to pay for it.
Had the merger not occurred (with Masa failing to infuse any cash into the business), Sprint would be in an even worse position as T-Mobile could have picked some up, unless AT&T or Verizon grabbed it all. Sprint was already circling the drain. This would have finished them off in my opinion. Sprint didn't have the money for lowband, and it wouldn't have had the money for this spectrum either.
The efficiencies realized through merger synergies should allow T-Mobile to pick up some if it wanted to.
Personally I'd keep the Airave 4. All the femtos are the same when it comes to VoLTE. Your resets are definitely delaying it getting reactivated. I know it sucks, but you just have to leave it be for 3 weeks. Eventually VoLTE will get turned back on. If your S10s are on Sprint (check the PLMN in the engineering screen, or use an app like Signal Check Pro), then they will eventually find the Airave again. The network completely controls what your phone connects to, unless you lose service completely. You will not end up on the Airave unless the network tells your phone to connect to it. Usually it takes up to a few weeks for the Airave to get integrated into the network and for the towers around you to know about it. Once they do, they'll allow handoffs and will move your phone to it when it's in range. As to why the other phones see it and connect, there are a number of possible reasons. One of which is because it doesn't have VoLTE enabled (I've found that devices that use VoLTE will avoid moving to something that doesn't have VoLTE enabled). But basically it will be inconsistent until the network has integrated it. Every time you factory reset (ie, the PCI changes), it wipes this and has to start over again with integration.