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
VoLTE works surprisingly well on an unsupported device at the moment. I've forced it on the Pixel 3 XL, which Sprint insists is not possible, and it works great. It ignores all the per eNB enable/disable settings that Sprint broadcasts, so it's working on magic boxes and in theory unlaunched markets. I tested the QoS on it today in a rush hour subway station where Hangouts messages were taking 30-60+ seconds to send due to congestion, and it worked flawlessly. Honestly, I think whatever weird/non-standard(?) thing Sprint is doing to enable/disable it on a per eNB level is causing a lot of stability problems with supported devices, where it turns off and won't go back on, etc. Once that is overridden, it works really well, at least if you're in an area without 3G drops Sent from my Pixel 3 XL using Tapatalk
I can't bring myself to do it...I'm skeered!! I don't understand what's going on...however, maybe it's a good thing that Justin last emailed me 2 days ago saying that "I'm sorry, after meeting with my team, it has been discovered that MB is no longer going to work in your location..."
Paraphrasing here..but that's pretty much what he said to me.
Then, I conducted my test .....by going to Walmart with my inverter and MB Gold edition... Once I saw that the MB connected and was finally working as it should, I unplugged and came home with it..and put the Gold in place of the Demo Acct magic box..which is where it's at right now and working normally.
I took some pics while at Wal-mart of the box connected to the relay, then broadcasting b41 like it should..and also saved my GPS coordinates in a longitude/latitude format...and when I got to my PC at home, I pieced together the photos of the mb, the GPS coordinates, and sent Justin an email saying that I hated to hear about the boxes no longer working..but that I have been using magic boxes flawlessly for over a year (since launch/inception) and never an issue. So it really was bad news for us to hear we can no longer use it after great service for the past 1 year +++.
I haven't heard back yet. I hope that's a sign that he took what I said and isn't going to just chalk it up to listening to GIS software...
This area should be fine for MB use...and I hope they discover what is causing this entire central AL area to show up as unavail to use magic box in the address tester.
I don't know exactly how much area it is but EVERY single address that I've entered in the magic box address site says unavailable. That CANNOT be right...especially with all the bandwidth that Sprint has in this area...
CAVEAT: At launch, this area was PERFECTLY APPROVED for a magic box. SOMETHING has changed in their GIS mapping software or location data..not sure what. But my kids raced through their roaming data in 1 week without the magic box being on...it's really starting to bite...