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.
I did double check, but it was doing about 2GB a day at 2.4 GHz and about 3GB a day on 5GHz. Now it's maybe couple hundred MB a day. Perhaps it's a slow rollout.
To be honest, I haven't tried VoLTE on MB yet. Sounds like it's time to give it a whirl...
BTW. This is all in San Francisco.
All depends on the terrain/intended coverage area, sector alignment/tilt and antennas used.
Wide beam antennas in a 4-sector 90° configuration can actually do a lot of damage to the SNR. Alternatively narrow beam antennas at a 3-sector 120° can leave big coverage holes between sectors. It's a pretty interesting balancing act.
I am not enjoying this t-mobile 5G in Astoria Queens or even LTE for that matter. Here is comparison between the 2 today at Astoria park. This area had even faster speeds before Sprint 5G was shut down. T-Mobile really needs to expand the N41 coverage outside of Manhattan asap. Some how Sprint really delayed it fast. Sent from my SM-G988U1 using Tapatalk
I'm still getting 50-90 Mbps (depending on how close I am to it). You might want to double check that it didn't fall to 2.4 GHz. Mine is Ethernet backhauled though.VoLTE has been live for many months on all the femtos. They don't need to cap anything for it to work. In my experience using LTE backhaul on a magic box with VoLTE, it didn't do well at congestion control (was cutting out because the donor was congested), so I'm skeptical that they tunnel VoLTE over a prioritized EUTRA session on relay. So if they aren't doing something as "basic" as this when they completely control the network, they almost certainly won't be doing anything on wifi or Ethernet backhaul to try to give VoLTE special treatment. Sent from my Pixel 4 XL using Tapatalk