in the interests of keeping this in the open I've been DM'd by @Aureliannn_ROG asking for further details as asus continue to skirt the problem and do nothing about it. of course your engineeering team is working on the issue, that's wwhy you provided so many details about their progress...
typed this up on the azoth as it's an unsellable mess - as you can see it's still totally bbroken,, repeating like crazy, thanks for destroying my device and doing below the bare minimum to resolve it.
you've had months to fix it and what have you come up with so faar? send us some logs and the firmware version,, lol you lot are aa joke
gamers nexus was bang on the money... I've learned my lesson buy anything asus in the future and if you'ree reading this i hope it steeers you away ffrom this abysmal company
@Aureliannn_ROGwrote:Hi, according to your post
Our engineering team is currently working on your issue.
To help us locate the problem more quickly, we need you to provide the following information:
- Armoury Crate logs: The log files record detailed information about the software's operation, which can help our engineers identify the root cause of the problem.
- Product serial number
- Screenshot of the Armoury Crate update center: Please take a screenshot of the Armoury Crate update center page, especially the keyboard firmware update information, as this will help us confirm if your device has the latest firmware installed.
Providing the above information will help our engineering team identify your issue more quickly. Thank you.
1. armoury crate is a junk bloated mess and you expect me to sift through it's entire file structure to find where it is logging to. how does it not enter your mind to tell me where these log files are located. I've spent time reinstalling this malware mess aagain to have zero clue where the log files are located. what kind of support is this? truly is 100% to the point GN made about AASUS you have zero clue what you are doing. you can shove this point I'm not going back over this, the problem is obvious and in your firmware and is easily rectifiable by allowing me to revert to the previous version, stop sidestepping the solution by droning on about log files and bs and revert the firmware to let me (and the others in this thread) update to a version that worked
3.
there's nothing more I'm offering to assist in this problem, you can't even think one step ahead to let me know where the log files are, I'm uninstalling this crap for the last time, sorry if you've got this keyboard I'm not assisting further, asus are useless
the fix is easy
-revert the firmwarae to the previous verison
-enablle it in armoury craate to update the device
