Bliss OS brings the best of what Android has to offer to your projects.
With a wide variety of compatibility for devices built in, we can help to bring the experience your customers demand, and the features they deserve.
Learn More
Bliss OS inherits the same Apache v2 licensing that AOSP uses for most of the components, while many of the other components like Android-Generic Project use GPL-2.0 license.
Proprietary components like Google Apps, Native-Bridge, and some features would require additional licensing to be obtained by the customer.
Bliss OS does however offer development contracts in order to help meet the specific needs of our customers. You can learn more about our contract development and consulting services by visiting the Bliss Co-Labs site
- AOSP Licenses - Bliss OS License - Bliss ROM License - Android-Generic Project License - Boringdroid License -
A: Yes, Bliss OS public releases are designed to be used as a daily replacement for Windows, ChromeOS, Mac OS or Linux and work is consistently being done to improve the User Experience.
A: Yes. Our main GMS/Gapps releases include proprietary software, and are intended for individuals, while our FOSS builds also include some proprietary parts as well.
Proprietary parts in all Bliss OS public builds:
- linux-firmware blobs
- proprietary linux drivers (broadcom-wl for example)
- media codecs (H.264/HEVC)
A: Yes, but not all builds. We produce standard (bare-bones) AOSP builds with basic x86/x86_64 PC hardware support, and no proprietary software included, and those are available to test with. If your company requires Google Apps, ARM/ARM64 Native-Bridge, or Widevine, please contact us to discuss licensing or alternative development options.
A: No. the public builds that we make available online are not fit for commercial use or meant to be included in products as they contain proprietary features and services that require per-product licensing through Google, Intel, us or others. Companies that would like to use Bliss OS or Bliss OS Go, with it's expanded hardware-support and features list, must contact us if they would like to use our projects for their commercial purposes, and form an agreement on a development contract to tailor things to their needs, and/or work out a per-device licensing agreement for company use.
A: Yes, but only the Vanilla versions. While those builds are very basic, they do include much of what would be needed to base a product off of. If you are a startup or a company interested in this options, please contact us to see if you are eligible to use these builds at no cost. Otherwise, we request you contact us to work out a per-device licensing agreement and setup a development contract for branding, optimizations and specific needs.
You can find the AOSP base builds here: Sourceforge
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.
| # Devices | Price |
|---|---|
| 5000 (or below) units license | $17/unit |
| 10,000 units license | $15/unit |
| 30,000 units license | $13/unit |
| 50,000 units license | $10/unit |
| ++50,000 units license | Contact Us |
We offer OEM toolkits, custom options for automatic installation, as well as endless other customization options.
We are available for contract work to help you with any specific device tuning and development in order to achieve the targets you require.
We offer OTA updates for a variety of hardware and offer Long Term Service contracts as well.
We develop a few different tools and one of them is Android Generic Project (AG), a rapid prototyping toolkit for Android on PC (x86) hardware.
AG uses GNU General Public License v2.0
If you decide to include our work in your project or product, we would appreciate you including a link to BlissLabs as well as the projects you used. We have included a branding guide below for your convenience if you also choose to represent our branding in your project.
We offer a loose branding guide for our partners to follow. Feel free to contact us with any questions you may have
Branding GuideWe have a few assets for our partners to use in their designs. Please see below for a few options and feel free to contact us for more if you are in need.
We recommend all software included in Bliss OS releases be inspected and agreed upon through official involvement with BlissLabs in order to ensure user privacy and security guidelnes. All third-party software must also agree to present source code for us to inspect as well. Failure to do this may void any support contracts or retail contracts.
We love to hear from potential partners and offer a way for you to talk directly with the team by emailing us Whether you’re an existing partner or want to explore offering BlissOS, we look forward to hearing from you.
© 2021 BlissLabs. All rights reserved