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.
Sigh. In attempting to put the database back on my phone this evening after doing an update, it obliterated the database again. It had been working as normal for several weeks.
I think I'm going to [finally] apply the Android 10 update and see what happens. Maybe it'll help...
EDIT: When I rebooted, it came back up with data included. No idea what to make of it. Reimported from the file just in case, and it remained present, so we'll see, I guess.
Separately, how hard would it be to make it possible to filter the Neighbor Notes? I noticed earlier today that I'm seeing neighbors on Bands 12 and 2 pretty often. Naturally, it tries to look for notes for those PCIs with PLMN 310120, even though they're clearly T-Mobile neighbors. Would it be possible to add a "Sprint transition mode" or something where it matches Band 25/26/41 neighbor notes to 310120 and other neighbor notes to 310260?
Interesting to read an update. But I remember a lot of people back then said, 'I will believe it when I see it.' Now, 5 years later, I can't help but hear those voices even louder now. They were certainly proven right. Even if it does eventually happen.
I know that. I'm talking about further down the line for 5G. What I'm saying is that with the addition of Sprint's PCS, they can expand LTE on PCS and shift HSPA from AWS to the remaining 5MHz in PCS-B so that they can have a 25MHz n66 carrier down the line and a 20MHz n2 carrier since n2 is not currently registered for greater than 20MHz carriers.
The other solution would be to simply get rid of HSPA altogether and have two 25MHz n66 and n25 carriers since n25 allows for 25MHz carriers. Then T-Mobile could retain the 5MHz PCS-G for legacy LTE service.