Can confirm that gGPU performance sucks if the 240w charger is plugged in and you try and game at anything less that ~90%
I am going to try and create a ticket for this and get it escalated beyond level 1 to report as a bug…
4 Likes
It looks like the same issue which was raised by Obasav in his earlier comment. He created github issue . There is comment from kiram9 (who works for framework) that he will investigate it try to fix in next release.
5 Likes
Thats much better than the traction I am getting in the support case.
1. May we know if you've followed this guide in installing the Windows 11? [Windows 11 installation on the Framework Laptop 16 DIY Edition](https://guides.frame.work/Guide/Windows+11+Installation+on+the+Framework+Laptop+16+DIY+Edition/305)
2. Check if the charger works stably with other USB-PD devices, if available.
3. If possible, test the laptop with a different 60W or greater USB-PD charger to confirm whether the issue is related to the Delta charger or the laptop.
4. Were you using a dock station, hub, third-party charger, or an eGPU before the issue started? If yes, kindly provide the specifications of the components used.
5. Disconnect any external devices (e.g., USB peripherals, external displays) while using the charger to rule out power conflicts.
6. Fully charge the battery to 100%, then let it drain to 0% under regular use. Recharge to 100% without interruption and see if this stabilizes performance.
7. Try to reproduce the issue with other ports.
These arent all terrible… But I stated when I created the issue that this looks to be a firmware issue… and needed to be sent to engineering. Then I get this…
#6 is the one that makes me mad… as this isn’t healthy for the battery.
A temporary workaround for it (at least from what I’ve seen in my experimenting) is to set the laptop to balanced mode. The dGPU performance will be more stable but may not be the same level you would normally get in performance mode.
1 Like
This is required for battery calibration. You’re right that with li-ions it produces more wear / stress, but doing it occasionally should not meaningfully impact battery health when normal usage wear is added in.
2 Likes
False for lithium batteries. Thats generally a myth from when ni-cad needed this:
https://saft.com/energizing-iot/lithium-ion-batteries-use-5-more-tips-longer-lifespan
Contrarily to some received ideas, Li-ion batteries don’t have a memory. They don’t need regular full discharge and charge cycles to prolong life. It’s actually the contrary: the smaller the discharge (low DoD), the longer the battery will last, the more cycles it will be able to do.
1 Like
It’s not about a charge memory like ni-cads had / have.
With Li-ions it’s done to calibrate / recalibrate charge level estimation. Li-ions have a rather flat voltage/charge percent relationship so it harder to gauge current charge level. And with the normal wear that goes on with use, the charge level estimation that the device believes can drift from what is reality. Doing a full zero to 100% cycle allows it to recalibrate it’s charge level estimation.
Whether or not charge level estimation could be an actual an problem here, with this 240w adapter issue, that’s another matter. But just customer service asking one to do a full zero to 100% cycle to recalibrate charge level estimation is not a problem or something to be mad about, in my opinion. It’s likely just a stanadard step they ask people to do when there are presented with some battery or charge issues.
3 Likes
I tried this last night. With the Fedora 41 change in how it handles power profiles, it actually did not help.
Actually, with the 180w adapter, I still lose battery in balanced mode now (where it used to maintain). This is seemingly related to how tuned handles the power profiles vs how PPD did.
Having the 240w adapted made the above a non-issue.
2 Likes
EDIT2: Bad news everyone. Turns out my quick testing (Furmark) is an outlier. Using both the 240w or the 180w adapter on Furmark it consistenly pulls 100w.
While normal gaming or 3DMark, the issue persists even on 3.05 for me as well.
It’s 100% a firmware issue, other USB-C chargers less powerful than 240w have the same problem.
Framework pls fix, we waited so long for the 240w… only for it to be sluggish in performance. Plenty of us here for you to ask logs to, we’re here to help! 
2 Likes
And my charge level estimation is not currently inaccurate. If it was - and I could confirm that the Framework didn’t just measure voltage to get the % - then I would consider it.
However, a full 100-0% discharge is bad for the battery - and not something I am willing to do for the above request. It shouldn’t be done as a request unless its something like “when I unplug my charger, it immediately drops to 75%” or something similar.
Limiting the amount of drain is the best for lithium batteries - with the ideal rate being from 40% - 80% if you really want to prolong life. Ideally, I would set my charge limit to 80% and just be happy - but the current issue with the 240w prevents that.
Im not “mad” at Framework for this issue - but rather just want to ensure they are looking at this from the firmware side - which seems to be what is being done in the bug filed by @Obasav - so it seems the right people are on this from the Framework side.
Had I thought to create a bug - I would have - I figured the best way to do that was through a support case. I was wrong 
If you could add your update to this bug?
I have to collect some data tonight and I will try and provide it as well - but it sounds like you have some solid data.
Adding this to the bug - but I drained my battery to test this out. Again, this does not happen at 100%… or even 90%
I start to notice it in the 80% range - and at 50% its really noticeable.
Here is a video of the issue happening.
Sorry, I had added to my post at about the same time you replied.
I agree that charge level estimation is not likely to be an actual issue in this case.
But it is a normal thing to ask, to me. And the impact of a single full zero to 100% cycle is low. A drop in the bucket. Also, considering how easy and quick Framework batteries are to replace if and when one get to that point, it’s not worth worrying about, in my opinion.
Certainly, it can be annoying when it feels like customer service is asking about things that aren’t likely to be an issue at play. I imagine I’d be annoyed as well. The fact that there is a github issue that someone said they will be looking into is good, though. Anyone seeing this problem can add themselves as tracking it, plus add to the reactions, to let them know there are a number of people seeing this issue. Looks like you commented on the github issue as well.
I wouldn’t think the Battery management system chip uses just voltage to estimate charge level. They also attempt to track current flow in and out. And the algorithm might try to factor in predicted wear from the number of cycles, depth and temperature during the cycles, it all plays into wear. But in the end, charge level estimation still drifts, sometimes a lot. So a full zero to 100% cycle to recalibrate estimation is something one should do anyway, if you normally never let your battery go through a full cycle like that.
1 Like
Any chance your issue is the same as Extremely weird dGPU power behaviour on 140W chargers (moved)? Seems like a lot of 140W USB-PD chargers and Framework 16 laptops don’t negotiate power in a friendly way, Baseus chargers being the exception.
i contributed to the Github Issue, as i wrote about “jumpy” GPU Performance since the Introduction of the 3.05 Bios
4 Likes
It looks like it could be related, at least with what I’m seeing regarding the symptoms.
Edit: Upon further reading it looks like it could actually be the same issue. I think the presumption was that with a higher wattage charger the battery draw and power fluctuations would be non-existent.
2 Likes
It literally is the same negotiation issue. The baseus works wonders, but the UGREEN Nexode 160W and the Delta 240W show the same symptoms.
Unstable dGPU power, a lot of stuttering.
2 Likes
I have recently filed a git issue that seems to be similar to what you described (and plus some more). I did some testing and if you and others see similar results to mine it would point to PD being wonky rather than GPU problems.
Yes, the problem is probably the USB PD negotiation. The thing is, you need the dGPU to be installed and under stress to replicate the issue, because the CPU power delivery is flawless. The problem only appears on the dGPU in combination with some >=140W power supplies.
It’s like the laptop has a hard time allocating the PSU power to the dGPU… Weird.
1 Like
not necessarily, there might be a case where A) CPU doesn’t pull more then 60w so it can get all the power from the battery meaning the power negotiation/plan is simplified and only factors in the powerplan set systemwide. The GPU can easily draw more than the battery max output and needs to know what is the connected charger wattage. B) i forgot what case B was while writing case A :-p
1 Like