Slashdot Mirror
Why the Google Pixel 3 Charges Faster On a Pixel Stand Than Other Wireless Chargers (arstechnica.com)
An anonymous reader quotes a report from Ars Technica: Google's Pixel 3 smartphone is shipping out to the masses, and people hoping to take advantage of the new Qi wireless charging capabilities have run into a big surprise. For some unexplained reason, Google is locking out third-party Qi chargers from reaching the highest charging speeds on the Pixel 3. Third-party chargers are capped to a pokey 5W charging speed. If you want 10 watts of wireless charging, Google hopes you will invest in its outrageously priced Pixel Stand, which is $79.
Android Police reports that a reader purchased an Anker wireless charger for their Pixel 3, and, after noticing the slow charging speed, this person contacted the company. Anker confirmed that something screwy was going on with Google's charging support, saying "Pixel sets a limitation for third-party charging accessories and we are afraid that even our fast wireless charger can only provide 5W for these 2x devices." Normally we would chalk this up to some kind of bug, but apparently Google told Android Police that this was on purpose. The site doesn't have a direct quote, but it writes that, after reaching out to Google PR, it was "told that the Pixel 3 would charge at 10W on the Pixel Stand [and that] due to a 'secure handshake' being established that third-party chargers would indeed be limited to 5W." In an update, Google said the reason has to do with the "proprietary wireless charging technology" it has via its Pixel Stand and other select wireless chargers. The Pixel 3 only supports 5W Qi charging; "Google's 10W proprietary wireless charging technology" is what will allow the phone to charge at faster speeds.
"Google says it is 'certifying' chargers for the Pixel 3 via the 'Made for Google' program and pointed us to one such device, a Belkin charger called the 'Boost Up Wireless Charging Pad 10W for Pixel 3 and Pixel 3 XL,'" reports Ars Technica. "Belkin's description is very enlightening, saying 'Made with the Google Pixel 3 and Pixel 3 XL in mind, this wireless charging pad uses Google's 10W proprietary wireless charging technology. It's certified for Pixel, so you know that the BOOST UP Wireless Charging pad has been made specifically for your Pixel 3 and meets Google's high product standards.'"
Android Police reports that a reader purchased an Anker wireless charger for their Pixel 3, and, after noticing the slow charging speed, this person contacted the company. Anker confirmed that something screwy was going on with Google's charging support, saying "Pixel sets a limitation for third-party charging accessories and we are afraid that even our fast wireless charger can only provide 5W for these 2x devices." Normally we would chalk this up to some kind of bug, but apparently Google told Android Police that this was on purpose. The site doesn't have a direct quote, but it writes that, after reaching out to Google PR, it was "told that the Pixel 3 would charge at 10W on the Pixel Stand [and that] due to a 'secure handshake' being established that third-party chargers would indeed be limited to 5W." In an update, Google said the reason has to do with the "proprietary wireless charging technology" it has via its Pixel Stand and other select wireless chargers. The Pixel 3 only supports 5W Qi charging; "Google's 10W proprietary wireless charging technology" is what will allow the phone to charge at faster speeds.
"Google says it is 'certifying' chargers for the Pixel 3 via the 'Made for Google' program and pointed us to one such device, a Belkin charger called the 'Boost Up Wireless Charging Pad 10W for Pixel 3 and Pixel 3 XL,'" reports Ars Technica. "Belkin's description is very enlightening, saying 'Made with the Google Pixel 3 and Pixel 3 XL in mind, this wireless charging pad uses Google's 10W proprietary wireless charging technology. It's certified for Pixel, so you know that the BOOST UP Wireless Charging pad has been made specifically for your Pixel 3 and meets Google's high product standards.'"
...but our proprietary wireless charging solution is A-OK!
Seriously, why buy a Pixel?
Google want$ to provide quick charging only from companie$ that give them obei$ance.
Fuck they are all the same :(
I want to know why Google and everybody else can make a wireless charger that doesn't overheat except Apple.
When all you have is a hammer, every problem starts to look like a thumb.
Seriously, why buy a Pixel?
Only android device you will get regular updates from
I mean they glued wear items (ie. the battery) into the phone making it difficult to replace, so it was never really an option for me anyway.
Still, what a poor, customer-hostile decision. Hopefully the Pixel 3 fails in the marketplace.
A government is a body of people notably ungoverned - AC
It's here! APK Hosts File Engine 1.0++ 64-bit for MacOS h t t p : / / a p k . i t - m a t e . c o . u k / A P K H o s t s F i l e E n g i n e F o r M a c O S . z i p
Yields more security/speed/reliability/anonymity vs. any 1 solution (99% of threats use hostnames vs. IP address most firewalls use) more efficiently/FASTER + NATIVELY 4 less!
Vs. "Bolt on 'MoAr' illogic-logic" slowing you hosts speed u up 2 ways: Adblocks + Hardcode fav. sites u spend most time @ vs. competition loaded w/ security bugs (DNS/AntiVir) + overheads slowing u (messagepass 'souled-out' to advertisers easily detected & blocked addons + firewall filtering drivers) & their complexity leads to exploitation!
* ONLY 1 of its kind in GUI 4 MacOS!
(Better vs. Windows model in speed/efficiency)
APK
P.S.=> I am God's gift to Slashdot. I am NOT c6gunner. My work is world-class. China copied my work because they can't do better. Protects against Spectre & Meltdown + all other known & unknown threats... apk
Enjoy your "open" platform under Google's evil dictatorship.
“Buy our expensive shit or fuck you!”
AC comments get piped to
It's so they can charge you MORE for the faster charger. DUH I prefer slow charging anyway. Typically safer charges are when you slow charge. And it typically has less chemical impact on the battery life.
I'm not surprised they're limiting power draw to the official standards for unknown chargers.
They're what, 50% efficient?
So charging at 10W means 10W of heat in the charger. Sitting right next to the battery, that you can't charge when it gets over 45 degrees or you risk it catching fire.
I bought a Samsung Galaxy Nexus because of this.
I still regret it. A few MINOR versions later, 18 months later if my memory serves me well, Google declared it an obsolete model and no more updates were released.
Fuck Google. I'll never get a Google device again.
LineageOS will give you some extra years of support.
100% this. Google fought and bitched and moaned and campaigned and actively brainwashed users to think that USB Power Delivery (which is ALSO proprietary) is the only acceptable, safe, safe, good, etc. option. (This all despite the fact that their own products violate the spec, including some in unsafe ways.) Now they turn around and pull this shit?
Fuck you, Google.
To be fair, there's a pretty big difference here.
1) qualcomm's quick charge actually violated the USB spec. Their quick charge still used USB cables to provide power. micro-usb wasn't designed to handshake or negotiate the cable's capabilities to the charger and the phone. The usb cable standard did NOT allow for quickcharge power draw. That actually IS dangerous.
2) Google's 10w proprietary standard is negotiated, and there's no intermediate medium (unless you count the air molecules between the charger and the device, and I'm pretty sure there's no specification defining their behavior)
By no standard definition is usb-pd proprietary. It's no more proprietary than USB is (so if you consider USB proprietary, well fine, here's some more tin foil).
But why do 5W Qi and 10W proprietary when most other phones do 5W Qi and 10W Qi?
Qi already goes up to 15W (though I'd imagine there are thermal concerns), so why do we need a proprietary Google standard for 10W when everybody else is just using 10W Qi pads?
Looking over Qi chargers for the past few months, all of them seem to list max 7W with various iPhones, and I think 12W with a number of Android devices.
Aren't those all Qi? Apple is for sure, so why would the pixel have a max of 5W when the iPhone can do 7?
It stuff like this that has kept me from owning any "wireless" chargers. (I'll drop the scare quotes the day no actual wires are connected to the charger itself at any time).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
... so why do we need a proprietary Google standard for 10W when everybody else is just using 10W Qi pads?
Because some bright product manager is banking on their model of the market that predicts a higher overall profit to Google via original hardware sales and proprietary protocol licensing.
With the way the updates have been lately that isn't a good thing. With Android 9 Google broke Bluetooth, fast charging on the Pixel XL, wrecked battery life, accidentally changed battery settings for apps, and numerous other problems. Android 8 was constantly a battle of them breaking Bluetooth every other week. At this point I think half the reason the other manufacturer's hold back on the updates is because Google tends to release them haphazardly and break stuff.
I've begun to consider just giving up on modern technology.
The hardware, for the most part, is acceptable, or at least tolerable. The big corporations, "big data", etc., I loathe a lilbit more each day. With RepubliKKKans, corporate evil, incredibly ignorant people and a few other awfulnesses, I'm finally finding myself grateful to be old. Mortality looks pretty good too, I wouldn't pay a nickel to be immortal,and I pity the young people of today.
Millennials, your future looks awful, brutish and SHORT.
That is a good question but if you look at this:
https://www.wirelesspowerconso...
There are surprisingly few phones that are certified for > 5w Qi charging. I'm guessing there's gotta be a reason for that.
Google updated my Nexus 4 for two years then said fuck you. I said, never again Google hardware.
Sure, many vendors are even worse, but this is supposed to be Google demonstrating how to do it right. Very much unimpressed.
When all you have is a hammer, every problem starts to look like a thumb.
USB-PD is proprietary? Is that why I can use an Apple 87W USB charger from a MacBook to charge my Dell XPS 15?
Yeah, that sounds horribly proprietary, and is the worst kind of Vendor lock-in.
Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
Is it Google though? Sony at one point for some new version of Android wanted the Z3+ to be a reference phone. However, Qualcomm did not release chipset drivers for the 801 (I think) for that release of Android, so it was declared unsupported and not updated, despite Sony's wishes at the time. Google could not have controlled that either.
Only android device you will get regular updates from
Do you mean "in perpetuity"? Because I get a security patch every month on my Sony.
are of higher quality
strikes me as odd the handshake hasn't been REed yet
Looking for people to chat about multicopters, coding, music. skype: gtsiros
That list may not be complete (or there are just lots of phones out there that support 10 watt charging without being certified). There are no Samsung phones on that list, and they're shipping 12w Qi chargers for their latest phones. Previous models used 9w Qi chargers.
I had the same experience and same conclusion.
For some unexplained reason, Google is locking out third-party Qi chargers
I'm sorry, is this Apple we're talking about here or Google? Or is Google finally catching up to Apple's standard operating procedure. In other words we're going to end up with Apple (Business practices) Classic and Apple (Business practices) from the Other Guy.
Same here. Also had the Nexus 4 which Google abandoned. So I abandoned them.
Same expectation and experience with the Nexus 5.
Slightly different conclusion though: Don't buy *expensive* Android phone models as they are likely to be throwaway devices security-wise in two years.
BTW, went Motorola. Happy. Much better value than Pixel.
When all you have is a hammer, every problem starts to look like a thumb.
with this "Made for Google" program, they are getting more and more like Microsoft of old
"The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
I bought a Motorola Backflip in Hong Kong back in 2010. Never buying a Motorola phone again. Two massive software bugs. The first was the SMS app popping up at random times and chewing up 20 to 40 percent CPU time in the background, causing the phone to get slow and hot. Using a 3rd party SMS app didn't matter. The second was a problem with the dialer. Press the call button and.... NOTHING happens. 60 seconds later, after you've already given up and went to another app, it starts connecting the call. Complete garbage that meet its end under my stomped foot. Oh, and the camera also sucked ass.
There are surprisingly few phones that are certified for > 5w Qi charging. I'm guessing there's gotta be a reason for that.
Probably a shitty database. I just looked up the two devices we have in the house that support high-speed Qi chargers just fine, and both of them are listed in that list only with the Basic Power Profile.
Or maybe certification isn't all that it's cracked up to be.
Microsoft? they're behaving fairly well actually. What you mean is that Google is become like Apple.
Only android device you will get regular updates from
That's simply not true.
Look into the android one project. OS updates for at least 2 years and security updates for at least 3 years. Vanilla android without all the bundled crap.
I have a Nokia 7 plus at half the price of a pixel and no complaints here. Maybe because it's not as popular, but I've seen far fewer issues online about it compared to the pixel range.
Having worked with wireless charging technology, I am not surprised. Despite a certain subset of consumers and manufacturers being in love with it, it's actually a pretty shitty way of delivering power. The limitations are mostly thermal. Sure: you can get do >5W charging, but all the other metal content of the phone is heating up, too, including the battery. Batteries charging while hot will have reduced lifespan or, at worse, a higher chance of catastrophic failure (read: fire).
The analogy I use is trying to fill a water bottle in the shower. It's really slow, much slower than sticking the same bottle under the tap, and you're going to get soaked in the process. You might be able to speed things along by holding the bottle closer to the spray, or using a funnel to capture more water, but you're still getting wet. Oh, and your water bill goes up, because most of it just goes down the drain.
About the same, bought the Nokia 6.1 months ago, it is ~$229 or something, part of Android ONE so stock OS, came with 8.1, Pie is rolling out this quarter and I will have, like you said, OS updates for 2 years and security update for 3 years on a vanilla OS. Never again the dozens of Samsung apps that you cannot even disable!!!
It is also rock solid, made from a one piece of aluminum, it cannot bend.
It has a 5.5" FHD screen, 5GHz WiFi, dual sim, micro SD, NFC, USB-C QC3.0 charging, audio jack, Zeiss camera, fingerprint sensor, what do you need more? for the price and my need it only has a SD6xx while the 7+ has a SD7xx, but it is still pretty fast, way faster than all the SD4xx available on the market for the same price.
"Science will win because it works." - Stephen Hawking
Its really that simple. Google is copying apple.
DIsclaimer: I know (and care) very little about wireless charging, so I'm not very well informed on the subject.
That said, I've been doing some reading about this, and from what I understand, the standard itself doesn't actually specify quick charging, so manufacturers have been left to invent their own method. Samsung created their method and lots of chargers were made to support it. Google also created their own. It sucks that they aren't compatible, but this is how almost every standard begin: lots of incompatible proprietary methods, and eventually one of them wins out and becomes the standard for all devices (except for apple devices).
Except they didn't, you are still getting security updates and updates to Google service apps to this day.
It's also worth noting that this was a $299 phone with decent hardware in 2012, which was rare. Considering you paid 1/3rd the price of an iPhone/Galaxy S you could afford to upgrade it twice (so total of 6 years of primary OS update support, plus hardware upgrades) compared to the competition.
You have a choice, either get OS updates for 5+ years but they make your phone slow and unusable, or stop after a couple of years but remain protected, or buy a cheaper phone every few years, or install a custom ROM...
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Isn't that why Barsteward compared it to "Microsoft of old"
Apple has always been big into proprietary Apple only (for the last 40 years). This is why Apple even though it is the world biggest company, doesn't have much corporate/business presence, for the large part because of Apple proprietary nature Apples standards and protocols rarely make it to the general use.
Compare to Microsoft 20 years ago. The browser war was full on, with the attempt to take control of the internet. and the Embrace, Extend, Extinguish approach. Microsoft wasn't making incompatible tools, that only worked with Microsoft. They made tools that worked with the standards, then they added Microsoft only features to them, in hope where their feature will over power the original use. For the browser war of the late 1990's Microsoft won, luckily they had failed their final objectives. What Microsoft really wanted with the browser war was.
1. Become the dominate browser [Embrace] (they got this)
2. Have web developers make sure IE was compatible first (they got this)
3. Add IE only features [Extend] such as Active X (they got this)
4. Have Active X become the primary way to access a website (This was limited to business apps)
5. Drop HTML and HTTP [Extinguish] and fully make Active X technology the dominate way of using the internet (this failed)
What happened with this plan? Well primarily Microsoft didn't account for security and for the individual when asked a question they will answer "Yes" Thus turning Active X the primary deployment method of Malware. Causing some major security problems in 2002-2004 which people actually decided to either switch to Firefox (Which at the time was the small, light, and fast browser) that supported internet standards better then IE did, or actually got Sick of PC's and moved to Mac's which used the Safari browser (Webkit based). This but a dent in Active X development, and more focus on DHTML. That and Microsoft got so delayed in making the next version of Windows and IE. That XP and IE 6 became outdated.
Apple isn't a saint, but you more or less know what you are going to expect with Apple. Microsoft of old was much more sneaky and underhanded.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Well, I'm eating my own words.
I always though wireless charging can't be as efficient as wired. Obviously, right?
https://www.wirelesspowerconsortium.com/blog/80/is-wired-charging-more-efficient
Apparently I was wrong but take this wit ha grain of biased salt .... look at the URL name. But wireless can be more efficient than wired? wow!
... Afraid to compete because they are unable to compete without a self-granted advantage.
Exactly! And they've seen Apple make even music playing require a per-device-supported royalty payment and get away with it.
But are they actually doing 10W Qi? My understanding is that they AREN'T using a 10W standard, but a 10W proprietary model. I'm not very familiar with this topic, but I'm looking up some 10W Anker chargers on amazon, and they seem to indicate that they have a 10 watt "Samsung" mode and a 5 watt "Standard mode".
I'm a consumer in love with it, and I understand it's never going to be as fast as wired. I don't use it exclusively, but it's really convenient in cases where I just don't need that kind of speed.
For example, in the car, I have both a 2A wired charger and a 500mA inductive. If my battery is in reasonable shape, I just pop the phone in the inductive charger/holder thingy and off I go. It's easily enough to run Waze and stream bluetooth music without draining the battery at all, and if I really need 2A (or it's going to be a long trip) I can always just plug it in.
Second example, overnight, I have an inductive charger in a little divot on the nightstand. Even from ~0%, 500mA over a night's sleep is enough to wake up at 100%.
Finally, your claim about the power bill going up is absolutely absurd because devices are basically zero fraction of anyone's electricity bill. The average consumption is 900 KWH/month. A phone is ~3000mAH. Even if you charged a phone once a day on an inductive charger at 10% efficiency, that would be (rounding up) ~1KWH = (3000mAH * 10x loss * 30 days/month) or ~0.1% of your total bill. You'd be paying like $0.20/month to charge the phone, of which 18Â was wasted.
Modern inductive chargers don't have excellent efficiency by the way, but they're better than 10% :-)
See subject: c6gunner's name on this post as submitter yet signed "APK" https://linux.slashdot.org/com... & he ran from a fair challenge I put to him https://linux.slashdot.org/com... after insulting me.
* I never say hosts cure Spectre/Meltdown OR it'd be on the Start64.com download page & I do NO MacOS X one!
I cut him to pieces for his lies:
https://tech.slashdot.org/comm...
https://tech.slashdot.org/comm...
https://tech.slashdot.org/comm...
https://news.slashdot.org/comm...
APK
P.S.=> You say hosts = shit https://slashdot.org/comments.... ? /.ers & security pros + RESULTS say DIFFERENT:
1st: /.ers https://slashdot.org/comments.... https://slashdot.org/comments.... https://slashdot.org/comments.... https://slashdot.org/comments.... https://slashdot.org/comments.... https://slashdot.org/comments....
2nd: SECURITY PROS https://slashdot.org/comments....
3rd: REAL RESULTS w/ hosts vs. threats https://slashdot.org/comments....
EAT YOUR WORDS
They tried wireless charging a few phone generations ago. I bought the $50 charger. It worked like shit and charged slow. Next generation, Google doesn't support it.
Fuck proprietary bullshit and fuck you, Google.
I'm a good cook. I'm a fantastic eater. - Steven Brust
I was seriously considering getting a Pixel 3. This decision made that real easy. If Google wants to start down the proprietary road they will do it without me.
WTF?
Do be careful: 3000 mAh is not a measure of total energy; it is a measure of electric charge (coulombs, if you want to get technical about it). To convert to energy, multiply by the nominal voltage of the battery you are talking about: 3.7 V for a typical Li-Ion. By that measure, the battery's energy capacity is about 11 Wh. Charging every day for a month at 10% outlet-to-battery efficiency yields 3.3 kWh.
I'll grant you that's still small compared to a typical household's total usage. (Your 900 kWh figure is the average for a U.S. household. But that's not the median, nor is it typical for Japan or the EU, which are substantially lower.) It still strikes me as a lot for the "convenience" of not having to plus in a USB cable. It's the equivalent of leaving a microwave running for about 3 hours.
I haven't looked at it recently, but my previous experience with inductive charging mats is that they had substantially higher quiescent draw than just an AC/DC converter. It'd be on the order of 5-10 W draw from the outlet, 24/7. At a typical residential electric rate of $.15/kWh, that'll cost you about $6-13/yr. A decent USB charger brick might be on the order of 0.5 W. Yes, you can cut that quiescent draw to zero by unplugging the mat, but that kind of defeats the purpose, no? (At least with the example of your car, I expect the mat is only powered when the car is on.)
Actually, the quiescent draw ends up being about the same monthly energy consumption as the actual energy for charging the battery. So perhaps I should have clarified: your water bill would go up, not just because most of the spray goes down the drain, but because the showerhead leaks all the rest of the time.
"Apple has always been big into proprietary Apple only (for the last 40 years). "
Why I've been boycotting things Apple for 40 years. Never have bought anything Apple. Won't.
I know you're frustrated with it, but you did know that they're essentially a completely different company now than they were in 2010 right? They've since been bought and sold by Google. After their ownership by Google their quality shot way up.
Motorola screwed me on Android updates, promising them then never delivering. I said, never again Motorola, and I meant it. They've also been acquired then divested by Google.
I don't get your point.
Apple may be less evil then old Microsoft. But that doesn't mean Apple isn't evil.
Besides "Boycotting" Apple because Apple isn't giving you the services you wan't or need, isn't boycotting them. Boycotting is putting yourself in a disadvantage to bring up a point.
I don't like squash, so I don't buy it. I am not boycotting squash, I just don't like it.
Now I like bacon, but say there is something that I feel strongly against in the Bacon Industry I would stop eating bacon, until they fixed it. Then I would happily begin eating it again.
You don't like Apple products, so you never bought them. if Apple changes its business practices you still will not buy from them... You are not boycotting, you just not a customer.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Google updated my Nexus 4 for two years then said fuck you.
Maintenance is boring, dude.
(Google's new corporate motto, I think).
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
I removed the Qi wireless doodad and the NFC antenna from my Sony Z3V in favor of adding a small heatsink where they used to be. No regrets.
Honest question? Who is better? I've had major issues with Samsung, hated the iPhone, had an older Google device that eventually went unsupported and now grabbed a Pixel 3. You're damned if you do, and damned if you don't. We need meaningful regulation in this space desperately.
My Pixel 3 "rapidly" charges when placed on the Anker 10W wireless charging pad. Is that not the most rapidliest?
You're switching to iPhone then right? I don't think there's an Android vendor better than Google on updates. Or if there is, I'd like to know about it.
That's possible (even if Qi itself does go up to 15), but if you've got products on the market like Anker's chargers that aren't necessarily having to license things and still support both "Qi" 5W mode, and "Samsung" 10W mode, and "Apple" 7.5W mode, that's still not as bad as Google actively blocking anybody who doesn't pay them money, no?
What model? My Moto g6 came with 8.0.0, I just checked and there is an update, downloading now. Only a few months out to be sure, but updates are definitely being provided. For how long remains to be determined. Happy camper so far and I love the phone. Way better value than the Pixel, as I meant to say above.
When all you have is a hammer, every problem starts to look like a thumb.
My Nexus 4 and Nexus 6p both got 2 major revisions of Android and security updates beyond that. Unfortunately Samsung and other manufacturers don't do this.
1) qualcomm's quick charge actually violated the USB spec.
It never claimed to BE part of the spec. It didn't violate it. It ignored it (or extended it since it didn't break any existing functionality).
Their quick charge still used USB cables to provide power. micro-usb wasn't designed to handshake or negotiate the cable's capabilities to the charger and the phone. The usb cable standard did NOT allow for quickcharge power draw. That actually IS dangerous.
Standard USB cables are fine. The extra power isn't gonna fry a cable - any cable crappy enough to get fried by a Quickcharge adapter that doesn't get a handshake would be fried by regular USB anyway. If handshaking fails, Quickcharge fails safe. If it succeeds, THEN Quickcharge comes into play. It's no more dangerous than anything the actual USB Implementers Forum has put out. It's dangerous only if you have shitty devices with no basic electrical engineering standards.
2) Google's 10w proprietary standard is negotiated, and there's no intermediate medium (unless you count the air molecules between the charger and the device, and I'm pretty sure there's no specification defining their behavior)
Quickcharge is negotiated. I think only 1.0 wasn't negotiated, but it had basic detection circuitry and also failed safe. If Quickcharge was dangerous I'd have jumped in on a bunch of class action suits to get several pittances. yet here we are.
By no standard definition is usb-pd proprietary.
ALL OF USB is proprietary. It is not open, it is not free, it is not extensible, it is not licensable, it is not sane, etc. It is WIDESPREAD and that's about it.
People try to claim things like Qualcomm's Quickchare is BAD because it's "proprietary", or because it "violates the standard".
USB is proprietary, locked down, expensive, etc. It's just widespread.
Quickcharge being proprietary is no worse then USB being proprietary. On technical merits alone, Qualcomm has been beating the shit out of the USB Implementers Forum when it comes to fast charging shit. They were already well established years before USB IF even tried anything, and Qualcomm keeps improving their offerings regularly.
Qualcomm isn't "violating the standard". When Quickcharge came about, it looked for COMPATIBLE devices, then gave them more juice. They EXTENDED the standard. Everything else worked just as before. Now that we have USB-PD, Quickcharge isn't in violation of it, it's a COMPETING standard.
Just checked with a Kill A Watt, the power draw when there are no devices handshaked is 1W.
Maybe yours were from before the handshake?