What I don’t understand is why the right USB C port causes problems?
Are both right ports affected by this?
II was responding to jwp who has done a more detailed study of the issue. Mine was the left back port flip-flopping. My guess would be that having a usb hub plugged in to the right back port reduces the power to the left meaning that there is no dedicated power plug USB C port at all.
I would wonder if the problem has to do with the problem where there was a component overheating causing the left side ports to go totally inop.
I have no idea. I am a pure layman here and will just leave it to those who can troubleshoot better than I.
Fwiw, when I tried this a while ago, I could reproduce the problem with all four ports, even with the modules removed. (Support had asked me to try this, that’s why I did some more tested.)
Please help me
If you are able to solve this problem ? I HAVE SAME PROBLEM battery is not charging now my laptop is dead ,it was keeping flipping btw charging and discharging, i have hp 12 gen laptop and had a kali linux base os
You should probably contact HP. Please don’t contact Framework support over this because they only support Framework laptops.
1 Like
Just upgraded to the latest BIOS 3.05 and this is still happening, when the limit is set at 80% it flips between charging and discharging it never says charged. It does seem less of a problem when the limit is set to 100% though, it seems to switch to discharging when put under stress then after a few seconds goes back to fully-charged.
1 Like
Dear Developer
It has been some more months now, and the problem persists. (On my 2034 AMD F-13, running Linux, and BIOS 3.05, intermittently the machine briefly discharges when connected to AC. I am using a Framework charger.) This thread suggests that quite a few people are affected. So: any progress, please?
2 Likes
For AMD, how about using Smokeless UMAF and select AMD_PBS Hidden > EC/PD Configurations, Enable Charger mode BYPASS
Thanks for the pointer and for the screenshot and the information but, no. For, I’m not at the stage where I’m going to flash my BIOS with something third-party, where that third-party BIOS has ‘use at your own risk’ written all over it in big letters.
You aren’t flashing it you are just booting it temporarily but the “use at your own risk” bit stays of course
1 Like
Sad to see that this is a problem on AMD too. I was hoping that the AMD models are not affected.
Any progress on this issue, please? (The issue is this: when a Framework laptop is connected to a charger, the computer continues to draw power intermittently from the battery or at least to indicate that it is so doing.)
Do you still need people to come up with reproducible cases, using Fedora or Ubuntu, and send them to support? If so, please give (or link from above) the exact way that one should try to reproduce (and record) the problem.
Look at the nonsense that I have had to implement on my AMD F-13 in order to workaround this bug.
I have a Bash script that at boot sets brightness according to power status. The script now contains this:
local stateToSet='battery'
[. . .]
case ${pwr_pc} in
"${pwr_pc_name[F13]}")
case ${F13_workaroundPowerBug} in
true)
local -i count=0
local -ir limit=3
while [[ $(/usr/bin/acpi) == *'Discharging'* ]]; do
${pwr_dbg} && dbg_log "F13 detected as discharging: #${count}."
sleep 5
((count++))
[[ ${count} -ge ${limit} ]] && break
done
[[ ${count} -lt ${limit} ]] && stateToSet='ac'
;;
*)
[[ $(/usr/bin/acpi) == *'Battery 1: Discharging'* ]] || stateToSet='ac'
;;
esac
;;
*)
[[ $(/usr/bin/acpi -a) == *'on-line' ]] && stateToSet='ac'
;;
esac
It is a blessing and something of a surprise that the program tlp is not affected: at boot it seems to detect the power status correctly somehow (though the bug makes it somewhat unclear even what it is for the status to be correct here!)
EDIT: unlike some others who have commented within this thread, I have not tried the ostensible fix that is the ‘Smokeless_UMAF’ thingy.
EDIT: I fixed an errors within the script. One of those errors was not coping with the fact that my Framework laptop gives data for two batteries, even though only one is installed and, to my knowledge, installable. What is going on there?
I changed it to ENABLE, and nothing happened. Charging wattage(using a USB meter) with 60W, 100W or 20W look almost exactly(at least I can’t tell the difference) the same.
Setting the battery charge limit lower when the battery level is higher still discharges the battery while the USB current 0.01A(no power directly from USB). i.e this so-called BYPASS setting does nothing
Really can you charge at 100W although you say with. I suppose you don’t therefore use the 60W Framework PSU
Just reading back a bit
“it seems to switch to discharging when put under stress then after a few seconds goes back to fully-charged.”
That seems ‘normal’ if the use temporarily requires more than the PSU can provide some will be taken from the battery and so ‘charging’ will begin.
My laptop is set to 78% charge limit and of course
when the limit is set at 80% it flips between charging and discharging it never says charged.
Mine is set to 78% Charge limit and never says ‘charged’ and even when plugging in to power it can take all the 60W for a while and use some battery too. But on Win 11 the icon doesn’t change with it’s 1 sig fig monitor 0.1% but with Ubuntu which I think has more ‘accurate’ reading then even a 0.01% will show such small changes that are not noticable in Win