That is indeed weird.
Can you share some more details? Like charger make andmodel, which port is used and all that. Does windows show what the charger negotiated somewhere?
That is indeed weird.
Can you share some more details? Like charger make andmodel, which port is used and all that. Does windows show what the charger negotiated somewhere?
I have a USB-PD analyzer at home (and I am not there). When I get back, I will take a look with the analyzer and post back with my findings here.
Thanks for the recommendation. I picked up the Anker 737 and it charges the laptop, thankfully!
Thanks to the others for the recommendations as well
With the 3.03b update my steamdeck charger is now working again for the framework, thanks
I retested my chargers with 3.03b, changes are in bold:
Cute little 18W power bank module:
Any idea when this update might be availble for the Framework Laptop 16? I have a no-name 4s lithium battery 140W PD board that I’d like to be able to use but it cuts out constantly trying to start charging because of the sudden load step which it sees as over current. Once the laptop does manage to start charging it’s mostly stable although still prone to seeing load steps as overcurrent events and dropping into over current protect again.
Thanks for these tests! These three were the ones I was most curious about. Sadly it seems the AMD framework laptop is still worse at charging than my deceased 11th gen Intel framework laptop.
Just wanted to chime in and say the Minix Neo P1 does not work on version 3.03b
It’s just got a bit of a mental block with those, since it’s possible to kickstart it is perfectly capable hardware wise so this may get fixed just as the sub 45w pd stuff got fixed.
I have the same issue, I brought with me only the steam deck charger, and it doesn’t charge my framework 13 amd 7640.
Cruelly, I can’t update the firmware to fix the charge without a charger plugged in.
Can second that this is the case
Adding data here: My FW13 AMD doesn’t charge through Apple’s USB-C dongle (A2119). Tried it with both the MacBook Pro charger, and my own Anker charger, which both work fine when hooked straight up to my laptop. I’m using Firmware 0.0.3.3, and running Arch Linux with Kernel 6.8.9-arch1-2.
Definitely upgrade to firmware 0.3.5 to confirm whether the issue still persists after the known bug is fixed. (Framework laptops do have a history of spotty compatibility with usb-c docks, which is what that is … there are some other threads about that.)
Updated via fwupd
. Went very smoothly, but it did not seem to fix the issue with the Apple USB-C adapter. I noticed that the power consumption in the Energy app is <10W, but on charger directly it’s 30-45W. I will note that on all ThinkPads I’ve tried this adapter with, it works fine. I’ve also tried several different adapters, and the issue is consistent across all of them.
I can confirm my Rocoren 100W GaN does the exact same thing. It charges my office Dell perfectly fine and nothing like this happens again. The work laptop also pulls 60W max charge as FW AMD does. Def a USB PD negotiation problem.
@patagona
Which usb pd tester did you use?
I have a problem with the fw16 providing power to an usb device and was wanting a tool that would capture the cc1/cc2 messages. Do you know of any?
Some more data points on working/non-working chargers (on a Framework 13, AMD):
Is there any chance of getting an updated firmware or similar to address these issues, or are we just stuck?
I think I can contribute to this thread after my FW13 AMD basically discharged to 0 and “crashed”.
I was using a Lenovo USB-C charger for the past weeks and it worked just fine on my docking station.
Today I noticed the battery discharging but since the day was kinda busy, I thought it just might be a visual bug… At some point the FW just turned off mid-work and was irresponsive to any inputs, any plugs I tried etc. I tried two Lenovo USB-C chargers and the Anker PowerPort III (A2667) and none of them brought the charging light to life.
Then I remembered, that I still have an Anker 737 PowerCore (which can charge laptops + gives a display response)
The charger was switching between modes and then told me that the charging voltage was too low (probably the over-currency protection) and stopped…before it caught itself into a charging state.
Now obviously this can’t be a solution, only being able to charge my new FW13 with a powerbank. So I really hope this can be fixed soon.
My docking station also doesn’t work properly with “just” 60W so the official charger won’t be an option for me either
Anyway, thanks to all in here giving me the idea to try other charging solutions (I’m up to 5 chargers now with USB-C lol), I’ve already given up on a bricked new laptop for a few hours ^^
You could plug the official charger into a seperate port, the Framework automatically takes power from the highest power source available.
Before anyone cries foul on using two cables, we use to regularly need a seperate power cable not long ago.
Thank you
I just tried that (even before/while reading your answer) and it works!
I know that the protocol should be intelligent enough to figure it’s ways out but even though I’m fine for now (just the docking station alone worked just fine for the past 2 weeks) but since this is something that happened over time, I can see many people running into this issue being helpless till they find this thread (at best).
As OP mentioned in the beginning of the thread, these aren’t cheep-o-Aliexpress chargers but chargers that are very common/most-likely be used outside. And if I’d not be at home but on a business trip, I would suffer from a dead laptop till I can eventually find a charger that works (thus being usb-c).
I’ll probably buy the official charger just to be covered in an emergency, but it’s not the kind of behavior I’d expect ^^
Edit: @MJ1 I think the most annoying part about it is that back then, we had more I/O on our laptops. Now 2 (out of 2) USB-C slots are occupied for charging and the dock. Kinda thankful my yubikey is USB-A and not C. Would be painful xD