- Joined
- Oct 5, 2021
- Messages
- 283
- Motherboard
- Asrock Z690 extreme
- CPU
- i7-12700K
- Graphics
- RX 580
Yeah Bluesnooze is a masterpiece, i am using it to because of some waking problems tha spikes the cpu in hackinstosh side.I use Bluesnooze myself on may hacks to toggle BT on and off during sleep, it get's around a know issue with Magic Mouse not working after wake from sleep :-
Yeah, I 've red something about macbook pro's with this situation. At the moment is the unique thing darkwaking, funny is with battery it takes 5-6 seconds, and with AC 45 seconds. What the hell should be!Have not come across this kext before, after a quick search it seems to be something do with driver management :-
CVE-2022-32917: AppleSPU out of bounds write
Information about 0-days exploited in-the-wild!
googleprojectzero.github.io
So probably quite important ....
Code:
Sleep/Wakes since boot at 2023-11-27 20:11:12 +0100 :12 Dark Wake Count in this sleep cycle:2
2023-11-28 05:05:05 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:17%) 8 secs
2023-11-28 06:40:08 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:16%) 5 secs
2023-11-28 08:15:25 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:16%) 6 secs
2023-11-28 09:50:48 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:16%) 5 secs
2023-11-28 11:25:48 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using BATT (Charge:16%) 9 secs
2023-11-28 11:48:32 +0100 Wake Wake from Deep Idle [CDNVA] : due to SMC.OutboxNotEmpty smc.70070000 lid/HID Activity Using BATT (Charge:16%) 2502 secs
Sleep/Wakes since boot at 2023-11-27 20:11:12 +0100 :18 Dark Wake Count in this sleep cycle:5
2023-11-28 14:05:32 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using AC (Charge:70%) 45 secs
2023-11-28 15:41:13 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using AC (Charge:70%) 45 secs
2023-11-28 17:17:06 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using AC (Charge:70%) 45 secs
2023-11-28 18:53:04 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using AC (Charge:70%) 45 secs
2023-11-28 20:28:41 +0100 DarkWake DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty spu_queue_overflow_ep42/ Using AC (Charge:70%) 45 secs
2023-11-28 21:46:34 +0100 Wake Wake from Deep Idle [CDNVA] : due to SMC.OutboxNotEmpty smc.70070000 lid/UserActivity Assertion Using AC (Charge:70%)
Yesterday I found something interesting in the middle of the night DarkWake from Deep Idle [CDN] : due to AOP.OutboxNotEmpty voice_trigger/
this voice_trigger part make me think something about the mic and Siri, but I tried to deactivate siri and still persist with the normal AOP.OutboxNotEmpty spu_queue_overflow_ep42/
In conclusion, Apple should offer his customers the option to choose what happens with the battery, is the more common replacement in this pieces of hardware, and there is no DIY cheap official option. Should be easy a ****n BIG button in the middle of the battery options, something like: Dont waste energy when lid is closed or sleeping, deactivating whatever services are needed. If Apple is choosing to priorice his services, and degrading intentionally the battery performance of his customers, goes for another debate.
Cheers!
Last edited: