4 ms·

I wonder if we'll see more of this from device OEMs, if only to protect against things like iffy USB-C and Qi chargers that don't conform to standards. Standar

I wonder if we'll see more of this from device OEMs, if only to protect against things like iffy USB-C and Qi chargers that don't conform to standards. Standard Qi chargers don't put out enough power/heat to cause lasting issues, but a fast charger could. Similarly, Google's already seen major issues first-hand from an off-spec USB-C cable [0]. [0] https://www.engadget.com/2016/02/03/benson-leung-chromebook-pixel-usb-type-c-test/ https://www.engadget.com/2016/02/03/benson-leung-chromebook-...

ConceptJunkie 8y ago
If only there were an organization that could test and certify that these products adhere to the standards...
- Fej 8y ago
  Too many counterfeits. The solution is basically what Apple did: put MFi chips in everything to ensure the valuable hardware isn't damaged, and lock down who can get the chips. Obviously this is very difficult for a standards body.
- CydeWeys 8y ago
  There are such organizations, and yet the counterfeit problem persists (and the world's largest retailer does little to stop it). On-device protection is way more effective anyway.
rkangel 8y ago
My guess is that the implementation is not good enough, and fast charging generates a lot of heat in the handset. Only with their own charging can they guarantee enough heat dispersion in the charger. Wireless charging is a bit lossy and can generate a lot of heat - I know this from experience designing devices, although everything else is guesswork. Whether it was always intended to be incompatible,or they had to put the hacky handshake in late in the process to prevent the device being 'a bit fiery' I don't know.
opencl 8y ago
What Google is doing here is specifically rejecting the chargers that do conform to the standard by tacking on a proprietary handshake. HP had a similar charging DRM scheme on their first few models with USB-C charging but seems to have dropped it. Apple has been doing this with non-MFi chargers since iOS 7. A lot of people were mad when the OS update made their perfectly good chargers stop working. Of course now there are clones of the MFi authentication chip and even with a new chip revision Apple can't reject them without also breaking all of the old legitimate chargers. So it completely failed to actually solve the problem anyway.
- djrogers 8y ago
  This is bunk - I use a TON aid non-MFI chargers, and without exception they work as long as I have a decent cable. Old, dodgy or worn out cables can cause an error message but it’s got nothing to do with an MFI chip in the charger.
  - opencl 8y ago
    Ah yes sorry, I meant to say cable rather than charger.

ConceptJunkie 8y ago

If only there were an organization that could test and certify that these products adhere to the standards...

Fej 8y ago
Too many counterfeits. The solution is basically what Apple did: put MFi chips in everything to ensure the valuable hardware isn't damaged, and lock down who can get the chips. Obviously this is very difficult for a standards body.
CydeWeys 8y ago
There are such organizations, and yet the counterfeit problem persists (and the world's largest retailer does little to stop it). On-device protection is way more effective anyway.

rkangel 8y ago

My guess is that the implementation is not good enough, and fast charging generates a lot of heat in the handset. Only with their own charging can they guarantee enough heat dispersion in the charger. Wireless charging is a bit lossy and can generate a lot of heat - I know this from experience designing devices, although everything else is guesswork. Whether it was always intended to be incompatible,or they had to put the hacky handshake in late in the process to prevent the device being 'a bit fiery' I don't know.

opencl 8y ago

What Google is doing here is specifically rejecting the chargers that do conform to the standard by tacking on a proprietary handshake. HP had a similar charging DRM scheme on their first few models with USB-C charging but seems to have dropped it. Apple has been doing this with non-MFi chargers since iOS 7. A lot of people were mad when the OS update made their perfectly good chargers stop working. Of course now there are clones of the MFi authentication chip and even with a new chip revision Apple can't reject them without also breaking all of the old legitimate chargers. So it completely failed to actually solve the problem anyway.

djrogers 8y ago
This is bunk - I use a TON aid non-MFI chargers, and without exception they work as long as I have a decent cable. Old, dodgy or worn out cables can cause an error message but it’s got nothing to do with an MFI chip in the charger.
- opencl 8y ago
  Ah yes sorry, I meant to say cable rather than charger.