A container-based approach to boot a full Android system on regular GNU/Linux systems running Wayland based desktop environments.
Using Waydroid's Multi-Window Mode
Brought To Life With Waydroid
With Waydroids Fullscreen Mode For Desktops & Kiosks
Waydroid uses Linux namespaces (user, pid, uts, net, mount, ipc) to run a full Android system in a container and provide Android applications on any GNU/Linux-based platform (arm, arm64, x86, x86_64). The Android system inside the container has direct access to needed hardware through LXC and the binder interface.
The Project is completely free and open-source, currently our repo is hosted on Github.
Waydroid integrated with Linux adding the Android apps to your linux applications folder.
Waydroid expands on Android freeform window definition, adding a number of features.
For gaming and full screen entertainment, Waydroid can also be run to show the full Android UI.
Get the best performance possible using wayland and AOSP mesa, taking things to the next level
Find out what all the buzz is about and explore all the possibilities Waydroid could bring
Waydroid brings all the apps you love, right to your desktop, working side by side your Linux applications.
The Android inside the container has direct access to needed hardwares.
The Android runtime environment ships with a minimal customized Android system image based on LineageOS. The used image is currently based on Android 13
Our documentation site can be found at docs.waydro.id
Bug Reports can be filed on our repo Github Repo
Our development repositories are hosted on Github
Please refer to our installation docs for complete installation guide.
You can also manually download our images from
SourceForge
For systemd distributions
Follow the install instructions for your linux distribution. You can find a list in our docs.
After installing you should start the waydroid-container service, if it was not started automatically:
sudo systemctl enable --now waydroid-container
Then launch Waydroid from the applications menu and follow the first-launch wizard.
If prompted, use the following links for System OTA and Vendor OTA:
https://ota.waydro.id/system
https://ota.waydro.id/vendor
For further instructions, please visit the docs site here
This article is for educational purposes. Modifying flash drive firmware may void warranties and risk data loss. Always back up your data.
Try switching from a USB 3.0 port to a stable USB 2.0 port on the back of the PC motherboard. Ensure no other heavy USB devices are drawing power simultaneously. "Looping" or Stuck at 99%
FirstChip (also associated with Appotech). Protocol: USB 2.0 (High Speed).
File transfers stall halfway through, or files become corrupted immediately after copying. Step 1: Identifying the Controller via Software
Return to the primary interface screen and click the prominent execution button. firstchip chipyc2019
Insert the faulty USB drive into a native USB 2.0 port on your PC (avoiding external unpowered hubs). Click the button inside the application. If compatible, the software will populate one of the grid squares with the device's current NAND details and controller code. 5. Configuration Settings
The Ghost in the Machine: Decoding the FirstChip chipYC2019 Controller
Are you seeing a specific or capacity mismatch after trying the MPTool?
Low-level flashing tools interact directly with memory hardware. Because of this, Windows Defender or antivirus programs might mistake them for malware. For the process to work, you may need to temporarily pause real-time protection. Extract the downloaded archive and run . This article is for educational purposes
– A green circle and a "Pass" message indicate success. Close MpTools, safely eject the drive, and reinsert it.
The is a specialized, proprietary software tool used for repairing, restoring, and mass-producing USB flash drives that utilize FirstChip controllers (such as the FC1178, FC1179, and chipsets commonly marked with year codes like 2019 or 2020) [1].
Plug your problematic USB drive into a direct motherboard port (avoid external USB hubs).
are used to identify the ChipYC2019 controller. Compatible repair software can often be found on technical sites like Repair Process: Try switching from a USB 3
By default, factory flashing utilities launch using a Chinese interface.
Standard Windows tools cannot typically fix firmware-level issues with these chips. Specialized "Mass Production Tools" (MPTools) are required for repair:
: Windows errors out with a code descriptor failure immediately upon plugging the device in.
Here are the members of our team
