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

Nothing here. I tried of everything that all people here said.

MAC SIERRA 10.12.6

Doing "pmset -g pslog" I know this

pmset -g pslog  18:27  06.08.17

Logging IORegisterForSystemPower sleep/wake messages

pmset is in logging mode now. Hit ctrl-c to exit.

2017-08-06 18:31:14 -0300

IOPSNotificationCreateRunLoopSource

Now drawing from 'AC Power'

2017-08-06 18:31:27 -0300

IORegisterForSystemPower: ...Sleeping...

2017-08-06 19:41:01 -0300

IORegisterForSystemPower: ...HasPoweredOn...

Wake Reason = UHC1 USB3 USB5 UHC7 . //I did this on purpose to test

2017-08-06 22:58:29 -0300

IORegisterForSystemPower: ...Sleeping...

2017-08-06 22:59:07 -0300

IORegisterForSystemPower: ...HasPoweredOn...

Wake Reason = pci1106,3483

Here is the result. I first do the tests according to the tips from you guys. I restart the MAC and then I'll send it to sleep. And he sleeps beautiful. But then I hit the mouse (test only with keyboard, no keyboard, only power button and nothing) to connect again. I use the Mac for a few minutes - I analyze if it has something in "prevented by" and I send a "sudo pmset sleepnow" - It takes a while to turn off completely, then it turns on very quickly.

It is in the second "revive" that mine loses the quality of sleep.

Something on PCI is calling back my mac from sleep instantaneously.

Nothing is attached, no USB, no Bluetooth, no internet sharing, no Chrome o other "sleep prevented by". Nothing. Could Apple be nice and solve this? Creating a simple option to override according to the user's need? They made the "Caffeine" to satisfy users that they did not want to "sleep" right? Why not this demand for sleep?

This problem is getting on my nerves, consuming my patience. Every single reboot I need to rearrange my work desktops because not even that, the Sierra knows how to do it alone sometimes.

Best Regards

I feel your pain.

I was so excited to download Mavericks and check out some of the new stuff, but I have been up all night trying to figure out what is making my computer go to sleep SO SLOWLY...it does eventually go to slepe buyit is not practicle as it takes 30-40 seconds. Much too slow.

When I put pmset -g assertions into terminal, this comes up:

BackgroundTask 0

PreventDiskIdle 0

ApplePushServiceTask 0

UserIsActive 1

PreventUserIdleDisplaySleep 0

InteractivePushServiceTask 0

PreventSystemSleep 0

ExternalMedia 0

PreventUserIdleSystemSleep 0

NetworkClientActive 0

Listed by owning process:

pid 537(hidd): [0x0000000a000001c0] 01:54:08 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"

Timeout will fire in 574 secs Action=TimeoutActionRelease

No kernel assertions.

Benjamins-MacBook-Pro:~ Ben$

This process is causing my mac to not sleep properly. Frustrating!!!

I am on a laptop. It is weird...I am not too familiar with the process, but from what I've learned, it is just an interface for the computer to deal with input devices, like keyboards, mice, bluetooth...ETC.

I don't use any external input devices. My trackpad and keyboard, and everything else for that matter work fine. All sharing is turned off.

I am curious if more people have had this problem? It could be a huge pain when I want to put my computer to sleep in a second and move onto the next class.

I have the same problem, but i cannot solve yet.

I have to wait almost 2 minutes for sleep mode when i close the screen

If i click sleep in the main menu is the same problem.

This is my log

Assertion status system-wide:

BackgroundTask 0

PreventDiskIdle 0

ApplePushServiceTask 0

UserIsActive 1

PreventUserIdleDisplaySleep 0

InteractivePushServiceTask 0

PreventSystemSleep 0

ExternalMedia 0

PreventUserIdleSystemSleep 0

NetworkClientActive 0

Listed by owning process:

pid 46(hidd): [0x0000000a00000269] 00:04:16 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"

Timeout will fire in 108 secs Action=TimeoutActionRelease

pid 323(apsd): [0x0000000c000002ee] 00:00:07 ApplePushServiceTask named: "com.apple.apsd-connectinguser-sandbox.push.apple.com"

pid 323(apsd): [0x0000000c000002ec] 00:00:12 ApplePushServiceTask named: "com.apple.apsd-connectinguser-push.apple.com"

No kernel assertions.

I am hoping a soon solution

I have the exact same log, Kroata. Still haven't found a solution either. Also, Targus: I tried your screensaver solution and it didn't work for me.

I just became aware that my iphone has a software update...perhaps something associated with the various syncing between the devices is causing the issue. I will keep you updated if this works.

In the meantime, if ANYONE finds a solution, I would be eternally grateful. It is not going to be a small inconvenience when it takes almost a minute to put my computer to sleep in class...

Did NOT fix my problem, unfortunately.

Went to the local apple store yesterday...the computer guy there had never seen it, and was too busy with easily fixable problems to delve into this with me. So, I went on the chat support thing last night, which...by the way, is WAY better than going into the store, and the woman I spoke with couldn't determine what the issue was, but she DID determine it is NOT a bluetooth issue.

I am set up to get a phone call from someone at 4:45 today and we're going to send some console info to some computer people at Apple and finally see what process is causing me problems.

Question for the other two wth this problem: have you or do you ever use logmein? Any other applications with deal with keyboards?

for my part, i do not use logmein, teamviewer, etc.

I cannot fix the problem yet

10 POINTS!!!!

I will keep you both updated if I learn anything new this evening after I speak with someone from Apple about this. Chances are it will get fixed with an update in a couple weeks. Judging from the OSX Mavericks discussions page, this is just a small bug in a world of various bugs in the new os. We're gonna squash it though...this process is doing something, we just have to figure out what!

Same here. My iMac will not entere sleep properly, and when it does my external hard drive no longer shuts down, I expected bugs but these should have been picked up on I would have thought. 😟