3 ms·
I have the same experience; something doesn't add up about this article. My Verizon Galaxy Nexus will charge (albeit slowly) as long as I'm using a charger that
by monitron 15y ago
I have the same experience; something doesn't add up about this article. My Verizon Galaxy Nexus will charge (albeit slowly) as long as I'm using a charger that supports the USB dedicated charging specification (One example is the Palm Vehicle Charger you can grab from sellers at Amazon).
I can run the screen at full brightness, 4G and all other radios firing, using Navigation while playing music streamed over 4G onto Bluetooth, and it still charges. I guess the CPU probably isn't pegged at 100% in my scenario but how often does that happen realistically?
- michaelcampbell 15y agoI don't know how it is on the GNex, but I did a quick unscientific test with the original Droid and it rarely used more than half of the CPU while using Google's Nav app. I was actually quite shocked at how little CPU it used.
- monitron 15y agoWell, all the pathfinding and at least some of the map rendering is being done server-side, and the 3D drawing is mostly offloaded to the GPU. So I would actually be surprised if the CPU was working hard for Nav. My guess is that a lot of the power suck during navigation comes from: - Keeping the screen on - Constantly reading the GPS - Loading new map tiles, traffic data, etc over the radio - GPU rendering at 30fps or so
- oldstrangers 15y agoThat charger actually provides more amps. The real problem is the shitty generic chargers carriers are providing for cars. But apple people will love to make more of this than it warrants.