Framework Laptop 13 Ryzen 7040 BIOS 3.08 Release BETA - Held

Same here (worked for a bit and now not working).

Set battery extender on and charge limit to 80%. Yesterday, the battery discharged to 80% and stayed there. Then used the laptop only on battery before putting on charge overnight. Woke up this morning and battery is at 100% and staying there. HWINFO shows battery charging (0W charge rate when laptop being used, so net charging).

Edit: Perhaps the battery extender is overwriting the charge limit once it has been reset by going on battery? This would be wrong behaviour. The charge limit should still be respected.

I’m honestly still confused as to how these two features are supposed to interact. The documentation at the top doesn’t make it clear (each feature is clear, just not the interaction). It would be good to get it clarified from an official source.

I understand that if I have charge limit enabled at 80%, and battery saver disabled, the battery should not charge over 80%.

I understand that if I have charge limit disabled, and battery saver enabled with default settings, the battery should charge to 100%, then after 5 days of being plugged in discharge to 90%, then after 7 days discharge to 85%, with a 5% floating window.

However, if I have charge limit enabled at 80%, and battery saver enabled with the default settings…? Does it take over from the charge limit? Do the percentage maxes above (100, 90, 85) get levelled at the charge limit (becoming 80, 70 and 65)? Should the battery saver only work without a charge limit?

Maybe it’s cause of where I am with work planning right now. but I am in dire need of some BDD ā€œgiven when thenā€ statements for these features lol.

3 Likes

I looked at the EC source code that is on github. It is basically a bit of a mess, with conflicting power rules so I am not surprised the result is something that does not quite work as expected.
I think if FW listed what there intended rules are, the community could then fix all the bugs for them.
It is not at all clear when the battery save features should apply and when the charge limit should apply, and when the battery should discharge even with a psu connected.
There should be a single function in the EC source code that runs through all the rules and gives the result. Not having the rules scattered about.

But to be fair, battery management is difficult. There are all sorts of edge cases where the battery might not respond correctly, and those all have to be detected and worked around.

4 Likes

Update went fine. First time I set the charge limit to 80%, it wasn’t respected (battery was above the limit and continued to charge). I went to the BIOS again, changing the charge limit to 90%, reboot, then back to 80%. For now it is respected, but that is no different from 3.0.7 which respected the limit for a while before breaking. Now I’ll need to wait if this time the charge limit sticks across multiple reboots. I’ll report back in a couple of days.

FWIW, ryzenadj is still missing sensors that worked with 3.0.5.

Technically, I think you should always use one or the other. The battery charge limit or the battery extender. Granted, I personally think the charge limit should override the extender, but it seems to be the other way around…maybe?

I think to ensure we do or do not have a bug, or whether we just want to suggest that the charge limit takes precedent instead of the battery life extender whenever both are on, we need to be clear about the testing and conditions during which the charge limit doesn’t seem to be honored.

Was the charge limit ignored with the battery life extender also turned on?

Was the charge limit ignored with the battery life extender turned off?

1 Like

There was a lengthy discussion about this on the thread about 3.07. The conclusion was that the charge limit was broken, whether the battery extender was enabled or not. Framework acknowledged that there was a bug.

Technically, both functions could work together: The absolute maximum charge of the battery set by the charge limit, and a decrease from maximum charge set by the battery extender if the laptop is plugged in for a long time. The release notes seem to suggest that the starting limit for the battery extender is always 100%, not the currently set charge limit, and the laptop probably just charges to the lower limit of the two, so a charge limit of 80% will effectively leave the battery extender without effect.

I left the battery extender enabled, just because it is the default setting and there is no indication that it needs to be switched off for the charge limit to work. If the two conflict, that should be handled in the logic of the BIOS settings, IMHO.

1 Like

I understand. But some people are starting to say it still isn’t working on 3.08, but it’s not quite clear if they are trying to use the battery charge limit and the battery life extender at the same time. Technically, the wording of the ā€œfixā€ is that they fixed a but that prevented the battery charge limit from working when the battery life extender is turned off.

So, I’m just hoping to clarify whether or not the battery charge limit will function properly when the battery life extender is turned off, or if that, at least, has been fixed.

I guess that’s what I’m hoping to determine. Do the two still conflict, and will the charge limit at least be honored if the battery life extender is turned off.

I had both enabled (as I described in the post above) and the battery stayed charging at 100%, charge limit being ignored. So, I disabled the battery extender, and the behaviour was the same - charge limit still being ignored. Finally, I went back into the BIOS and changed the charge limit. Now the charge limit seems to be applied correctly.

Maybe I’ve just been lucky, but for everything I’ve done, my AMD FW 13 has never had an issue for me. It has always worked with any charger I’ve tried to use, the fan is a little goofy sometimes, but not bad, all my ports always work for what I want to use them for, and the battery charge limit has always just worked.

I just updated to 3.08. Fingers crossed, lol. I’ll report back if I find any oddities. I currently have the battery extender turned off with the charge limit set to 80%, as I’ve always done. We’ll see.

1 Like

Yes, it would be helpful if the installation instructions described a validated way to get the charge limit to stick. @Leo3418 mentions a cold boot. I guess time will tell as we gather more experience with this release. It is a shame we are back to debugging this. After the third successive BIOS release, surely it should just work?

2 Likes

Mine is holding at the 75% value I set so far, but I have switched off the battery extender because the description of how the extender works mentions charging to 100%.

That seems right to me, using the battery extender with your own limit doesn’t really make sense because the battery extender is designed to stop you holding the battery at 100% for too long. which you won’t (and indeed can’t) be doing if you’re staying at a lower value.

2 Likes

Had issues last night as noticed today that laptop had charged to 100% instead the 65% which I had set.

But i noticed i had the battery extender enabled. So disabled that now so lets see if this works.

But I still think there should be clearer instructions on these features.

4 Likes

Battery extender should initiate a toggle of battery limit and set to 100 and then grey it out so you can’t modify it, giving a clear indication that choosing to enable battery extender will disable the ability to set your battery limit.

9 Likes

Currently I have 3.08, battery extender off, charge limit set at 80%. I’ve done re-boots, connect charger while off, while sleeping, etc. So far, the charge limit is being honored. I’ll update if this changes, but so far, with 3.08 and the battery extender off, the charge limit seems to be working for me.

Does anyone know if it is safe to update from 3.0.5 to 3.0.8 ?

Or should one do upgrade from 3.0.5 to 3.0.7 and then 3.0.8 ?

1 Like

I can’t say 100%, but normally if there is some requirement to step through intermediate versions, they would say so. However, I will say that 3.07 is basically the same as 3.08, except with a bug fix for the battery charge limit. And 3.07 was ā€œheld.ā€ So if it’s safe to go straight to 3.07, it should certainly be safe to go straight to 3.08.

This morning I updated from 3.06 to 3.08. I know, that’s not 3.05, but I didn’t have to go to 3.07 first. I had no issues. The update went very smooth.

2 Likes

This is what I am finding as well. The charge limit seems to stick and apply as long as you have ā€˜battery extender’ off completely. This should certainly be noted in the documentation, especially since the ā€˜battery extender’ is apparently turned on by default. I also agree with @Arriad that one option should grey out the other.

So, thanks framework for fixing the battery limit.

3 Likes

Sorry, it was late. With battery extender off, the charge limit seems to now be an actual charge limit. But with both options on, the machine would seem to stop at the battery limit for a short (1-2 hours?) period of time, but then charge itself awkwardly slow, trickling up to being 100%, eventually. It wasn’t a normal charge rate, even up towards the top end of charging a full battery, but an artificially slow limit – As if it were attempting to listen to both ā€˜no more than 85% charge limit’ and the rules set that battery extender has behind it.

My results agree with bbrewer: now with 3.08 beta the charge limit (I’m using 80%) stays in effect with the battery extender disabled.

The battery extender function is irrelevant to me. I don’t plan to test the combination of both ā€œonā€.

1 Like

Doesn’t respect charge limit every time. Maybe 1/2 the time…