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.....
I've come across a number of Crown Castle oDAS nodes (small cells) on T-Mobile. I think a bunch used to belong to MetroPCS. I found 3 in my own neighborhood and one in Williamsburg. The ones on my neighborhood all share the same the same eNB ID which makes it annoying to track on Cellmapper since it's 3 separate "sites" but only one marker.
I'm not seeing any frequency info on my T-mobile phone, but the stale data issue appears fixed. When I force it to B12 the 5G info disappears immediately. I can't test on my AT&T phone ATM, it appears they are working on my home site again and all I'm getting from it right now is B12. Sent a diagnostic report from my T-mobile phone and will send one from my AT&T phone once I get an NR connection on it. Sent from my SM-G986U using Tapatalk