-
Notifications
You must be signed in to change notification settings - Fork 116
Device Specific Configurations
ChimeraOS's design philosophy is to cast a wide net when it comes to compatibility of hardware. The ability to install on as many configurations as possible sometimes presents the opportunity for conflicts with necessary quirks or workarounds for specific devices. As such, these are not normally enabled by default but if well understood they can be included in the image in a disabled state. This page attempts to document these quirks and how to enable them for a given device.
While we do our best to thoroughly test each device quirk that is listed here, a multitude of variables can change the efficacy and/or safety of any particular tweak. ChimeraOS and the ChimeraOS Development Team provide no guarantee that the following tweaks, quirks, workarounds, fixes, and information contained herein will not cause malfunctions or damage to the installed equipment or users. Any use of this information constitutes agreement by the user that it shall be considered at ones own risk and no liability shall be incurred on any member of the ChimeraOS Development Team or the ChimeraOS Organization. If any adverse affects are noted, please report the issue so the circumstances can be understood and the information updated and/or removed.
Some mobile devices handle gamescope differently, and while we make every effort to ensure compatibility across as many devices as possible some may require some additional tweaks. A common tweak that is required is rotating the screen on some devices.
Gamescope is initiated when the OS loads, and when you click "Game Mode" from the desktop environment. It is a highly flexible system but can work differently on mobile devices. After preforming these steps, you will have a custom Gamescope launch command that should address screen rotation. In these steps you will be asked to create a custom XX-my.conf file where the XX denotes order it should be run. We will use 01 as the numeral in the fix below.
- Boot the system normally
- In GamepadUI press the “menu” button in the bottom left of the screen
- In the menu click “Shutdown” >> “Switch to Desktop”
- At the Desktop click the icon with 9 squares >> Applications
- Open Console
- Use the following command:
echo “export GAMESCOPECMD="/usr/bin/gamescope -e --generate-drm-mode-fixed --xwayland-count 2 -O *,DSI-1, --default-touch-mode --hide-cursor-delay 3000 --fade-out-duration 200 --force-orientation right” > ~/.config/environment.d/01-my.conf”
- Verify the file was created in the above command and contains the values expected.
You can verify by running this command:
“cat ~/.config/environment.d/01-my.conf”
- Reboot your system.
Depending on the system you may need to modify the above command, we'll update the wiki with Gamescope variables.
There are three main issues with the AOKZOE A1. The audio is distorted, the rotation of the TTY is not correct, and the display EDID is incomplete, leading to certain refresh rates not working properly. There is a dedicated script that solves all of these issues in a single step.
1.) Run the device quirks script
1.1) sudo /etc/id_device
- Solutions:
1.) (v42+) Enable the systemd unit that controls the LED's.
1.1) sudo systemctl enable --now ayaled
1.2) See the ayaled readme for usage instructions.
- Solutions: This solution is not currently available as the script needs to be updated for systemd-boot.
This is due to a hardware defect from the factory
- Identification: Watch this video. If the in/out of phase sections seem backwards, apply this fix.
- Solutions:
1.) (v42+) Enable the systemd unit that inverts the phase of one speaker.
1.1) sudo systemctl --user enable --now aya-air-audio
1.2) In the audio settings, select the new AYANEO device.
2.) AYANEO have recently announced they are offering a hardware kit with updated speakers. This will require disassembly of the unit. Contact service@ayaneo.com for information on a replacement.
- Solutions:
1.) Enable the systemd unit that controls the LED's.
1.1) sudo systemctl enable --now ayaled
1.2) See the ayaled readme for usage instructions.
- Solutions:
1.) (v42+) Enable the systemd unit that controls the LED's.
1.1) sudo systemctl enable --now ayaled
1.2) See the ayaled readme for usage instructions.
- Solutions: This solution is not currently available as the script needs to be updated for systemd-boot.