Project Updates

By Luke JonesJanuary 9, 2021

Hi all, Luke here. I'm going to try and give a project status update here so that it is easy for all to find.

First up is my own status: I'm very busy. Still, yeah. So I don't have much time for the project (and haven't since I started it tbh). But I will be trying to get some updates finished soon.

Others involved with the various parts of the project are also very busy. Please be patient.

Keyboard driver

The keyboard driver for device 0x0b05:0x1866 whcih is the N-Key keyboard is merged in kernel 5.11 series which is currently in RC, this means you can try it right now; if you do then be sure to remove the hid_asus_rog DKMS module.

Kernels older than 5.11 will still require the DKMS module, and this will be updated only when required, and kept in sync with the changes for 0x8166 only.

Mic-Mute: The current keycode used for mic-mute is specific to Wayland unfortunately. X11 requires a different key code and I'm not likely to be changing it in DKMS module or upstream. If you build the DKMS module yourself, or want to change the source as installed by packaging then you can - this info will be in a FAQ later.

Fan control key: this requires you to map the key to an action in your desktop, for example asusctl profile -n to switch to next power profile.

AniMe Matrix Display

The code and functionality for this needs contributors with this laptop feature.

TODO: link third-party bling app.

Sound

Laptop sound. Let me be blunt and say that this is the biggest fucking pain in the arse ever. To be very clear, the issue for these laptops is NOT pulse audio or alsa or any other thing, it is the fact that vendors customise the Realtek Audio codec chip and rely on drivers to configure it correctly.

I fixed sound for my own laptop (GX502GW), and there was a team effort between many people to try and fix the G14 sound. Both of these patches are upstreamed to the kernel. Other ASUS ROG laptops may or may not work, and if not then they will require some trial and error hacking to fix.

A blog post covering hacking the realtek sound driver is incoming.

asusctl Supported distros

Distros that refuse to update many core or critical components and stay stuck in the past with 6-12 month or older packages are no-longer suported. Why? The Rust compiler is too old to compile asusctl. It's not the asusctl code itself at fault; it's crates that explicitly use newer language features and there is not much to be done about it. You will need to build and install asusctl yourself.

As such, the only (officially) supported distros are:

  • Fedora 33
  • OpenSUSE Tumbleweed

asusctl will work on distros, there just won't be any packaged versions if the rust compiler is too old. Others have packaged it for arch and gentoo.

Website

A FAQ has now been added, you will see the link in the sidebar.

Some minor cleanup has been done. The discord invite link is also updated, and the main guide for asusd/keyboard/anime has been updated.

The G14/G15 guides need checking and updating - someone in the community will hopefully have time to do so (PR's are absolutely welcome).

Legal Matters

ASUS and ROG Trademark is either a US registered trademark or trademark of ASUSTeK Computer Inc. in the United States and/or other countries.

Reference to any ASUS products, services, processes, or other information and/or use of ASUS Trademarks does not constitute or imply endorsement, sponsorship, or recommendation thereof by ASUS.

The use of ROG and ASUS trademarks within this website and associated tools and libraries is only to provide a recognisable identifier to users to enable them to associate that these tools will work with ASUS ROG laptops.

Privacy Policy

We use Matomo

Matomo is an open source web analytics platform. A web analytics platform is used by a website owner in order to measure, collect, analyse and report visitor data for purposes of understanding and optimizing their website.

Purpose of the processing

Matomo is used to get an idea how our website is used by our users so we can optimize things further so that the user may find the most relevant information more quickly.

Data Matomo is processing

  • User IP address
  • Optional User ID
  • Date and time of the request
  • Title of the page being viewed
  • URL of the page being viewed
  • Referrer URL
  • Screen resolution being used
  • Time in local user’s timezone
  • Files that were clicked and downloaded
  • Links to an outside domain that were clicked
  • Page generation time
  • User location: country, region, city, approximate latitude and longitude
  • Main Language of the browser being used
  • User Agent of the browser being used

Pick up the one you are using:

  • Cookies
  • IP address
  • User ID
  • Custom Dimensions
  • Custom Variables
  • Location of the user

And also:

  • Date and time
  • Title of the page being viewed
  • URL of the page being viewed
  • URL of the page that was viewed prior to the current page
  • Screen resolution
  • Time in local timezone
  • Files that were clicked and downloaded
  • Link clicks to an outside domain
  • Pages generation time
  • Country, region, city
  • Main Language of the browser
  • User Agent of the browser

This list can be completed with additional features such as:

  • Form interactions
  • Media interactions
  • A/B Tests

The processing of personal data with Matomo is based on legitimate interests

If you wish us to not process any personal data with Matomo, you can opt-out from it at any time. There will be no consequences at all regarding the use of our website.

You can withdraw at any time your consent by clicking here

The right to lodge a complaint with a supervisory authority

If you think that the way we process your personal data with Matomo analytics is infringing the law, you have the right to lodge a complaint with a supervisory authority.

We are not doing any profiling.