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 see both Verizon and AT&T are getting this. Has anyone heard rumblings for a Sprinter variant? I was hoping since they at least have a CDMA version that Sprint would be able to get their bands on it also.
So the official complete render as per ev leaks has been leaked http://androidandme.com/2014/05/news/htc-m8-prime-m8-ace-image-leaks-show-backsides-of-unannounced-phones/?utm_source=rss&utm_medium=rss&utm_campaign=htc-m8-prime-m8-ace-image-leaks-show-backsides-of-unannounced-phones
Looks not like what I anticipated I really hope that is an early design and color scheme.
Copy and pasted from androidcentral.com
These leaks come courtesy of none other than @evleaks, and considering that the came out in a spat with Jeff Gordon (HTC's Senior Global Online Communications Manager, not the race car driver), they should be taken with a bit of a skeptical eye. It's also worth considering that, like the Galaxy S5 Prime, we don't expect that any One M8 Prime device would be a replacement for the One M8. Think of it more as a next generation HTC One Max. So on to the leaks:
Quad-core 2.5GHz Qualcomm Snapdragon 805 processor
5.5" 1440x2560 QHD display
Cat. 6 LTE
Those specs, while open to change, would be in line with what we might expect from a phone like this, and they line up with an earlier leak out of China. There's one more leak, and this one we're strapping on our skeptic helmets: it's made out of "a composite of aluminum and liquid silicone."http://www.androidcentral.com/htc-one-m8-prime-rumored-exotic-material-composition-faster-lte
On my iPhone XS Max, Bands 2 & 4 LTE shows up as Sprint native service on the device, but in Field Test Mode you know it's T-Mobile because the MCC MNC is 310 260. So it never actually states that it's T-Mobile except for the MCC MNC.
And yes, my phone kept jumping 5 hours behind and back.
I replied to your Reddit post. But so others here know, it's an issue with eCSFB and IMS on the Airave. Devices which maintain SRLTE don't have the issue, since calls and texts go over CDMA instead of LTE. I have a ticket open about it, but so far they can't find anything wrong. Been a problem that has been ongoing for months, and I know other people in different markets with different devices and accounts have the exact same issue. It affects all phones that rely on eCSFB and IMS instead if SRLTE.
A "solution" is to block the LTE ipsec tunnel on your router's firewall. In my experience, blocking access to 22.214.171.124 and rebooting the Airave resulted in just CDMA and no LTE. That being said, if your non-SRLTE phone can pick up the macro LTE signal at all, it will almost certainly never use the Airave. I don't believe that macro eCSFB will setup a call via the Airave.
Sent from my Pixel 2 XL using Tapatalk