moreaboutbatteries wrote:
… They[Apple] should never put out something that does this. It is terrible. It is the first MacBook Pro I have owned. UGGGG.
Apple didn’t «put out something that does this.»
In the Alpha testing phase, where the Operating System (OS) is installed as a clean install on pristine hardware, there was never such an issue, by the time it was ready to “graduate” to Beta testing: otherwise, it cannot go on to Beta.
In Beta testing, less pristine hardware is used, and not all installs are clean installs. Beta testing starts with not only Apple, but large software developers (so they can get started in getting their software ready for the new OS), then on to smaller developers in a more general Beta program.
Later still, the OS goes on to Public Beta, where a far broader class of users, on their, typically, more worn hardware and more varied mix of third-party software, can test the OS.
The OS doesn’t go outside the Beta program unless it works well for All Beta testers (at least, all those that properly report any issues to Apple).
Some of these, likely, had similar issues to what you and others have been experiencing, but all were tracked to third-party software incompatibilities.
One such method is the following:
- Backup your entire system.
- Completely wipe your system and perform a clean install of Big Sur. Your system should “settle down” almost immediately. (This is what proves that the issue is not with Big Sur on your Mac.)
- Then, only migrate/restore your data, on your Mac.
- Let your system “settle down”. This will take a day or two, or more, depending upon how much data you “dumped” upon Big Sur’s “plate”, so to speak.
- Once your system has “settled down”, with your data, try to migrate/restore your Apps, utilities, kernel and system extensions, etc. This is best done one by one, in order to track-down the incompatible software.
Of course, even getting to step 4 shows that the issue is third-party software. Step 5 simply helps to find which ones (so such can be reported to the respective software developers).
Elsewhere, I and others have expressed other methods to track down, using Activity Monitor (with the Views set to All Processes, rather than the default “My Processes”), to see what processes are using the most CPU (or GPU, or memory, or networking [Wi-Fi, cellular, Bluetooth, etc.]).
(Unfortunately, apparently not all background processes seem to be instrumented for Energy use. Otherwise, finding the culprit would be far simpler. However, the primary Energy users will be processes that use the most CPU and/or GPU processing. [Most background processes don’t tend to use much GPU processing.] High network use can also use quite a bit of Energy, through Wi-Fi, especially if not close to a base-station.)
We’re here to help you in this hunt for the errant software on your system!
Please let us know how this goes, and how we can help you!