search

hieplpvip / Asus-Zenbook-Hackintosh

Run macOS on Asus Zenbook with OpenCore
199 stars 44 forks source link

better check your UX410UQK hotpatch compatibility with latest 309 BIOS #25

Closed LeeBinder closed 5 years ago

LeeBinder commented 5 years ago

Greetings @hieplpvip :

https://www.asus.com/Laptops/ASUS-ZenBook-UX410UQ/HelpDesk_BIOS/

Also (suggestion): indicate in your supported models list after each model: "tested working up to BIOS xyz" :)

👍

Alphonse99 commented 5 years ago

Do you got prblem with battery drain in this model?

LeeBinder commented 5 years ago

@Alphonse99 sorry I don't have this model but Asus Vivobook S15. Just wanted to alert hieplpvip/ baohiep to the latest BIOS 309.

Apart from that, I would not exactly call the Vivobook's general poor battery performance - even in Windows - a full-on "drain". In all sorts of tests and reviews, Asus has been accused of putting too weak batteries into the Vivobook S15 series Laptops. Maybe it's the same with Zenbook.

To narrow down:

  1. check in macOS Activity Monitor:
    • Energy Tab (the one in the middle)
    • View/ All Processes
    • sort by Energy Impact, highest on top

See which processes consume the most. If it's apps, uninstall them, reboot

  1. Try a different BIOS

  2. Boot Windows and work in it for a while to find out if battery performance is as bad in Windows, too

  3. For finetuning, if you are not already using the correctly modded CPUFriend kexts, you can run a tool like freqVectorsEdit.sh

hieplpvip commented 5 years ago

Running latest BIOS. Everything is good

LeeBinder commented 5 years ago

Welcome back, @hieplpvip :) Did you see that Asus updated to BIOS v.311 for your UX410UQK on 2019/06/06?

https://www.asus.com/Laptops/ASUS-ZenBook-UX410UQ/HelpDesk_BIOS/

For all current Vivobook series, all newer BIOS suddenly require RehabMan's VoodooTSCSync (Time Stamp Counter) kext. Does that not apply to your Zenbook UX410UQK? Or have you found a substitute for the kext right in Clover (hotpatch or alike)?

The little issue with the TCS kext is somewhat of a slow-down (a bit worse benchmarks), so we're looking for a way to substitute it with something more efficient.