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?
I posted the below on the essential subreddit. Wonder if others on sprint have the same issue?
"It is well noted that the essential has reception / radio problems but today, when I roamed on to US Cellular, it completely abandoned 1x and connected to LTE only. Which is fine when connected to Sprint because the phone can pass text messages over LTE.
However, while roaming, the phone would not send or receive text messages and could not make or receive calls because it was latched to USCC LTE and needs a 1x connection to do this. My 5X (and I assume every other phone), when it connected to USCC LTE, would somehow get notification of a text or call and idle back over to 1x to take care of things and then dump the 1x connection until needed again (signal check shows all of this happening). Same deal when I would try to send a text as well. Seems the essential is dead in the water under these conditions and just can not bring it self to go to 1x when needed while roaming, at least on USCC. I do not have other roaming carriers up here to test with.
I am sure we do not need to go into the problems with being completely unable to make a phone call in the very large areas that Sprint uses USCC to roam on.
I can accept if it was just the area I was in. So in that case, any other Sprint users roamed on USCC LTE without any voice or text problems recently? I am on Oreo Beta for what its worth."