What about high power? My adapter is 165W and it’s having basically the same issue. The only way I can get it to work is by plugging in my ohone to another port first and even then its very incosistent and takes several agtamots to begin charging.
I’m using a Satechi 165W charger (https://satechi.net/products/165w-usb-c-4-port-pd-gan-charger)
Some higher powered adapters also get offended by what the current firmware does so there is a solid chance the update’ll fix that once it’s out.
If not it’ll at least be easier to tell what else is wrong after the biggest issue is fixed.
Hi Kieran, awesome thanks for the updates. Really appreciate it! Any estimation for when the next BIOS update will come out?
How exactly do you use it?
Which devices are connected to which ports of the charger?
I see on the site that depending on how many devices you connected, power to the ports is limited:
1 x USB-C PD connected - up to 100W
2 x USB-C PD connected - up to 100W/60W
3 x USB-C PD connected - 60W/60W/45W or 100W/30W/30W
4 x USB-C PD connected - 60W/45W/30W/30W
I assume you connect the FW to port 1 for at least 60W charging speed. Nonetheless, this is a more advanced device, with different protocols, also depending on what is connected. (Which I also suspect is why it sometimes works after you (dis)connect your phone: the protocols are updated.)
I try plugging it into every port till it works. Usually I end up on one with the phone on 2- but it’s really trial and error- plug in the phone to 2, then keep plugging and unplugging the laptop or even leaving it all plugged in and turning off power to the adapter. It sometimes just works immediately sometimes doesn’t, but the phone needs to be plugged in first. After that it doesn’t matter if I unplug the phone so long as the laptop stays connected it’ll continue charging at full speed.
Without understanding too much I assume it’s some issue with the handshake at the start and the phone is somehow able to disrupt that and get it to lock in the proper wattage.
There is now a Beta upgrade:
From my limited testing, everything seems to work just fine after the upgrade and the laptop charges without issues with a 30W charger.
Charging with a “dumb” 5V charger via A-to-C still doesn’t work, however that is not a very useful use case to begin with, so that’s fine.
Nice, will definitely test it too once I am home
Does it still work with kickstarting? I would still very much like this to work.
Still does as it did before
30 W and even less capable USB-C Power supplies (ie. the 15 W iPhone/iPad charger or the 5V 1A USB-C port of my Dock) do work for me with 3.03b too.
All tested A-to-C supplies still does not work, even though they are capable of at least 1A (or more) as well. Kickstarting the charge with a different power supply does work, which might indicate that it is possible to solve this issue via firmware updates as well. However, this doesn’t have anywhere near as high priority as the current-during-voltage-ramp issue fixed with 3.03b.
Agreed on both points.
I do hope the 18/22W pd implementations used in a lot of small powerbanks works, gonna test that eventually.
Did some quick tests with Bios 3.03b Beta:
Hoco N3 18W charger (5V 3A, 9V 2A, 12V 1,5A (QC 3.0, no PD))
Charges for about one second
Ultron Powerbank RealPower PB-20000PD+ (18W, 5V 3A, 9V 2A, 12V 1,5A)
USB-A-Port (without PD): Charges for about one second
USB Type C Port (PD): Powerbank gets charged by Framework Laptop
So I will have to get a charger to charge my Laptop when I’m on the go. I currently only charge at the docking station.
Dumb charger doesn’t work, the computer only supports PD. After the BIOS update I got 4.85V2.94A(5V3APD), 14.87V1.34A(15V1.5APD), 12.04V1.52A(12V1.6APD), 19.8V1.38A(can’t tell protocol as 100WPD charging 3 devices simultaneously). Now it supports both low voltage and current(below 3A). The only exception is when using a 100W PD the FW13 only pulls 2.73A even when the battery is low and/or during heavy gaming.
I can confirm the Bios 3.03b Beta fixes charging with the Raspberry Pi 27W USB-C charger (don’t have access to the other charger rn but it generally worked, just occasionally would not).
This bios also dramatically improves charging during a PD re-negotiation (like what happens on plugging in another device into a multi-port usb-c charger). Previously it would take ~10 seconds for the framework to start charging again after I plugged in another device to the charger. Now the framework never changes its charging status from charging (ie: the re-negotiation is so fast that the status indicator does not change, just like my other devices).
Posted on the other thread, but for the sake of keeping the discussion here:
My charger STILL doesn’t work on this update.
https://satechi.net/products/165w-usb-c-4-port-pd-gan-charger
I have to plug my phone in to the second port, then unplug it to trigger the charger to actually work on my laptop otherwise the charging indicator just goes on and off and it doesn’t seem to charge.
I bought a USB PD GaN charger which is supposed to be the spec and I’ve had to do hacky work arounds for 3 months with no feedback until a beta bios update that doesn’t even address the issue.
Like guys- I love this laptop, but this and the random blue screens are a joke. At least tell us what’s happening- we’ve had nothing but silence until this update which hasn’t even resolved the issue. Clearly something is wrong with power negotiation because once I do this workaround I can leave the laptop plugged in by itself for as long as I want but if I unplug the laptop I need to do it over again.
Sounds like there might just as well be something wrong with the charger. After the update (which seems to make the Framework behave spec-compliant as far as I can tell), I wouldn’t blame the laptop without any proper fault analysis.
Be aware that other devices working on a charger doesn’t mean the charger is spec-compliant, it might just be spec-incompliant in a way that doesn’t break with some devices.
For example, when the current draw of the charged device increases suddenly instead of gradually (which is totally fine by the spec) the charger’s output might become unstable / shut off if it is not designed properly.
Also, taking a look at the charger (Satechi 165W 4-Port GaN) on Amazon, there are several reviews talking about the charger not being able to charge their laptop.
At least two reviews (one in german, one in french) talk about similar problems to you (charging laptop doesn’t work except when a phone is plugged in as well).
Other reviews also talk about only being able to charge when plugging in things in a specific order, etc.
I think the odds of all those people also having a Framework Laptop aren’t too great, so I’m pretty certain there’s just an issue with that specific charger model.
The recent bios update failed to fix the issue of this not charging. It in theory should be able to provide ample power, but when I plug it in, the laptop pings because I plugged something in, then a few tenths of seconds later, it pings like I unplugged something, then repeats this every second or so.
This doesnt happen with my partners Huawei charger which I’ve been having to use while this gets sorted out.
I’ve tried different ports and even removing the adapters and plugging directly into the usb-c port embedded in the laptop, but to no avail. 
Can anyone recommend a charger on Amazon they have that works and I can replace this charger with? One than can charge the laptop plus a phone or something?
I have an Anker 100W USB C Charger Block(GaN II), 3 Port Fast Compact Wall Charger and it works well without needing to do any plugging dance.
https://www.amazon.com/dp/B09Q52CXX1?th=1
It works well with my Nintendo Switch dock, Pixel 7, and Raspberry Pi5 as well.
To be honest I have never heard of the Satechi company that your charger comes from until you posted about it. As already mentioned, the only real way to check for blame as to why that charger isn’t working is to use a USB-C PD analyzer like the OP did and inspect to see if the charger is failing when the framework is attempting to operate within the USB-C PD specifications.
that is simply misinformation and untrue. USB-C PD sinks have mandatory transient load behavior per the spec, see iLoadStepRate and iOvershoot. It is mandatory that USB-C PD sources handle “25% load step increments from minimum load to maximum load and also from maximum load to minimum load” at the iLoadStepRate (see Output Voltage Tolerance and Range).