Anker power adaptor is incompatible with Framework 13

I got the exact same problem with my Ai 350 and Anker 737 charger.
Honestly i love this charger so this is very disappointing. My charger has always worked great with all my other devices. This and the bad wifi on linux really makes me consider returning the laptop.

I know, one good thing about framework is that i can just replace the wifi card with another one and i could also buy a charger but i would somehow expected better first impression for the price of 2100 euro.

I seem to be having the same issue with an Anker PowerPort 3 (A2144). HX 370, BIOS 3.03. Fedora 42 is installed, but the issue still occurs while the laptop is fully powered down.

With ports 1 and 2 (100W and 60W), the charging indicator on the laptop turns on for a split second, then turns off. A USB C power meter confirms the port is active and set to 20V, there’s just no current being sent.

With ports 3 and 4 (20W), the laptop does charge, albeit slowly.

I tried the same charger and cables with different devices, and they all work as expected. I also tested with an Anker 735, and it works as expected. The issue seems to be between the laptop and the PowerPort 3.

For anyone interested. I contacted both Anker and Framework support.

Anker basically told me “Sorry dude, you got that charger as a present and thus have no bill, nothing we can do about it” - which is sad, but understandable.

Framework is currently escalating the ticket, so lets see if something comes out of that.

2 Likes

Man we desperately need some more polished pd controller firmware.

i also have an anker 737 and a previous amd gen (7840u). The power adapter works just fine in this combination. It also worked without a battery plugged in, as that needed to be replaced. So the issue seems to be specific to the newer amd models.

Well there goes my hopes of maybe getting hand-me-down pd-controller fixes from the ai 300 models since they seem to use the same one.

According to the “schematics” they use the same pd controller and power mux chips but different redrivers so yeah there goes that.

I do hope those new redrivers are actually better than the ones on the 7x40u platform otherwise they just produced unnecessary product fragmentation.

Anker 547 and Framework 13 AMD Ryzen™ AI 300 running Fedora 42. Seeing the same problem. It will charge slowly if I plug it into one of the lower power phone ports, but the charging light blinks briefly and goes out when attached to the high power computer ports.

dmesg shows:
[398538.206428] ucsi_acpi USBC000:00: unknown error 256

When I plug it in to the computer ports now.

I ran into the same issue with my Anker 737 120W (Model A2148).

I got my hands on a USB-C PD tester and ran PD Analyser to see whats happening, and tried the following chargers:

  • Anker 737 120W
  • Macbook 96W
  • Samsung 45W

with both my AI 370 Framework laptop and my Macbook. The Anker charger + the framework was the only pairing that didn’t work.

Here are the PD logs with each of the Anker, Mac and Samsung chargers after they are connected to a framework laptop or macbook:

Framework laptop

Macbook

I’m no expert in the PD protocol, so please correct me if I am wrong. Both the framework and the macbook manage to negotiate 15V or 20V power with all chargers.

The framework attempts to “DR Swap” which means it wants to swap data roles, i.e. making the charger the USB host without changing the direction of power flow. The anker charger accepts, while mac and samsung chargers reject.

After the anker charger accepted becoming the host, the laptop sends a “VCONN SWAP”. My understanding is that VCONN is whats powering the chips inside the type C cable plugs and is different from VBUS which is what charges the laptop. The anker charger responds with “Not Supported” and then a “Soft Reset” message (I don’t know who sends this) appears, resetting the session and preventing any charging…

The same session reset thing seems to happen with the Macbook + anker, but it retries without doing DR and VCONN SWAP after the first failure.

I don’t know which device is more wrong here, but it seems weird to me that the anker charger accepts becoming the USB host. Whats the point of that?

Maybe someone more knowledgeable about USB Power Delivery can share some insights.

3 Likes

That “soft reset” should not be worrying. That seems to be just how communication with the cable’s eMarkers is initiated.
If you check the PDOs (in Source Cap) that is probably limited to 3A in the first one. And after they confirmed that the cable is good for 5A, the charger updates its Source Cap with >3A abilities. That part is all fine.

Its the Framework ever picking 15V, 1A on a charger that supports 20V that is weirder. And the FW not starting to draw power again after the PS RDY was received for its 20V request.

But the Macbook also only requests 20V, 0.75A at first, but later 4.7A. Is the charger advertising it weird? I think this may be a specific combination of this Anker power supply behaving weirdly and the FW not being as robust as it could be in handling the weirdness…

Because no problems with my Anker 140W charger (the one with the display, before they renamed them “prime”).

1 Like

Issue confirmed on
Framework Laptop 13 AI 7 350 (DIY), with Anker 737 120W (Model A2148).
same dmesg USBC000:00: unknown error 256

Tried two cables.
Same cables with powerbank works.
Different power-adapter with integrated cable also works.

Update -
Anker A2669 67W GaN does charge the laptop.
dmessg provides the same unkown error, but does charge.

same for me, any updates on this issue from Framework?

The new AI Models have several Issues,

  • keyboard backlite
  • battery charging threshold
  • anker powersupplie
1 Like

My anker 735 is not charging fw 13 HX 370 either.

I just got an email - New BIOS out - BIOS 3.04

I haven’t tested it yet, but it looks promising as it explicitly mentions amongst other things:

  • PD firmware updated to 0.0.E.
  • Fixed charging issue with Anker GaNPrime 65W adapter.

Now I am just hoping the different re-driver is similar enough that the 7040u platforms can also benefit from a new pd controller firmware XD

I have been working out this issue with the support team through e-mail for a couple of weeks. I have a bunch of Anker 747 chargers, which I use for all my devices. So having my new Framework 13 AI 300 laptop not charge with them was problematic. I’ve had to charge it through my Anker 737 Power Bank, which did work.

A few days ago they suggested I try the 3.04 beta BIOS to see if that would change the behaviour. I’m happy to report that this is the case. It seems that whatever they did with

Fixed charging issue with Anker GaNPrime 65W adapter.

fixed my issue as well. I’d imagine that this was not specific to any particular charger, rather the firmware not being robust enough to work with Anker’s less-than-ideal PD implementation.

I would suggest others try flashing it as well. You can find details for how to do that here: https://community.frame.work/t/framework-laptop-13-ryzen-ai-300-bios-3-04-release-beta/71934

1 Like

After flashing BIOS 3.04, the A2144 works as expected.

For what it’s worth, I also tried a few more adapters back on 3.03, and they all worked as expected:

  • Anker A1902 (Prime Charging Base)
  • Anker A2697 (140w Laptop Charger)
  • HP M52946-053 (110w Laptop Charger)

So I’m thinking this was an issue between the 3.03 firmware and one or two generations of Anker chargers.

1 Like

Confirmed. Thanks for all your time and energy to collab with the support team.
Update of the bios also worked flawless on Fedoro Plasma.

love being part of this open source platform. This would not be possible with my previous Dell or HP systems.

1 Like

Turns out I had a faulty product that overheated and the top port didn’t work when connected to the wall and after working with the Anker support on getting a replacement, my new Anker charger is working without issue on my FW13.

Add this to the list of Anker products that work with FW13:

  • Anker A2688 (100w Laptop Charger)

OOI which PD analyser hardware is this?

Looks like it is a Power-Z KM003C/KM002C.

1 Like