Your AULA F75 recording fails because you are likely releasing Fn too early. Or the deck is in a mode that blocks onboard memory writes. Hold Fn+Space for 3 full seconds until the indicator lights flash. Ensure no utility is overriding the board. This single action resolves the vast majority of “custom color recording not saving” complaints for the AULA F75. Yet the exact timing and environmental conditions are almost always misunderstood.
The correct AULA F75 recording timing most people miss
Most owners tap Fn+Tab and expect an instant save, but the peripheral requires a deliberate hold. Press and hold the 'M' button for three full seconds. Count “one-one-thousand, two-one-thousand, three-one-thousand” in your head. You will see the backlight flash two or three times in rapid succession. That flash is the only confirmation that the custom color layer has been written to the onboard memory. If you release early, even by half a second, no flash occurs. The device silently discards your work. This is the number one reason recording fails silently. To verify success, immediately press the 'M' button again with a single tap to replay the recorded color. If the lights change, the save worked. If nothing happens, repeat the three-second hold. This exact method is also the core step when you want to change color of aula gaming keyboard through hardware profiles, while laptop users can change keyboard color on asus tuf gaming laptop through built-in software instead. The F75 does not require a desktop utility for basic custom recording.
Utility conflicts that block onboard saves
The AULA driver program, if running in the background, can intercept the custom recording command. It treats the command as a temporary layer rather than a permanent save. The driver’s “live preview” mode overrides hardware memory. Even when you follow the three-second hold correctly, the tool discards the profile the moment you close the app. To fix this, completely exit the AULA driver. Right-click its tray icon and select “Exit” or kill the process in Task Manager. Then perform the custom recording hold. After the lights flash, reopen the application only if you need advanced effects. Otherwise, leave it closed. Background programs can hijack the hardware commands. Always close the companion app before saving. The F75’s hardware memory is fully independent of the driver. The driver only reads from, or writes to, that memory when you explicitly click “Apply to Device” in the interface. It does not write during a live custom recording session.
When the board resets after power loss
Some early production runs of the AULA F75 store custom lighting in volatile memory only. This affects some early firmware versions. In these units, the Fn+Tab recording works and the lights flash. But the profile vanishes the moment you unplug the USB cable or restart your computer. To check your firmware, open the AULA driver and look at the bottom-left corner for a version number. If it is below 1.0.4, you must update the firmware via the manufacturer’s support page. The update moves the storage to non-volatile flash memory. If you own a later unit and still see resets, test by recording a simple solid color. Then unplug the peripheral for 10 seconds and plug it back in. If the lights revert to the default rainbow cycle, the onboard memory chip may be defective. Contact AULA support for replacement. While you wait for a fix, you can change lighting color on gaming mouse to quickly match your setup without onboard memory. There, the lighting is controlled entirely by the laptop’s BIOS and Armoury Crate platform. It does not rely on a separate hardware memory chip. Resets are not an issue there. For the F75, a firmware update is the only reliable fix for power-loss resets.
