undefined | Better HN

0 pointshedora4mo ago0 comments

I’m getting about 2 hours with current macos on an arm macbook pro. I used to get 4-5 last year.

This is out of the box. With obvious fixes like ripping busted background services out, it gets more than a day. There’s no way normal users are going to fire up console.app and start copy pasting “nuke random apple service” commands from “is this a virus?” forums into their terminal.

Apple needs to fix their QA. I’ve never seen power management this bad under Linux.

It’s roughly on par with noughties windows laptops loaded with corporate crapware.

0 comments

QuiEgo4mo ago

That's unfortunate, perhaps your particular macbook is having a hardware problem?

As a point of comparison, I daily two ARM macs (work M4 14 + personal M3 14), and I get far better battery life than that (at least 8 hours of "normal" active use on both). Also, antidotally, the legion of engineers at my office with macs are not seeing battery life issues either.

That said, I have yet to encounter anyone who is in love with macOS Tahoe and it's version of Liquid Glass.

hedoraOP4mo ago

The current issue is iOS 26.1’s wallpaper renderer crashes in a tight loop if the default wallpaper isn’t installed. It isn’t under Xcode.

I have macos crash reporting turned off, but crashreport pins the CPU for a few minutes on each ios wallpaper renderer crash. I always have the iOS simulator open, so two hours battery, max.

I killed crashreport and it spun the cpu on some other thing.

In macos 25, there’s no throttle for mds (spotlight), and running builds at a normal developer pace produces about 10x more indexing churn than the Apple silicon can handle.

j / k navigate · click thread line to collapse