ROG Azoth Extreme OLED Hardware Info

[Draresh]

Hello everyone!

I just recveived my Azoth extreme and am so far super happy with the hardware. But i cannot get the OLED to work like i want it to:

I used Armory Crate and enbled that the OLED can display dual hardware Info (CPU and GPU temp). But whenever i restart my system the display defaults to a single hardware info of CPU freq. But it cannot even display that (CPU Freq. __ MHz). 

A profile switch on the keyboard doesnt solve this. So right now the only solution is to go into the Armory Crate settings and manually confirm the dual display setting again.

I am using the polling booster and updated the  firmware to KB: 4.00.09 / Dongle 6.00.21 / Booster 2.00.08. 

Can anyone help me figure out how to get the keyboard to remember the correct settings?

Thx in advance!

[Silent_Scone]

Hi @Draresh,

This is an issue since the most recent HTML update for the device. I've made the team aware it's happening, as having to manually apply stats at each boot is far less than ideal.

[BrooBrou]

Hi, I just signed up to report this same issue. Has Asus acknowledged that this is a problem and given a timeframe for when it may be rectified? 

I'm on the verge of returning the board since my base Azoth doesn't have this issue. But if they'll have a fix for it soon I'd rather hang on to it. 

Since this is related to an update, can I fix it by resetting the board, deleting, and reinstalling Armoury Crate, and skipping any update prompts?

[BrooBrou]

I just updated to FW 4.00.11 today (October 21st). "CPU Freq." still shows up on the screen and the temps still won't display unless I go into Armoury Crate's OLED tab and click "apply." 

Over $500 and they can't get basic advertised functions to work. This is nuts. 

[Aureliannn_ROG]

Hi @Draresh @BrooBrou,

Thank you for providing detailed information about the abnormal OLED dual display function on your ROG Azoth Extreme keyboard.

To accurately pinpoint the issue and provide you with the best possible solution, we would like to ask you to provide the following information:

• Armoury Crate Logs:
  Please go to the settings in the Armoury Crate software and export the complete system logs. This log will help us understand how the system is behaving when the problem occurs.
• Video recording of the issue:
  Please record a video of the issue occurring and provide it to us. The video should include:

1. The steps you took to trigger the issue
2. The abnormal display
3. Any relevant error messages

• Confirm connection mode:
  Please confirm whether the same issue occurs in different connection modes, such as wired, wireless 2.4GHz, and wireless Bluetooth.

The logs contain detailed information about the software's operation and can help the team identify the problem.
Please ensure that the logs accurately record the occurrence of the issue.
Here are the steps to collect Armoury Crate logs:
Please refer to Q5: What is APP Diagnostics? (New Feature)
https://www.asus.com/support/FAQ/1043747/#a14
Once you have completed the above steps, please upload the collected log files to a cloud storage service and send us the link via private message. 
Also, please provide us with your product serial number.
Thank you for your understanding and cooperation.

[BrooBrou]

I paid $533 for this keyboard. I'm not doing any of that. I shouldn't have to. It should be flawless. It's being returned to Amazon. 

Thanks for your input, Silent Scone. 

[Draresh]

Hello Aurelian,

thank you for your reply but it feels as if you didnt read it at all and just gave me the tried and true premade support message.

I gave all the details on how to trigger the issue (restart system) and what the abnormal display is. The armory crate log also asks me to replicate the issue, which again wont work as it is restarting the system. When i manually set it again it works flawlessly - until the next restart where it didnt remember the settings.

[Silent_Scone]

Yeah, I totally understand. This firmware update didn't aim to address that issue and was already scheduled before the HTML update went live. I'm on the case at the moment pushing for a resolution to this. I use the stats, so I appreciate it's frustrating.

[Draresh]

Hey Silent! Thx for your reply. 

Would be great if you just let me know when a solution can be expected. 

Thx in advance!

[Silent_Scone]

Of course. No need to do any more steps on your end, it's easily reproducible.