I got this power bank for my 7840u, have had no issues with multiple charges:
Model: UGREEN 100W 20000mAh
Link: https://www.amazon.com/dp/B0C3GTMX5M
At 72Wh it has more capacity than the internal battery, original or upgraded.
2 Likes
HI @Kieran_Levin , could you comment on if theres any update on this?
Many users including myself currently don’t have any way of reliabilty charging their laptop. I feel this should be a P1/S1 bug but its been over 2 months since we’ve had an update. Charging is an essential function for a laptop so not being able to charge makes the laptop difficult to use. I can only seem to get it charging while the laptop is turned off and kept off which makes long continuous work sessions impossible.
Thank you
9 Likes
Bot my 65W baseus and the no name 45W chinesium one work fine right now.
So, just to start off, I am using Windows on an AMD Framework 13, and I have seen the exhortations to not make a “me too” reply but since I am also having problems with Framework’s very own charger, I thought I would chime in. I have experienced issues with USB-C charging, particularly with various Anker and UGreen chargers. I, of course, found this pretty vexing, as the main reason I purchased those chargers was so I wouldn’t have to carry around multiples when I traveled. No matter - I can deal with carrying around the Framework Charger for a while. Surely, that will have been validated to work with the Framework laptop… right? Right?
Well, I dug the old Framework charger out of mothballs. I plug it in, the charging lamp briefly flashes, goes out, and then (most of the time, but not all) finally illuminates and stays on. If I’m unlucky, it stays off and my laptop doesn’t charge. Other times, it works immediately. There’s simply no telling what it will decide.
So, I guess what I aim to find out is this - is the official framework charger known to be problematic? Because I am at the point of suspecting every USB-C charger I own of being incompatible. Either that or I have a defective / damaged board that is on its way to having no reliable way to charge. At this point I could be convinced either way. It seems wild to me - absolutely wild - that Framework’s official charger that they ship with the laptop would have problems, but I’m not even the only one with the problem in this thread.
The only way I can reliably charge my laptop is by connecting to a CalDigit dock via thunderbolt. That has always worked immediately and without issue (though now I feel like I should go back and check).
Some chargers that have worked fine for me (AMD, Win 11, BIOS 3.03) are
- Framework’s supplied charger
- Anker Prime 100W GaN Wall Charger
- Anker 737 Charger (GaNPrime 120W)
- Anker 525 Charging Station
- Anker Prime 12,000mAh Power Bank (130W)
An important note for all of the multi-port systems above. The Framework laptop will not trickle charge below a certain spec. This is is really noticeable on the 525 Charging station plugging in another USB-C PD device will rebalance and prevent the Framework from charging.
I do not recommend the Anker 737 in general, it pulls out of sockets (they included a freaking support suction cup system) and doesn’t work well with the SteamDeck.
If you are having issues with the official charger and other chargers, sounds like the common issues is the laptop. Contacting support would be my suggestion.
1 Like
No, definitely not. It looks like either your charger, or more likely the laptop has some issue. Please contact Support.
I don’t have the Framework charger, but I do have a 100W charger which should not have any issue.
My experience is that, if you use a charger which triggers the overload (ie. triggers the PD issue with the FW laptop), then the port becomes “unusable” for some time. I also use a Thunderbolt dock, which seems to have intermittent issues with the FW laptop because it only supplies 60W over PD.
Sometimes a hard reset (hold the power button for 15 secs) resets things (I think this re-initialises the EC).
Maybe try consistently using the Framework charger only for a while to see if things work out?
2 Likes
It’s now been over 2 months, and I still can’t use any of my chargers.
@framework, what is the plan for addressing this issue?
2 Likes
Have people been submitting support tickets for this issue? I know Framework employees read these forums at times, but they are community support forums. The best way to get Framework’s attention on this issue os to submit a support ticket.
It definitely sounds like something that warrants a support ticket. My AMD unit has no problems with any charger I’ve tried so far (Belkin 60W, Framework 60W, Lenovo 65W, 90W hub built into a monitor I have, Steam Deck 45W). I’m on 3.03 BIOS.
1 Like
Since @Kieran_Levin responded to this thread and said they will be working on a fix for the next bios release, I didn’t think it would be necessary to also submit a support ticket (given that the support was also very overloaded at that time, with up to a week of response time, so creating more tickets didn’t feel like it would be helping). But it’s been over 2 month now and we didn’t get any status update of progress or when we can expect a bios update where this gets fixed. So maybe we should create a support ticket now to ask for an update? 
5 Likes
Any news on this ? I’m not asking for a specific release date of the new BIOS fixing this issue, but I’d like to know if there has been any internal news ? On this issue ?
Is there any expectation we should have for the fix to land maybe in Q2, Q3, Q4 2024 ?
Almost impossible to fix an issue for which no ticket exists and for which no systematic troubleshooting has been done. “My charger doesn’t work” is probably assumed to be user error or damaged hardware before anything else.
- What model of FW is this occuring on?
- What operating system/BIOS?
- How to reproduce the issue?
- Which troubleshooting has been attempted to eliminate various causes of the observed issue?
Support will walk you through the process of documenting the issue so this information can be used to help produce a fix.
Vague comments on a message board are not actionable for support purposes, unfortunately. 
Have you read the initial post of this thread? OP made very detailed analysis of what exactly goes wrong and why some chargers are not working. So this is far from “no systematic troubleshooting has been done” and it’s not just “My charger doesn’t work” and it’s very clear it’s not just “user error”.
Also, in the second post, somebody from the framework team acknowledged the issue and said they are going to working on a fix. So I’d assume they created an internal ticket without everybody from us needing to create their own ticket which then gets closed as duplicate.
If they need more info from us, or if they want us to create tickets for everybody who has this issue, they could have stated that in the second post instead of telling us they are going to work on a solution.
So I disagree that it’s “Almost impossible to fix” if they have a very detailed analysis and how to reproduce the issue and told us they are going to work on a fix. The only problem is, it’s been over 2 month without any visible progress or other feedback. So we don’t know if they are still working on it, or what’s happening.
7 Likes
The original post is about 3rd party charger compatibility and is systematically documented. The thread has since devolved into a catch-all for users who are apparently having issues using any charger, including the FW-supplied one, with their laptop. These two issues are not the same, and I respectfully submit that the FW employee is likely not even aware of the subsequent (and completely different) issues reported in the thread.
“My third-party chargers don’t work” is not the same as “My laptop doesn’t charge at all”… that is my point. The latter issue seems to me to be a borked laptop - the hardware is almost assuredly damaged (or the user is attempting to charge in an inappropriate port - see expansion card matrix).
1 Like
Yes, if the original charger doesn’t work, then it’s probably a different issue, and these people should create a ticket.
But most issues with 3rd party chargers are probably related to the issue described in the original post and I hope there will be a fix for that, and if people still have problems with some 3rd party chargers after that fix, they should probably also create a new ticket. But before this fix, it’s probably not worth it to debug every 3rd party charger when there is a known issue with them.
4 Likes
The Framework BIOS team is likely still working on the 12th gen 3.08 BIOS update, or at least they have until a few days ago. That update took more than a year and is still in BETA.
I think we have to be patient.
1 Like
It seems that way, yes.
I think it helps that people share other brands/modelnumbers of chargers that don’t work, so Framework knows which ones they can use to test their new firmware.
But it’s getting quite annoying.
We bought a laptop, and the product is advertised as being compatible with a range of chargers.
Now it turns out to be a major issue; which means the product is currently non-conformant. I.e. the product does not match the specifications it was sold as (or all of the reported chargers are bad).
Theoretically in the EU, we could return the laptop now for that reason.
I bring the charger from work now, every day.
Although I have 4 chargers in my home that, according to the specs, all should work.
Very annoying, but fine as I want to support Framework and cut them some slack.
But we don’t get any update, and no sign of them really taking this seriously.
I will create a ticket anyway, maybe it’s a good idea.
1 Like
Framework 13 AMD 7640U refuses to charge with various cables. Im running Fedora 39. My main charging brick is a minix 66W charger. I use it to charge my phone, which can charge in ‘super charging mode’. Heres a link to the charger:
these are the cables im using:
https://www.amazon.com/dp/B08J2HXYPH?psc=1&ref=ppx_yo2ov_dt_b_product_details
I’ve also tried some generic usb-c to usb-c charger cable that I primarily use for my phone and that doesnt work either.
I’ve tried my partners Huawei usb-c charger and that DOES work, which I find strange.
I find a dmesg error when I plug in a cable that wont charge. The message repeats at regular intervals while the cable is plugged in. Heres an example output from dmesg:
[60520.959808] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[60522.954660] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[60524.944807] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[60526.935804] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[60528.928432] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[60529.405632] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
the same message gets put in the journal as well:
Jan 22 10:20:03 <hostname> kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Interestingly, I just noticed as of writing that the error message of the power state is repeating with my usb-c dongle attached, which only has an ethernet cable attached to it.
I appreciate any help.
Updated Troubleshooting:
I plugged in my office mates Apple charger, but with my INIU cable and it charges as expected, however I still get the following dmesg errors:
[61412.088236] ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-5)
[61412.189972] ucsi_acpi USBC000:00: unknown error 0
[61412.189982] ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-5)
[61413.333646] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61415.328126] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61417.324504] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61418.336028] ucsi_acpi USBC000:00: unknown error 0
[61418.336033] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
[61419.317194] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61421.310719] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61423.301767] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61423.971033] ucsi_acpi USBC000:00: unknown error 0
[61423.971037] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
[61425.292466] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61427.294642] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61429.284164] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61429.483225] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[61431.269084] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[61433.252729] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
even though its charging. I unplugged my USB-C dongle with my ethernet cable to make sure it wasn’t that, and the error still persists at regular intervals.
Hi @shane_bell , welcome to the community.
Might be best to stick with charger that came with framework, as we don’t usually test other chargers from other brands.
Hi @Loell_Framework, thank you for your response.
I bought the DIY version without the optional charger since I have the 65W MINIX adapter, in accordance with Frameworks recommendation. I’ve noticed this is an ongoing issue, so I will keep myself updated on the community support page. Nonetheless, its a bummer my adapter that works with all my other devices (Samsung phone, steam deck, etc.) doesnt work with my Framework .