Anker power adaptor is incompatible with Framework 13

I‘m running Fedora 42 (latest updates as of May 15th 2025) on the latest Framework 13 (AMD Ryzen AI 300) and I‘m experiencing charging issues with an Anker 737 120W USB-PD adaptor.

I‘ve read several threads on what I think is the issue: apparently, the laptop does not go into sink-mode. When I connect to the adaptor using USB-C, the laptop doesn‘t charge. Looking at the power_role, it says source [sink]. So it is capable of receiving power, but it seems to choose not to. I tried overwriting that value, but it won’t let me (Input/output error). Usually, people seem to have this problem with power banks, which makes a lot more sense to me. For a simple adaptor though, I didn’t expect a problem like this.

I‘ve tried power adaptors from Anker that do not have PD and those work fine. Since Anker is a popular brand, I hope this can be fixed. It seems like there is not much I can do about this, but if anyone has any suggestions, I can give it a try or provide further information for debugging.

Any help is appreciated!

Till

1 Like

There are electronics in the cable - try a different one. Look for cables that say they are PD 3.0 or 3.1 certified - that should help.

1 Like

Framework can be powered by an adapter without PD?

No, I was mistaken about that. USB is such a confusing standard and the devices are usually badly labelled :sweat_smile: Maybe the difference lies between PD 3.0 (> 100 W) and PD 3.1 (> 240 W). Or maybe it is something else or a coincidence.

not really … on a lot of Type-C phones you can set the role via the .. ??
Developer options. But the phone is completely different compared to a laptop.

Framework laptop cannot be powered by a adapter that don’t have PD. He probably meant EPR (extended power range).

Which might make sense

I’m in china, so this is a chinese review of the 120. Says it support not the EPR (because it is capped at 20V 5A), but support FCP, SCP, AFC, QC3.0, QC4+, PD3.0 and PPS.

I dont fully understand how/why your thing doesn’t charge from one of those; maybe contact Anker support?
Also try charging other things via the type-c ports on the charger (use C to C cable).

What the cable are you using? Sometimes Anker supplies “140W” cable with their power banks or power adapters that actually has 180W when reading the e-marker information. This might confuse the laptop. Try using a “generic” cable so the laptop should draw 60W normally

1 Like

My guess is that this problem is caused by both the laptop and the 737 being dual mode devices, and the laptop chooses to try and charge the 737, instead of the other way around.
The laptop EC firmware probably needs some changes, to let the user switch the direction of charge when they wish.

Thanks everyone for being incredibly helpful!

I‘ve looked up the cable and it‘s rated for 100 W, so i assume it should work. It is able to charge my phone and a MacBook, only the Framework has issues. I will try and find a PD 3.1 cable and see if there is any difference.

Also, sorry for the confusion about other adapters, I didn’t realise that USB without PD can only deliver up to 15 W and there are different versions of PD. Now I know :sweat_smile:

@James3 It looks like that to me, too. However, why would a simple charger (not a power bank) introduce itself as a dual mode device? :thinking:

1 Like

I misread your original post. I thought it was a Anker 737 Power Bank instead of the Anker 737 Charger.
A charger should not be a dual mode thing.
The Framework laptop prefers Chargers that are EPR capable but should charge from SPR devices OK.

Not really. The 13 AFAIK runs on SPR. Does it pull 100W on a big power supply? I don’t have one of those USB PD snooper to test.

What the FW13 does with 60W vs 100W PSU is explained quite well here (Both SPR chargers):

In summary, a FW13 has been seen to draw power peaks of 88W, this causes the laptop to top up from the battery during these peaks.
If you use a 100W charger with the FW13, it will dip into the battery less during these peaks.
Also, the FW13 will only ever draw 52W from a 60W charger, and 88W from a 100W charger.
I don’t know why it sets those level limits.

1 Like

Thank you for your help! I’ve been unable to get to the bottom of this. However, I was able to try a few things. I bought a new cable, one that is specifically rated to be USB PD 3.1 compatible and is rated to deliver the maximum wattage. Unfortunately, this did not have any effect, the laptop is still not charging with the Anker 737 charger. I’ve also tried two other Anker chargers: Anker 232 (33 W) and Anker PowerPort III (65 W, PPS). Both are charging the laptop.

It might be that they are using some elements of the circuitry from the 737 power bank, and just didnt configure it. Definitely contact Anker as well.

I’m having exactly the same problem with the same devices - an Anker 737 120W wall charger, and a Framework 13. The charger works with every other device I tested it with, including multiple laptops and phones. The issue is specific to the laptop. I tried multiple cables.

The charging LED on the laptop turns on for a split second upon plugging, then turns off. When connect through a power sensing cable, the cable display stays on, indicates PD mode, but reads 0W throughout.

1 Like

What chipset are you using?

I have a Ryzen HX 370. I’m also running Fedora and latest BIOS 3.03.

1 Like

I can confirm that I cannot charge on the 737 or the 747 (150W) Anker chargers but I can charge on a 515 (65W), a powercore+ 26800 battery bank (45W), and a Anker Prime 27650 power bank (250W)

I seem to have the same problem. I used a proper usbc-pd cable and the laptop won’t take charge from my 735 charger (A2668).

Anker A2343 charger with Anker A80E6 cable is working for me on Framework 13 300 series.

Anker A2669 (Anker Prime 67W GaN Wall Charger) with a variety of USB-C cables works ok in ports 1, 2, 3 in my pre-built 370. It keeps to the set 80% charge limit when the charger is plugged in while the laptop is on. Sometimes when the charger is plugged in when the laptop is off it exceeds the charging limit. I’ll try port 4 later today.