Since you mentioned it, mine does that, too.Mine just shuts off mid sleeping and I’m forced to turn it on and I lose my open programs, webpages etc. quite annoying
Since you mentioned it, mine does that, too.Mine just shuts off mid sleeping and I’m forced to turn it on and I lose my open programs, webpages etc. quite annoying
I can report that after turning off "put hardware to sleep whenever possible" in the energy saver settings, my MBA no longer freezes when I open the lid. Hopefully that's the only reason and not 10.5.2 itself.hi yes, corrected my machine device to being 2018.
I'm just trying to think what could possibly be the difference.
wake from sleep settings is almost totally (only) controllable through a very few user defined settings.
if you still have problems after that change, i would next do a painless SMC reset. its easy to do. look on the net and read several articles about it and try it. it attempts to reset certain energy/power/display settings to default.
I can report that after turning off "put hardware to sleep whenever possible" in the energy saver settings, my MBA no longer freezes when I open the lid. Hopefully that's the only reason and not 10.5.2 itself.
[automerge]1577262627[/automerge]Hi everyone,
I can't find any info on this so I'd like to check if I'm alone. I'm running Catalina on a MBA late 2013 and have been upgrading from Mojave to 10.15.1.
Everything was working fine until 10.15.2 dropped.
Since I installed 10.15.2 my MBA freezes every single day. Mostly when trying to open a new finder window or switching folders in finder. Right now it was when I was trying to save a Numbers-file to PDF. It's not that everything hangs up, it usually is that this particular app (until now mostly Finder, a few minutes ago Numbers) doesn't respond and there's no way to quit or force quit it. Not even on Terminal.
When you try to restart the MBA all apps close until that last app and waiting for hours doesn't help. What helps is pressing the power-button for a few seconds to force a restart.
Is anyone else having this issue?
And/or a solution to this?
It's driving me nuts. If I'm unable to use the standby mode and have to restart the MBA every time, the whole concept of picking up where you left off is useless.
Everything was working on 10.15.1 … I can't understand how Apple can screw up every single OS they got. iPadOS 13.2 was working alright, 13.3 makes my iPad Air 2 sluggish like hell with up to 10 seconds to open an app following the lock screen.
As much as I love my Apple products – the software right now is a mess beyond anything I've worked with on these machines.
Thanks in advance for any input.
VSG
Hey @VSG ... any updates?
MBA’s have been SSD only since 2010. I don’t think MLC NAND would be failing in 6 years of normal use.[automerge]1577262627[/automerge]
I always hate to have to tell users this but if you are running the original HD in your MBA then it is 6 years old and displaying the classic symptoms of a dieing drive. It’s also often an installation or reinstallation of an operating system that pushes a failing HD over the edge to a complete crash. I would suggest you make a full backup now, either Time Machine or better yet a clone if the drive is up to it. A clone will enable you to easily restore to a new SSD but Time Machine will do.
I had similar issues on 10.15.2. I restored back to 10.15.1 and this enabled sleep on the 2017 MBP to work again without crashing.
MBA’s have been SSD only since 2010. I don’t think MLC NAND would be failing in 6 years of normal use.
Check the Kernel Panic thread(s) - there is a LOT of this going on. Some with external monitors, some with replacement and/or external SSDs. No easy solution except to set my Mac to never sleep or turn the screen off.
I had a Kernel Panic a month ago upon wake and then turned off the setting for the computer to go to sleep automatically (you can still sleep it manually) and I haven't seen a Kernel Panic upon wake since. I hope Apple is on it with the 10.15.3 update.
Just to add to this, one of my colleagues has just made an interesting observation - he thinks that this whole crashing issue could be the graphics card problem, and to do with power-nap, so we are going to turn that off and see what happens - it's a gimmick and not really needed anyway, so we shall see.
The Finder freezes also seemed to me to be connected with network shares since I didn't see the drives of my NAS starting up when the MBA woke up, which usually happened using macOS 10.14 and up until 10.15.1.I don't necesarally think it's a problem with Automounter - but in the way Apple and the implementation ration of SaMBa is handling networking shares - and I'm thinking that this is the main reason I'm seeing so many finder freezes, which in turn freeze the entire machine.