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?
Had not seen a thread for this yet,
I see some definite consumer advantages with Sprint's Network combined with TMob and Wi-fi.
I have had many Nexus devices and I love my Nexus 6, although it is a bit big.
The price is good for the service. ($20 / unl talk/txt, $10/gb)
I hope the technical aspects work as they propose. I am a Google Voice Number user and love the "Any device" call capability and use it on my Tablet, Chromebook and phone. I rarely actually answer my Phone at the house. Answer the tablet or Chromebook.....
I love Sprint's network, the upgrades they are putting forth and this Site, but if Project Fi works as advertised, it might lure me to sign on.....
I'm not exactly sure of the reason yet.. there were no issues until I started "targeting" Android 10 in my compiler. I had not changed the core functionality of the app, so it must be something that changed in the way Android 10 behaves. Unfortunately, as you have experienced, I have not found a perfect solution yet. The solution I implemented in the most recent update apparently fixes it for some users, but not all. Complicating things further is that I do not experience the problem at all on my Pixel 3 or Pixel 4, and there are no error messages being logged by any devices -- it's just not updating. Oddly, if you launch another similar app (like Cellmapper), SignalCheck starts updating regularly. I am stumped so far!
Okay now after going back into a small town in rural mo where I go on the weekend a lot i am able to connect to b71 again. First time I’ve been on b71 around here in over a year.
One question.Is there anyway to see how wide the the LTE channels are on an iPhone?