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.....
Interesting to read an update. But I remember a lot of people back then said, 'I will believe it when I see it.' Now, 5 years later, I can't help but hear those voices even louder now. They were certainly proven right. Even if it does eventually happen.
I know that. I'm talking about further down the line for 5G. What I'm saying is that with the addition of Sprint's PCS, they can expand LTE on PCS and shift HSPA from AWS to the remaining 5MHz in PCS-B so that they can have a 25MHz n66 carrier down the line and a 20MHz n2 carrier since n2 is not currently registered for greater than 20MHz carriers.
The other solution would be to simply get rid of HSPA altogether and have two 25MHz n66 and n25 carriers since n25 allows for 25MHz carriers. Then T-Mobile could retain the 5MHz PCS-G for legacy LTE service.
They poached it from the lower 5MHz of Sprint's PCS B-block. I'm assuming the plan is to eventually expand PCS to 20MHz, leaving two 5MHz blocks (one in B-block and one in G-block) for legacy HSPA and Sprint LTE.