Waydroid is available under different licensing options designed to accommodate the needs of our various users:
Waydroid also contains third-party code that is licensed under specific open-source licenses from the original authors (See Third-Party Code in Waydroid below).
Note: For open-source licensed Waydroid, some specific parts are available under the GNU General Public License (GPL). For commercial licensees, all Waydroid related changes are available under commercial Waydroid licenses.
Waydroid documentation is available under commercial licenses from Navotpala Tech (Bliss Co-Labs), and under the terms of the GNU Free Documentation License (FDL) version 1.3, as published by the Free Software Foundation.
Educational licenses are available for students and educators in qualified educational institutions or universities.
To purchase a commercial Waydroid license, contact us with your request.
For further information and assistance about Waydroid licensing, contact us or see our website for further details.
The following documents the open-source licenses used in different parts of Waydroid:
- AOSP Licenses - Bliss OS License - Android-Generic Project License - Boringdroid License -
A: Yes, Waydroid public releases are designed to be used to allow Android applications to run on top of a normal Linux environment
We offer users multiple types of builds to help fit their needs:
- Gapps Builds: Comes with Google Play Store
- Vanilla Builds: Comes with no added apps and services.
A: Yes. Our GMS/Gapps releases include proprietary software, and are intended for individuals only, while our Vanilla builds might include some proprietary parts as well.
Proprietary redistributables in all Waydroid public builds:
- some media codecs (for decoding H.264/HEVC)
Extra proprietary redistributables in Waydroid Gapps builds include Google Play Serivces & Google Play Store.
A: Yes, but not all builds. We produce vanilla Waydroid builds. While those builds are very basic, they do include much of what would be needed to base a product off of. If your product requires no additional changes on top of what is released to the public, then you are free to use it at no cost.
If your product requires Google Apps, ARM/ARM64 Native-Bridge, or Widevine, due to licensing restrictions, we suggest that you reach out and we can help you look into alternative options using open-source solutions.
A: No. The Waydroid versions that include Google Play Store, native-bridge, or widevine are not fit for commercial use or meant to be included in products as they contain proprietary features and services that typically require per-product licensing through Google, Intel, or others. We do however release public Vanilla builds that do not contain any proprietary resources.
Most of those proprietary licenses are not eligible for use in generic operating-system setups. Some require the device to pass certification programs that is only meant for single device certifications. For this reason, we do offer open-source alternatives.
A: Yes, If you are an individual developer, a startup, or represent some other business enterprise and you are interested in using our sources, the open-source licenses we maintain allow you to use the source at no cost as long as you use it: A) as-is, B) you contribute any changes made back to the source, or C) produce the full source to the public independently. If you would like to use our source and make changes to it that you do not plan on releasing as open-source, we request you contact us to work out a per-device licensing agreement and/or setup a development contract for branding, optimizations and specific needs.
A: This all depends on where the changes in the source were made, as many repos in the project retain a different OSS Licenses, there are different requirements per repo. If you are unsure if your company needs to release the source for any of the changes made, please feel free to contact us.
Another thing to pay attention to is if the tools being used require the end product or alterations to be released. Some Apache 2.0 licensed projects allow for that requirement to be made. Some versions of Android-Generic Project also have similar licensing requirements. We have put together a toolkit to help identify these types of licenses within the source. You can find that here.
If you are not sure if you need a license, or just have some questions on our licensing options, please feel free to contact us. We love helping out others find the best way to contribute back to the source.
Contact Us
