Speed chargers – Good or Bad?

One thing all our portable electronics have in common, whether smartphone, tablet, phablet, or wearable; or Android, Windows Phone, or iOS, is the battery. Unlike desktop computers that get their power through a plug in the wall, all of these devices have to carry their own power source onboard, and battery capacity hasn’t really kept up with the rest of the tech inside our devices. To combat this, OEMs have tried to introduce new ways to keep our portables charged. From SoCs that are more energy efficient, more power conscious code, Qi wireless chargers, and now we even have speed chargers to help us get a quick boost right when we need it – well, almost.

Charging a battery isn’t a fast endeavor. Sometimes it seems like it takes as long to charge a battery as the usable time you get out of it. Luckily that’s more perception than reality, but it underscores just how slowly batteries charge. Recently, however, various manufacturers have begun to ship “speed chargers” that promise to give us oodles of run time on just a short charge. This seems contradictory, and flies in the face of what most would pass off as “good care and upkeep” for our batteries.

Now, however, companies like HTC and Motorola are coming out with “Turbo Chargers” that promise to cut charging time drastically, some even promising to give you an extra six hours of battery life from just 15 minutes of charging.

No, it’s not sorcery, it’s science! Looking at the fine print on the charger that comes packaged with the Nexus 6, for example, you’ll see various ratings on it:

• Standard Output: 5v, 1.6A
• Turbo 1 Output: 9v, 1.6A
• Turbo 2 Output: 12V, 1.2A

Other chargers have ratings of 1.5A and even 2A. Shouldn’t this cause problems? In short, yes. Yes it can – if your device can’t handle it.

As long as you’re using the charger that came with your device (or an approved accessory), you don’t have anything to worry about. As long as you’re charging from a computer’s USB port, you’re safe. Once you branch out into the wild world of third-party chargers, that’s where you need to do a little homework. You don’t ever want to exceed the ratings of your device, going below them (at least on amperage) isn’t going to hurt. It’s when you go over that’s cause for concerns.

Voltage, amperage, and resistance are all interconnected. The higher the voltage, the less loss you’ll have (electricity flows more efficiently at higher voltages), but higher voltage can be dangerous, too. Similarly, amps can be dangerous – even moreso than volts. Since everything is interconnected, you need an intelligent charge controller to monitor the battery and adjust the incoming voltage and amperage accordingly.

Apply the same thinking to your battery and its charger and you’re on the right track. These new speed chargers work with a chip in your device to help regulate the flow of electricity into the battery. They start off slowly until they get a feel for how it reacts to being filled, then fill more quickly in the middle. Finally, they slow down and trickle to top it off.

Will this shorten the expected lifespan of the battery? Probably not, thanks to the extra intelligence in the charging circuit. However, it should be reiterated, even though our devices use similar charging ports, before you use a charger, make sure your device is rated to handle what it’s dishing out. Failure to do so will very likely shorten your battery life. However, if you simply use the one that came with your device, you’ll be just

 

 

BPG: A new, superior image format that really ought to kill off JPEG

For all of the massive technological advances that we’ve seen over the last few years, there are still a number of dinosaurs from a bygone era that, rather unfortunately, just won’t die. JPEG is one of the most prominent examples: It was created more than 20 years ago, and yet its antiquated, bloated, blocky algorithm still dominates the web. You would think, with the modern web being so image-oriented, that we would replace JPEG with something better — but no, it’s 2014 and JPEGs (and multi-megabyte GIFs!) still reign supreme.It’s not like people haven’t tried to replace JPEG — but, much like MP3 or ZIP, it’s very hard to unseat an incumbent file format (or, more accurately, a compression technology). The fact is, despite any misgivings we might have about JPEGs or GIFs, almost every computer system in the world can display them — and generally, in the grand scheme of communication, it’s much more important to make sure that your message was seen at all, rather than making sure the message is as small and as optimized as possible. Yes, ExtremeTech could start using a JPEG alternative, and revel in our smaller and faster page loads — but our excitement would be rather short-lived when we discover that, for 99.9% of our readers, the site looks like ass.

One of the most famous attempts to replace JPEG was attempted by Google, with its WebP format — but four years on, and it’s still nothing more than a niche file format that hasn’t gained much widespread support outside of Google’s products and services. (The recent trend towards replacing animated GIFs with WebP is pleasing to see, however.) More recently, Mozilla started experimenting with mozjpeg, which reduces file sizes slightly (~10%) while still retaining JPEG compatibility (a big plus). And now, from the creator of FFMPEG and QEMU, Fabrice Bellard, we have BPG!

Short for Better Portable Graphics, BPG offers around the same image quality as JPEG, but at half the file size. To perform such witchcraft, BPG simply uses a newer codec — x265, the open-source implementation of HEVC/H.265. In essence, a BPG image is the same thing as taking a single frame out of an x265/H.265 video stream. We’ve talked about H.265 at length in the past, but basically it’s just a much better algorithm than JPEG — or MPEG-2 or H.264. Furthermore, BPG also has H.265’s ability to render 14 bits per color channel (JPEG is just 8), plus BPG also brings an alpha channel (transparency). Lossless compression is available (though I haven’t seen how it compares to PNG).

To see how BPG compares to JPEG and WebP. Move your mouse left and right and marvel at how bad JPEG is. The differences will be less pronounced if you go up to “medium” or “large” file sizes, but that’s because the window is very small — plus, with the shift towards mobile computing, it’s highly compressed images that are most important right now. BPG isn’t just for mobile users, though: 14-bit color, which allows for a much higher dynamic range than 8-bit JPEG or WebP, is perfectly suited to newer cameras and displays.

But, of course, at the end of the day, BPG is still just another file format/codec that has a grand total of no native support anywhere. For now, the only way of rendering a BPG file is with a BPG decoder written in JavaScript — about 71 kilobytes of JS, to be exact. Obviously, if you’re trying to cut down the footprint of a mobile website, downloading and executing yet more JavaScript kind of defeats the point. (On desktop PCs, though, the performance hit from using the JavaScript decoder will be minimal.) There is an open-source BPG library that browser makers and other software developers can build into their apps, but obviously mass integration will take months or years.

There is one other interesting aspect of BPG, too: Because it’s based on HEVC/H.265, any device with hardware decode support for H.265 can also decode BPGs in hardware. This is a big deal, because more advanced compression methods tend to require more computation (and thus power) to decode — which is a no-no on mobile devices. Hardware-decoded BPG would be better than JPEG in every which way — now we just have to pray for adoption by software developers.