Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementing Full Speed mode from ProArt Creator Hub on Vivobook 14X #1645

Closed
rumifloss opened this issue Nov 24, 2023 · 1 comment
Closed

Comments

@rumifloss
Copy link

Is your feature request related to a problem? Please describe.
The Vivobook 14X has two sets of controls for CPU/fan modes. One of them is in the MyASUS app (which the Silent → Balanced → Turbo modes correspond to) and the other set is tucked away in the Armoury Crate–like ProArt Creator Hub (Whisper → Standard → Performance → Full Speed)

14X_ProArt_Modes

The first three modes in ProArt Creator Hub correspond 1:1 to the options in MyASUS. The fourth mode, Full Speed, seems to switch on fans permanently and changes the PBP of the processor to 65W, instead of 55W with the Performance/Turbo mode. There is a Notebookcheck review of the Vivobook 14X that lists the Creator Hub power modes of the i5-13500H as follows:

14X_modes

Here are the CPU readings corresponding to the Performance mode and the Full Speed mode respectively:

PBP_GHelper_ProArt_Performance PBP_GHelper_ProArt_FullSpeed

And here is a CPU reading of the Turbo mode in GHelper (55W, same as Performance in Creator Hub):

PBP_GHelper_Turbo

Describe the solution you'd like
It would be great to have a mode that corresponds to Full Speed inside GHelper, or maybe tweak the existing Turbo mode to change PBP to 65W instead of current cap 55W

Additional context
MyASUS is uninstalled. The ProArt Creator Hub controls only work with the Asus services enabled in GHelper

@seerge
Copy link
Owner

seerge commented Nov 24, 2023

@rumifloss hello, you can already do that by adding a custom mode, and setting corresponding setting a config file

Check this comment for explanation #1301 (comment) :)

@seerge seerge closed this as completed Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants