We include many options for customization and theming throughout the OS
We offer many custom options for big screens and small screens alike that allow you to setup your device for various different tasks.
We built the OS with a focus on speed and stability with tweaks to assist in the most demanding applications.
Extra options are provided to help tune battery consumption to the best levels
Additional security options and features are found throughout the OS. And AOSP security updates are merged regularly.
We bring Bliss to every device we own. And our PC builds include extras for ARM/ARM64 app compatibility
Bliss OS lets the user choose between Desktop or Tablet UI, based on the launcher being used. You can even mix the two for a truly customized experience
An Open Source Desktop launcher that allows the use of a bottom taskbar, with Bliss button (start menu)
An Open Source launcher that is more geared towards a tablet interface. Based off AOSP Launcher 3
Bliss OS comes with a variety of added features for compatibility with ARM & ARM64 apps. As well as added configurations for many gamepads and profiles for Tincore Keymapper, allowing users to game like never before.Go to Downloads
Many of our competitors do offer a free download, but they are still making money off your data.
Not only do we respect your privacy, but we vow to never include anything to put your data in jeopardy. We are also constantly updating things with the latest security updates from Google for our currently developed version(s) of Bliss OS. And all our source code is also available to help make sure that your data and safety are at the top of our concerns. For users that have an even greater concern about their user data, we also offer Bliss OS builds that are Google Services free, and come with fDroid & microG for a truly secure user experience.Go To Downloads
Bliss OS 11:
Bliss OS 12:
Our Bliss OS 12 builds are considered Beta status, and users should expect some bugs. These builds should not be considered for daily use.
Since we are usually working across multiple versions of Android with Bliss OS, things can get a little confusing when it comes to figuring out what build type is right for you. Here is a little explanation of our currently supported variants to help things along.
These are generic builds based on Android 9 (Pie) and BlissROMs sources.
These are considered our current stable branch
These are Microsoft Surface & Lenovo X1 Tab specific builds based on Android 9 (Pie) and BlissROMs sources.
Only download these if you have an IPTS device. Ask your manufacturer if unsure.
These are generic builds based on Android 10 (Q) and BlissROMs sources.
They should be considered Beta status, thus there may be dragons.
These are generic builds based on Android 10 (Q) using mostly AOSP and a tiny bit of Bliss sprinkled on top.
They should be considered Beta status, thus there may be dragons.
A: Because we felt the need to include the various branches for Kernel, Mesa, & Firmware in the build name. So, when you see a name like this: Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso It can be broken into 3-4 parts. Build ID: "Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457" Kernel Branch: "_kernel-4.9" Mesa Branch: "_m18.3.0-devel_w40_LLVM70" Firmware Branch: "_dev-kernel.org"
A: When we add a batch of commits to the kernels, we like to save that version with an identifier. So the most common parts to the kernel names are as follows: -ax86 : Means that this kernel started off from the Android-x86 repo, or has the majority of Chih Wei's commits for that kernel -ma : Means this started out from Maurossi's repo. (https://github.com/maurossi/linux) -gal : Means that this kernel also includes compatibility with Chromebook devices, from the peeps at Gallium OS (https://github.com/GalliumOS/linux) -ipts : Means that we are including some specific commits for the Intel IPTS touchscreens (mostly in the Surface line of devices) These builds likely won't run well on most other devices.
A: Well, we have a method to all our madness there. We build Bliss OS with different kernels that work as a way to make it more compatible with different types of devices. Here is the breakdown on those: Kernel-4.9 These are considered the most "Stable" builds, they will work across most older and recent devices. Kernel-4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices. Kernel 4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One" Kernel 4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support kernel 4.19+ Intended for newer devices. Even more touchscreen support and ACPI support Kernel 4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support Kernel 5.0+ This is where things will start getting tricky. Even more touchscreen support, and added support for ARM/ARM64/ATOM etc, but also a ton of Android kernel commits start making their way into things. If you would like to know if any others using your device have booted Bliss OS yet, we do offer our OS stats site to help with that question.
We do make an update post on our XDA thread for each release. Those posts contain details on any special instructions, fixes, updates, etc. And our docs site is updated often with tips and tricks to help make things easier on everyone. For new bugs found, we like to keep things pretty simple and straight forward, so we've setup a Bug Reports repo on our GitHub to track things.
We recommend running Bliss OS on most Chromebooks, Windows/Linux PCs or tablets released in the last 4 years. Intel CPU/GPU for best results. AMD CPU/GPU/APU support is limited. VM support is very limited. Please install on native hardware for best results.
Make sure to check the docs section for more information.
Bliss ROMs documentation can be found on our docs site, while our development update posts can be found on the XDA thread for that devices release version.
We recommend all users start with using the documentation we have provided before trying to hunt us down online and ask us questions as this action takes away the valuable development time we have committed towards this project. None of us are paid for the work we do on Bliss, so please set your expectations accordingly.
For questions on if Bliss will work on your device, please search our public OS stats site for your device, failing that, join our Telegram Community Support chat Here and search for answers in there.
We're always adding to Bliss OS development, and if this is your way of giving back, then feel free to download the source and submit commits through Bliss OS's Gerrit Review or check out our GitHub repo
Bliss OS (x86) is just one of the many projects developed and maintained by Bliss Family of ROMs, an 501 (c3) Non-Profit organization who's mission is to provide a variety of resources to the open-source community and others around the world by creating and fostering an all-inclusive learning environment for seasoned developers and newcomers.
Our vision is to help provide the tools and knowledge to inspire innovation by sharing and collaborating on projects with individuals of all ages and walks of life that donate their time and knowledge to open-source development.
© 2019 Bliss Family of ROMs. All rights reserved