Atm, I am terribly annoyed with the optimised charging mode not holding up. It just have frequent dips and then stay at 100% (really about 96.7%). It should stay at 80%, as advertised. If I remember correctly, even with Sonoma, it took a while get that mode to work well, so I'll wait. Feedback sent anyway.
Yeah. I wish I could just select a limit (e.g. 80%) and have it hold it because yeah, sometimes it decides to stay at 80% (what I want most of the time) and other times (frequently), it decides to go to 100%.
BTW, back to my uptime comment, the 14" personal M1 Pro MB Pro I'm typing on has an uptime of 6 days and 21 hours (yes, it's asleep most of the time) so this is since last reboot.
From looking at my software installation report via the hint at
https://discussions.apple.com/thread/3009484?sortBy=rank, when Terminal was restored and thus uptime was reset was when I updated to MacOS 14.7 back on 9/25/24, probably from 14.6.1.
My work Mac (M1 Pro 16" MB Pro) is at 28 days and over 23:40. The reboot was probably due to installing Mac OS 14.6.1 on 9/3/24. This machine gets plugged into and unplugged from a ton of different things like a bunch of different USB-C monitors (we have many models at work + 1 more I have at home), 2 different external hard drives, a
https://us.moshi.com/products/symbus-compact-usb-c-dock (with its own HDMI, USB ports, wired Ethernet ports), 2 Apple Thunderbolt Displays via adapter (has USB ports on the back, Ethernet, 2 cameras, speakers and Mics), and some USB dongles besides being woken and slept a lot. We also need to use my work's crap VPN software running and our IT group has put on Crowdstrike.
Are things perfect? Of course not. Sometimes, there seems to be some runaway Apple process that's chewing up a ton of CPU time for no reason. I kill it and things seem ok afterward. My formerly used Intel heater 2017 MacBook Pro 15" used to kernel and GPU panic a lot more than my Apple Silicon Macs.
Awhile ago, for kicks, I tried using my iPad Pro 10.5" as an extended display for my 14" MB Pro. I did it wirelessly (no cable connection). It worked at first then I got MASSIVE graphics corruption problems on the laptop's LCD which I've NEVER seen before, so I had to stop (and I think I rebooted). Since then, I've not bothered to try again. Seems like a broken feature that wasn't well-tested.