mhammett
-
Posts
1,162 -
Joined
-
Last visited
mhammett's Achievements
Member Level: 4G WiMax (10/12)
616
Reputation
-
You can always use CellMapper to take a look at what towers and coverage are like in an area.
-
I guess I haven't been paying attention. https://www.cellmapper.net/map?MCC=310&MNC=260&type=LTE&latitude=41.953659214207136&longitude=-88.73794697304687&zoom=11&showTowers=true&showTowerLabels=true&clusterEnabled=true&tilesEnabled=true&showOrphans=false&showNoFrequencyOnly=false&showFrequencyOnly=false&showBandwidthOnly=false&DateFilterType=None&showHex=false&bands=5,13,17,25,71&showVerifiedOnly=false&showUnverifiedOnly=false&showLTECAOnly=false&showENDCOnly=false&showBand=0&showSectorColours=true&mapType=roadmap I've seen them, per CellMapper!
-
Does anyone have a Pixel 3 XL case recommendation that's more rugged than the Spigen Rugged Armor? Let's just say it's not rugged enough.
-
5G is purely about manufacturers trying to sell more equipment.
-
Did you run CellMapper when driving around?
-
Was the problem in the messaging (calling it charging rapidly when it was really charging slowly) or was the problem in that Google forgot to enable the DRM in the release version? The only real way to know is a screenshot of a battery management app before the update showing what the charge rate actually is when "charging rapidly".
-
I am looking for more observations on this. I believe the restriction on the Google-approved wireless chargers for charging rapidly was instituted in a software update. Out of the box, my 3 XL was "charging rapidly" from my old generic wireless charger. I installed the update and now it's "charging slowly". Can anyone else confirm? Can I roll back my update?
-
Apparently, the 10w wireless charging is a Google standard. If you wish to use Qi, you're limited to 5w. The Qi standard goes up to 15w. Why, Google, why?
-
The Nexus 6 was the last Pixel\Nexus that had wireless charging, so it was the last one worth considering. Now it's back. Is the Pixel 3 an RF powerhouse like the Nexus 6 was?
-
The problem is generally the power from the handset back to the tower, not from the tower to the handset. Voice calls should require less capacity than a speed test. A speed test is the most intensive thing you can do on a network, well, short of BitTorrent.
-
The one I was looking at was 8290, so that should hold true. https://www.cellmapper.net/map?MCC=310&MNC=120&type=LTE&latitude=41.85563059481918&longitude=-88.50457084856009&zoom=11&showTowers=true&clusterEnabled=true&tilesEnabled=true&heatMapEnabled=false&showOrphans=false&showNoFrequencyOnly=false&showFrequencyOnly=false&showBandwidthOnly=false&DateFilterType=Last&showHex=false&showVerifiedOnly=false&showUnverifiedOnly=false&showLTECAOnly=false&showBand=0&mapType=custom_map&showSectorColours=true
-
If a Sprint channel is on 1875 MHz, what size of channel is it? What is the Chicago-area currently running on?
-
I noticed that Fi doesn't have all of the Google Voice features. No voicemail to email, no call screening.
-
Okay, so I'm likely to move down to 3G with the RRPP coverage (if any)?
-
Right, but that doesn't really address my questions (about Google Fi vs. Google Voice feature parity or Sprint rural partnerships).
