Apple Releases macOS Catalina 10.15.6 With New Apple News Features and Fix for USB Issue

[FrakeTrain]

It is a strange one indeed, after all the scaremongering by others on this forum I was initially quite pleased that the charging behaviour was what had been predicted. I would say that if this charge cycle to a 100% charge level is 'normal', I will start to count the days until I see any change back down to a charge level of 80% or so. I will start my count at approx. 7 days just be on the safe side, so today would be day 8 since am 80% cut off.

Thanks for your update Big Ron. I still have two "senior" CS advisors that I am in contact with for a little while longer and have pressed this issue as a sideline with them. They are trying to locate some internal engineer files that should reveal more of how this feature should function. Do you have any screen shots or evidence that shows your rig stayed at 80% for a while until just recently? I am trying to upload them some info so I can open an official ticket. Anyone else out there have an experience with the new BHM feature? Please post screenshots or any history of how it is performing with the model number of your rig. I don't want to hijack this post any further on this specific subject so please post here: https://forums.macrumors.com/threads/new-battery-health-management-feature.2234627/page-2

After watching the fallout, I will attempt to update to .6 today and see if that changes anything.

That "Battery Management" feature on my new MBP 16" hasn't worked yet...I have mine enabled and still charges it to 100% in clamshell mode.

Hey AMTYVLE if you could view my long post #35 mentioned above, and let me know if you are witnessing the same thing or different? Thx

UPDATE on cloning software. As of late yesterday, both Dave (SuperDuper!) and Mike (CCC) have posted in their blogs that .6 did fix the firmware links bug. Since Dave waited (hoped to high hell) for the fix, SuperDuper! users need do nothing to obtain full reliable usage of the program after updating to .6. Mike, however put out a few point releases using apple's less reliable method of copying as a workaround, so CCC users will need to wait for his upcoming release that goes back to his own more reliable method (though the present workaround method should work fine on .6, but I'm not sure on that one).

 

[Big Ron]

Thanks for your update Big Ron. I still have two "senior" CS advisors that I am in contact with for a little while longer and have pressed this issue as a sideline with them. They are trying to locate some internal engineer files that should reveal more of how this feature should function. Do you have any screen shots or evidence that shows your rig stayed at 80% for a while until just recently? I am trying to upload them some info so I can open an official ticket. Anyone else out there have an experience with the new BHM feature? Please post screenshots or any history of how it is performing with the model number of your rig. I don't want to hijack this post any further on this specific subject so please post here: https://forums.macrumors.com/threads/new-battery-health-management-feature.2234627/page-2

After watching the fallout, I will attempt to update to .6 today and see if that changes anything.


Hey AMTYVLE if you could view my long post #35 mentioned above, and let me know if your are witnessing the same thing or different? Thx

UPDATE on cloning software. As of late yesterday, both Dave (SuperDuper!) and Mike (CCC) have posted in their blogs that .6 did fix the firmware links bug. Since Dave waited (hoped to high hell) for the fix, SuperDuper! users need do nothing to obtain full reliable usage of the program after updating to .6. Mike, however put out a few point releases using apple's less reliable method of copying as a workaround, so CCC users will need to wait for his upcoming release that goes back to his own more reliable method (though the present workaround method should work fine on .6, but I'm not sure on that one).

Hi FrakeTrain

I’m sorry I don’t have any screenshots of it stopped at around 80%. I just remember watching it stop at 80% for a few days then mentally filing it away as working. As of today my MacBook still charges from pretty much whatever percentage I’ve run it down to right up to 100%.

 

[Yurk]

I use my Mac for serious work, and have had no problems with Catalina. In fact, I've found some features (namely, sidecar), especially useful during work from home.

I use my Mac for serious work (writing Nvidia CUDA code, writing equations with 32-bit applications like Mathtype, etc). I can no longer do any serious work on Catalina. The only way apple has left us with is to use High Sierra, or Windows BootCamp, or connect remotely to an actual computer. I have a $3300 Nvidia Titan V eGPU that I can no longer use with my $2700 16" MacBook 'Pro'.

I shall upgrade to a Fischer Price laptop. It is just as capable of not supporting scientific computing, and does not overheat when I plug in an external monitor.

 

[ProTruckDriver]

I shall upgrade to a Fischer Price laptop. It is just as capable of not supporting scientific computing, and does not overheat when I plug in an external monitor.

ROFLMAO 🤣

 

[briloronmacrumo]

I was guessing that .6 would to that for Dave and Mike (CCC) and all us cloners. But where did you see that? I just checked Dave's blog and it's still the same one from the .5 bug on May 28th.

Dave mentioned it in a support email to me.

 

[ptlu]

Just a warning to those who have been holding off on upgrading fro Mojave... don't do it.

I just took a plunge, and immediately got a filesystem error. Can't repair it, just a full system wipe and restore from backup.

Edit: Prior to the upgrade I did a fsck to ensure the Mojave filesystem was good. So it was directly caused by the upgrade from 10.14.6 > 10.15.6

 

[posguy99]

I just took a plunge, and immediately got a filesystem error. Can't repair it, just a full system wipe and restore from backup.

That's an error on a snapshot. What's the big deal?