I was taking a look at the HTC 5G Hub that's supposed to be launching on Sprint sometime this month. It looks like it could technically be Sprint's first foray into the WISP space. On HTC's site they mention it as a sort of replacement for your WiFi router with the ability to connect up to 20 devices to it. I wonder what data caps will be on this when it launches and what they plan on charging people for using it?
It seems to be a lot of things smashed into one device. It's combining a wireless router, a streaming box, and a cloud gaming device all into one. It also has support for pretty much every U.S. LTE band.
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.
Should be able to draw some good interest once we get these torn down and figured out. Expect lots of proprietary protocol so finding a comm port on the modem will be tricky if that is your thing. Getting an antenna design going is what I am excited for most. All I can do with the software is try to break it hard enough in the most blatant manner possible.
I have to be nice to this case though, I shredded a MR100 Nighthawk and a couple of magic boxes no problem, I'm trying to keep this thing at least a few more months, so I am excited to see what I can come up with. If you manage to teardown Sprint's premiere 5G home router and set up some externals that would be really neat to see.
Jim @LTEfix is great. We boomer chat on facebook and get confused by all the software, bitmaps and such. He really has a great domestic business going sourcing all this stuff. Thanks to his services I have an elaborate junkyard going and now 3 year Ever Improving LTE Internet Project.
Doesn't look like it. It only supports Band 2, 4, 5, 12, 13, 17, 26, 41, 66, and LTE-U. It also doesn't have CDMA support. That said, U.S. variants of Samsung phones tend to have U on the end of their name while international variants tend to be F. This is the international variant.
I'm noticing some new giant dead spots along I-29 in ND now. Central MN as well. Also SE MN, central MI, southern OH, parts of KY, VA, NC, SC, GA. It's like they just went in and carved some areas out. Seems like they cut out along major interstates. Maybe a cost saving measure to remove roaming?
I just took a trip up Hwy 395 in Central CA between Mojave and Bishop and was roaming on Verizon in some areas. This was for voice at least as I test called customer service and got the Verizon recording. I also had data roaming in some places but not sure who's signal that was as it worked fine for internet browsing (Ebay, Yahoo and Facebook) but wouldn't allow me to send pictures or search google in my web browser. I'm guessing the file size on the pictures I was trying to send were probably too large for what the roaming partner allows. Also wherever Sprint had coverage LTE worked fine and the voice signal was on 800 Mhz according to debug mode.