"Also in this update:
We now have a cpuidle driver, which significantly lowers idle power consumption by enabling deep CPU sleep. You should also get better battery runtime both idle and during sleep, especially on M1 Pro/Max machines.
Thanks to the cpuidle driver, s2idle now works properly, which should fix timekeeping issues causing journald to crash.
Also thanks to the cpuidle driver, CPU boost states are now enabled for single- and low-threaded workloads, noticeably increasing single-core performance.
Thermal throttling is now enabled, which should keep thermals in check on fanless (Air) models. There was never a risk of overheating (as there are hard cutoffs), but the behavior should now more closely match how macOS works, and avoid things getting too toasty on your lap.
Random touchpad instability woes should now finally be gone, thanks to bugfixes in both the M1 (SPI) and M2 (MTP) touchpad drivers.
A bugfix to the audio subsystem that fixes stability issues with the headphone jack codec.
New firmware-based battery charge control, which offers fixed a 75%/80% threshold setting. To use this, you need to update your system firmware to at least version 13.0, which you can do by simply updating your macOS partition to at least that version or newer. This new charge control method also works in sleep mode.
U-Boot now supports the Type A USB ports (and non-TB ports on the iMac), so you can use a keyboard connected to any port to control your bootloader.
And last but not least, this kernel release includes base support for the M2 Pro/Max/Ultra SoCs! We are not enabling installs on these machines yet as we still have some loose ends to tie, but you can expect to see support for this year's new hardware soon."
This is interesting, am I correct in thinking this a feature implemented by Apple and now supported by the Asahi team? Does that mean that macOS supports this charge control feature?
I really hope Apple brings the same charge limiting to iPhone as well.
This was added to iPhones in 2019.
> If your iPhone stops charging at 80%, it's most likely due to a feature Apple introduced in iOS 13 called Optimized Battery Charging. It aims to prevent over-stressing the battery and hence extend the battery life of your iPhone by limiting the charge to 80%.
Your iPhone learns your usage patterns and delays 100% charging until moments before you wake up in the morning.
https://www.makeuseof.com/why-your-iphone-stops-charging-at-...
The way it's implemented on my mom's android, it always shows 80 or 85% (can't recall which one it is), even if she leaves it plugged in for the whole weekend.
On my HP laptop, if I activate the "battery saver mode" (as opposed to "AI"), it reports the maximum capacity as somewhere around 80% of the design capacity. I don't know whether Linux cooperates with this, but probably not. HP only talks about OS compatibility for the "AI" mode, which not only requires Windows but a specific HP app.
Yes.
It learns your normal waking time (if you have one) and gives you a full charge before you wake up.
Which is what I want. A full charge for the working day, without needlessly shortening the batteries functional lifetime.
This also seems to work only if you've drained the battery below 80%. If it says 90% and I plug it in? It'll charge it fully right away.
It doesn't charge the battery over 80% at all, unless it detects that you have a normal waking time, in which case it charges fully right before you normally wake up.
Unfortunately, other companies copied the 80% charge bit without copying the part about figuring out if you have a normal waking time and giving you a full charge right before that.
For instance, Samsung's S23:
>Once you turn off the battery protection function, you'll be able to charge your battery up to 100%
https://www.samsung.com/ae/support/mobile-devices/battery-pr...
My iPhone disagrees with you. I go to bed and wake up at just about the same time. If I somehow managed to drain the battery below 80%, when I plug it in, it'll charge to 80 and then tell me that by the time I wake up in the morning, it'll be fully charged. Which is the case.
But the most common use case, for me, is waking up, leaving the phone plugged in (WFH). Maybe go for a walk around noon, snap a picture or two. Forget to plug it back in and get back to work. Plug it in as I go to bed at 95%. It tops right up, doesn't wait until the morning.
> Unfortunately, other companies copied the 80% charge bit without copying the part about figuring out if you have a normal waking time and giving you a full charge right before that.
But that's actually what I want. With very, very rare exceptions, I never need a full charge on my phone. Hell, until a few weeks back, I was rocking an iphone 7 with a battery in a questionable state (started bulging). That thing never went below 60% with my use patterns. 60% meant night out, so a hefty dose of maps use. Normal days, it didn't go below 85-90%.
I think the issue is that Apple expects that when you wake up in the morning, you unplug your phone for the day and actually use it a significant amount. Which isn't my case at all. If I don't leave my house, it'll stay plugged in. I usually forget about my phone since everything I need to do, I do on my computer. For the occasional phone call, I can either keep it plugged in (the cord is long enough) or it's already connected to my headset, so don't even need to go fetch the phone. If I don't go to work, it can stay plugged in for days on end (I don't always grab it when I go out).