Bluetooth drivers prevent system from sleeping in Mavericks - what's going on!?

The template is a good idea.

Here it is (sorry for my English, it isn't my native language).

Bugreporter wasn't working a few weeks ago, now it works again. I'll also explain where to click etc.

1. Go to https://bugreport.apple.com/

2. Login with you Apple ID

3. At the top of the page click "New"

4. Click "OS X"

5. Enter everything.

This is what I entered:

Classification: Serious Bug (That fits this problem the best I guess)

Reproducibility: Always (since it occurs everytime we put the Mac to sleep

Title: "It takes a minute for my Mac to go to sleep"

Description:

Since the OS X Mavericks update it takes about a minute for my Mac to go to sleep. In OS X Mountain Lion, on the default sleep mode, it took about 15 seconds. I turned it to the fast-sleep-mode (via Terminal. It doesn't save the RAM to the HD). After I did that, it took 1 second for it to go to sleep.

After I upgraded to OS X Mavericks, it took about a minute to go to sleep, which is way too long. I checked which sleep-mode it had, and it still had the most insecure and fast method I used on ML.

When I close the MacBook the indicator light stays on for a minute, after that it's slowly flashing. You can hear the HD and fans for a minute.

I Googled the problem, and found this thread: https://discussions.apple.com/thread/5468637?start=0&tstart=0

Everyone who has posted in that thread has the same problem.

We found out what probably causes it. When we use the "pmset -g assertions" command in Terminal, we all get something like this:

"pid 51(hidd): [0x0000000a0000013f] 01:24:02 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"

The thread is marked as solved, but it is not solved. The topic-starter accidentally clicked that.

I really hope you could help us solve this problem.

Steps to reproduce:

1. Close your MacBook

2. You'll see that the white indicator light stays on and you can hear the HD and fans while it's on.

3. When the indicator light starts flashing, the HD and fans turn off, and the MacBook sleeps. This is after 40-60 seconds.

Expected results:

The MacBook has to sleep after max. 5 seconds. It did that in Mountain Lion.

Actual results:

It takes 40-60 seconds to go to sleep.

Configuration:

For the configuration I opened System Information (About this Mac > More info > System report) and uploaded it.

It happens with bluetooth on or off.

It happens with the bluetooth keyboard and/or trackpad connected or not.

So the bluetooth devices connected or not don't cause the problem.

For the hardware-configuration I saved the system report. See the attachment.

Version/Build:

"Software OS X 10.9.1 (13B42)"

I hope Apple will finally help us.

I'm still denied access. I still think it's for devs only.

I only have a free dev account.

OK, I got a free ID and submitted.

@DanteLectro

This is the website i found the information at:

http://macs.about.com/od/usingyourmac/qt/Change-How-Your-Mac-Sleeps-Pick-The-Sle ep-Setting-You-Want-Your-Mac-To-Use.htm

@AJ Soares

So in response to your post on Dec 21, 12:32 AM:

The default sleep mode for portable macs built after 2005 is 'safe sleep' (hibernatemode 3), and not 'hibernation' (hibernatemode 1).

Mine is set to hibernatemode 0, so the RAM remains powered but nothing's written to disk. It's the same setting you described you have on your mac, but you say your mac goes to sleep in 4 seconds, mine takes ~40 seconds. (Are you sure this 4s is on Mavericks and not Mountain Lion?)

Since the RAM is not written to disk, from this aspect I don't think it matters how much memory is allocated under Mavericks. In my experience it's only a few gigabytes more: under Mountain Lion it used to be like 3-5 GB, now it's 6-8 GB. At the moment it's 7.96 used out of 8 GB, but only 2.6 Megabytes of it is compressed.

Well yeah, but Mavericks takes time to write everything over. I've sure it has some programming and checklist that it has to run through, I'm just thinking the new process of writing ram to the HDD is programmed to take longer, because of the way that mav uses ram. You get what I'm trying to say? like maybe the check list is something like

-write ram for open apps

-check for compressed ram

-uncompress ram

-write data for compressed ram

etc etc. not saying i KNOW any of this, it's all speculation, it's the only thing i can think that would cause the issue we are all having.

Yeah, the thing is we can presume all we like about what the OS is doing behind the scenes, but at the end of the day none of us has any visibility into the deepest-darkest reaches of the operating system's code. This has nothing to do with WHAT it's doing, but rather I think it's more that people just want it fixed.

At the end of the day, this is about user experience. Apple touts how great they are at user experience compared to the competition. And they're right; they are better (provisionally, see below) which is why many of us are here using Mac instead of Windows or Linux.

For my part, I am a user of all three major platforms in my day to day life and enjoy each of them. However, this specific bug should be a huge black eye to Apple. My daily work laptop is a Dell E6430 with 16GB of RAM and the exact same 750GB hybrid drive in my personal Mac. It runs Windows 8 and goes to sleep as quickly as my Mac did before the upgrade to Mavericks. Now, while we can debate the merits or not of Windows 8's interface it's not germane to the discussion. The simple fact that my MBP now takes minutes to sleep as opposed to seconds means that when I am leaving to walk out the door even to go to a cofffee shop I am not far more likely to grab my E6430 than my MBP. Mostly these days the applications are identical enough that it doesn't matter which platform I choose, and thanks to Dropbox, Google Drive and even iCloud I now have ALL of my crucial files with me no matter the platform I'm on.

Note; there's NOTHING I can do on the Mac that I can't do just as well in Windows. ****, there's precious little I can't do with my other laptop which is an Alienware M11xR2 with Ubuntu on it I play with occasionally... I just find the screen a little small for my day to day usage. However, my (and I suspect other's) frustration with this problem is that it's a step backward from previous versions of the same OS, and even a step backward from Mac OS's prime competition. The lack of care being demonstrated by Apple so far to this issue combined with the numerous other missteps I've noticed lately in addition to the fact that the competition has massively caught up with where Apple was ahead a few years ago mean that I'm less and less likely to choose Mac next time I come up for a personal hardware refresh. As a Mac lover and user for almost two decades, this should worry Apple. But I suspect it doesn't, and won't.

Apple supposedly "Just Works"... or doesn't it do that any more? If this is the future of "working", then who exactly is it working for?

Yeah i agree, i feel roughly the same way, i had my mbp boot camped and windows on it just worked. so once this sleep issue came up i started regularly booting in windows, as it was just easier to do what i needed to do. I was just trying to offer some clarity on why it may be taking so long right now. and a fix around it. Only problem with turning off the safe sleep is that if your battery dies while it's sleeping you lose whatever unsaved work you were working on....

Why you would put the computer to sleep without clicking save is beyond me. but just the precaution.

Heh... I completely agree. While it's interesting to dig into why it might happen, it's not getting us any closer. Yes, as a workaround I have turned off Safe Sleep... but that simple change in my system required dropping to a terminal session and using pmset... something I shouldn't HAVE to do on a Mac. I personally don't ever close my laptop without everything being saved either, but I'm also probably not your typical user.

Simply put, this change in behaviour is a problem for those of us who have older Macs, or those who have chosen to go with a spinning disk for capacity reasons. We are the kind of people Apple SHOULD want to keep buying Apple, but we're also exactly the people who they seem to care less and less about these days.

While I will continue to happily use my Mac for my work when I can, there's no doubt this change has significantly reduced the utility of my MBP over any of my other possible tools. And one more nail in a coffin that's still not completely closed but is getting steadily closer every day... a coffin that once closed will mean my next hardware investment might go to Dell or Lenovo. And as a trusted technical person, so will the money from my friends and relatives who ask for hardware advice.

So I guess the question is; did SafeSleep not work before and has only now been fixed? Perhaps that's it... and perhaps Apple should come clean about that. At least that would put people's minds at ease as to why this is happening.

My bug report for this issue was recently marked as "Duplicate of 13740708 (Open)".

At least that one's still open, I hope they're fixing it...

Update from the apple dude:

This is the text of his last email, after I took his advice (from engineering, according to him), to do a clean install and see if the problem went away. I did a clean install and nothing changed.

"Ben,

I left you a voice message just now advising of the engineering instructions since we received your email. Since a clean install didn’t resolve the issue it is not a software related item, and the recommendation is to have your computer serviced. If you need help getting that done or making an appointment, or it’s not convenient for you to get to a retail store or service provider, I can send a box for you to ship your computer to the repair depot in Austin.

Please let me know if you require further assistance from me."

Needless to say, I was kind of ****** when I read this, because the fact that my exact same hardware under ML did not exhibit this issue pretty much proves that it is a SOFTWARE issue, not a hardware issue. It seems Apple is simply dancing around the problem, rather than admitting that their OS is doing something screwy that affects usability.

It's super inconvenient to send my laptop into a service provider, or waste MORE time at an Apple store listening to them tell me that there is no problem with the OS, and that this is normal.

It's not normal!!

Unfortunately this is what I've come to expect of Apple lately. Despite their protestations to the contrary they don't care about the Mac platform any more; they'd rather turn it into big-screen iOS where they control the entire software and hardware stack all the way up and down.

I love my Mac, but it slept just fine under ML and also sleeps just fine under the Windows 7 install I have on my BootCamp partition. It's not a hardware issue, and since my hardware is now out of AppleCare I guess I'll just plan on migrating to Windows (probably upgrade to 8.1) and when my next purchase comes around start looking at other options. I wish that weren't the case, but honestly the platform has somewhat become irrelevant. There are precious few applications that are only available on Mac any more with no good alternatives elsewhere. While I feel older versions of Windows fell far behind OSX, that hasn't been the case since Windows 7 was released. ****, I have a better experience with my Ubuntu 12.04 install on my aging but still blindingly fast Alienware M11xR2 then I get with my Mac these days.

I just feel Apple has spoken, and they don't want to deal with a problem they themselves introduced because it does not help them get to iOSX version 1.0

My engineer asked me for "sudo sysdiagnose".

I am not interested in giving him so much private data of my computer. I checked the package and I am really shocked which kinds of information it contains. 😮

Maybe one of you guys who has a clean install could send me his sysdiagnose for the bug report?

The sysdiagnose should run after the issue occured. After the Mac wakes up from sleep mode.

@croonix

What kind of information did it contain exactly that was shocking to you?