[Asus Zenbook 13 UX333 Big Sur 11.5.2] It works, but there's a catch!

[Asus Zenbook 13 UX333 Big Sur 11.5.2] It works, but there's a catch!

macOS 11.5.2

The laptop itself

HARDWARE SPECIFICATIONS
CPU Intel Core i5-8265U at 1.60GHz
Memory 8GB LPDDR3 soldered
iGPU Intel UHD Graphics 620
Storage WDC SN520 M.2 NVMe 256GB
Sound Realtek ALC294

SOFTWARE:

Running macOS Big Sur 11.5.2 posing as MacBook Pro 13" 2018 with four thunderbolt ports

WHAT WORKS:

-WiFi and BT (courtesy of Airportitlwm and InteBluetoothFirmware)

-Proper power management (thanks to SSDT-PLUG and CPUFriend)

-CPU sync (CpuTscSync with -cputsclock boot-arg because the current one doesn't work on Big Sur)

-Sound (patched with SSDT-ALC294 and codeccommander to work)

-Trackpad gestures (thanks to SSDT-GPIO, although sometimes it's unresponsive, but that's due to Asus's buggy touchpad, and it happens on Windows too

-GPU Acceleration and backlight (using 0900A53E platform-id and SSDT-PNLF-CFL.aml for backlight)

-Keyboard and KB backlight (Patched with AsusSMC and SSDT-AsusSMC)

-Sleep (USB mapped, but wait for the catch)

WHAT DOES NOT WORK:

-Airdrop (needs native WiFi card)

-Webcam (can't get it to work, but that's fine)

-IR Camera for Face Unlock (.....yeah, it shouldn't work)

-Tap two fingers to zoom is spotty and doesn't work most of the time

UNTESTED:

-HDMI

-Continuity features

-Sidecar

So... What's the catch?

Sleep mostly works. But for some unknown reason (and the thing that hinders me from having a near perfect setup), *sometimes* the system won't turn on after sleep, and the light indicator also stays on. The only way to recover would be to force reset the system. Doing so, I will be greeted with this crash report message that says "Sleep Wake Failure in EFI"

https://preview.redd.it/tivhosirip591.png?width=1112&format=png&auto=webp&s=098ea466edfd0653d27506e05bd668e9f2ecf306

It's very unusual because this had never happened before. This is actually my 6th time installing macOS. First and second was almost last year (July 2021), then I went back to just Windows in November. Last May, I decided to give it another shot with Monterey, and that was when this issue started popping up. I initially thought it was a Monterey issue so I rolled back to Catalina, but the problem persisted, and then Big Sur, same thing. So for the 6th time, I installed macOS the same way I did the first time, which was by installing Catalina first then updating to Big Sur... but sleep wake failure still occurs.

The weirdest thing is there is no discernible pattern as to when it will happen. It just happens sporadically; sometimes I could go on for a day without a single failure, or 4 sleep failures in 8 hours.

I tried every software-related fixes I know:

-NVRAM reset

-Updating OC

-disabling wake on network and bluetooth; disabling power nap

-SSDT AWAC and HPET

-enabling disablertcchecksum

-USB Mapping (tried both hackintool and USB Map Tool Method)

-rtcmemoryfixup with rtcfx_exclude=00-FF boot arg (fixes the 8 hour time lag between BIOS and macOS, but not the sleep wake failure)

-different smbios (Pro15,2 and Air8,1)

-different GPU platform IDs

-hibernationfixup

-pmset terminal commands according to Dortania guide

-disabling all ports on BIOS

Oddly enough...

When I try to put the laptop to sleep, it will either take the machine 16-20ish secs or 35-40 secs to fully sleep, and it's with the latter that *sometimes* the laptop will crash and won't wake.

macOS is installed on the same drive along with Windows 11, but that can't be the problem because the issue still happens with only macOS installed.

Moreover, almost nothing really changed with that one year of use; except for the battery, which has since degraded such that heavy use using best performance on Windows will shut the laptop down even at 60%.

More oddly enough, I can still use the laptop on macOS with 1% battery although with heavy lag (I can even run CPU and GPU and SSD stress tests without shutting down!), whereas booting on Windows will automatically shut down the machine.

Could it be a hardware issue?

submitted by /u/higmil1010
[link] [comments]