2 résultats taggé rog

Some poor workaround for Aura Creator saying there is no device

TL,DR: use Aura Creator with USB only, switch to 2.4GHz later.

So I bought an AZERTY ROG Falchion some days ago, working fine, was detected by Aura Creator… until the compatibility broke. Aura Creator was saying there is no device, but Aura Sync was working, and I could change my settings in Armoury Crate.

So, I reinstalled Aura Creator, losing my profiles. It was working until it broke again. I checked the log (DebugLog.log at \AppData\Local\Packages\XXXXX.AURACreator_xxxxx\LocalState\) and it was saying [Rescan] Get unsupported device ROG FALCHION, type: Keyboard which was weird. So, I messed around until I could get a grab on how this software was poorly designed.

The trick is: ROG Live Service detects connected devices and saves them to C:\ProgramData\ASUS\ROG Live Service\devices.ini. When the ROG Falchion is connected through USB only, there is one unique device in this file, with an US Layout. But when it is connected through 2.4GHz, there are two devices with two different PID. Somehow, the one with EU Layout isn't recognized by Aura Creator (but works fine with Aura Sync and Armoury Crate), despite the facts that Aura Creator has the correct .csv.

My workaround for users of EU layouts is quite simple: use Aura Creator with USB only, the 2.4GHz button off. Then you may be able to edit profiles to use when you'll switch to 2.4GHz later on. I hope this helps you.

Oh, and btw, before reinstalling Aura Creator you could save your profiles located in the \AppData\Local\Packages\XXXXX.AURACreator_xxxxx\ folder.

How do I stop my ROG Falchion wireless keyboard from rebooting Ubuntu?

For a more permanent solution, append the following config to /usr/share/X11/xorg.conf.d/40-libinput.conf:

Section "InputClass"
Identifier         "disable asus falchioh sys control"
MatchIsKeyboard    "on"
MatchProduct       "ASUSTeK ROG FALCHION System Control"
Option             "Ignore" "on"
EndSection