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.....
On recent versions of Android, you are not likely to see it update every second except for in specific scenarios, but I'm glad it's updating regularly for you!
For the benefit of whoever is interested.. signal updates from the OS are likely to be more frequent (but not guaranteed) if your device is moving fairly quickly (ie in a vehicle), and you are actively transferring data over the mobile network. When the connection is idle (including when you are using another connection method, like Wi-Fi), some things are not updated as frequently. Android does not publicly state anything much more specific than that.
In reality, the signal strength is constantly changing, every millisecond, faster than the screen can even update.. but there's no reason for any mobile device to monitor it that intensely, the CPU and power impacts would be crazy. An overwhelming majority of mobile users don't even need it updating even every 10 seconds. As of last year, over 314 million Americans had mobile phones.. with some quick math, SCP is on less than 0.0032% of them 😆
I got frustrated enough to go to the nuclear option. Full factory reset and did not restore from a backup. SCP is now refreshing every 5 to 10 seconds, not quite the every second I prefer but still much more usable than when it takes several minutes. I wish I could identify specifically what is causing this. I don't think it is intended behavior if it is indeed the result of power management. Sent from my LM-G820 using Tapatalk